Hi Liou, It sounds like you might have first started the masters without specifying the --master_addresses setting, so they each initialized their own local storage separately with no knowledge of each other. That is to say, each master thinks it is its own cluster, and now is refusing to restart with a different configuration (it's not possible to "merge" clusters after initialization).
To recover the situation, I suggest 'rm -rf /var/lib/kudu/master/*' on all three machines before restarting the service with the new configuration. Of course, please note that this will remove all data from your Kudu cluster, if you have any data loaded. If you are instead trying to migrate from a 1-master cluster to 3-master cluster, you can find instructionns to do so in the docs. -Todd On Fri, Nov 17, 2017 at 1:36 AM, Dylan <dylan_li...@163.com> wrote: > Hi: > > I am installing kudu in distributed mode. I wanna 3 > masters(10,11,12) and 3 tservers. > > I configured the master.gflagfile and only added > --master_addresses option. > > > > File content: > > > > > > # Do not modify these two lines. If you wish to change these variables, > > # modify them in /etc/default/kudu-master. > > --fromenv=rpc_bind_addresses > > --fromenv=log_dir > > > > --fs_wal_dir=/var/lib/kudu/master > > --fs_data_dirs=/var/lib/kudu/master > > > > --master_addresses=10.15.213.10:7051,10.15.213.11:7051,10.15.213.12:7051 > > > > > > When I started the kudu-master service, it reported an error. > > `Check failed: _s.ok() Bad status: Invalid argument: Unable to initialize > catalog manager: Failed to initialize sys tables async: on-disk and > provided master lists are different: 10.15.213.10:7051 10.15.213.11:7051 > 10.15.213.12:7051 :0` > > > > It was the same on the other 2 master machine. > > > > I have no idea what’s going on. Am I misunderstanding this configure > option? > > > > > > > > Best wishes. > > > > Liou Fongcyuan > -- Todd Lipcon Software Engineer, Cloudera
