<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 03:12:11 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[SERVER-6605] How to add a replica set&apos;s member into the sharding&apos;s shards</title>
                <link>https://jira.mongodb.org/browse/SERVER-6605</link>
                <project id="10000" key="SERVER">Core Server</project>
                    <description>&lt;p&gt;Hi, a sharding cluster has two shard groups:&lt;/p&gt;

&lt;p&gt;shards:&lt;/p&gt;
      {  &quot;_id&quot; : &quot;shard1&quot;,  &quot;host&quot; : &quot;shard1/10.136.16.67:27032,10.136.16.68:27032&quot; }
      {  &quot;_id&quot; : &quot;shard2&quot;,  &quot;host&quot; : &quot;shard2/10.136.16.69:27032,10.136.16.70:27032&quot; }


&lt;p&gt;The shard shard1 is consisted by three nodes: two mongod nodes and a arbiter node. Then, a new secondary nodes was added. Like below. &lt;/p&gt;

&lt;p&gt;shard1:&lt;br/&gt;
PRIMARY&amp;gt; rs.config()&lt;br/&gt;
{&lt;br/&gt;
        &quot;_id&quot; : &quot;youninameshard1&quot;,&lt;br/&gt;
        &quot;version&quot; : 3,&lt;br/&gt;
        &quot;members&quot; : [&lt;br/&gt;
                &lt;/p&gt;
{
                        &quot;_id&quot; : 0,
                        &quot;host&quot; : &quot;10.136.16.67:27032&quot;,
                        &quot;priority&quot; : 2
                }
&lt;p&gt;,&lt;br/&gt;
                &lt;/p&gt;
{
                        &quot;_id&quot; : 1,
                        &quot;host&quot; : &quot;10.136.16.68:27032&quot;
                }
&lt;p&gt;,&lt;br/&gt;
                &lt;/p&gt;
{
                        &quot;_id&quot; : 2,
                        &quot;host&quot; : &quot;10.136.16.68:37032&quot;,
                        &quot;arbiterOnly&quot; : true
                }
&lt;p&gt;,&lt;/p&gt;
                {
                        &quot;_id&quot; : 3,
                        &quot;host&quot; : &quot;10.136.16.73:27032&quot;
                }
&lt;p&gt;        ]&lt;br/&gt;
}&lt;/p&gt;


&lt;p&gt;Now, how to add the member 3 node into the shard shard1?&lt;/p&gt;</description>
                <environment></environment>
        <key id="45448">SERVER-6605</key>
            <summary>How to add a replica set&apos;s member into the sharding&apos;s shards</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="2" iconUrl="https://jira.mongodb.org/images/icons/priorities/critical.svg">Critical - P2</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="3">Duplicate</resolution>
                                        <assignee username="william.zola@10gen.com">William Zola</assignee>
                                    <reporter username="popgo">Jianfeng Xu</reporter>
                        <labels>
                    </labels>
                <created>Thu, 26 Jul 2012 14:52:24 +0000</created>
                <updated>Wed, 15 Aug 2012 14:04:12 +0000</updated>
                            <resolved>Wed, 1 Aug 2012 17:44:16 +0000</resolved>
                                    <version>2.0.6</version>
                                                    <component>Sharding</component>
                                        <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="149551" author="william.zola@10gen.com" created="Wed, 1 Aug 2012 18:04:24 +0000"  >
&lt;p&gt;Hi Jianfeng!&lt;/p&gt;

&lt;p&gt;Thanks for following-up.  I&apos;m having a hard time understanding your last response.&lt;/p&gt;

&lt;p&gt;1) You&apos;re correct: the output of &apos;sh.status()&apos; is the result of querying the data in the config server, and the &apos;config.shards&apos; collection in particular.&lt;/p&gt;

&lt;p&gt;2) You&apos;re correct: all three config servers must be up and running properly in order for there to be any changes to the metadata of the sharded cluster.  If one of the config servers is down, then the metadata for the cluster becomes read-only.  &lt;/p&gt;

&lt;p&gt;This means that if one of the config servers goes down, all chunk splitting and migration stops.  &lt;/p&gt;

&lt;p&gt;This also means that if one of the config servers goes down, MongoDB cannot make changes to the &quot;seed list&quot; in the config server metadata.&lt;/p&gt;

