[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: Text File shard.txt    
Participants:

 Description   

We had three system running with following ip's on same network.
out of three systems two are of 64 bit and one is 32 bit.

config server IP's:
192.168.1.121:27019
192.168.1.122:27019
10.42.43.10:27019

shard server IP's:
192.168.1.121:27018
192.168.1.122:27018
10.42.43.10:27018

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.
2015-10-20T11:17:43.893+0530 I CONTROL
2015-10-20T11:17:43.895+0530 I SHARDING [mongosMain] MongoS version 3.0.6 starting: pid=7355 port=27017 32-bit host=localhost.localdomain (--help for usage)
2015-10-20T11:17:43.895+0530 I CONTROL [mongosMain] db version v3.0.6
2015-10-20T11:17:43.895+0530 I CONTROL [mongosMain] git version: 1ef45a23a4c5e3480ac919b28afcba3c615488f2
2015-10-20T11:17:43.895+0530 I CONTROL [mongosMain] build info: Linux build2.ny.cbi.10gen.cc 2.6.32-431.3.1.el6.x86_64 #1 SMP Fri Jan 3 21:39:27 UTC 2014 x86_64 BOOST_LIB_VERSION=1_49
2015-10-20T11:17:43.895+0530 I CONTROL [mongosMain] allocator: tcmalloc
2015-10-20T11:17:43.895+0530 I CONTROL [mongosMain] options: { sharding:

{ configDB: "192.168.1.121:27019,192.168.1.122:27019,10.42.43.10:27019" }

}
2015-10-20T11:17:43.924+0530 W SHARDING [mongosMain] config servers 192.168.1.121:27019 and 192.168.1.122:27019 differ
2015-10-20T11:17:43.927+0530 W SHARDING [mongosMain] config servers 192.168.1.121:27019 and 192.168.1.122:27019 differ
2015-10-20T11:17:43.930+0530 W SHARDING [mongosMain] config servers 192.168.1.121:27019 and 192.168.1.122:27019 differ
2015-10-20T11:17:43.934+0530 W SHARDING [mongosMain] config servers 192.168.1.121:27019 and 192.168.1.122:27019 differ
2015-10-20T11:17:43.934+0530 E SHARDING [mongosMain] could not verify that config servers are in sync :: caused by :: config servers 192.168.1.121:27019 and 192.168.1.122:27019 differ:

{ chunks: "d41d8cd98f00b204e9800998ecf8427e", databases: "a07b514cc5121c09ea76a50e14243810", shards: "1615b31aeadba8edcaa364f5cefe6d5a", version: "e67b3d339142847dd02338fb425c0530" }

vs {}
2015-10-20T11:17:43.934+0530 I - [mongosMain] configServer connection startup check failed



 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,
Stephen

Generated at Thu Feb 08 03:56:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.