[SERVER-12009] Broken Replication errors for getLastError Created: 09/Dec/13 Updated: 10/Dec/14 Resolved: 09/Dec/13 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Christian Amor Kvalheim | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
single mongod --nojournal |
||
| Issue Links: |
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
In 2.4.3 and 2.5.4 a getLastError with {j:true}on a single mongod with nojournal produces.
But on 2.5.5 nightly it produces
|
| Comments |
| Comment by Eliot Horowitz (Inactive) [ 09/Dec/13 ] |
|
No, the current behavior is correct. |
| Comment by Christian Amor Kvalheim [ 09/Dec/13 ] |
|
On ordered updates a replication error is not considered a failure to write just a failed write concern. Ordered bulks will continue until there is a non-replication error. For legacy ops we use jnote, wnote and wtimeout to recognize an error as being a write concern error and not an op error. I think we are ok if the code is just changed to 64 instead of 2 |
| Comment by Eliot Horowitz (Inactive) [ 09/Dec/13 ] |
|
I do not see how this has anything at all to do with bulk api. |
| Comment by Christian Amor Kvalheim [ 09/Dec/13 ] |
|
this will break the legacy support for bulk api |
| Comment by Eric Milkie [ 09/Dec/13 ] |
|
This was changed as part of |
| Comment by Eliot Horowitz (Inactive) [ 09/Dec/13 ] |
|
See |