&lt;p&gt;3) You are also correct that you can continue to write data to the cluster, even if the metadata is read-only.&lt;/p&gt;

&lt;p&gt;This behavior is the result of deliberate design decisions by the MongoDB architects.  You can read here for more information about those decisions:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;&lt;a href=&quot;http://www.mongodb.org/display/DOCS/Sharding+Introduction&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://www.mongodb.org/display/DOCS/Sharding+Introduction&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;4) It sounds like you&apos;re saying that your problem was due to one of your config servers being down.  Is this the case?  It also sounds like you&apos;re saying that bringing up the full set of config servers fixed your problem.  Please let me know if my understanding is correct.&lt;/p&gt;

&lt;p&gt;Please let me know if you have further questions.&lt;/p&gt;

&lt;p&gt; -William&lt;/p&gt;</comment>
                            <comment id="149539" author="renctan" created="Wed, 1 Aug 2012 17:47:11 +0000"  >&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;I have created a new ticket (&lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-6680&quot; title=&quot;Replica seed list in the config servers can be left outdated&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-6680&quot;&gt;&lt;del&gt;SERVER-6680&lt;/del&gt;&lt;/a&gt;) that describes the bug that you are having. For the meantime, if you want the config database to get updated, either:&lt;/p&gt;

&lt;p&gt;1. Make sure all config servers are up and healthy.&lt;br/&gt;
or&lt;br/&gt;
2. Update the document inside config.shards collection to reflect the latest seed list (and you have to do this on all config servers). This option is a sure fire way to do it but can be a little bit risky if you made a mistake.&lt;/p&gt;</comment>
                            <comment id="149355" author="popgo" created="Wed, 1 Aug 2012 07:38:26 +0000"  >&lt;p&gt;Thanks!&lt;/p&gt;

&lt;p&gt;I guess that the mongos can listen a new node that is added into a mongod&apos;s replica set(refers log of mongos), but the config servers metadata are not synced to all of mongods and the collection &quot;config.shards&quot; data is error. So when using &quot;sh.status()&quot; to query, it just find the data of &quot;config.shards&quot;. &lt;/p&gt;

&lt;p&gt;This case is easy to reproduct.&lt;/p&gt;

&lt;p&gt;It&apos;s a big problem when the config servers&apos; metadata are not synced to all of mongods. For example, when a config server goes down, other of config servers is read-only, but the whole sharding is write-read(refers mongodb document) and APP write request is alway writing data to mongod.&lt;/p&gt;</comment>
                            <comment id="149156" author="renctan" created="Tue, 31 Jul 2012 19:05:18 +0000"  >&lt;p&gt;There seems to be nothing wrong based on the mongos logs. Would it be possible to provide the verbose logs of all the config servers? You can set the logging to a higher verbosity without shutting down the server by using the setParam command:&lt;/p&gt;

&lt;p/&gt;
&lt;div id=&quot;syntaxplugin&quot; class=&quot;syntaxplugin&quot; style=&quot;border: 1px dashed #bbb; border-radius: 5px !important; overflow: auto; max-height: 30em;&quot;&gt;
&lt;table cellspacing=&quot;0&quot; cellpadding=&quot;0&quot; border=&quot;0&quot; width=&quot;100%&quot; style=&quot;font-size: 1em; line-height: 1.4em !important; font-weight: normal; font-style: normal; color: black;&quot;&gt;
		&lt;tbody &gt;
				&lt;tr id=&quot;syntaxplugin_code_and_gutter&quot;&gt;
						&lt;td  style=&quot; line-height: 1.4em !important; padding: 0em; vertical-align: top;&quot;&gt;
					&lt;pre style=&quot;font-size: 1em; margin: 0 10px;  margin-top: 10px;   margin-bottom: 10px;  width: auto; padding: 0;&quot;&gt;&lt;span style=&quot;color: black; font-family: &apos;Consolas&apos;, &apos;Bitstream Vera Sans Mono&apos;, &apos;Courier New&apos;, Courier, monospace !important;&quot;&gt;db.adminCommand({ setParameter: 1, logLevel: 5 });&lt;/span&gt;&lt;/pre&gt;
			&lt;/td&gt;
		&lt;/tr&gt;
			&lt;/tbody&gt;
