[SERVER-12240] Shard stock in recovering state Created: 02/Jan/14 Updated: 10/Dec/14 Resolved: 07/Jan/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 2.4.8 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Dwayne Mcnab | Assignee: | Thomas Rueckstiess |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Testing |
||
| Attachments: |
|
| Operating System: | ALL |
| Participants: |
| Description |
|
after an upgrade from 2.4.6 to 2.4.8, the shard is stock in the "recovering" state. |
| Comments |
| Comment by Dwayne Mcnab [ 07/Jan/14 ] | ||
|
That explains it. Thanks a lot Eliot. Myself and my company are new to On Tue, Jan 7, 2014 at 12:26 AM, Thomas Rueckstiess (JIRA) <jira@mongodb.org | ||
| Comment by Thomas Rueckstiess [ 07/Jan/14 ] | ||
|
Hi Dwayne, When the server was started on Dec 16 (version 2.4.6) the options were:
After the upgrade to 2.4.8, on Jan 02, the options of mongod are:
Notice the additional auth parameter that you are now using. That would explain the many command denied messages. You either need to run all nodes in the replica set with the --keyFile parameter, or completely without authentication. --auth is only used for single stand-alone nodes, not for replica sets / sharded clusters, see our documentation on Authentication. Regards, | ||
| Comment by Dwayne Mcnab [ 06/Jan/14 ] | ||
|
Thanks for replying Eliot, Please see a copy of the server's log file. | ||
| Comment by Eliot Horowitz (Inactive) [ 04/Jan/14 ] | ||
|
Can you send the full mongod log on that server? |