On Jun 12, 2008, at 21:47, Сергей Курцев wrote:
Damien,
thanks for you replies. I've put them into wiki since it will be
useful
to others
http://wiki.apache.org/couchdb/Compaction
Good thinking, thanks Sergey!
Cheers
Jan
--
With best regards,
Sergey.
On Thu, 12/06/2008 at 15:02 -0400, Damien Katz wrote:
CouchDB works like this to have the least impact possible on
clients,
the database remains online and fully functional to readers and
writers. Yes, its a design limitation that database compaction can't
complete when at capacity for write load, however I don't think its
unreasonable to schedule compactions during off-peak hours either.
As
you point out, in a clustered environment the write load can
switched
off for any node during compaction and brought back up to date with
replication once complete.
In the future, a single couchdb node can be changed to stop or fail
other updates if the write load is too heavy for it to complete in a
reasonable time.
