[
https://issues.apache.org/jira/browse/KUDU-3011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17022539#comment-17022539
]
ASF subversion and git services commented on KUDU-3011:
-------------------------------------------------------
Commit 14cbaeea009d5787dbf1b830a7e62964dad7a53a in kudu's branch
refs/heads/master from Andrew Wong
[ https://gitbox.apache.org/repos/asf?p=kudu.git;h=14cbaee ]
KUDU-3011 p7: add tool to quiesce server
Adds the following commands:
$ kudu tserver quiesce start <tserver_addr>
- sets the server to start quiescing
- optionally, if --error_if_not_fully_quiesced is true, the server
will respond with the number of leaders and active scanners, and if
either are non-zero, the tool will return an error
- users can orchestrate this to wait for a fully quiesced server. An
example of this is shown in RollingRestartITest.
$ kudu tserver quiesce stop <tserver_addr>
- sets the server to not be quiescing
Tests:
- Added some tests to exercise the quiescing tool in the context of a
rolling restart alongside the maintenance mode tooling.
- Also added some basic testing for the quiescing tooling alone.
Change-Id: I89657808cc2b0afc4e1b37ce75937ab12e098d9c
Reviewed-on: http://gerrit.cloudera.org:8080/15091
Tested-by: Kudu Jenkins
Reviewed-by: Adar Dembo <[email protected]>
Reviewed-by: Alexey Serbin <[email protected]>
> 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
>
> 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)
