Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
0.22.0
-
None
-
None
-
Reviewed
Description
Given that 0.13 is incredibly old at this point, I think the likelihood of anyone trying to start an 0.20+ namenode on an 0.13 directly layout is essentially nil. The intentionally-corrupt "${dfs.name.dir}/image/" directory just serves to confuse new users at this point, so I propose removing it.
If no one objects, I'll submit a patch. If there are objections, I propose at least adding a README explaining its purpose (same text as in the corrupt fsimage file)