You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Jan Lehnardt (JIRA)" <ji...@apache.org> on 2013/02/06 21:51:13 UTC

[jira] [Resolved] (COUCHDB-1667) Gracefully update from view_index_dir to index_dir

     [ https://issues.apache.org/jira/browse/COUCHDB-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jan Lehnardt resolved COUCHDB-1667.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3
    
> Gracefully update from view_index_dir to index_dir
> --------------------------------------------------
>
>                 Key: COUCHDB-1667
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1667
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 1.3
>            Reporter: Alexander Shorin
>            Priority: Blocker
>             Fix For: 1.3
>
>         Attachments: COUCHDB-1667.1-revert_to_view_index_dir.patch, COUCHDB-1667.1-update_to_index_dir.patch
>
>
> CouchDB 1.3 ships with new couch_index app[1] that uses `index_dir` config option to locate directory to store view indexes. However, it replaces[2] old `view_index_dir`option creating situation when recently updated default.ini will have only `index_dir` option and old, but production used local.ini would still have `view_index_dir`. There is a fallback[3], but there no insurance that it will let user gracefully update.
> This situation may leads to very bad situations, when all indexes will be rebuilded against location that may not expects their on disk size (since `view_index_dir` was pointed to the another mount point) which leads to server fall.
> [1]: https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=35e57870
> [2]: https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=e83352f3
> [3]: https://github.com/apache/couchdb/blob/master/src/couch_index/src/couch_index_util.erl#L22

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira