You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Andrew Wong (JIRA)" <ji...@apache.org> on 2017/09/05 23:30:01 UTC

[jira] [Assigned] (KUDU-2136) Add a "crashed"/"failed" mode to tablets

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

Andrew Wong reassigned KUDU-2136:
---------------------------------

    Assignee: Andrew Wong

> Add a "crashed"/"failed" mode to tablets
> ----------------------------------------
>
>                 Key: KUDU-2136
>                 URL: https://issues.apache.org/jira/browse/KUDU-2136
>             Project: Kudu
>          Issue Type: Improvement
>            Reporter: Andrew Wong
>            Assignee: Andrew Wong
>
> There are a number of errors that currently crash Kudu tablet servers (e.g. disk failure). In the push to keep tablet servers alive in spite of these failures, the affected tablets should no longer service any type of request. Writes should not proceed, scans should be bounced to another tablet server, flushes and compactions should exit early, etc. The tablet should act as though it were deleted, with the exception that its data is not yet deleted, for the sake of durability in case it is the last remaining replica.
> This mode may be need to be entered from a myriad of tablet operations: from corruptions in reading a cfile, from disk failures when flushing to disk (while locks may be held), etc.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)