New answers tagged

0

To upgrade to MongoDB 3.0 all members of a replica set must be running the previous major release (MongoDB 2.6). See: Upgrade a replica set to 3.0. A replica set configuration mixing 2.4 and 3.0 nodes is not supported or tested and will likely lead to unexpected errors. Since you have 1.7TB of data, I would definitely follow the recommended upgrade ...


0

You can do: output="$(mongodump 2>&1)" || echo -e "$output" This save both stdout and stderr into output variable, then if the command exit with not 0 exit code, echo the saved output.


0

Maybe there is a way to tell it to synchronize faster? Since the amount of data copied to the new secondary is very large (7TB) so the issue happens. MongoDB suggests the following procedure for a large amount of data set. Sync by Copying Data Files from Another Member This approach “seeds” a new or stale member using the data files from an existing ...


0

Is there any managed MongoDB as a service available in Microsoft Azure which will: a) Auto scale. b) Charge me only for my usage. Yes, As per MSDN BOL documentation here Azure Cosmos DB is Microsoft's globally distributed, multi-model database service. With a click of a button, Cosmos DB enables you to elastically and independently scale throughput ...


0

MongoDB Atlas in a managed database as a service officially provided by MongoDB and it is readily available in all the three (aws, azure, gcp) major cloud providers. Automated MongoDB service on Azure


0

You can use this to update the first matching array element without knowing the index: db.students.update( { first_name: 'AA',name_school:'EPFC' }, { $set: { "cours_reussis.$.name_school": 'ENSA' } } )


Top 50 recent answers are included