You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Jacques Nadeau (JIRA)" <ji...@apache.org> on 2014/12/29 00:31:19 UTC
[jira] [Updated] (DRILL-1431) Drillbit continue to report positive
status after hitting out of memory condition
[ https://issues.apache.org/jira/browse/DRILL-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jacques Nadeau updated DRILL-1431:
----------------------------------
Component/s: (was: Client - C++)
Execution - Flow
Fix Version/s: Future
Priority: Minor (was: Major)
Summary: Drillbit continue to report positive status after hitting out of memory condition (was: Zookeeper returns unhealthy drillbits)
> Drillbit continue to report positive status after hitting out of memory condition
> ---------------------------------------------------------------------------------
>
> Key: DRILL-1431
> URL: https://issues.apache.org/jira/browse/DRILL-1431
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Flow
> Reporter: Norris Lee
> Priority: Minor
> Fix For: Future
>
>
> Over time, a drillbit tends to hang. Eg. If a drillbit runs out of memory, the drillbit will still be in the list of drillbits returned by zookeeper. Since Drill Client randomly selects a drillbit from that list, the drillbit it connects to may be unhealthy. Drill Client should do a quick connection check to determine whether drillbit is actually healthy. If not, it should select another drillbit and test again until it has found a healthy drillbit.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)