Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Errors gathering consensus info for Tablet Server -Kudu 1.4.0-

avatar
Master Collaborator

Hello,

In the master of Kudu cluster, when I run the bellow command :

kudu cluster ksck 38.95.234.26


I has this messages

Connected to the Master
WARNING: Errors gathering consensus info for Tablet Server 2dde98b3e6984f858be32c53g73e6177 (nod1.emd:7050): Remote error: could not fetch all consensus info: Not authorized: unauthorized access to method: GetConsensusState
WARNING: Errors gathering consensus info for Tablet Server 267e129e783446e0ba8ed5cea6c57dec (nod9.hdm1.emd:7050): Remote error: could not fetch all consensus info: Not authorized: unauthorized access to method: GetConsensusState
WARNING: Errors gathering consensus info for Tablet Server 6702cbbe311d4fce93167eam77bc9365 (nod10.hdm1.emd:7050): Remote error: could not fetch all consensus info: Not authorized: unauthorized access to method: GetConsensusState
WARNING: Errors gathering consensus info for Tablet Server 18590d0f0b134dccad08714f6md15e23 (nod8.hdm1.emd:7050): Remote error: could not fetch all consensus info: Not authorized: unauthorized access to method: GetConsensusState
WARNING: Errors gathering consensus info for Tablet Server ab8ca29738c5412c80ed2daj8a6e6499 (nod7.hdm1.emd:7050): Remote error: could not fetch all consensus info: Not authorized: unauthorized access to method: GetConsensusState
Fetched info from all 5 Tablet Servers
Table impala::kudu_test.test_2p is HEALTHY (2 tablet(s) checked)

The metadata for 1 table(s) is HEALTHY
OK



Any idea please!
Thanks in advance.

1 ACCEPTED SOLUTION

avatar
Expert Contributor

You need to run ksck as the Kudu superuser in order to get the full functionality, this is defined by "--superuser_acl" and it defaults to the user that runs Kudu which is normally "kudu".

View solution in original post

1 REPLY 1

avatar
Expert Contributor

You need to run ksck as the Kudu superuser in order to get the full functionality, this is defined by "--superuser_acl" and it defaults to the user that runs Kudu which is normally "kudu".