hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-12256) Ozone : handle inactive containers on DataNode
Date Wed, 06 Sep 2017 18:59:01 GMT

     [ https://issues.apache.org/jira/browse/HDFS-12256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anu Engineer updated HDFS-12256:
--------------------------------
    Labels: ozoneMerge  (was: )

> Ozone : handle inactive containers on DataNode
> ----------------------------------------------
>
>                 Key: HDFS-12256
>                 URL: https://issues.apache.org/jira/browse/HDFS-12256
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Chen Liang
>            Assignee: Lokesh Jain
>              Labels: ozoneMerge
>
> 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
(v6.4.14#64029)

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


Mime
View raw message