You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2016/05/17 06:55:12 UTC

[jira] [Updated] (KUDU-1372) Verify cluster-wide master and tserver connectivity

     [ https://issues.apache.org/jira/browse/KUDU-1372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Todd Lipcon updated KUDU-1372:
------------------------------
    Issue Type: Improvement  (was: Bug)

> Verify cluster-wide master and tserver connectivity
> ---------------------------------------------------
>
>                 Key: KUDU-1372
>                 URL: https://issues.apache.org/jira/browse/KUDU-1372
>             Project: Kudu
>          Issue Type: Improvement
>          Components: ops-tooling, supportability
>    Affects Versions: 0.7.1
>            Reporter: Adar Dembo
>
> Kudu clusters need full-duplex connectivity inside of Raft configurations (masters or tservers), as well as between masters and tservers themselves. No doubt users will run into all sorts of issues with only partially configured firewalls.
> Let's do what we can to surface connectivity failures, be they inside of a Raft configuration or between a particular master and tserver. Metrics, log output, and web UI dashboards are all good places to surface these failures.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)