hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chen Liang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HDFS-12256) Ozone : handle inactive containers on DataNode side
Date Thu, 03 Aug 2017 17:45:00 GMT
Chen Liang created HDFS-12256:

             Summary: Ozone : handle inactive containers on DataNode side
                 Key: HDFS-12256
                 URL: https://issues.apache.org/jira/browse/HDFS-12256
             Project: Hadoop HDFS
          Issue Type: Bug
            Reporter: Chen Liang

When a container gets created, corresponding metadata gets added to {{ContainerManagerImpl#containerMap}}.
What {{containerMap}} stores is a containerName to {{ContainerStatus}} instance map. When
datanode starts, it also loads this map from disk file metadata. As long as the containerName
is found in this map, it is considered an existing container.

An issue we saw was that, occasionally, when the container creation on datanode fails, the
metadata of the failed container may still get added to {{containerMap}}, with active flag
set to false. But currently such containers are not being handled, containers with active=false
are just treated as normal containers. Then when someone tries to write to this container,
fails can happen.

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