&lt;/table&gt;
&lt;/div&gt;
&lt;p/&gt;

&lt;p&gt;and change it back later to the original value.&lt;/p&gt;</comment>
                            <comment id="148938" author="popgo" created="Tue, 31 Jul 2012 01:01:49 +0000"  >&lt;p&gt;Hi, Randolph&lt;/p&gt;


&lt;p&gt;1. 3 config servers. You can look at the previous detail comments i chat with William.&lt;br/&gt;
2. I posted a mongos node&apos;s log that mongos is starting with -vvvvv parameter. Pls download the attachment file mongs.log.&lt;/p&gt;


&lt;p&gt;Thanks&lt;/p&gt;</comment>
                            <comment id="148693" author="renctan" created="Mon, 30 Jul 2012 15:36:04 +0000"  >&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;Couple of questions/requests:&lt;/p&gt;

&lt;p&gt;1. How many config servers do you have?&lt;br/&gt;
2. Can you try running mongos with a higher verbosity by passing -vvvvv as the parameter and post the full logs?&lt;/p&gt;

&lt;p&gt;Thanks!&lt;/p&gt;</comment>
                            <comment id="148576" author="popgo" created="Mon, 30 Jul 2012 06:10:22 +0000"  >&lt;p&gt;Hi William!&lt;/p&gt;

&lt;p&gt;Please look at the output of rs.status(), the &quot;10.136.16.73:27032&quot; node is in the SECONDARY status, but it&apos;s not work well and the sh.status() is not updated automatically. I also restarted all of mongos servers and config servers. I check all mongos logs and the mongos servers have successed to connect to &quot;10.136.16.73:27032&quot; node before they start. I guess that the config servers&apos; metadata are not updated correctly.&lt;/p&gt;

&lt;p&gt;Any ideas? Thanks!&lt;/p&gt;


