[
https://issues.apache.org/jira/browse/KUDU-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436049#comment-15436049
]
Adar Dembo commented on KUDU-687:
---------------------------------
bq. is this on your radar for 1.0?
Sort of. I think we can get away with deferring this until after 1.0; I think
ksck would work as long as the single address is the leader master. That's
certainly not ideal in that the admin would have to manually "chase" the
leader, but at least it would work.
But, if you think that's too poor an experience, we can certainly fix it in
1.0. I think the easiest way forward is to add a few more "informational"
functions to the C++ client, then build ksck around the client. That seems far
more palatable to me than making pieces of the client available for ksck.
> ksck should work against multi-master
> -------------------------------------
>
> Key: KUDU-687
> URL: https://issues.apache.org/jira/browse/KUDU-687
> Project: Kudu
> Issue Type: Bug
> Components: ops-tooling
> Affects Versions: Public beta
> Reporter: Todd Lipcon
>
> ksck currently creates an rpc proxy directly to the master, and is only
> configured by a single address. This doesn't work in a multi-master cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
