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

Already on GitHub? Sign in to your account

the max-age option might interfer with a run #213

tarekziade opened this Issue Feb 27, 2014 · 3 comments


None yet
3 participants

tarekziade commented Feb 27, 2014

nothing prevents a agent to stop after a max-age cycle - and we had a max-age at 1 hour on the cluster

That's probably why the tests "stopped" in the middle of some tests (stop being the agent unregistring from the cluster)

I deactivated max-age for now to see if this resolves the issue @jbonacci had.

A real fix if that proves to be the problem, is to simply postpone the stop event if an agent is busy running a test.

@jbonacci jbonacci added the *** label Feb 27, 2014


rfk commented Mar 5, 2014

@jbonacci to confirm, but I'm pretty sure this has resolved the issues with long-running tests and they now complete reliably


jbonacci commented Mar 5, 2014

Probably, yes, but then the broker died a horrible death overnight.
Waiting to hear back from @tarekziade in order to get that running.
Then I can accurately give feedback on this issue.


jbonacci commented Mar 6, 2014

Yea, I think we are ok. I don't think the broker issue overnight was related in any way to max-age or running along load test...

@jbonacci jbonacci closed this Mar 6, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment