[SERVER-302] Unable to connect to a pair during a blocking operation Created: 18/Sep/09 Updated: 12/Jul/16 Resolved: 12/Feb/10 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 1.1.0 |
| Fix Version/s: | 1.3.3 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Joakim Sernbrant | Assignee: | Eliot Horowitz (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
mongo --host left,right hangs until the blocking operation completes. |
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 12/Feb/10 ] |
|
ismaster no longer blocks at all, so that should take care of this as well |
| Comment by Eliot Horowitz (Inactive) [ 26/Jan/10 ] |
|
The goal is to ask a node if its master while a write lock is held. |
| Comment by Aaron Staple [ 26/Jan/10 ] |
|
Are we planning to allow asking a node if it's master while a write lock is held by another operation, or should we just make the c++ paired connection class lazy so it doesn't need to learn who is master until the client requests an operation? |
| Comment by Eliot Horowitz (Inactive) [ 28/Nov/09 ] |
|
this needs concurrency, so pushing |
| Comment by Eliot Horowitz (Inactive) [ 20/Oct/09 ] |
|
this will most likely be fixed automatically with the concurrency changes |