[
https://issues.apache.org/jira/browse/KUDU-3182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190335#comment-17190335
]
ASF subversion and git services commented on KUDU-3182:
-------------------------------------------------------
Commit a59d3821bfbc87ac3c910c602d2bdf037eeb9d9b in kudu's branch
refs/heads/master from Bankim Bhavsar
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=a59d382 ]
[master] KUDU-3182 Allow single master to specify --master_addresses
'last_known_addr' field is not persisted for a single master Raft
configuration. This is okay as long as we have a single master
configuration. On dynamically transitioning from single master
to two master configuration, ChangeConfig() request to ADD_PEER
fails the validation in VerifyRaftConfig().
In order to transition to multi-master configuration, 'last_known_addr'
must be specified.
Some options considered were using the --rpc_bind_addresses flag, if
specified. If not, use GetHostName(). None of these are reliable.
So it's best to let user to specify the address of the single master
as is the case for specifying master address in tablet servers.
Currently --master_addresses flag must be empty for single master
configuration and --master_addresses with single address is not
permitted.
So the idea is to use existing --master_addresses flag for single
master configuration too and not just distributed configuration.
This change allows specifying --master_addresses flag for
single master configuration. To be backward compatible with existing
deployments, specifying this flag for single master configurations
is still optional and not required. If specified, it's used to set the
'last_known_addr' field in the master Raft configuration.
This change also provides mechanism for existing single master
Kudu deployments to specify the --master_addresses flag and populate
the 'last_known_addr' field in the master Raft configuration.
This change is a pre-requisite for upcoming dynamic multi-master
changes.
Change-Id: I4fe1bcd217d68f66db72c321397d596cba4224be
Reviewed-on: http://gerrit.cloudera.org:8080/16340
Tested-by: Kudu Jenkins
Reviewed-by: Andrew Wong <[email protected]>
> 'last_known_addr' is not specified for single master Raft configuration
> -----------------------------------------------------------------------
>
> Key: KUDU-3182
> URL: https://issues.apache.org/jira/browse/KUDU-3182
> Project: Kudu
> Issue Type: Task
> Components: consensus, master
> Reporter: Bankim Bhavsar
> Assignee: Bankim Bhavsar
> Priority: Major
>
> 'last_known_addr' field is not persisted for a single master Raft
> configuration. This is okay as long as we have a single master
> configuration. On dynamically transitioning from single master
> to two master configuration, ChangeConfig() request to ADD_PEER
> fails the validation in VerifyRaftConfig().
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
