[
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983183#comment-15983183
]
ASF subversion and git services commented on COUCHDB-3288:
----------------------------------------------------------
Commit bebf3a7cdc7fac53ad09c980ae6e30c364672bcd in couchdb's branch
refs/heads/COUCHDB-3287-pluggable-storage-engines from [~paul.joseph.davis]
[ https://gitbox.apache.org/repos/asf?p=couchdb.git;h=bebf3a7 ]
Add clause for mixed cluster upgrades
Pluggable storage engines will want to have a 2-arity version of
create_db to be able to pass engine options during creation. Users that
do rolling reboots upgrading to CouchDB including PSE will want to
ensure that they don't include an alternative storage engine
configuration or this will result in some shards not having the correct
storage engine for any database when the cluster exists in a mixed
state with pre-PSE versions.
COUCHDB-3288
> Remove public db record
> -----------------------
>
> Key: COUCHDB-3288
> URL: https://issues.apache.org/jira/browse/COUCHDB-3288
> Project: CouchDB
> Issue Type: Improvement
> Reporter: Paul Joseph Davis
>
> To enable a mixed cluster upgrade (i.e., rolling reboot upgrade) we need to
> do some preparatory work to remove access to the #db{} record since this
> record is shared between nodes.
> This work is all straight forward and just involves changing things like
> Db#db.main_pid to couch_db:get_main_pid(Db) or similar.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
