[
https://issues.apache.org/jira/browse/HDFS-11650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999182#comment-15999182
]
Chen Liang edited comment on HDFS-11650 at 5/15/17 7:03 PM:
------------------------------------------------------------
After some investigation, the direct cause of this is that when loading the
image files, the storage directory in the image file are not correctly
recognized. i.e. unexpectedly running into
{code}INFO common.Storage (DataStorage.java:loadStorageDirectory(275)) -
Storage directory with location [DISK]file:.../test/data/dfs/data/dn1_data0 is
not formatted for namespace -386152743. Formatting...{code}
while the normal execution (from trunk) does not have this error, instead, it
has
{code}INFO common.Storage (DataStorage.java:doUpgradePreFederation(780)) -
Upgrading storage directory .../test/data/dfs/data/data5.
old LV = -33; old CTime = 1306118715307.
new LV = -57; new CTime = 1494029187672{code}
Regarding the code, the difference happens at
{code}StorageState curState = sd.analyzeStorage(startOpt, this, true);{code}
in {{BlockPoolSliceStorage#loadStorageDirectory}}. In the error execution there
returned state is {{NOT_FORMATTED}} while in the normal execution it is
{{NORMAL}}.
was (Author: vagarychen):
After some investigation, the direct cause of this is that when loading the
image files, the storage directory in the image file are not correctly
recognized. i.e. unexpectedly running into
{code}INFO common.Storage (DataStorage.java:loadStorageDirectory(275)) -
Storage directory with location [DISK]file:.../test/data/dfs/data/dn1_data0 is
not formatted for namespace -386152743. Formatting...{code}
while the normal execution (from trunk) does not have this error, instead, it
has
{code}INFO common.Storage (DataStorage.java:doUpgradePreFederation(780)) -
Upgrading storage directory .../test/data/dfs/data/data5.
old LV = -33; old CTime = 1306118715307.
new LV = -57; new CTime = 1494029187672{code}
Regarding the code, the difference happens at
{code}StorageState curState = sd.analyzeStorage(startOpt, this, true);{code}
in {{BlockPoolSliceStorage#loadStorageDirectory}}. In the error execution there
returned state is {{NOT_FORMATTED}} while in the normal execution it is
{{NORMAL}}. For now, I suspect it is because HDFS-7240 is missing the changes
HDFS-8578 and HDFS-9654 as in trunk. If this turns out to be the case, we might
just want to disable this test for the time being.
> Ozone: fix the consistently timeout test testUpgradeFromRel22Image
> ------------------------------------------------------------------
>
> Key: HDFS-11650
> URL: https://issues.apache.org/jira/browse/HDFS-11650
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Chen Liang
> Assignee: Chen Liang
>
> Recently, the test TestDFSUpgradeFromImage.testUpgradeFromRel22Image has been
> consistently failing due to timeout. JIRAs that encountered this include (but
> not limited to) HDFS-11642, HDFS-11635, HDFS-11062 and HDFS-11618. While this
> test passes in trunk.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
