[
https://issues.apache.org/jira/browse/COUCHDB-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571508#comment-13571508
]
Jan Lehnardt commented on COUCHDB-1667:
---------------------------------------
Ah yes, the alternative is to put cleverness into code, but in the grander
scheme of things, whether the base directory for indexes is called
view_index_dir or index_dir does *not* make a huge difference, so I thought we
skip being smart and stick with the old name. With 1.3.x and later indexes will
be separated by index module anyway ([view_]index_dir/mrview, /geocouch etc),
so I don’t think we gain much by renaming things.
> 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
> 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
