Reaper status logs are printed even if we are killing a worker, and they
show information for each worker. Information is presented in a key=value
fashion which is way easier to parse, and correctly handled by most log
analysis tools.
Since this is breaking former log parsing, I've taken the liberty to
also clarify logs, showing that master is included in the total.
NOTES:
I've seen in the mean time that this last part is already in #96,
I'd be glad to leave rebase on top of if, leaving the credit to the
original author,
Seeing there was no test for set_workers, I did not add any. Yet
I could add some for set_master_memory if it feels right.
I may make this an option if you are too worried about breaking actual
parsing. Yet I don't think it is necessary!
Thank you for that very useful gem 🙂 (and all of your work!)
Reaper status logs are printed even if we are killing a worker, and they show information for each worker. Information is presented in a key=value fashion which is way easier to parse, and correctly handled by most log analysis tools.
Since this is breaking former log parsing, I've taken the liberty to also clarify logs, showing that master is included in the total.
NOTES:
set_workers, I did not add any. Yet I could add some forset_master_memoryif it feels right.Thank you for that very useful gem 🙂 (and all of your work!)
Ulysse