[SERVER-4356] Sharded getLastError doesn't wait for all writes to go to all shards Created: 23/Nov/11 Updated: 15/Aug/12 Resolved: 12/Apr/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
If do a lot of inserts to a sharded collection really fast, then call getLastError, there can still be some inserts that haven't been processed yet. I have attached a test that reproduces the error, but it is very flaky. So far I haven't been able to make a test that's consistently reproducible. The test is entirely taken from sharding/auth.js, but with all other parts of the test (including all uses of authentication) removed. http://buildbot.mongodb.org/builders/Linux%2064-bit%20Legacy/builds/3958/steps/test_3/logs/stdio has the output from a run of sharding/auth.js that failed b/c of this. |
| Comments |
| Comment by auto [ 23/Nov/11 ] |
|
Author: {u'login': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@10gen.com'}Message: Fix test that's flaky due to |