[
https://issues.apache.org/jira/browse/KUDU-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Will Berkeley resolved KUDU-2650.
---------------------------------
Resolution: Information Provided
Fix Version/s: n/a
For help on Cloudera's distribution of Apache Kudu, please direct questions to
Cloudera forums.
At first startup, the masters write the list of masters in --master_addresses
to disk as part of their consensus configuration. On subsequent startups, the
master list in --master_addresses must agree with the configuration that was
written to disk. The error message you see indicates that those two things do
not agree.
For instructions on removing a master, see
https://kudu.apache.org/docs/administration.html#_removing_kudu_masters_from_a_multi_master_deployment.
> cloudera manager can not add kudu master role
> ---------------------------------------------
>
> Key: KUDU-2650
> URL: https://issues.apache.org/jira/browse/KUDU-2650
> Project: Kudu
> Issue Type: Bug
> Reporter: qinzl_1
> Priority: Major
> Fix For: n/a
>
>
> when i add kucu master role in cloudera manager ,can not start kudu master
> role
> Unable to init master catalog manager: Invalid argument: Unable to initialize
> catalog manager: Failed to initialize sys tables async: on-disk master list
> (serverA1:7051, serverA2:7051, serverA3:7051, shyt-dz-12-bigdata-200-23:7051)
> and provided master list (serverA1:7051, serverA2:7051, serverA3:7051)
> differ. Their symmetric difference is: shyt-dz-12-bigdata-200-23:7051
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
