couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <>
Subject [jira] Updated: (COUCHDB-753) Add config option for view compact dir
Date Sun, 02 May 2010 14:36:57 GMT


Adam Kocoloski updated COUCHDB-753:

Hi Till, I'm having trouble figuring out how this would work.  Are you saying you want to
create the .compact file on another volume, then move it back to the volume hosting the view_index_dir
when it's time to do the switchover?

The trouble I see with that approach is that the final move of the compacted view index file
would take a very long time.  If the server crashed during the move, how would it know which
file to choose?  I guess one possible priority list might be

1) .view file in view_index_dir
2) .view.compact file in view_compact_dir
3) .view.compact file view_index_dir

This would hopefully take care of the case where the .view file has been deleted but the server
crashed before the .view.compact file could be completely transferred over to the original
volume and renamed.

> Add config option for view compact dir
> --------------------------------------
>                 Key: COUCHDB-753
>                 URL:
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: Database Core
>            Reporter: Till Klampaeckel
> CouchDB creates a "foo.view.compact" file in the view directory ("view_index_dir") when
you run compact against a view.
> I'd really like to be able to specify another directory where this ".compact" file is
created and worked on. This is especially helpful when it's difficult to run compaction because
you run out of disk space on the same device.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message