Add code to detect valid length of an edits file
Key: HDFS-1792
URL: https://issues.apache.org/jira/browse/HDFS-1792
Project: Hadoop HDFS
Issue Type: Sub-task
Reporter: Todd Lipcon
I've created this branch "HDFS-1073" as discussed. In this branch there's a
new CHANGES.HDFS-1073.txt file -- please add entries into this file rather
than CHANGES.txt if you commit stuff to the branch. This will simplify our
merges later on, I think. We'll transfer the changes back into CHANGES.tx
[
https://issues.apache.org/jira/browse/HDFS-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon resolved HDFS-1521.
---
Resolution: Fixed
Committed to the HDFS-1073 branch. We will address the BackupNode issues
mentioned
See https://hudson.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/575/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2792 lines...]
[junit] Running org.apach
+1
On Mon, Mar 28, 2011 at 9:39 PM, Konstantin Shvachko
wrote:
> HADOOP-6949 introduced a very important optimization to the RPC layer. Based
> on the benchmarks presented in HDFS-1583 this provides an order of magnitude
> improvement of current RPC implementation.
> RPC is a common component of
This is a very effective optimization, +1 on pulling it to 0.22.
-dhruba
On Mon, Mar 28, 2011 at 9:39 PM, Konstantin Shvachko
wrote:
> HADOOP-6949 introduced a very important optimization to the RPC layer.
> Based
> on the benchmarks presented in HDFS-1583 this provides an order of
> magnitude
HADOOP-6949 introduced a very important optimization to the RPC layer. Based
on the benchmarks presented in HDFS-1583 this provides an order of magnitude
improvement of current RPC implementation.
RPC is a common component of Hadoop projects. Many of them should benefit
from this change. But since
+1 for creating a branch.
Agree with Jakob this should not mean less intensive reviewing.
--Konstantin
On Mon, Mar 28, 2011 at 4:39 PM, Jakob Homan wrote:
> Doing this work on a branch makes sense. +1.
>
> However, the patches that have been committed so far required
> extensive review and revi
See https://hudson.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/574/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2791 lines...]
[junit] Running org.apach
See https://hudson.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/573/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 2791 lines...]
[junit] Running org.apach
See https://hudson.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/572/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 1092 lines...]
[copy] Copying 1 file to
Doing this work on a branch makes sense. +1.
However, the patches that have been committed so far required
extensive review and revision, and in one case, an addendum patch.
Additionally, the patches in related JIRAs such as HDFS-1557 and
HDFS-1572 have required multiple revisions and corrections
+1. I think this will be very helpful in moving the design forward quickly.
-dhruba
On Mon, Mar 28, 2011 at 1:14 PM, Todd Lipcon wrote:
> Hi all,
>
> I discussed this with a couple folks over the weekend who are involved in
> the project, but wanted to let the dev community at large know:
>
>
Hi all,
I discussed this with a couple folks over the weekend who are involved in
the project, but wanted to let the dev community at large know:
I'm planning on creating a new SVN branch for HDFS-1073 and its subtasks.
For those not aware, HDFS-1073 is a rethinking of how the NN, 2NN, and
Backup
See https://hudson.apache.org/hudson/job/Hadoop-Hdfs-trunk/620/
###
## LAST 60 LINES OF THE CONSOLE
###
[...truncated 690185 lines...]
[junit] at java.lang.Threa
15 matches
Mail list logo
