Todd Lipcon created KUDU-1392:
---------------------------------
Summary: Remote bootstrapping a replica to an unexpected node does
not cause it to get deleted
Key: KUDU-1392
URL: https://issues.apache.org/jira/browse/KUDU-1392
Project: Kudu
Issue Type: Bug
Components: tserver
Affects Versions: 0.8.0
Reporter: Todd Lipcon
Priority: Minor
I hacked together a little CLI tool to trigger a remote bootstrap of a new
replica of an existing tablet. The new replica was not part of the consensus
configuration. When the bootstrap finished, the tablet started up and then
started logging lines like this once every couple seconds:
W0405 10:51:08.138592 20088 raft_consensus.cc:434] T
141e7fd5de494dc9a9f018254075020f P 2fb5cdac22b0418bb2df456906e42eb4 [term 27
NON_PARTICIPANT]: Failed to trigger leader election: Illegal state: Not
starting election: Node is currently a non-participant in the raft config:
opid_index: -1 local: false peers { permanent_uuid:
"09d6bf7a02124145b43f43cb7a667b3d" member_type: VOTER last_known_addr { host:
"vd0336.halxg.cloudera.com" port: 7050 } } peers { permanent_uuid:
"c9633273962a4521a32d5e177a118a84" member_type: VOTER last_known_addr { host:
"vd0334.halxg.cloudera.com" port: 7050 } } peers { permanent_uuid:
"3c305734ab9d4e0ebfbd0def74841a5d" member_type: VOTER last_known_addr { host:
"vd0240.halxg.cloudera.com" port: 7050 } }
I am surprised that it didn't report the tablet to the master and get a
deletion request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
