hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nanda kumar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDDS-1652) HddsDispatcher should not shutdown volumeSet
Date Thu, 06 Jun 2019 18:19:01 GMT

    [ https://issues.apache.org/jira/browse/HDDS-1652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16857969#comment-16857969

Nanda kumar commented on HDDS-1652:

Thanks [~xyao] for the contribution. Committed this to trunk.

> HddsDispatcher should not shutdown volumeSet
> --------------------------------------------
>                 Key: HDDS-1652
>                 URL: https://issues.apache.org/jira/browse/HDDS-1652
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaoyu Yao
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 40m
>  Remaining Estimate: 0h
> Currently both OzoneContainer#stop() and HddsDispatcher#stop() both invoke volumeSet.shutdown()
explicitly to shutdown the same volume set.
> In addition, OzoneContainer#stop() will invoke HddsDispatcher#stop(). Since the volume
set object is created by OzoneContainer object, it should be the responsibility of OzoneContainer
to shutdown. This ticket is opened to remove the volumeSet.shutdown() from HddsDispatcher#stop(). 
> There are benchmark tools relies on HddsDispatcher#stop() to shutdown volumeSet object,
that we could fix with explict volumeSet#shutdown call. 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message