Red Hat Bugzilla – Bug 855307
trigger multi scale-up at same time will cause the gear unmatched between node and mongodb
Last modified: 2015-05-14 22:04:29 EDT
Created attachment 610682 [details]
Description of problem:
trigger 3 scale-up events at same time, check the gear number for the app, check the gear directory on instance under /var/lib/stickshift. The gears number does not match.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create scalable app and disable auto-scaling
2.Trigger 3 scale-up events at same time
for i in `seq 1 3`; do curl -k -H 'Accept: application/xml' --user firstname.lastname@example.org:123123 https://localhost/broker/rest/domains/bmengdev/applications/php1s/events -XPOST -d event=scale-up & done
Some gears exist on node but does not exist in mongodb. And the gear number is incorrect for the scalable app.
Should not return any issue when running rhc-admin-chk, and the gear number should be 5 for the scalable app. (2+3)
Attached the development log for debug.
Will not be fixed until the model refactor is in place. Marking FutureFeature.
*** Bug 841527 has been marked as a duplicate of this bug. ***
*** Bug 871660 has been marked as a duplicate of this bug. ***
Marking ON_QA with delivery of model refactor.
Checked on devenv_2735, triggered scale-up 5 times at the same time. Some of the operations failed with meaningful error message, all the succeed ones has the same record between mongodb and node. No error info found in broker log. oo-admin-chk can pass after scale-up finished.
for i in `seq 1 5`; do curl -k -H 'Accept: application/xml' --user email@example.com:123123 https://localhost/broker/rest/domains/bmengdev/applications/sapp1/events -XPOST -d event=scale-up & done
<text>Application is currently busy performing another operation. Please try again in a minute.</text>