[
https://issues.apache.org/jira/browse/KUDU-687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436081#comment-15436081
]
Todd Lipcon commented on KUDU-687:
----------------------------------
I do think that's a bad experience, since admins may want to run ksck (in the
non-checksum mode at least) as part of an alerting system once every few
minutes.
Would be nice to see which functionality would have to be exposed. I'm hesitant
to increase the surface area of the public client that much since those APIs
are expensive to maintain (and a hassle to build, given pimpling, etc).
Exposing some of the utility code like 'SyncLeaderMasterRPC" seems easier to
stomach to me.
> 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)
