Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New expiration keys for operations #5

Open
hchac opened this issue Mar 18, 2014 · 0 comments
Open

New expiration keys for operations #5

hchac opened this issue Mar 18, 2014 · 0 comments
Assignees

Comments

@hchac
Copy link

hchac commented Mar 18, 2014

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.

  1. 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.

  2. 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.

@hchac hchac self-assigned this Mar 18, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant