[SERVER-21021] Sharding Created: 20/Oct/15 Updated: 20/Oct/15 Resolved: 20/Oct/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | MMAPv1 |
| Affects Version/s: | 3.0.6 |
| Fix Version/s: | None |
| Type: | Question | Priority: | Critical - P2 |
| Reporter: | dharanikumar bodla | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Participants: |
| Description |
|
We had three system running with following ip's on same network. config server IP's: shard server IP's: mongos : mongos --configdb 192.168.1.121:27019,192.168.1.122:27019,10.42.43.10:27019 2015-10-20T11:17:43.893+0530 I CONTROL ** WARNING: You are running this process as the root user, which is not recommended. } vs {} |
| Comments |
| Comment by Stennie Steneker (Inactive) [ 20/Oct/15 ] |
|
Hi, The SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related community support discussion or general questions please post on the mongodb-user group (http://groups.google.com/group/mongodb-user) or Stack Overflow. A question like this involving more discussion would be best posted on the mongodb-user group. FYI, the error message "could not verify that config servers are in sync" indicates that some of your config servers have different checksums for sharded cluster metadata, so you will need to compare the data and determine which config server to replace. > out of three systems two are of 64 bit and one is 32 bit. 32-bit servers are not suitable for production usage as there are limits on data size of about 2GB (or half of that with journal enabled). For more information, see: What are the limitations of 32-bit versions of MongoDB?). Thanks, |