[jira] [Commented] (HDFS-2123) 1073: Checkpoint interval should be based on txn count, not size

[ https://issues.apache.org/jira/browse/HDFS-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059671#comment-13059671 ] dhruba borthakur commented on HDFS-2123: +1, sounds good to me. > 1073: Checkpoint

[jira] [Updated] (HDFS-1739) When DataNode throws DiskOutOfSpaceException, it will be helpfull to the user if we log the available volume size and configured block size.

[ https://issues.apache.org/jira/browse/HDFS-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-1739: -- Affects Version/s: 0.23.0 > When DataNode throws DiskOutOfSpaceException, it will be hel

[jira] [Updated] (HDFS-1979) HDFS-1073: Fix backupnode for new edits/image layout

[ https://issues.apache.org/jira/browse/HDFS-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-1979: -- Attachment: hdfs-1979-prelim.txt Preliminary patch with checkpointnode and backupnode working. Needs to

[jira] [Resolved] (HDFS-2123) 1073: Checkpoint interval should be based on txn count, not size

[ https://issues.apache.org/jira/browse/HDFS-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon resolved HDFS-2123. --- Resolution: Fixed Release Note: The SecondaryNameNode and CheckpointNode no longer respect the v

[jira] [Updated] (HDFS-2123) 1073: Checkpoint interval should be based on txn count, not size

[ https://issues.apache.org/jira/browse/HDFS-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2123: -- Attachment: hdfs-2123.txt New patch issues a warning like this: 11/07/04 15:42:18 WARN namenode.Seconda

[jira] [Commented] (HDFS-2123) 1073: Checkpoint interval should be based on txn count, not size

[ https://issues.apache.org/jira/browse/HDFS-2123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059629#comment-13059629 ] Todd Lipcon commented on HDFS-2123: --- hmm.. I added it as a deprecated key, but I think it

[jira] [Commented] (HDFS-1753) Resource Leak in org.apache.hadoop.hdfs.server.namenode.StreamFile

[ https://issues.apache.org/jira/browse/HDFS-1753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059608#comment-13059608 ] Todd Lipcon commented on HDFS-1753: --- +1 > Resource Leak in org.apache.hadoop.hdfs.server

[jira] [Updated] (HDFS-2124) Namenode HA using Backup Namenode as Hot Standby

[ https://issues.apache.org/jira/browse/HDFS-2124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Justin Joseph updated HDFS-2124: Attachment: Namenode HA using Backup Namenode as Hot Standby.pdf The solution document is attached

[jira] [Created] (HDFS-2124) Namenode HA using Backup Namenode as Hot Standby

Namenode HA using Backup Namenode as Hot Standby Key: HDFS-2124 URL: https://issues.apache.org/jira/browse/HDFS-2124 Project: Hadoop HDFS Issue Type: New Feature Components: data-nod

[jira] [Commented] (HDFS-1880) When Namenode network is unplugged, DFSClient operations waits for ever

[ https://issues.apache.org/jira/browse/HDFS-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059349#comment-13059349 ] Aaron T. Myers commented on HDFS-1880: -- bq. Yes , we may need to control this retries,

[jira] [Commented] (HDFS-1257) Race condition on FSNamesystem#recentInvalidateSets introduced by HADOOP-5124

[ https://issues.apache.org/jira/browse/HDFS-1257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059347#comment-13059347 ] ade commented on HDFS-1257: --- hi, I believe that I am running into this problem 2 times. > Ra