[jira] [Resolved] (HDFS-1885) Recurring failures in TestFileConcurrentReader for > 12 days

[ https://issues.apache.org/jira/browse/HDFS-1885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley resolved HDFS-1885. -- Resolution: Duplicate Duplicate of HDFS-1401 > Recurring failures in TestFileConcurrentReader for > 12

[jira] [Resolved] (HDFS-1679) TestFileConcurrentReader fails intermittently

[ https://issues.apache.org/jira/browse/HDFS-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley resolved HDFS-1679. -- Resolution: Duplicate > TestFileConcurrentReader fails intermittently >

[jira] [Resolved] (HDFS-1882) Recurring failures in TestDatanodeBlockScanner since HDFS-1052

[ https://issues.apache.org/jira/browse/HDFS-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins resolved HDFS-1882. --- Resolution: Fixed Assignee: Eli Collins I think I fixed this in the patch for HDFS-1850. See the

Hadoop-Hdfs-trunk-Commit - Build # 620 - Still Failing

See https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk-Commit/620/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 2858 lines...] [junit] Test org.apache.h

[jira] [Created] (HDFS-1886) Recurring failures in TestFileAppend4, TestLargeBlock, TestWriteConfigurationToDFS for > 12 days

Recurring failures in TestFileAppend4, TestLargeBlock, TestWriteConfigurationToDFS for > 12 days Key: HDFS-1886 URL: https://issues.apache.org/jira/browse/HDFS-1886

[jira] [Created] (HDFS-1885) Recurring failures in TestFileConcurrentReader

Recurring failures in TestFileConcurrentReader -- Key: HDFS-1885 URL: https://issues.apache.org/jira/browse/HDFS-1885 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Matt Foley

[jira] [Created] (HDFS-1884) Recurring failures in TestDFSStorageStateRecovery since HDFS-1052

Recurring failures in TestDFSStorageStateRecovery since HDFS-1052 - Key: HDFS-1884 URL: https://issues.apache.org/jira/browse/HDFS-1884 Project: Hadoop HDFS Issue Type: Sub-task

[jira] [Created] (HDFS-1883) Recurring failures in TestBackupNode since HDFS-1052

Recurring failures in TestBackupNode since HDFS-1052 Key: HDFS-1883 URL: https://issues.apache.org/jira/browse/HDFS-1883 Project: Hadoop HDFS Issue Type: Sub-task Reporter: Mat

[jira] [Created] (HDFS-1882) Recurring failures in TestDatanodeBlockScanner since HDFS-1052

Recurring failures in TestDatanodeBlockScanner since HDFS-1052 -- Key: HDFS-1882 URL: https://issues.apache.org/jira/browse/HDFS-1882 Project: Hadoop HDFS Issue Type: Sub-task

[jira] [Created] (HDFS-1881) After taking snapshot (upgrade) on Federation, the current directory of data node is emtpy.

After taking snapshot (upgrade) on Federation, the current directory of data node is emtpy. Key: HDFS-1881 URL: https://issues.apache.org/jira/browse/HDFS-1881

Re: HDFS-1839 - Is it okay to remove the endcheckpoint() call made at doCheckpoint

I don't see any other impacts. Could you submit a patch? --Konstantin On Tue, May 3, 2011 at 4:30 AM, Sreehari G wrote: > > In issue HDFS-1839 , is it safe to remove the endcheckpoint() call made at > doCheckpoint after namenode.rollfsimage() ?? As Konstantin Shvachkopointed > out , this call

Hadoop-Hdfs-trunk - Build # 655 - Still Failing

See https://builds.apache.org/hudson/job/Hadoop-Hdfs-trunk/655/ ### ## LAST 60 LINES OF THE CONSOLE ### [...truncated 778925 lines...] [junit] at java.lang.Threa

HDFS-1839 - Is it okay to remove the endcheckpoint() call made at doCheckpoint

In issue HDFS-1839 , is it safe to remove the endcheckpoint() call made at doCheckpoint after namenode.rollfsimage() ?? As Konstantin Shvachko pointed out , this call seems to be redundant .. Or is there any other impact if we remove this ? HUAWEI TECHNOLOGIES CO.,LTD. huawei_logo Solitaire

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

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