[SERVER-4294] ReplicaSet Intial Sync gives replSet syncTail: 11000 E11000 duplicate key error index Created: 16/Nov/11 Updated: 11/Jul/16 Resolved: 13/Feb/12 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.0.1 |
| Fix Version/s: | 2.1.1 |
| Type: | Bug | Priority: | Critical - P2 |
| Reporter: | Steffen | Assignee: | Kristina Chodorow (Inactive) |
| Resolution: | Done | Votes: | 1 |
| Labels: | duplicates | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux 2.6.32-35-server, Ubuntu 10.04, MongoDB 2.0.1, Replicaset with 3 Nodes, NUMA, 2x XEON E5620 , 24 GB RAM |
||
| Attachments: |
|
| Operating System: | Linux |
| Participants: |
| Description |
|
What we want to do: What error do we get: ] } } Differences between old nodes and the new node: What we suspect that the use of $addToSet in combination with upsert might cause the replication errors: we also have an mms account assigned with my user account. |
| Comments |
| Comment by Kristina Chodorow (Inactive) [ 07/May/12 ] |
|
@Justin: that is a different error. It looks like corruption. |
| Comment by Justin Patrin [ 02/May/12 ] |
|
I'm seeing this same error, but this is on existing secondaries, not a new server. When I try deleting the data directory for a full resync I get an assertion error: Wed May 2 15:12:01 [rsSync] Assertion failure database db/pdfile.h 488 |
| Comment by Kristina Chodorow (Inactive) [ 13/Feb/12 ] |
|
I don't think this can be backported, unfortunately. |
| Comment by Dominik Gehl [ 23/Jan/12 ] |
|
Just happend to me too ... so now starting a new initial sync (of approx 1TB of data) |
| Comment by Kristina Chodorow (Inactive) [ 21/Nov/11 ] |
|
@Steffen: not sure. I'm doing some refactoring to make this more testable, so I'm not sure if we'll be able to backport. We'll try! |
| Comment by Steffen [ 17/Nov/11 ] |
|
Is it possible to make a backport to 2.0.x? |
| Comment by auto [ 16/Nov/11 ] |
|
Author: {u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}Message: Do not leave initial sync until minvalid is reached |
| Comment by Kristina Chodorow (Inactive) [ 16/Nov/11 ] |
|
Thanks for the logs! It looks like you guys hit an edge case we're not handling correctly with initial sync. To get around this for now, you could:
|
| Comment by Eliot Horowitz (Inactive) [ 16/Nov/11 ] |
|
Can you attach full logs from both primary and new secondary? |