[
https://issues.apache.org/jira/browse/DRILL-6010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16280452#comment-16280452
]
Arina Ielchiieva commented on DRILL-6010:
-----------------------------------------
I saw this on test cluster. Test cluster runs functional / advanced tests.
Cluster has 4 nodes. Nodes are restarted using drillbits.sh script in order to
run tests on clear env. All nodes are restarted at the same time using
{{clush}} (example: {{clush -a /drill/bin/drillbit.sh restart}}). I ran tests
on master so grace period was set 0 (the current default).
{quote}
Did you see it running even after 120 sec ?
{quote}
Yes, it did. It might be the case that Drillbit was restarted (stop + start)
and some how drillbit status was not updated. Drillbit status remained in
quiescent, though drillbit was running and it mode supposed to be online. Maybe
Zk missed status update.
> Working drillbit showing as in QUIESCENT state
> ----------------------------------------------
>
> Key: DRILL-6010
> URL: https://issues.apache.org/jira/browse/DRILL-6010
> Project: Apache Drill
> Issue Type: Bug
> Reporter: Arina Ielchiieva
> Attachments: online_vs_quiescent.JPG
>
>
> After DRILL-4286 once I got a situation that after running all functional
> tests three drillbits were in ONLINE state, another one in QUIESCENT. Though
> from the one in quiescent state I could run queries and so it was online.
> drillbit.sh stop could not shutdown it and had to do kill -9 of the process
> (online_vs_quiescent.JPG).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
