HDFS-5942. Merging change r1569124 from trunk to branch-2.
git-svn-id: https://svn.apache.org/repos/asf/hadoop/common/branches/branch-2@1569133 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
3452748b21
commit
3151800acd
|
@ -166,6 +166,8 @@ Release 2.4.0 - UNRELEASED
|
||||||
HDFS-5759. Web UI does not show up during the period of loading FSImage.
|
HDFS-5759. Web UI does not show up during the period of loading FSImage.
|
||||||
(Haohui Mai via Arpit Agarwal)
|
(Haohui Mai via Arpit Agarwal)
|
||||||
|
|
||||||
|
HDFS-5942. Fix javadoc in OfflineImageViewer. (Akira Ajisaka via cnauroth)
|
||||||
|
|
||||||
BREAKDOWN OF HDFS-5698 SUBTASKS AND RELATED JIRAS
|
BREAKDOWN OF HDFS-5698 SUBTASKS AND RELATED JIRAS
|
||||||
|
|
||||||
HDFS-5717. Save FSImage header in protobuf. (Haohui Mai via jing9)
|
HDFS-5717. Save FSImage header in protobuf. (Haohui Mai via jing9)
|
||||||
|
|
|
@ -51,28 +51,16 @@ import com.google.common.collect.Maps;
|
||||||
import com.google.common.io.LimitInputStream;
|
import com.google.common.io.LimitInputStream;
|
||||||
|
|
||||||
/**
|
/**
|
||||||
* This is the tool for analyzing file sizes in the namespace image. In order to
|
* LsrPBImage displays the blocks of the namespace in a format very similar
|
||||||
* run the tool one should define a range of integers <tt>[0, maxSize]</tt> by
|
* to the output of ls/lsr. Entries are marked as directories or not,
|
||||||
* specifying <tt>maxSize</tt> and a <tt>step</tt>. The range of integers is
|
* permissions listed, replication, username and groupname, along with size,
|
||||||
* divided into segments of size <tt>step</tt>:
|
* modification date and full path.
|
||||||
* <tt>[0, s<sub>1</sub>, ..., s<sub>n-1</sub>, maxSize]</tt>, and the visitor
|
|
||||||
* calculates how many files in the system fall into each segment
|
|
||||||
* <tt>[s<sub>i-1</sub>, s<sub>i</sub>)</tt>. Note that files larger than
|
|
||||||
* <tt>maxSize</tt> always fall into the very last segment.
|
|
||||||
*
|
|
||||||
* <h3>Input.</h3>
|
|
||||||
* <ul>
|
|
||||||
* <li><tt>filename</tt> specifies the location of the image file;</li>
|
|
||||||
* <li><tt>maxSize</tt> determines the range <tt>[0, maxSize]</tt> of files
|
|
||||||
* sizes considered by the visitor;</li>
|
|
||||||
* <li><tt>step</tt> the range is divided into segments of size step.</li>
|
|
||||||
* </ul>
|
|
||||||
*
|
|
||||||
* <h3>Output.</h3> The output file is formatted as a tab separated two column
|
|
||||||
* table: Size and NumFiles. Where Size represents the start of the segment, and
|
|
||||||
* numFiles is the number of files form the image which size falls in this
|
|
||||||
* segment.
|
|
||||||
*
|
*
|
||||||
|
* Note: A significant difference between the output of the lsr command
|
||||||
|
* and this image visitor is that this class cannot sort the file entries;
|
||||||
|
* they are listed in the order they are stored within the fsimage file.
|
||||||
|
* Therefore, the output of this class cannot be directly compared to the
|
||||||
|
* output of the lsr command.
|
||||||
*/
|
*/
|
||||||
final class LsrPBImage {
|
final class LsrPBImage {
|
||||||
private final Configuration conf;
|
private final Configuration conf;
|
||||||
|
|
|
@ -55,28 +55,8 @@ import com.google.common.collect.Lists;
|
||||||
import com.google.common.io.LimitInputStream;
|
import com.google.common.io.LimitInputStream;
|
||||||
|
|
||||||
/**
|
/**
|
||||||
* This is the tool for analyzing file sizes in the namespace image. In order to
|
* PBImageXmlWriter walks over an fsimage structure and writes out
|
||||||
* run the tool one should define a range of integers <tt>[0, maxSize]</tt> by
|
* an equivalent XML document that contains the fsimage's components.
|
||||||
* specifying <tt>maxSize</tt> and a <tt>step</tt>. The range of integers is
|
|
||||||
* divided into segments of size <tt>step</tt>:
|
|
||||||
* <tt>[0, s<sub>1</sub>, ..., s<sub>n-1</sub>, maxSize]</tt>, and the visitor
|
|
||||||
* calculates how many files in the system fall into each segment
|
|
||||||
* <tt>[s<sub>i-1</sub>, s<sub>i</sub>)</tt>. Note that files larger than
|
|
||||||
* <tt>maxSize</tt> always fall into the very last segment.
|
|
||||||
*
|
|
||||||
* <h3>Input.</h3>
|
|
||||||
* <ul>
|
|
||||||
* <li><tt>filename</tt> specifies the location of the image file;</li>
|
|
||||||
* <li><tt>maxSize</tt> determines the range <tt>[0, maxSize]</tt> of files
|
|
||||||
* sizes considered by the visitor;</li>
|
|
||||||
* <li><tt>step</tt> the range is divided into segments of size step.</li>
|
|
||||||
* </ul>
|
|
||||||
*
|
|
||||||
* <h3>Output.</h3> The output file is formatted as a tab separated two column
|
|
||||||
* table: Size and NumFiles. Where Size represents the start of the segment, and
|
|
||||||
* numFiles is the number of files form the image which size falls in this
|
|
||||||
* segment.
|
|
||||||
*
|
|
||||||
*/
|
*/
|
||||||
@InterfaceAudience.Private
|
@InterfaceAudience.Private
|
||||||
public final class PBImageXmlWriter {
|
public final class PBImageXmlWriter {
|
||||||
|
|
Loading…
Reference in New Issue