You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the new expiration keys "server_queue_ttl" and "agent_queue_ttl" in each operation to determine if an operation should be placed in queue and/or processed.
With "server_queue_ttl" the agent should determine, by checking if the current epoch time is less than the value of this key, if the operation is worth putting into the agent queue. This serves as a backup to what the server is already doing, by checking if the operation is past its "pickup time," meaning the operation should have not been picked up by the agent due to its expiration.
With "agent_queue_ttl" the agent should determine, by checking if the current epoch time is less than the value of this key, if the operation should be processed. This tells the agent to avoid processing operations that have been sitting in queue for too long.
The text was updated successfully, but these errors were encountered:
toppatch/vFense#32
Use the new expiration keys "server_queue_ttl" and "agent_queue_ttl" in each operation to determine if an operation should be placed in queue and/or processed.
With "server_queue_ttl" the agent should determine, by checking if the current epoch time is less than the value of this key, if the operation is worth putting into the agent queue. This serves as a backup to what the server is already doing, by checking if the operation is past its "pickup time," meaning the operation should have not been picked up by the agent due to its expiration.
With "agent_queue_ttl" the agent should determine, by checking if the current epoch time is less than the value of this key, if the operation should be processed. This tells the agent to avoid processing operations that have been sitting in queue for too long.
The text was updated successfully, but these errors were encountered: