Re:“MongoDB is dead. Long live Postgresql”
by functional_test on Tuesday November 26, 2013 @04:07PM
(#6804213)
In a proper production environment, you just compact each slave one at a time because you have a replica set rather than a single instance.
Of course, if you aren't replicating your business's production database, you have a whole world of problems.
Of course, if you aren't replicating your business's production database, you have a whole world of problems.
Not really. In RDBMS you can have offline backups (assuming you aren't building for high availability). I don't know if that exists for MongoDB.
Even pre-auto-vacuuming Postgres (ie, before Postgres v8) would allow you to vacuum the database while online. You had a performance hit, but there was no need to switch to a backup server or anything.
Re:“MongoDB is dead. Long live Postgresql”
by jeffdavis on Tuesday November 26, 2013 @09:41PM
(#6805931)
Good point, but that would make me a little nervous. What happens if the compaction takes a while and the replica gets far behind? And wouldn't the compaction time just keep getting longer and longer as data grows?
Can you repartition the data online to keep the cleanup work bounded?
Re:“MongoDB is dead. Long live Postgresql”
by darkarmani on Tuesday November 26, 2013 @11:30PM
(#6806397)
> In a proper production environment, you just compact each slave one at a time because you have a replica set rather than a single instance.
That's the solution?? That sounds like a workaround in a production environment.
Re:“MongoDB is dead. Long live Postgresql”
by lmm on Wednesday November 27, 2013 @05:04AM
(#6807359)
Yes and no. Deleting is a hard problem that many databases don't handle well. Explicitly deciding to punt the problem like this is a much better approach than allowing performance to degrade unpredictably.
https://jira.mongodb.org/browse/SERVER-11763
It looks like compaction is an offline process. That really puts the user between a rock and a hard place.