&lt;p&gt;##rs.status()############################################################&lt;br/&gt;
PRIMARY&amp;gt; rs.status()&lt;br/&gt;
{&lt;br/&gt;
        &quot;set&quot; : &quot;shard1&quot;,&lt;br/&gt;
        &quot;date&quot; : ISODate(&quot;2012-07-30T05:24:31Z&quot;),&lt;br/&gt;
        &quot;myState&quot; : 1,&lt;br/&gt;
        &quot;syncingTo&quot; : &quot;10.136.16.68:27032&quot;,&lt;br/&gt;
        &quot;members&quot; : [&lt;br/&gt;
                {&lt;br/&gt;
                        &quot;_id&quot; : 0,&lt;br/&gt;
                        &quot;name&quot; : &quot;10.136.16.67:27032&quot;,&lt;br/&gt;
                        &quot;health&quot; : 1,&lt;br/&gt;
                        &quot;state&quot; : 1,&lt;br/&gt;
                        &quot;stateStr&quot; : &quot;PRIMARY&quot;,&lt;br/&gt;
                        &quot;optime&quot; : &lt;/p&gt;
{
                                &quot;t&quot; : 1343616819000,
                                &quot;i&quot; : 1
                        }
&lt;p&gt;,&lt;br/&gt;
                        &quot;optimeDate&quot; : ISODate(&quot;2012-07-30T02:53:39Z&quot;),&lt;br/&gt;
                        &quot;self&quot; : true&lt;br/&gt;
                },&lt;br/&gt;
                {&lt;br/&gt;
                        &quot;_id&quot; : 1,&lt;br/&gt;
                        &quot;name&quot; : &quot;10.136.16.68:27032&quot;,&lt;br/&gt;
                        &quot;health&quot; : 1,&lt;br/&gt;
                        &quot;state&quot; : 2,&lt;br/&gt;
                        &quot;stateStr&quot; : &quot;SECONDARY&quot;,&lt;br/&gt;
                        &quot;uptime&quot; : 9756,&lt;br/&gt;
                        &quot;optime&quot; : &lt;/p&gt;
{
                                &quot;t&quot; : 1343616819000,
                                &quot;i&quot; : 1
                        }
&lt;p&gt;,&lt;br/&gt;
                        &quot;optimeDate&quot; : ISODate(&quot;2012-07-30T02:53:39Z&quot;),&lt;br/&gt;
                        &quot;lastHeartbeat&quot; : ISODate(&quot;2012-07-30T05:24:29Z&quot;),&lt;br/&gt;
                        &quot;pingMs&quot; : 0&lt;br/&gt;
                },&lt;br/&gt;
                {&lt;br/&gt;
                        &quot;_id&quot; : 2,&lt;br/&gt;
                        &quot;name&quot; : &quot;10.136.16.68:37032&quot;,&lt;br/&gt;
                        &quot;health&quot; : 1,&lt;br/&gt;
                        &quot;state&quot; : 7,&lt;br/&gt;
                        &quot;stateStr&quot; : &quot;ARBITER&quot;,&lt;br/&gt;
                        &quot;uptime&quot; : 9758,&lt;br/&gt;
                        &quot;optime&quot; : &lt;/p&gt;
{
                                &quot;t&quot; : 0,
                                &quot;i&quot; : 0
                        }
&lt;p&gt;,&lt;br/&gt;
                        &quot;optimeDate&quot; : ISODate(&quot;1970-01-01T00:00:00Z&quot;),&lt;br/&gt;
                        &quot;lastHeartbeat&quot; : ISODate(&quot;2012-07-30T05:24:29Z&quot;),&lt;br/&gt;
                        &quot;pingMs&quot; : 0&lt;br/&gt;
                },&lt;br/&gt;
                {&lt;br/&gt;
                        &quot;_id&quot; : 3,&lt;br/&gt;
                        &quot;name&quot; : &quot;10.136.16.73:27032&quot;,&lt;br/&gt;
                        &quot;health&quot; : 1,&lt;br/&gt;
                        &quot;state&quot; : 2,&lt;br/&gt;
                        &quot;stateStr&quot; : &quot;SECONDARY&quot;,&lt;br/&gt;
                        &quot;uptime&quot; : 9634,&lt;br/&gt;
                        &quot;optime&quot; : &lt;/p&gt;
{
                                &quot;t&quot; : 1343616819000,
                                &quot;i&quot; : 1
                        }
&lt;p&gt;,&lt;br/&gt;
                        &quot;optimeDate&quot; : ISODate(&quot;2012-07-30T02:53:39Z&quot;),&lt;br/&gt;
                        &quot;lastHeartbeat&quot; : ISODate(&quot;2012-07-30T05:24:29Z&quot;),&lt;br/&gt;
                        &quot;pingMs&quot; : 0&lt;br/&gt;
                }&lt;br/&gt;
        ],&lt;br/&gt;
        &quot;ok&quot; : 1&lt;br/&gt;
}&lt;br/&gt;
###sh.status()#################################################################&lt;br/&gt;
mongos&amp;gt; sh.status()&lt;br/&gt;
&amp;#8212; Sharding Status &amp;#8212; &lt;br/&gt;
  sharding version: &lt;/p&gt;
{ &quot;_id&quot; : 1, &quot;version&quot; : 3 }
&lt;p&gt;  shards:&lt;/p&gt;
        {  &quot;_id&quot; : &quot;shard1&quot;,  &quot;host&quot; : &quot;shard1/10.136.16.67:27032,10.136.16.68:27032&quot; }
        {  &quot;_id&quot; : &quot;shard2&quot;,  &quot;host&quot; : &quot;shard2/10.136.16.69:27032,10.136.16.70:27032&quot; }
&lt;p&gt;  databases:&lt;/p&gt;
        {  &quot;_id&quot; : &quot;admin&quot;,  &quot;partitioned&quot; : false,  &quot;primary&quot; : &quot;config&quot; }
        {  &quot;_id&quot; : &quot;d_name&quot;,  &quot;partitioned&quot; : true,  &quot;primary&quot; : &quot;shard1&quot; }
&lt;p&gt;                d_name.t_name chunks:&lt;br/&gt;
                                shard2  244&lt;br/&gt;
                                shard1  245&lt;br/&gt;
                        too many chunks to print, use verbose if you want to force print&lt;/p&gt;
        {  &quot;_id&quot; : &quot;test&quot;,  &quot;partitioned&quot; : false,  &quot;primary&quot; : &quot;shard1&quot; }

