You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Grant Henke (Jira)" <ji...@apache.org> on 2020/06/03 02:53:00 UTC
[jira] [Updated] (KUDU-2436) Add WRONG_SERVER_UUID for master
server matrix
[ https://issues.apache.org/jira/browse/KUDU-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Grant Henke updated KUDU-2436:
------------------------------
Component/s: test
> Add WRONG_SERVER_UUID for master server matrix
> ----------------------------------------------
>
> Key: KUDU-2436
> URL: https://issues.apache.org/jira/browse/KUDU-2436
> Project: Kudu
> Issue Type: Improvement
> Components: test
> Reporter: Attila Bukor
> Priority: Minor
>
> KUDU-2364 and KUDU-2426 added a WRONG_SERVER_UUID status for tablet servers where the UUID doesn't match the expected one (i.e a new tablet server was created on an existing bind address). This should be added for masters as well.
> This is trickier for masters as the tablet server's UUIDs are known ahead of time from a central authority (leader masters). We do not have authoritative uuids for the masters, just the addresses from the command line. The test that comes to mind is that if a leader master expected UUID A but the master reports UUID B, it's an imposter. We can't do that check in FetchInfo. We also can't do it if there's no leader master.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)