hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weiwei Yang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-11844) Ozone: Recover SCM state when SCM is restarted
Date Mon, 22 May 2017 02:15:05 GMT

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

Weiwei Yang updated HDFS-11844:
-------------------------------
    Description: 
SCM losses its state once being restarted. This issue can be found by a simple test with following
steps

# Start NN, DN, SCM
# Create several containers via SCM CLI
# Restart DN
# Get existing container info via SCM CLI, this step will fail with container doesn't exist
error.

{{ContainerManagerImpl}} maintains a cache of container mapping {{containerMap}}, if DN is
restarted, this information is lost. We need a way to restore the state from DB in a background
thread.

  was:
SCM losses its state once being restarted. This issue can be found by a simple test with following
steps

# Start NN, DN, SCM
# Create several containers via SCM CLI
# Restart SCM
# Get existing container state via SCM CLI, this step will fail with container doesn't exist
error.

{{ContainerManagerImpl}} maintains a cache of container mapping {{containerMap}}, if SCM is
restarted, this information is lost. We need a way to restore the state from DB in a background
thread.


> Ozone: Recover SCM state when SCM is restarted
> ----------------------------------------------
>
>                 Key: HDFS-11844
>                 URL: https://issues.apache.org/jira/browse/HDFS-11844
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone, scm
>            Reporter: Weiwei Yang
>            Assignee: Weiwei Yang
>
> SCM losses its state once being restarted. This issue can be found by a simple test with
following steps
> # Start NN, DN, SCM
> # Create several containers via SCM CLI
> # Restart DN
> # Get existing container info via SCM CLI, this step will fail with container doesn't
exist error.
> {{ContainerManagerImpl}} maintains a cache of container mapping {{containerMap}}, if
DN is restarted, this information is lost. We need a way to restore the state from DB in a
background thread.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
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