&lt;p&gt;###mongos log###################################################################&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; SyncClusterConnection connecting to &lt;span class=&quot;error&quot;&gt;&amp;#91;10.136.20.59:20000&amp;#93;&lt;/span&gt;&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; starting new replica set monitor for replica set shard1 with seed of 10.136.16.67:27032,10.136.16.68:27032&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; successfully connected to seed 10.136.16.67:27032 for replica set shard1&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; changing hosts to &lt;/p&gt;
{ 0: &quot;10.136.16.67:27032&quot;, 1: &quot;10.136.16.73:27032&quot;, 2: &quot;10.136.16.68:27032&quot; }
&lt;p&gt; from shard1/&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; trying to add new host 10.136.16.67:27032 to replica set shard1&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; successfully connected to new host 10.136.16.67:27032 in replica set shard1&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; trying to add new host 10.136.16.68:27032 to replica set shard1&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; successfully connected to new host 10.136.16.68:27032 in replica set shard1&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; trying to add new host 10.136.16.73:27032 to replica set shard1&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; successfully connected to new host 10.136.16.73:27032 in replica set shard1&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; replica set monitor for replica set shard1 started, address is shard1/10.136.16.67:27032,10.136.16.68:27032,10.136.16.73:27032&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;ReplicaSetMonitorWatcher&amp;#93;&lt;/span&gt; starting&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; starting new replica set monitor for replica set shard2 with seed of 10.136.16.69:27032,10.136.16.70:27032&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; successfully connected to seed 10.136.16.69:27032 for replica set shard2&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; changing hosts to &lt;/p&gt;
{ 0: &quot;10.136.16.69:27032&quot;, 1: &quot;10.136.16.70:27032&quot; }
&lt;p&gt; from shard2/&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; trying to add new host 10.136.16.69:27032 to replica set shard2&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; successfully connected to new host 10.136.16.69:27032 in replica set shard2&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; trying to add new host 10.136.16.70:27032 to replica set shard2&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; successfully connected to new host 10.136.16.70:27032 in replica set shard2&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; replica set monitor for replica set shard2 started, address is shard2/10.136.16.69:27032,10.136.16.70:27032&lt;br/&gt;
Mon Jul 30 13:53:28 &lt;span class=&quot;error&quot;&gt;&amp;#91;Balancer&amp;#93;&lt;/span&gt; config servers and shards contacted successfully&lt;/p&gt;

</comment>
                            <comment id="148196" author="william.zola@10gen.com" created="Fri, 27 Jul 2012 18:04:24 +0000"  >&lt;p&gt;Hi Jianfeng!&lt;/p&gt;

&lt;p&gt;All of that looks good.  As I said before, the sh.status() should update automatically.  Can you please send me the output of rs.status() from one of the nodes in shard1.  It is possible that your new host is not yet in SECONDARY status, and the output of this command will check for that.&lt;/p&gt;

&lt;p&gt;Please let me know.  Have a great day!&lt;/p&gt;

&lt;p&gt; -William &lt;/p&gt;</comment>
                            <comment id="147938" author="popgo" created="Fri, 27 Jul 2012 01:27:27 +0000"  >&lt;p&gt;Thanks!&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;MongoDB version: mongodb-linux-x86_64-2.0.6&lt;/li&gt;
	&lt;li&gt;PRIMARY&amp;gt; db.isMaster()&lt;br/&gt;
{&lt;br/&gt;
        &quot;setName&quot; : &quot;shard1&quot;,&lt;br/&gt;
        &quot;ismaster&quot; : true,&lt;br/&gt;
        &quot;secondary&quot; : false,&lt;br/&gt;
        &quot;hosts&quot; : [&lt;br/&gt;
                &quot;10.136.16.67:27032&quot;,&lt;br/&gt;
                &quot;10.136.16.73:27032&quot;,&lt;br/&gt;
                &quot;10.136.16.68:27032&quot;&lt;br/&gt;
        ],&lt;br/&gt;
        &quot;arbiters&quot; : [&lt;br/&gt;
                &quot;10.136.16.68:37032&quot;&lt;br/&gt;
        ],&lt;br/&gt;
        &quot;primary&quot; : &quot;10.136.16.67:27032&quot;,&lt;br/&gt;
        &quot;me&quot; : &quot;10.136.16.67:27032&quot;,&lt;br/&gt;
        &quot;maxBsonObjectSize&quot; : 16777216,&lt;br/&gt;
        &quot;ok&quot; : 1&lt;br/&gt;
}&lt;/li&gt;
&lt;/ul&gt;


