[jira] [Created] (HDFS-2016) 1073: remove/archive unneeded/old storage files

1073: remove/archive unneeded/old storage files --- Key: HDFS-2016 URL: https://issues.apache.org/jira/browse/HDFS-2016 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Todd Lipcon

[jira] [Created] (HDFS-2015) Remove checkpointTxId from VERSION file

Remove checkpointTxId from VERSION file --- Key: HDFS-2015 URL: https://issues.apache.org/jira/browse/HDFS-2015 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Todd Lipcon Assig

[jira] [Created] (HDFS-2014) RPM packages broke bin/hdfs script

RPM packages broke bin/hdfs script -- Key: HDFS-2014 URL: https://issues.apache.org/jira/browse/HDFS-2014 Project: Hadoop HDFS Issue Type: Bug Components: scripts Affects Versions: 0.23.0

[jira] [Created] (HDFS-2013) Recurring failure of TestMissingBlocksAlert on branch-0.22

Recurring failure of TestMissingBlocksAlert on branch-0.22 -- Key: HDFS-2013 URL: https://issues.apache.org/jira/browse/HDFS-2013 Project: Hadoop HDFS Issue Type: Bug Componen

[jira] [Created] (HDFS-2012) Recurring failure of TestBalancer on branch-0.22

Recurring failure of TestBalancer on branch-0.22 Key: HDFS-2012 URL: https://issues.apache.org/jira/browse/HDFS-2012 Project: Hadoop HDFS Issue Type: Bug Components: balancer, test

[jira] [Created] (HDFS-2011) Removal and restoration of storage directories on checkpointing failure doesn't work properly

Removal and restoration of storage directories on checkpointing failure doesn't work properly - Key: HDFS-2011 URL: https://issues.apache.org/jira/browse/HDFS-2011

Re: Expectation during Rollback after a partially failed Upgrade .. Should DELTA be visible ?

Hi Sreehari, Which versions are you using for this test? In step 1 below, how does the upgrade fail? Can you provide specific steps to reproduce? Smells like a bug to me, if I understand the scenario correctly. -Todd On Mon, May 30, 2011 at 5:29 AM, Sreehari G wrote: > Hi all , > > What is

Expectation during Rollback after a partially failed Upgrade .. Should DELTA be visible ?

Hi all , What is the expectation in the following scenario : Namenode has 3 name dirs configured .. 1) Namenode upgrade starts - Upgrade fails after 1st directory is upgraded (2nd and 3rd dir is left unchanged ..) 2) Namenode starts 3) Namenode shutdown and rollbacked Are the new changes done

Hadoop-Hdfs-22-branch - Build # 58 - Still Failing

See https://builds.apache.org/hudson/job/Hadoop-Hdfs-22-branch/58/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 3040 lines...] compile-hdfs-test: [delete] D