Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
1.11.0
-
None
-
None
Description
In a cluster with some sort of networking issue, it's conceivable for ksck to fail to reach some servers even though they're able to heartbeat to the masters (or if the servers were masters themselves, be reachable by the leader master).
It would be nice if ksck cross-referenced its own connectivity results with that of the masters and surfaced discrepancies in a useful way. This could help diagnose live networking issues.
Attachments
Issue Links
- relates to
-
KUDU-1372 Verify cluster-wide master and tserver connectivity
- Open