&lt;ul&gt;
	&lt;li&gt;There are three config servers in this sharding: 10.136.20.57:20000,10.136.20.58:20000,10.136.20.59:20000. All of nodes are online and active. I show some informations from mongos log.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Fri Jul 27 09:09:39 &lt;span class=&quot;error&quot;&gt;&amp;#91;LockPinger&amp;#93;&lt;/span&gt; cluster 10.136.20.57:20000,10.136.20.58:20000,10.136.20.59:20000 pinged successfully at Fri Jul 27 09:09:39 2012 by distributed lock pinger &apos;10.136.20.57:20000,10.136.20.58:20000,10.136.20.59:20000/mongos-2057:30000:1343047408:1804289383&apos;, sleeping for 30000ms&lt;/p&gt;

&lt;ul&gt;
	&lt;li&gt;Almost one day. &quot;Thu Jul 26 15:07:26&quot;, i added it. Now &quot;Fri Jul 27 09:24:16&quot;, the sh.status()&apos;s output is like this. It is not update by itself.&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@mongodb-1667 ~&amp;#93;&lt;/span&gt;# date&lt;br/&gt;
Fri Jul 27 09:24:16 CST 2012&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;root@mongodb-1667 ~&amp;#93;&lt;/span&gt;# mongo --host=10.136.20.57:30000&lt;br/&gt;
MongoDB shell version: 2.0.6&lt;br/&gt;
connecting to: 10.136.20.57:30000/test&lt;br/&gt;
mongos&amp;gt; sh.status()&lt;br/&gt;
&amp;#8212; Sharding Status &amp;#8212; &lt;br/&gt;
  sharding version: &lt;/p&gt;
{ &quot;_id&quot; : 1, &quot;version&quot; : 3 }
&lt;p&gt;  shards:&lt;/p&gt;
        {  &quot;_id&quot; : &quot;shard1&quot;,  &quot;host&quot; : &quot;shard1/10.136.16.67:27032,10.136.16.68:27032&quot; }
        {  &quot;_id&quot; : &quot;shard2&quot;,  &quot;host&quot; : &quot;shard2/10.136.16.69:27032,10.136.16.70:27032&quot; }
&lt;p&gt;  databases:&lt;/p&gt;
        {  &quot;_id&quot; : &quot;admin&quot;,  &quot;partitioned&quot; : false,  &quot;primary&quot; : &quot;config&quot; }
        {  &quot;_id&quot; : &quot;d_name&quot;,  &quot;partitioned&quot; : true,  &quot;primary&quot; : &quot;shard1&quot; }
&lt;p&gt;                d_name.t_name chunks:&lt;br/&gt;
                                shard1  243&lt;br/&gt;
                                shard2  243&lt;br/&gt;
                        too many chunks to print, use verbose if you want to force print&lt;/p&gt;
        {  &quot;_id&quot; : &quot;test&quot;,  &quot;partitioned&quot; : false,  &quot;primary&quot; : &quot;shard1&quot; }



&lt;p&gt;&amp;#8211; popgo&lt;/p&gt;</comment>
                            <comment id="147787" author="william.zola@10gen.com" created="Thu, 26 Jul 2012 20:12:25 +0000"  >&lt;p&gt;Hi Jianfeng!&lt;/p&gt;

&lt;p&gt;I&apos;ll need additional information to diagnose this problem.  Please let me know the following:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;What version of MongoDB are you running?&lt;/li&gt;
	&lt;li&gt;Please send me the output of db.isMaster() when you are connected to a node in the shard1 replica set&lt;/li&gt;
	&lt;li&gt;How many config servers are you running?  Are they all currently active?&lt;/li&gt;
	&lt;li&gt;How long did you wait between adding the new node and running sh.status()?&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;I&apos;d like to help you solve this problem.  I can&apos;t move forward without this information.  &lt;/p&gt;

