[DOCS-8954] Shards should retry contacting config servers indefinitely Created: 28/Sep/16 Updated: 30/Oct/23 Resolved: 19/Jul/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Emily Hall | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 6 years, 30 weeks ago | ||||||||
| Epic Link: | 3.4: Sharding Updates | ||||||||
| Description |
|
Root cause found - see comment 4 For testing I set up a 3.2-rc1 cluster with 32 shards. WT, Zlib - EVERYTHING on LOCALHOST I used a SINGLE , non replica set config server which rc1 allows me to do ( I raised a previous ticket that it should) I was able to successfully load 800GB of sharded data using a Java based loader. After restarting the cluster I get.
sh.status appears to work OK Show collections gives
All mongod logs show
I can connect to the config server with mongo on localhost:27019 |
| Comments |
| Comment by Githook User [ 19/Jul/17 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 19/Jul/17 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 19/Jul/17 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |
| Comment by Githook User [ 19/Jul/17 ] |
|
Author: {u'username': u'kay-kim', u'name': u'kay', u'email': u'kay.kim@10gen.com'}Message: |