Comment 3 for bug 1274614
Revision history for this message
| Evgeniy L (rustyrobot) wrote Re: nailgund needs to be running multiple threads | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
eee2d0b
(Get the code!)
I don't think that it's ok to make several instances of nailgun, it may cause several problems
1. in each instance of nailgun we have keep_alive thread, we don't need 8 instances of this thread
2. in each instance of nailgun we have rpc thread which listen on rabbit and receive messages from orchestrator
So, it's ok to configure several instances of nailgun as a fast hack.
How to solve it
1. refactor nodes collection handler, e.g. make separate handler for agent and not update db state if node wasn't changed
2. to reduce overhead which I've described above we can use this patch from services (but we need to test it and fix puppet manifests) https:/
On the first item our new Engineer already started to work, the status you cat track here https:/