[jira] [Updated] (KUDU-2663) src/kudu/consensus/consensus.txt seems out of date

["Adar Dembo (JIRA)" <ji...@apache.org>]

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

Adar Dembo updated KUDU-2663:
-----------------------------
    Affects Version/s: 1.8.0
               Labels: newbie  (was: )
             Priority: Minor  (was: Major)
          Component/s: documentation

{quote}
Is this still valid that consensus does not support membership changes?

Can we update consensus.txt to reflect current reality? 
{quote}

Indeed, this seems to be an oversight; we added the ability to perform membership changes a long time ago.

Would you be interested in fixing this? We have docs on contributing patches to Kudu [here| https://kudu.apache.org/docs/contributing.html]. Feel free to ping us in our [Slack|https://getkudu-slack.herokuapp.com] if you need any help. 



> src/kudu/consensus/consensus.txt seems out of date
> --------------------------------------------------
>
>                 Key: KUDU-2663
>                 URL: https://issues.apache.org/jira/browse/KUDU-2663
>             Project: Kudu
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 1.8.0
>            Reporter: Anirban Rahut
>            Priority: Minor
>              Labels: newbie
>
> I am trying to build Kudu from source and also improve it more, and running into some understanding issues. 
> Here is some of the documentation in consensus.txt   
>  
> RaftConfig membership changes:
> ------------------------------
> A two-phase joint consensus protocol is used for making cluster membership changes, including changing members of the config or the size of the majority. See RAFT section 6 and figure 11 for details.         
>  
> NOTE: membership changes are not yet implemented in Kudu.  
>  
> ----
> Is this still valid that consensus does not support membership changes?
> Can we update consensus.txt to reflect current reality?  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)