hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nanda kumar (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (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:all-tabpanel
]

Nanda kumar resolved HDDS-1652.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 0.4.1
                   0.5.0

> 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
>             Fix For: 0.5.0, 0.4.1
>
>          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
(v7.6.3#76005)

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


Mime
View raw message