Searilization process in Nailgun locks the database
Bug #1643024 reported by
Evgeniy L
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Georgy Kibardin | ||
Mitaka |
Fix Released
|
High
|
Georgy Kibardin | ||
Newton |
Fix Released
|
High
|
Georgy Kibardin |
Bug Description
Detailed bug description:
On 300-node environment Nailgun locks the database so no other handler is available.
Steps to reproduce:
Run 300-node cluster, start deployment, force nailgun-agent to start, run `fuel node` handler.
Expected results:
`fuel node` slowly but shows the result.
Actual result:
`fuel node` just stucks, until searilization process if finished.
Reproducibility:
100%
Workaround:
No workaround.
Impact:
Huge impact for big-deployments.
Description of the environment:
9.1, 8 cores, 16G RAM.
One of the bug was found during the same debugging session
https:/
Changed in fuel: | |
milestone: | none → 9.2 |
assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
status: | New → Confirmed |
milestone: | 9.2 → 11.0 |
tags: | added: area-python |
Changed in fuel: | |
assignee: | Fuel Sustaining (fuel-sustaining-team) → Georgy Kibardin (gkibardin) |
Changed in fuel: | |
status: | Confirmed → In Progress |
Changed in fuel: | |
status: | In Progress → Invalid |
Changed in fuel: | |
status: | Invalid → In Progress |
tags: | added: area-scale |
tags: | added: scale |
To post a comment you must log in.
Evgeniy, could you please give me an access to your lab so that I could play with it?