[Kudu] Master consensus error

[#1]

Hi

When I run kudu cluster ksck , return this error: Corruption: master consensus error: there are master consensus conflicts

All Tables in this Cluster Kudu is ok (Tablet Server), but the problem is in Kudu Master.

Follow the Master Sumary:

UUID | Address | Status
----------------------------------+-----------------------------+---------
42e0db81612f46a4bb5fee541b1316eb | node02 | HEALTHY
7b6a3355b027464c98fe5f77c7548350 | node04 | HEALTHY
83e343ec25aa48e2b22f0de244e42a6d | node03 | HEALTHY

All reported replicas are:
A = 42e0db81612f46a4bb5fee541b1316eb
B = 83e343ec25aa48e2b22f0de244e42a6d
C = 7b6a3355b027464c98fe5f77c7548350
The consensus matrix is:
Config source | Replicas | Current term | Config index | Committed?
---------------+--------------+--------------+--------------+------------
A | A B C | 218 | -1 | Yes
B | A B* C | 218 | -1 | Yes
C | A B* C | 218 | -1 | Yes


The problem is in Master Node 03 (B)?

[#2]

@prfbessa Welcome to the Cloudera Community!

To help you get the best possible solution, I have tagged our Kudu experts @jromero @ChrisGe  who may be able to assist you further.

Please keep us updated on your post, and we hope you find a satisfactory solution to your query.

[#3]

The problem is from Master A (node02) as you can see A thinks there is no leader for this election even their election cycle is same (218). suggest you to check the Master log on A (node02) host to understand why A failed to elect a leader just like other nodes (B and C think that B is the leader)

The consensus matrix is:
Config source | Replicas | Current term | Config index | Committed?
---------------+--------------+--------------+--------------+------------
A | A B C | 218 | -1 | Yes
B | A B* C | 218 | -1 | Yes
C | A B* C | 218 | -1 | Yes

[#4]

@prfbessa Has the reply helped resolve your issue? If so, please mark the appropriate reply as the solution, as it will make it easier for others to find the answer in the future. Thanks.