hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6066) logGenerationStamp is not needed to reduce editlog size
Date Sat, 02 May 2015 05:02:11 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14524959#comment-14524959
] 

Hadoop QA commented on HDFS-6066:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:red}-1{color} | patch |   0m  0s | The patch command could not apply the patch during
dryrun. |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12633573/HDFS-6066-trunk.3.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / f1a152c |
| Console output | https://builds.apache.org/job/PreCommit-HDFS-Build/10670/console |


This message was automatically generated.

> logGenerationStamp is not needed to reduce editlog size
> -------------------------------------------------------
>
>                 Key: HDFS-6066
>                 URL: https://issues.apache.org/jira/browse/HDFS-6066
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>            Reporter: chenping
>            Priority: Minor
>         Attachments: HDFS-6066-trunk.1.patch, HDFS-6066-trunk.2.patch, HDFS-6066-trunk.3.patch
>
>
> almost every logGenerationStamp has a logAddBlock followed, so we can get the newest
gs from the logAddBlock operation indirectly.this will reduce the edit log size.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message