MongoDB sharding problems -


our mongodb server deployed 2 shards, each has 1 master server , 2 slave servers. 4 slave servers run mongo config proxy, , 2 of slave servers run arbiters. mongodb coundn't used now.

i can connect 192.168.0.1:8000(mongos) , exec queries 'use database' or 'show dbs', cann't exec queries in choosed database such 'db.foo.count()', 'db.foo.findone()'

here error log:

mongos> db.dev.count() fri aug 16 12:55:36 uncaught exception: count failed: {     "assertion" : "dbclientbase::findn: transport error: 10.81.4.72:7100 query: { setshardversion: \"\", init: true, configdb: \"10.81.4.72:7300,10.42.50.26:7300,10.81.51.235:7300\", serverid: objectid('520db0a51fa00999772612b9'), authoritative: true }",     "assertioncode" : 10276,     "errmsg" : "db assertion failure",     "ok" : 0 }     fri aug 16 11:23:29 [conn8431] dbclientcursor::init call() failed fri aug 16 11:23:29 [conn8430] socket recv() errno:104 connection reset peer 10.81.4.72:7100 fri aug 16 11:23:29 [conn8430] socketexception: remote: 10.81.4.72:7100 error: 9001 socket exception [1] server [10.81.4.72:7100]  fri aug 16 11:23:29 [conn8430] dbclientcursor::init call() failed fri aug 16 11:23:29 [conn8430] dbexception in process: not initialize cursor across shards because : dbclientbase::findn: transport error: 10.81.4.72:7100 query: { setshardversion: "", init: true, configdb: "10.81.4.72:7300,10.42.50.26:7300,10.81.51.235:7300", serverid: objectid('520d99c972581e6a124d0561'), authoritative: true } @ s01/10.36.31.36:7100,10.42.50.24:7100,10.81.4.72:7100 

i can start on mongos, queries wouldn't exec if more 1 mongos run @ same time, error log:

mongos> db.dev.count() fri aug 16 15:12:29 uncaught exception: count failed: { "assertion" : "dbclientbase::findn: transport error: 10.81.4.72:7100 query: { setshardversion: \"\", init: true, configdb: \"10.81.4.72:7300,10.42.50.26:7300,10.81.51.235:7300\", serverid: objectid('520dd04967557902f73a9fba'), authoritative: true }", "assertioncode" : 10276, "errmsg" : "db assertion failure", "ok" : 0 } 

could please clarify if set-up working before, if setting now?

to repair mongodb, might want follow link: http://docs.mongodb.org/manual/tutorial/recover-data-following-unexpected-shutdown/

references

mongodb documentation : deploying shard-cluster

mongodb documentation : add shards existing cluster

older, outdated(!) info:

youtube video on setting-up sharding mongodb

corresponding blog on blog.serverdensity.com


Comments

Popular posts from this blog

c# - Send Image in Json : 400 Bad request -

javascript - addthis share facebook and google+ url -

ios - Show keyboard with UITextField in the input accessory view -