[SERVER-18307] Increased lock time Created: 04/May/15 Updated: 05/May/15 Resolved: 05/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Concurrency |
| Affects Version/s: | 2.6.9 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Minor - P4 |
| Reporter: | Aristarkh Zagorodnikov | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
After upgrade from 2.6.8 to 2.6.9 our monitoring system detected increased lock time for almost all databases. Attaching graph for one of them (upgrade was done on 06.04). While this did not create any real problems yet, all of our databases exhibited this lock time growth and I wonder if it's a real change or maybe it's just an adjustment in lock time calculations/reporting? |
| Comments |
| Comment by Aristarkh Zagorodnikov [ 05/May/15 ] |
|
Thank you, for your reply. It appears that [election] priorities were updated as a part of the upgrade process, which resulted in primary being moved to another server (the one in question). Please excuse me for the false alert and thank you again. |
| Comment by Sam Kleinman (Inactive) [ 04/May/15 ] |
|
Hi, Looking over the changes in 2.6.9, nothing would obviously explain the effect that you're witnessing; however, If
Regards, |
| Comment by Aristarkh Zagorodnikov [ 04/May/15 ] |
|
P.S. The second lock time growth is a result of the node becoming primary, it was secondary at the time of upgrade. |