[ 
https://issues.apache.org/jira/browse/KUDU-1578?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235089#comment-16235089
 ] 

Todd Lipcon commented on KUDU-1578:
-----------------------------------

I put up a patch at http://gerrit.cloudera.org:8080/8451 which partially 
addresses this.

In particular I didn't go through the complexity of trying to be "partially up" 
while NTP is down. Rather, I changed the clock to ride over brief periods of 
NTP synchronization loss, which logging errors to the log. Assuming typical 
configurations this should allow Kudu to stay up even if NTP goes out for tens 
of minutes.

> 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
>          Components: tserver
>            Reporter: zhangsong
>            Assignee: Todd Lipcon
>            Priority: Major
>
> 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.4.14#64029)

Reply via email to