[ https://issues.apache.org/jira/browse/COUCHDB-3288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163113#comment-16163113 ]
ASF subversion and git services commented on COUCHDB-3288: ---------------------------------------------------------- Commit d6f65c46bce90cd9f67bc9b4e10aa4e069d23fab in couchdb's branch refs/heads/COUCHDB-3288-mixed-cluster-upgrade from [~paul.joseph.davis] [ https://gitbox.apache.org/repos/asf?p=couchdb.git;h=d6f65c4 ] Allow for mixed db record definitions This change is to account for differences in the #db record when a cluster is operating in a mixed version state (i.e., when running a rolling reboot to upgrade). There are only a few operations that are valid on #db records that are shared between nodes so rather than attempt to map the entire API between the old and new records we're limiting to just the required API calls. COUCHDB-3288 > Allow mixed clusters for PSE deployment > --------------------------------------- > > 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.4.14#64029)