[
https://issues.apache.org/jira/browse/IMPALA-1760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615029#comment-16615029
]
ASF subversion and git services commented on IMPALA-1760:
---------------------------------------------------------
Commit 16a04ce81b71462a62858196ad09f4d59bd8489a in impala's branch
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=16a04ce ]
Revert "IMPALA-1760: Implement shutdown command"
This reverts commit fda44aed9d4df818e95dc1b7d02ac080cdff1102.
A couple of the tests broken on S3 and erasure coding. Reverting
to unblock testing until we can come up with a proper fix.
Change-Id: Icef47b3aa67bc056c40592d47e93c4ebc57be98c
Reviewed-on: http://gerrit.cloudera.org:8080/11435
Tested-by: Impala Public Jenkins <[email protected]>
Reviewed-by: Tim Armstrong <[email protected]>
> Add decommissioning support / graceful shutdown / quiesce
> ---------------------------------------------------------
>
> Key: IMPALA-1760
> URL: https://issues.apache.org/jira/browse/IMPALA-1760
> Project: IMPALA
> Issue Type: New Feature
> Components: Distributed Exec
> Affects Versions: Impala 2.1.1
> Reporter: Henry Robinson
> Assignee: Tim Armstrong
> Priority: Critical
> Labels: resource-management, scalability, scheduler, usability
>
> In larger clusters, node maintenance is a frequent occurrence. There's no way
> currently to stop an Impala node without failing running queries, without
> draining queries across the whole cluster first. We should fix that.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
