[SERVER-4096] Call GLE after shard major version change for shardedConns Created: 18/Oct/11 Updated: 10/Dec/14 Resolved: 06/Mar/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | Greg Studer |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
This would preserve the ordering of unverified inserts to mongodb without the need to call GLE after every update, even if a version change occurred resulting in the updates being redirected via the WritebackListener. Optimizations could also be added so that GLE would only be called once-per-migration-per-mongos (this could also be done for setShardVersion as well), and inserts or updates in the same ns not impacted by the migration could be allowed to continue in the meantime. conn.waitForShardVersionIfNeeded( update ) |
| Comments |
| Comment by Greg Studer [ 06/Mar/14 ] |
|
With the write command changes in 2.6, this is no longer applicable. |
| Comment by Greg Studer [ 24/Oct/11 ] |
|
... though this would ensure that after inserting a number of documents, calling GLE would ensure that all updates to the collection via a connection have been applied sequentially or not-at-all. |
| Comment by Greg Studer [ 24/Oct/11 ] |
|
Clarification - this would preserve the ordering of document updates, not collection updates. Ordering collection updates per-connection would be much more expensive. |