[
https://issues.apache.org/jira/browse/DRILL-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143266#comment-16143266
]
Venkata Jyothsna Donapati commented on DRILL-4286:
--------------------------------------------------
Thank you so much for you feedback @weijietong. Adding to Paul's answer,
"drillbit.sh stop" will issue a SIGKILL to shutdown the drillbit immediately.
Although we don't have an equivalent for that in the WebUI or through the
RestAPI call if that is all we need we can add that functionality but we assume
that if the user wants to shutdown the drillbit immediately they can always
kill the process. We had a discussion with John Omernik about having two
implementations of shutting down the drillbit one being graceful shutdown and
the other being immediate shutdown and this is what he thinks "If a user wants
to bring down a drillbit, Drill is not stopping them from triggering a
SIGKILL". With that being said, I don't think adding a force shutdown option in
both WebUI or in RestAPI call is a huge change. So I can add that as well.
Also, graceful shutdown follows lame duck analogy since the drillbit that is
shutting down advertises that its state (QUIESCENT) in Zookeeper, but there
might be a delay on Zookeeper end in updating state information to other
drillbits. That is the reason behind having graceperiod. Once other drillbits
are updated by Zookeeper, they don't plan any new queries on the drillbit that
is shutting down. And the typical use cases we are trying to solve are shutting
down drillbit due to maintenance activities or to optimize hardware utilization
by bringing down drillbits when there is not much load on the cluster. In both
the cases, a user can wait for quite some amount of time for the running
queries to complete and drillbit to shutdown. I'd like to hear any suggestions
or comments.
> Have an ability to put server in quiescent mode of operation
> ------------------------------------------------------------
>
> Key: DRILL-4286
> URL: https://issues.apache.org/jira/browse/DRILL-4286
> Project: Apache Drill
> Issue Type: New Feature
> Components: Execution - Flow
> Reporter: Victoria Markman
> Assignee: Venkata Jyothsna Donapati
>
> I think drill will benefit from mode of operation that is called "quiescent"
> in some databases.
> From IBM Informix server documentation:
> {code}
> Change gracefully from online to quiescent mode
> Take the database server gracefully from online mode to quiescent mode to
> restrict access to the database server without interrupting current
> processing. After you perform this task, the database server sets a flag that
> prevents new sessions from gaining access to the database server. The current
> sessions are allowed to finish processing. After you initiate the mode
> change, it cannot be canceled. During the mode change from online to
> quiescent, the database server is considered to be in Shutdown mode.
> {code}
> This is different from shutdown, when processes are terminated.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
