You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Deneche A. Hakim (JIRA)" <ji...@apache.org> on 2015/05/11 07:57:59 UTC

[jira] [Commented] (DRILL-3022) Ensure sequential shutdown of Drillbits

    [ https://issues.apache.org/jira/browse/DRILL-3022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14537618#comment-14537618 ] 

Deneche A. Hakim commented on DRILL-3022:
-----------------------------------------

making DrillMetrics.resetMetrics() synchronized "may" actually solve this issue.

> Ensure sequential shutdown of Drillbits
> ---------------------------------------
>
>                 Key: DRILL-3022
>                 URL: https://issues.apache.org/jira/browse/DRILL-3022
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Tools, Build & Test
>    Affects Versions: 0.9.0
>            Reporter: Hanifi Gunes
>            Assignee: Hanifi Gunes
>
> When we run multiple bits within a JVM, shutting down bits might cause a race condition due to concurrent access to static MetricRegistry instance. This causes ugly error messages show up in the terminal. The proposal is to serialize shutdown of each bit via use of a global lock.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)