&lt;p&gt; -William &lt;/p&gt;
</comment>
                            <comment id="147602" author="popgo" created="Thu, 26 Jul 2012 15:24:21 +0000"  >&lt;p&gt;Thanks for your reply.&lt;/p&gt;

&lt;p&gt;Yes, u can look the output of sh.status().&lt;/p&gt;

&lt;p&gt;mongos&amp;gt; sh.status()&lt;br/&gt;
&amp;#8212; Sharding Status &amp;#8212; &lt;br/&gt;
  sharding version: &lt;/p&gt;
{ &quot;_id&quot; : 1, &quot;version&quot; : 3 }
&lt;p&gt;  shards:&lt;/p&gt;
        {  &quot;_id&quot; : &quot;shard1&quot;,  &quot;host&quot; : &quot;shard1/10.136.16.67:27032,10.136.16.68:27032&quot; }
        {  &quot;_id&quot; : &quot;shard2&quot;,  &quot;host&quot; : &quot;shard2/10.136.16.69:27032,10.136.16.70:27032&quot; }
&lt;p&gt;  databases:&lt;/p&gt;
        {  &quot;_id&quot; : &quot;admin&quot;,  &quot;partitioned&quot; : false,  &quot;primary&quot; : &quot;config&quot; }
        {  &quot;_id&quot; : &quot;d_name&quot;,  &quot;partitioned&quot; : true,  &quot;primary&quot; : &quot;shard1&quot; }
&lt;p&gt;                d_name.t_name chunks:&lt;br/&gt;
                                shard1  243&lt;br/&gt;
                                shard2  243&lt;br/&gt;
                        too many chunks to print, use verbose if you want to force print&lt;/p&gt;
        {  &quot;_id&quot; : &quot;test&quot;,  &quot;partitioned&quot; : false,  &quot;primary&quot; : &quot;shard1&quot; }</comment>
                            <comment id="147596" author="renctan" created="Thu, 26 Jul 2012 15:12:50 +0000"  >&lt;p&gt;It should be able to update itself over time. Is it not in your case?&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10010">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="46009">SERVER-6680</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="18528" name="mongos.log" size="111934" author="popgo" created="Tue, 31 Jul 2012 01:01:49 +0000"/>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10050" key="com.atlassian.jira.toolkit:comments">
                        <customfieldname># Replies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>12.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10055" key="com.atlassian.jira.ext.charting:firstresponsedate">
                        <customfieldname>Date of 1st Reply</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>Thu, 26 Jul 2012 15:12:50 +0000</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10052" key="com.atlassian.jira.toolkit:dayslastcommented">
                        <customfieldname>Days since reply</customfieldname>
                        <customfieldvalues>
                                        11 years, 29 weeks ago
    
                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_18254" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Dependencies</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[]]></customfieldvalue>


                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_10057" key="com.atlassian.jira.toolkit:lastusercommented">
                        <customfieldname>Last comment by Customer</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>true</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10056" key="com.atlassian.jira.toolkit:lastupdaterorcommenter">
                        <customfieldname>Last commenter</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>ian@mongodb.com</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_11151" key="com.atlassian.jira.toolkit:LastCommentDate">
                        <customfieldname>Last public comment date</customfieldname>
                        <customfieldvalues>
                            11 years, 29 weeks ago
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10000" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Old_Backport</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10000"><![CDATA[No]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10032" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Operating System</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10026"><![CDATA[ALL]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_10051" key="com.atlassian.jira.toolkit:participants">
                        <customfieldname>Participants</customfieldname>
                        <customfieldvalues>
                                        <customfieldvalue>popgo</customfieldvalue>
            <customfieldvalue>randolph@mongodb.com</customfieldvalue>
            <customfieldvalue>william.zola@10gen.com</customfieldvalue>
    
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        <customfield id="customfield_14254" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Product Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|hrntvr:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hrgnbb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>10732</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_23361" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Requested By</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_10053" key="com.atlassian.jira.ext.charting:timeinstatus">
                        <customfieldname>Time In Status</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_22870" key="com.onresolve.jira.groovy.groovyrunner:scripted-field">
                        <customfieldname>Triagers</customfieldname>
                        <customfieldvalues>
                                

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_14350" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>serverRank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1|ht09pr:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                    </customfields>
    </item>
</channel>
</rss>