[SERVER-27530] Secondary showing all queries waitingForLock = true intermittently once in a while Created: 28/Dec/16 Updated: 03/Jan/17 Resolved: 03/Jan/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.0.4 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Vineet Sharma | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
Hi, We are using Mongo 3.0.4 with 3 member replica set in production. Our primary and one of the secondary is in one AWS zone(A) and other secondary is in different zone (B). All the queries have proper index and works fine otherwise. The problem is once in a while, we see high load on one of the secondary in B zone and when we check the currentOp, all the queries are waitingForLock : true. We are using read preference as "secondary preferred" in our application. After looking at different forums, is there a possibility that the replica worker thread is taking long time to sync and acquire the lock? Is there any issue with the particular version? Should we upgrade it to the latest version? |
| Comments |
| Comment by Kelsey Schubert [ 03/Jan/17 ] |
|
Hi sharma.vineet86, Thanks for your report. Please note that SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-users group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. Kind regards, |