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 2020/06/03 19:01:00 UTC

[jira] [Resolved] (KUDU-3011) Support for smooth maintenance window

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

Andrew Wong resolved KUDU-3011.
-------------------------------
    Fix Version/s: 1.12.0
       Resolution: Fixed

1.11 introduced a tserver maintenance state to prevent re-replication, and 1.12 introduced tserver quiescing to move new workloads away from tservers while allowing existing workloads to finish.

> Support for smooth maintenance window
> -------------------------------------
>
>                 Key: KUDU-3011
>                 URL: https://issues.apache.org/jira/browse/KUDU-3011
>             Project: Kudu
>          Issue Type: New Feature
>            Reporter: LiFu He
>            Assignee: Andrew Wong
>            Priority: Major
>             Fix For: 1.12.0
>
>
> A scan corresponding to a tablet failure causes the entire SQL to fail on the common query engines, such as Impala. Though we have the fault-tolerant feature by "SetFaultTolerant()", Impala doesn't use it right now since that will make lower throughput. Thus, lots of SQL that are running will fail when we shutdown/reboot/upgrade the tserver. That can be scary.
> Maybe we can do some improvement in this area, for example, the tablets are not allowed to be scanned after the tserver is in maintenance mode (KUDU-2069). And for the LEADER_ONLY mode scanning, the leader role needs to be shifted from the maintenance tserver. Then we can shutdown the tserver smoothly after all the existing SQL are completed.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)