[SERVER-4267] getLastError "n" is 0 if previous writes goes through writebackListener Created: 11/Nov/11 Updated: 13/Dec/12 Resolved: 14/Apr/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | writeback | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
If a write hits the wrong shard, immediately after a migrate, and has to go through the writebackListener then the getLastError call returns n:0. We should indicate a special state (writeback:true, or n:-1, or something) if we can't correctly report the "n" value. |
| Comments |
| Comment by Scott Hernandez (Inactive) [ 14/Apr/12 ] |
|
Probably a dup of |
| Comment by Matthew Barlocker [ 19/Dec/11 ] |
|
We weren't doing anything fancy.
|
| Comment by Scott Hernandez (Inactive) [ 16/Nov/11 ] |
|
Matthew, do you have tests you can attach? |
| Comment by Eliot Horowitz (Inactive) [ 12/Nov/11 ] |
|
@scott - do you have a case? |
| Comment by Matthew Barlocker [ 12/Nov/11 ] |
|
I've had instances where inserting a single record into a sharded database will return n:2. This could be related. |