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 2017/03/06 20:38:33 UTC

[jira] [Updated] (KUDU-1578) kudu-tserver should refuse service or "freeze" instead of crash when NTP loses sync

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

Todd Lipcon updated KUDU-1578:
------------------------------
    Summary: kudu-tserver should refuse service or "freeze" instead of crash when NTP loses sync  (was: kudu-tserver should refuse service or "freeze" instead of crash)

> kudu-tserver should refuse service or "freeze" instead of crash when NTP loses sync
> -----------------------------------------------------------------------------------
>
>                 Key: KUDU-1578
>                 URL: https://issues.apache.org/jira/browse/KUDU-1578
>             Project: Kudu
>          Issue Type: Bug
>            Reporter: zhangsong
>
> Currently, kudu-tserver will crash when ntp is unsynchronized.
> However this behavior maybe not the right in large cluster ,when crash can lead to replicate which can be useless or harm to cluster availability.
> Instead, kudu-tserver should suspend it self like refusing to serve write , let the administrator decide what to do.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)