top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

MongoException on Mongo Insert (errorCode=72): Command failed with error 72

0 votes
558 views

MongoException on Mongo Insert (errorCode=72): Command failed with error 72: 'Writes to config servers must have batch size of 1, found 1000'
I have this error on a collection bulk insert via mongos. Can you help?

posted Jul 21, 2016 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+3 votes
Mongo: Get list of databases with a UNIX command

I would like to get the list of the database manage by on server through a single shell command, on UNIX. The objective is to be able to do a full export of all dbs for validation purposes.
Right now, I can see only two ways to do this.
- Start mongo, type show dbs, to a manual copy of the list and exit. I do not like this way as this requires several manual operations.
- Scan the files.*.0 in the db directory.
This works but is dependent on the format of the database.Is there any better way to list all the DBs managed by a server through a single command? I am using MongoDB 3.0.4 on Scientific Linux.

0 votes
Starting mongod (via systemctl): Job for mongod.service failed because the control process exited with error code...

Starting mongod (via systemctl): Job for mongod.service failed because the control process exited with error code. See "systemctl status mongod.service" and "journalctl -xe" for details.

Please guide me, how to overcome this issue.

+1 vote
DBClientCursor::init call() failed while trying to shutdown mongo

I am running these commands through mongo shell in a bash script

db=db.getSiblingDB('admin'); db.shutdownServer(); quit();

but it seems that db is not getting shutdown, this is the response i am getting :

MongoDB shell version: 2.6.10 connecting to: localhost:27000/test 2015-06-27T10:05:54.375+0000 DBClientCursor::init call() failed server should be down...

Any advice on what to do and what is going wrong? I tried to shutdown mms agents first,but that didn't help

...