MongoDB 3.2.10 Index rebuilding did not complete: 11000 E11000 duplicate key error collection
MongoDB 3.2.10
Getting the following error when adding a replica set as WiredTiger. This is sharded cluster ( 3 shards nodes ).
2 Shards replica sets created using wiredTiger storage so only 1 shard is having a problem when creating the replica set.
2016-11-11T00:51:55.005+0000 I - [initandlisten] Index Build: 39291000/39372845 99%
2016-11-11T00:51:58.032+0000 I - [initandlisten] Index Build: 39345000/39372845 99%
2016-11-11T00:52:04.696+0000 E INDEX [initandlisten] Index rebuilding did not complete: 11000 E11000 duplicate key error collection: XYZ.ALBUM index: _id_ dup key: { : 59000012923579 }
2016-11-11T00:52:04.696+0000 I INDEX [initandlisten] note: restart the server with --noIndexBuildRetry to skip index rebuilds
2016-11-11T00:52:04.696+0000 I - [initandlisten] Fatal Assertion 26100
2016-11-11T00:52:04.696+0000 I - [initandlisten]
I did not have issue when I was using mmapv1 replica set but now I have dropped old replica set.
How to fix this issue?
replication mongodb errors
edited Feb 27 '17 at 13:27
Paul White♦
49.5k14261415
asked Nov 11 '16 at 1:00
SanjaySanjay
163
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
MongoDB 3.2.10
Getting the following error when adding a replica set as WiredTiger. This is sharded cluster ( 3 shards nodes ).
2 Shards replica sets created using wiredTiger storage so only 1 shard is having a problem when creating the replica set.
2016-11-11T00:51:55.005+0000 I - [initandlisten] Index Build: 39291000/39372845 99%
2016-11-11T00:51:58.032+0000 I - [initandlisten] Index Build: 39345000/39372845 99%
2016-11-11T00:52:04.696+0000 E INDEX [initandlisten] Index rebuilding did not complete: 11000 E11000 duplicate key error collection: XYZ.ALBUM index: _id_ dup key: { : 59000012923579 }
2016-11-11T00:52:04.696+0000 I INDEX [initandlisten] note: restart the server with --noIndexBuildRetry to skip index rebuilds
2016-11-11T00:52:04.696+0000 I - [initandlisten] Fatal Assertion 26100
2016-11-11T00:52:04.696+0000 I - [initandlisten]
I did not have issue when I was using mmapv1 replica set but now I have dropped old replica set.
How to fix this issue?
replication mongodb errors
edited Feb 27 '17 at 13:27
Paul White♦
49.5k14261415
asked Nov 11 '16 at 1:00
SanjaySanjay
163
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
mongos> db.ALBUM.find({_id:59000012923579}).count() 1
– Sanjay
Nov 11 '16 at 1:12
add a comment |
MongoDB 3.2.10
Getting the following error when adding a replica set as WiredTiger. This is sharded cluster ( 3 shards nodes ).
2 Shards replica sets created using wiredTiger storage so only 1 shard is having a problem when creating the replica set.
2016-11-11T00:51:55.005+0000 I - [initandlisten] Index Build: 39291000/39372845 99%
2016-11-11T00:51:58.032+0000 I - [initandlisten] Index Build: 39345000/39372845 99%
2016-11-11T00:52:04.696+0000 E INDEX [initandlisten] Index rebuilding did not complete: 11000 E11000 duplicate key error collection: XYZ.ALBUM index: _id_ dup key: { : 59000012923579 }
2016-11-11T00:52:04.696+0000 I INDEX [initandlisten] note: restart the server with --noIndexBuildRetry to skip index rebuilds
2016-11-11T00:52:04.696+0000 I - [initandlisten] Fatal Assertion 26100
2016-11-11T00:52:04.696+0000 I - [initandlisten]
I did not have issue when I was using mmapv1 replica set but now I have dropped old replica set.
How to fix this issue?
replication mongodb errors
edited Feb 27 '17 at 13:27
Paul White♦
49.5k14261415
asked Nov 11 '16 at 1:00
SanjaySanjay
163
MongoDB 3.2.10
Getting the following error when adding a replica set as WiredTiger. This is sharded cluster ( 3 shards nodes ).
2 Shards replica sets created using wiredTiger storage so only 1 shard is having a problem when creating the replica set.
2016-11-11T00:51:55.005+0000 I - [initandlisten] Index Build: 39291000/39372845 99%
2016-11-11T00:51:58.032+0000 I - [initandlisten] Index Build: 39345000/39372845 99%
2016-11-11T00:52:04.696+0000 E INDEX [initandlisten] Index rebuilding did not complete: 11000 E11000 duplicate key error collection: XYZ.ALBUM index: _id_ dup key: { : 59000012923579 }
2016-11-11T00:52:04.696+0000 I INDEX [initandlisten] note: restart the server with --noIndexBuildRetry to skip index rebuilds
2016-11-11T00:52:04.696+0000 I - [initandlisten] Fatal Assertion 26100
2016-11-11T00:52:04.696+0000 I - [initandlisten]
I did not have issue when I was using mmapv1 replica set but now I have dropped old replica set.
How to fix this issue?
replication mongodb errors
replication mongodb errors
edited Feb 27 '17 at 13:27
Paul White♦
49.5k14261415
asked Nov 11 '16 at 1:00
SanjaySanjay
163
edited Feb 27 '17 at 13:27
Paul White♦
49.5k14261415
asked Nov 11 '16 at 1:00
SanjaySanjay
163
edited Feb 27 '17 at 13:27
Paul White♦
49.5k14261415
edited Feb 27 '17 at 13:27
Paul White♦
49.5k14261415
edited Feb 27 '17 at 13:27
Paul White♦
49.5k14261415
49.5k14261415
asked Nov 11 '16 at 1:00
SanjaySanjay
163
asked Nov 11 '16 at 1:00
SanjaySanjay
163
asked Nov 11 '16 at 1:00
SanjaySanjay
163
163
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 9 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
mongos> db.ALBUM.find({_id:59000012923579}).count() 1
– Sanjay
Nov 11 '16 at 1:12
add a comment |
mongos> db.ALBUM.find({_id:59000012923579}).count() 1
– Sanjay
Nov 11 '16 at 1:12
mongos> db.ALBUM.find({_id:59000012923579}).count() 1
– Sanjay
Nov 11 '16 at 1:12
mongos> db.ALBUM.find({_id:59000012923579}).count() 1
– Sanjay
Nov 11 '16 at 1:12
add a comment |
1 Answer
1
active
oldest
votes
I have deleted all data from dbpath and again restarted replica set sync and it looks it is going fine now. I was trying to restart a failed replica set sync and it looks like MongoDB was not able to handle it, once I cleaned up failed replica set data and restart mongo and looks like it is passed point where it was failing before.
Basically,I have removed host from relica set configuration, cleanup dbpath, restarted mongo and again added host in replica set configuration.
answered Nov 11 '16 at 17:33
SanjaySanjay
163
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f154918%2fmongodb-3-2-10-index-rebuilding-did-not-complete-11000-e11000-duplicate-key-err%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have deleted all data from dbpath and again restarted replica set sync and it looks it is going fine now. I was trying to restart a failed replica set sync and it looks like MongoDB was not able to handle it, once I cleaned up failed replica set data and restart mongo and looks like it is passed point where it was failing before.
Basically,I have removed host from relica set configuration, cleanup dbpath, restarted mongo and again added host in replica set configuration.
answered Nov 11 '16 at 17:33
SanjaySanjay
163
add a comment |
I have deleted all data from dbpath and again restarted replica set sync and it looks it is going fine now. I was trying to restart a failed replica set sync and it looks like MongoDB was not able to handle it, once I cleaned up failed replica set data and restart mongo and looks like it is passed point where it was failing before.
Basically,I have removed host from relica set configuration, cleanup dbpath, restarted mongo and again added host in replica set configuration.
answered Nov 11 '16 at 17:33
SanjaySanjay
163
add a comment |
I have deleted all data from dbpath and again restarted replica set sync and it looks it is going fine now. I was trying to restart a failed replica set sync and it looks like MongoDB was not able to handle it, once I cleaned up failed replica set data and restart mongo and looks like it is passed point where it was failing before.
Basically,I have removed host from relica set configuration, cleanup dbpath, restarted mongo and again added host in replica set configuration.
answered Nov 11 '16 at 17:33
SanjaySanjay
163
I have deleted all data from dbpath and again restarted replica set sync and it looks it is going fine now. I was trying to restart a failed replica set sync and it looks like MongoDB was not able to handle it, once I cleaned up failed replica set data and restart mongo and looks like it is passed point where it was failing before.
Basically,I have removed host from relica set configuration, cleanup dbpath, restarted mongo and again added host in replica set configuration.
answered Nov 11 '16 at 17:33
SanjaySanjay
163
answered Nov 11 '16 at 17:33
SanjaySanjay
163
answered Nov 11 '16 at 17:33
SanjaySanjay
163
answered Nov 11 '16 at 17:33
SanjaySanjay
163
163
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f154918%2fmongodb-3-2-10-index-rebuilding-did-not-complete-11000-e11000-duplicate-key-err%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
mongos> db.ALBUM.find({_id:59000012923579}).count() 1
– Sanjay
Nov 11 '16 at 1:12