Browse Source

HDFS-9158. [OEV-Doc] : Document does not mention about '-f' and '-r' options (Contributed by nijel)

Vinayakumar B 9 years ago
parent
commit
b925cf1006

+ 3 - 0
hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt

@@ -1492,6 +1492,9 @@ Release 2.8.0 - UNRELEASED
     HDFS-9151. Mover should print the exit status/reason on console like
     HDFS-9151. Mover should print the exit status/reason on console like
     balancer tool. (Surendra singh lilhore via vinayakumarb)
     balancer tool. (Surendra singh lilhore via vinayakumarb)
 
 
+    HDFS-9154. [OEV-Doc] : Document does not mention about "-f" and "-r" options
+    (nijel via vinayakumarb)
+
 Release 2.7.2 - UNRELEASED
 Release 2.7.2 - UNRELEASED
 
 
   INCOMPATIBLE CHANGES
   INCOMPATIBLE CHANGES

+ 1 - 1
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/tools/offlineEditsViewer/OfflineEditsViewer.java

@@ -69,7 +69,7 @@ public class OfflineEditsViewer extends Configured implements Tool {
       "                       edits file)\n" +
       "                       edits file)\n" +
       "-h,--help              Display usage information and exit\n" +
       "-h,--help              Display usage information and exit\n" +
       "-f,--fix-txids         Renumber the transaction IDs in the input,\n" +
       "-f,--fix-txids         Renumber the transaction IDs in the input,\n" +
-      "                       so that there are no gaps or invalid " +
+      "                       so that there are no gaps or invalid\n" +
       "                       transaction IDs.\n" +
       "                       transaction IDs.\n" +
       "-r,--recover           When reading binary edit logs, use recovery \n" +
       "-r,--recover           When reading binary edit logs, use recovery \n" +
       "                       mode.  This will give you the chance to skip \n" +
       "                       mode.  This will give you the chance to skip \n" +

+ 2 - 0
hadoop-hdfs-project/hadoop-hdfs/src/site/markdown/HdfsEditsViewer.md

@@ -51,6 +51,8 @@ Usage
 | [`-o` ; `--outputFile`] *output file* | Specify the output filename, if the specified output processor generates one. If the specified file already exists, it is silently overwritten. Required. |
 | [`-o` ; `--outputFile`] *output file* | Specify the output filename, if the specified output processor generates one. If the specified file already exists, it is silently overwritten. Required. |
 | [`-p` ; `--processor`] *processor* | Specify the image processor to apply against the image file. Currently valid options are `binary`, `xml` (default) and `stats`. |
 | [`-p` ; `--processor`] *processor* | Specify the image processor to apply against the image file. Currently valid options are `binary`, `xml` (default) and `stats`. |
 | [`-v` ; `--verbose`] | Print the input and output filenames and pipe output of processor to console as well as specified file. On extremely large files, this may increase processing time by an order of magnitude. |
 | [`-v` ; `--verbose`] | Print the input and output filenames and pipe output of processor to console as well as specified file. On extremely large files, this may increase processing time by an order of magnitude. |
+| [`-f` ; `--fix-txids`] | Renumber the transaction IDs in the input, so that there are no gaps or invalid transaction IDs. |
+| [`-r` ; `--recover`] | When reading binary edit logs, use recovery mode. This will give you the chance to skip corrupt parts of the edit log. |
 | [`-h` ; `--help`] | Display the tool usage and help information and exit. |
 | [`-h` ; `--help`] | Display the tool usage and help information and exit. |
 
 
 Case study: Hadoop cluster recovery
 Case study: Hadoop cluster recovery