You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Will Berkeley (JIRA)" <ji...@apache.org> on 2018/05/01 21:29:00 UTC
[jira] [Assigned] (KUDU-2426) ksck reports WRONG_SERVER_UUID on any
RemoteError
[ https://issues.apache.org/jira/browse/KUDU-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Will Berkeley reassigned KUDU-2426:
-----------------------------------
Assignee: Will Berkeley
> ksck reports WRONG_SERVER_UUID on any RemoteError
> -------------------------------------------------
>
> Key: KUDU-2426
> URL: https://issues.apache.org/jira/browse/KUDU-2426
> Project: Kudu
> Issue Type: Bug
> Components: ops-tooling
> Affects Versions: 1.8.0
> Reporter: Andrew Wong
> Assignee: Will Berkeley
> Priority: Major
> Attachments: ksck_output.txt
>
>
> I ran ksck on a relatively recent 1.8.0-snapshot build of kudu and was met with the following:
>
> {{WARNING: Errors gathering consensus info for Tablet Server 70f7ee61ead54b1885d819f354eb3405 ([vc1316.halxg.cloudera.com|http://vc1316.halxg.cloudera.com/]:7050): Remote error: could not fetch all consensus info: Not authorized: unauthorized access to method: GetConsensusState}}
>
> This is somewhat expected if not running as the kudu user. What was unexpected was that all of the tservers reported WRONG_SERVER_UUID, even though the UUIDs were fine (the ksck report was otherwise healthy). Upon reviewing some ksck-related code, it seems we're taking all remote errors to mean WRONG_SERVER_UUID, which isn't always the case. I've attached a ksck output with the this issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)