MongoDB convert standalone mongod to sharded replica set cluster
I have a single replica set having 3 mongod instance, collection in this instance has data already.
I want to convert this instance to sharded cluster. I followed Convert a Replica Set to a Sharded Cluster but when I access my mongod at the end of the setup it doesn't show the existing data.
Any suggestions?
mongodb sharding
asked Jul 3 '17 at 9:57
GeekGeek
11
bumped to the homepage by Community♦ 10 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 |
I have a single replica set having 3 mongod instance, collection in this instance has data already.
I want to convert this instance to sharded cluster. I followed Convert a Replica Set to a Sharded Cluster but when I access my mongod at the end of the setup it doesn't show the existing data.
Any suggestions?
mongodb sharding
asked Jul 3 '17 at 9:57
GeekGeek
11
bumped to the homepage by Community♦ 10 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 |
I have a single replica set having 3 mongod instance, collection in this instance has data already.
I want to convert this instance to sharded cluster. I followed Convert a Replica Set to a Sharded Cluster but when I access my mongod at the end of the setup it doesn't show the existing data.
Any suggestions?
mongodb sharding
asked Jul 3 '17 at 9:57
GeekGeek
11
I have a single replica set having 3 mongod instance, collection in this instance has data already.
I want to convert this instance to sharded cluster. I followed Convert a Replica Set to a Sharded Cluster but when I access my mongod at the end of the setup it doesn't show the existing data.
Any suggestions?
mongodb sharding
mongodb sharding
asked Jul 3 '17 at 9:57
GeekGeek
11
asked Jul 3 '17 at 9:57
GeekGeek
11
edited Jul 3 '17 at 12:57
Geek
asked Jul 3 '17 at 9:57
GeekGeek
11
asked Jul 3 '17 at 9:57
GeekGeek
11
asked Jul 3 '17 at 9:57
GeekGeek
11
11
bumped to the homepage by Community♦ 10 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♦ 10 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 |
add a comment |
1 Answer
1
active
oldest
votes
- You have config server replica set installed?
- You are running at least one mongoS -service
- You are connecting (with mongo) to mongoS when you are working with cluster
- You have added your replica set(s) to the cluster with sh.addShard() -command
- You have added (at least one) your databases to cluster with command sh.enableSharding("yourDBname")
This point your collection is still there, sitting on original location with all data. You still need to shard your collections, which data is needed to "spread" to other shards (nodes).
answered Jul 3 '17 at 10:59
JJussiJJussi
3,0141314
I apologize for error in my question. I have a single replica set which was build for exploration purpose. Now i am trying to partition it to sharded cluster. But i don't want to loose the data in the rpl set currently present
– Geek
Jul 3 '17 at 12:59
You are not loosing data, because nothing is removed or moved during sharding procedure. After you have added at least one new replica set to cluster AND start sharding at least one collection, data is moved but only IF you start balancer procedure. Connect to your mongos -service and give command sh.status() and provide result here, then we can check what is wrong with your setup.
– JJussi
Jul 3 '17 at 13:13
re-writing answer...
– JJussi
Jul 3 '17 at 13:28
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%2f177840%2fmongodb-convert-standalone-mongod-to-sharded-replica-set-cluster%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
- You have config server replica set installed?
- You are running at least one mongoS -service
- You are connecting (with mongo) to mongoS when you are working with cluster
- You have added your replica set(s) to the cluster with sh.addShard() -command
- You have added (at least one) your databases to cluster with command sh.enableSharding("yourDBname")
This point your collection is still there, sitting on original location with all data. You still need to shard your collections, which data is needed to "spread" to other shards (nodes).
answered Jul 3 '17 at 10:59
JJussiJJussi
3,0141314
I apologize for error in my question. I have a single replica set which was build for exploration purpose. Now i am trying to partition it to sharded cluster. But i don't want to loose the data in the rpl set currently present
– Geek
Jul 3 '17 at 12:59
You are not loosing data, because nothing is removed or moved during sharding procedure. After you have added at least one new replica set to cluster AND start sharding at least one collection, data is moved but only IF you start balancer procedure. Connect to your mongos -service and give command sh.status() and provide result here, then we can check what is wrong with your setup.
– JJussi
Jul 3 '17 at 13:13
re-writing answer...
– JJussi
Jul 3 '17 at 13:28
add a comment |
- You have config server replica set installed?
- You are running at least one mongoS -service
- You are connecting (with mongo) to mongoS when you are working with cluster
- You have added your replica set(s) to the cluster with sh.addShard() -command
- You have added (at least one) your databases to cluster with command sh.enableSharding("yourDBname")
This point your collection is still there, sitting on original location with all data. You still need to shard your collections, which data is needed to "spread" to other shards (nodes).
answered Jul 3 '17 at 10:59
JJussiJJussi
3,0141314
I apologize for error in my question. I have a single replica set which was build for exploration purpose. Now i am trying to partition it to sharded cluster. But i don't want to loose the data in the rpl set currently present
– Geek
Jul 3 '17 at 12:59
You are not loosing data, because nothing is removed or moved during sharding procedure. After you have added at least one new replica set to cluster AND start sharding at least one collection, data is moved but only IF you start balancer procedure. Connect to your mongos -service and give command sh.status() and provide result here, then we can check what is wrong with your setup.
– JJussi
Jul 3 '17 at 13:13
re-writing answer...
– JJussi
Jul 3 '17 at 13:28
add a comment |
- You have config server replica set installed?
- You are running at least one mongoS -service
- You are connecting (with mongo) to mongoS when you are working with cluster
- You have added your replica set(s) to the cluster with sh.addShard() -command
- You have added (at least one) your databases to cluster with command sh.enableSharding("yourDBname")
This point your collection is still there, sitting on original location with all data. You still need to shard your collections, which data is needed to "spread" to other shards (nodes).
answered Jul 3 '17 at 10:59
JJussiJJussi
3,0141314
- You have config server replica set installed?
- You are running at least one mongoS -service
- You are connecting (with mongo) to mongoS when you are working with cluster
- You have added your replica set(s) to the cluster with sh.addShard() -command
- You have added (at least one) your databases to cluster with command sh.enableSharding("yourDBname")
This point your collection is still there, sitting on original location with all data. You still need to shard your collections, which data is needed to "spread" to other shards (nodes).
answered Jul 3 '17 at 10:59
JJussiJJussi
3,0141314
edited Jul 3 '17 at 13:28
answered Jul 3 '17 at 10:59
JJussiJJussi
3,0141314
answered Jul 3 '17 at 10:59
JJussiJJussi
3,0141314
answered Jul 3 '17 at 10:59
JJussiJJussi
3,0141314
3,0141314
I apologize for error in my question. I have a single replica set which was build for exploration purpose. Now i am trying to partition it to sharded cluster. But i don't want to loose the data in the rpl set currently present
– Geek
Jul 3 '17 at 12:59
You are not loosing data, because nothing is removed or moved during sharding procedure. After you have added at least one new replica set to cluster AND start sharding at least one collection, data is moved but only IF you start balancer procedure. Connect to your mongos -service and give command sh.status() and provide result here, then we can check what is wrong with your setup.
– JJussi
Jul 3 '17 at 13:13
re-writing answer...
– JJussi
Jul 3 '17 at 13:28
add a comment |
I apologize for error in my question. I have a single replica set which was build for exploration purpose. Now i am trying to partition it to sharded cluster. But i don't want to loose the data in the rpl set currently present
– Geek
Jul 3 '17 at 12:59
You are not loosing data, because nothing is removed or moved during sharding procedure. After you have added at least one new replica set to cluster AND start sharding at least one collection, data is moved but only IF you start balancer procedure. Connect to your mongos -service and give command sh.status() and provide result here, then we can check what is wrong with your setup.
– JJussi
Jul 3 '17 at 13:13
re-writing answer...
– JJussi
Jul 3 '17 at 13:28
I apologize for error in my question. I have a single replica set which was build for exploration purpose. Now i am trying to partition it to sharded cluster. But i don't want to loose the data in the rpl set currently present
– Geek
Jul 3 '17 at 12:59
I apologize for error in my question. I have a single replica set which was build for exploration purpose. Now i am trying to partition it to sharded cluster. But i don't want to loose the data in the rpl set currently present
– Geek
Jul 3 '17 at 12:59
You are not loosing data, because nothing is removed or moved during sharding procedure. After you have added at least one new replica set to cluster AND start sharding at least one collection, data is moved but only IF you start balancer procedure. Connect to your mongos -service and give command sh.status() and provide result here, then we can check what is wrong with your setup.
– JJussi
Jul 3 '17 at 13:13
You are not loosing data, because nothing is removed or moved during sharding procedure. After you have added at least one new replica set to cluster AND start sharding at least one collection, data is moved but only IF you start balancer procedure. Connect to your mongos -service and give command sh.status() and provide result here, then we can check what is wrong with your setup.
– JJussi
Jul 3 '17 at 13:13
re-writing answer...
– JJussi
Jul 3 '17 at 13:28
re-writing answer...
– JJussi
Jul 3 '17 at 13:28
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%2f177840%2fmongodb-convert-standalone-mongod-to-sharded-replica-set-cluster%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
