[ 
https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15983548#comment-15983548
 ] 

ASF subversion and git services commented on COUCHDB-3288:
----------------------------------------------------------

Commit 99b179c807101337f0fe7c8500f6c3a0b4c9e616 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=99b179c ]

Add clause for mixed cluster upgrades

A mixed cluster (i.e., during a rolling reboot) will want to include
this commit in a release before deploying PSE code to avoid spurious
erros during the upgrade.

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)

Reply via email to