[jira] [Created] (HDFS-2075) Add Number of Reporting Nodes to namenode web UI

Add Number of Reporting Nodes to namenode web UI -- Key: HDFS-2075 URL: https://issues.apache.org/jira/browse/HDFS-2075 Project: Hadoop HDFS Issue Type: Improvement Components:

[jira] [Updated] (HDFS-2075) Add Number of Reporting Nodes to namenode web UI

[ https://issues.apache.org/jira/browse/HDFS-2075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Xing Jin updated HDFS-2075: --- Attachment: HDFS-2075.patch.txt patch for the issue Add Number of Reporting Nodes to namenode web UI

[jira] [Commented] (HDFS-1989) When checkpointing by backup node occurs parallely when a file is being closed by a client then Exception occurs saying no journal streams.

[ https://issues.apache.org/jira/browse/HDFS-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049710#comment-13049710 ] ramkrishna.s.vasudevan commented on HDFS-1989: -- Hi Todd, In the backup name

[jira] [Updated] (HDFS-1788) FsShell ls: Show symlinks properties

[ https://issues.apache.org/jira/browse/HDFS-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bochun Bai updated HDFS-1788: - Attachment: HDFS-1788.patch A field fs.shell.PathData.statLink is added. PathData.stat is renamed to

[jira] [Commented] (HDFS-2076) ERROR org.apache.hadoop.hdfs.server.datanode.DataNode: DatanodeRegistration(1

[ https://issues.apache.org/jira/browse/HDFS-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049767#comment-13049767 ] Harsh J commented on HDFS-2076: --- This appears to be more of a usage question with the details

[jira] [Updated] (HDFS-1981) When namenode goes down while checkpointing and if is started again subsequent Checkpointing is always failing

[ https://issues.apache.org/jira/browse/HDFS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HDFS-1981: - Status: Patch Available (was: Open) When namenode goes down while checkpointing

[jira] [Updated] (HDFS-1981) When namenode goes down while checkpointing and if is started again subsequent Checkpointing is always failing

[ https://issues.apache.org/jira/browse/HDFS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ramkrishna.s.vasudevan updated HDFS-1981: - Attachment: HDFS-1981.patch When namenode goes down while checkpointing and if

[jira] [Commented] (HDFS-1805) Some Tests in TestDFSShell can not shutdown the MiniDFSCluster on any exception/assertion failure. This will leads to fail other testcases.

[ https://issues.apache.org/jira/browse/HDFS-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049800#comment-13049800 ] ramkrishna.s.vasudevan commented on HDFS-1805: -- Hi Daryn, Thanks for the

[jira] [Commented] (HDFS-941) Datanode xceiver protocol should allow reuse of a connection

[ https://issues.apache.org/jira/browse/HDFS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049863#comment-13049863 ] stack commented on HDFS-941: I reran tests, same three failed. I backed out my patch and the

[jira] [Updated] (HDFS-1942) If all Block Pool service threads exit then datanode should exit.

[ https://issues.apache.org/jira/browse/HDFS-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-1942: -- Resolution: Fixed Hadoop Flags: [Reviewed] Status: Resolved (was: Patch

[jira] [Commented] (HDFS-1989) When checkpointing by backup node occurs parallely when a file is being closed by a client then Exception occurs saying no journal streams.

[ https://issues.apache.org/jira/browse/HDFS-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049914#comment-13049914 ] Todd Lipcon commented on HDFS-1989: --- my point is that the client cannot issue a close()

[jira] [Commented] (HDFS-1981) When namenode goes down while checkpointing and if is started again subsequent Checkpointing is always failing

[ https://issues.apache.org/jira/browse/HDFS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049924#comment-13049924 ] Hadoop QA commented on HDFS-1981: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-1692) In secure mode, Datanode process doesn't exit when disks fail.

[ https://issues.apache.org/jira/browse/HDFS-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049925#comment-13049925 ] Suresh Srinivas commented on HDFS-1692: --- Minor comments: # DataNode.java - in finally

[jira] [Assigned] (HDFS-2071) Use of isConnected() in DataXceiver is invalid

[ https://issues.apache.org/jira/browse/HDFS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee reassigned HDFS-2071: Assignee: Kihwal Lee Use of isConnected() in DataXceiver is invalid

[jira] [Updated] (HDFS-1981) When namenode goes down while checkpointing and if is started again subsequent Checkpointing is always failing

[ https://issues.apache.org/jira/browse/HDFS-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HDFS-1981: -- Priority: Blocker (was: Major) Affects Version/s: (was: 0.23.0)

[jira] [Updated] (HDFS-2071) Use of isConnected() in DataXceiver is invalid

[ https://issues.apache.org/jira/browse/HDFS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-2071: - Attachment: HDFS-2071.patch Use of isConnected() in DataXceiver is invalid

[jira] [Updated] (HDFS-2054) BlockSender.sendChunk() prints ERROR for connection closures encountered during transferToFully()

[ https://issues.apache.org/jira/browse/HDFS-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-2054: - Fix Version/s: 0.23.0 0.22.0 Status: Patch Available (was: Open)

[jira] [Commented] (HDFS-2071) Use of isConnected() in DataXceiver is invalid

[ https://issues.apache.org/jira/browse/HDFS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049957#comment-13049957 ] Harsh J commented on HDFS-2071: --- Kihwal - Since HDFS-941 is not yet committed, I think you

[jira] [Commented] (HDFS-2071) Use of isConnected() in DataXceiver is invalid

[ https://issues.apache.org/jira/browse/HDFS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049959#comment-13049959 ] Kihwal Lee commented on HDFS-2071: -- HDFS-941 is already in trunk. The current discussion

[jira] [Commented] (HDFS-2071) Use of isConnected() in DataXceiver is invalid

[ https://issues.apache.org/jira/browse/HDFS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049968#comment-13049968 ] Harsh J commented on HDFS-2071: --- Gah, missed that, and the comments there. I take back my

[jira] [Commented] (HDFS-1989) When checkpointing by backup node occurs parallely when a file is being closed by a client then Exception occurs saying no journal streams.

[ https://issues.apache.org/jira/browse/HDFS-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049973#comment-13049973 ] Konstantin Shvachko commented on HDFS-1989: --- Seems like a valid bug. Client does

[jira] [Commented] (HDFS-2054) BlockSender.sendChunk() prints ERROR for connection closures encountered during transferToFully()

[ https://issues.apache.org/jira/browse/HDFS-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049977#comment-13049977 ] Hadoop QA commented on HDFS-2054: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-2071) Use of isConnected() in DataXceiver is invalid

[ https://issues.apache.org/jira/browse/HDFS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049978#comment-13049978 ] Hadoop QA commented on HDFS-2071: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-2071) Use of isConnected() in DataXceiver is invalid

[ https://issues.apache.org/jira/browse/HDFS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049994#comment-13049994 ] Kihwal Lee commented on HDFS-2071: -- Test failures: * TestHDFSCLI: The quota related test

[jira] [Commented] (HDFS-2054) BlockSender.sendChunk() prints ERROR for connection closures encountered during transferToFully()

[ https://issues.apache.org/jira/browse/HDFS-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13049995#comment-13049995 ] Kihwal Lee commented on HDFS-2054: -- Test failures: TestHDFSCLI: The quota related

[jira] [Resolved] (HDFS-1811) Create scripts to decommission datanodes

[ https://issues.apache.org/jira/browse/HDFS-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HDFS-1811. --- Resolution: Duplicate Already fixed as a part of HDFS-1703. Create scripts to decommission

[jira] [Updated] (HDFS-1692) In secure mode, Datanode process doesn't exit when disks fail.

[ https://issues.apache.org/jira/browse/HDFS-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bharath Mundlapudi updated HDFS-1692: - Attachment: HDFS-1692-v0.23-2.patch I have cleaned up a little bit, like the logging

[jira] [Commented] (HDFS-2054) BlockSender.sendChunk() prints ERROR for connection closures encountered during transferToFully()

[ https://issues.apache.org/jira/browse/HDFS-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050045#comment-13050045 ] Todd Lipcon commented on HDFS-2054: --- Hey Kihwal. Don't we want to check for Connection

[jira] [Updated] (HDFS-2071) Use of isConnected() in DataXceiver is invalid

[ https://issues.apache.org/jira/browse/HDFS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2071: -- Resolution: Fixed Fix Version/s: (was: 0.20.3) 0.22.0 Hadoop Flags:

[jira] [Updated] (HDFS-941) Datanode xceiver protocol should allow reuse of a connection

[ https://issues.apache.org/jira/browse/HDFS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-941: - Resolution: Fixed Fix Version/s: 0.22.0 Status: Resolved (was: Patch Available)

[jira] [Updated] (HDFS-2034) length in getBlockRange becomes -ve when reading only from currently being written blk

[ https://issues.apache.org/jira/browse/HDFS-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Todd Lipcon updated HDFS-2034: -- Status: Open (was: Patch Available) length in getBlockRange becomes -ve when reading only from

[jira] [Commented] (HDFS-2054) BlockSender.sendChunk() prints ERROR for connection closures encountered during transferToFully()

[ https://issues.apache.org/jira/browse/HDFS-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050062#comment-13050062 ] Kihwal Lee commented on HDFS-2054: -- I found the following from Sun's NIO example. :)

[jira] [Commented] (HDFS-1788) FsShell ls: Show symlinks properties

[ https://issues.apache.org/jira/browse/HDFS-1788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050065#comment-13050065 ] Daryn Sharp commented on HDFS-1788: --- Very nice! First off, this isn't a HDFS change.

[jira] [Commented] (HDFS-2054) BlockSender.sendChunk() prints ERROR for connection closures encountered during transferToFully()

[ https://issues.apache.org/jira/browse/HDFS-2054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050072#comment-13050072 ] Kihwal Lee commented on HDFS-2054: -- The new patch has been uploaded.

[jira] [Resolved] (HDFS-2073) Namenode is missing @Override annotations

[ https://issues.apache.org/jira/browse/HDFS-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas resolved HDFS-2073. --- Resolution: Fixed Hadoop Flags: [Reviewed] I committed the patch. Namenode is missing

[jira] [Commented] (HDFS-1295) Improve namenode restart times by short-circuiting the first block reports from datanodes

[ https://issues.apache.org/jira/browse/HDFS-1295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050105#comment-13050105 ] Hudson commented on HDFS-1295: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-1948) Forward port 'hdfs-1520 lightweight namenode operation to trigger lease reccovery'

[ https://issues.apache.org/jira/browse/HDFS-1948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050108#comment-13050108 ] Hudson commented on HDFS-1948: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2061) two minor bugs in BlockManager block report processing

[ https://issues.apache.org/jira/browse/HDFS-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050106#comment-13050106 ] Hudson commented on HDFS-2061: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2069) Incorrect default trash interval value in the docs

[ https://issues.apache.org/jira/browse/HDFS-2069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050107#comment-13050107 ] Hudson commented on HDFS-2069: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2063) libhdfs test is broken

[ https://issues.apache.org/jira/browse/HDFS-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050109#comment-13050109 ] Hudson commented on HDFS-2063: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2066) Create a package and individual class files for DataTransferProtocol

[ https://issues.apache.org/jira/browse/HDFS-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050111#comment-13050111 ] Hudson commented on HDFS-2066: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2067) Bump DATA_TRANSFER_VERSION in trunk for protobufs

[ https://issues.apache.org/jira/browse/HDFS-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050113#comment-13050113 ] Hudson commented on HDFS-2067: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2058) DataTransfer Protocol using protobufs

[ https://issues.apache.org/jira/browse/HDFS-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050115#comment-13050115 ] Hudson commented on HDFS-2058: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-1942) If all Block Pool service threads exit then datanode should exit.

[ https://issues.apache.org/jira/browse/HDFS-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050114#comment-13050114 ] Hudson commented on HDFS-1942: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-1052) HDFS scalability with multiple namenodes

[ https://issues.apache.org/jira/browse/HDFS-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050118#comment-13050118 ] Hudson commented on HDFS-1052: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2071) Use of isConnected() in DataXceiver is invalid

[ https://issues.apache.org/jira/browse/HDFS-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050116#comment-13050116 ] Hudson commented on HDFS-2071: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2041) Some mtimes and atimes are lost when edit logs are replayed

[ https://issues.apache.org/jira/browse/HDFS-2041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050112#comment-13050112 ] Hudson commented on HDFS-2041: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2040) Only build libhdfs if a flag is passed

[ https://issues.apache.org/jira/browse/HDFS-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050110#comment-13050110 ] Hudson commented on HDFS-2040: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2073) Namenode is missing @Override annotations

[ https://issues.apache.org/jira/browse/HDFS-2073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050117#comment-13050117 ] Hudson commented on HDFS-2073: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2046) Force entropy to come from non-true random for tests

[ https://issues.apache.org/jira/browse/HDFS-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050129#comment-13050129 ] Hudson commented on HDFS-2046: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-1586) Add InterfaceAudience annotation to MiniDFSCluster

[ https://issues.apache.org/jira/browse/HDFS-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050123#comment-13050123 ] Hudson commented on HDFS-1586: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-1149) Lease reassignment is not persisted to edit log

[ https://issues.apache.org/jira/browse/HDFS-1149?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050125#comment-13050125 ] Hudson commented on HDFS-1149: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-1875) MiniDFSCluster hard-codes dfs.datanode.address to localhost

[ https://issues.apache.org/jira/browse/HDFS-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050130#comment-13050130 ] Hudson commented on HDFS-1875: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-1520) HDFS 20 append: Lightweight NameNode operation to trigger lease recovery

[ https://issues.apache.org/jira/browse/HDFS-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050128#comment-13050128 ] Hudson commented on HDFS-1520: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-1954) Improve corrupt files warning message on NameNode web UI

[ https://issues.apache.org/jira/browse/HDFS-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050132#comment-13050132 ] Hudson commented on HDFS-1954: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-988) saveNamespace race can corrupt the edits log

[ https://issues.apache.org/jira/browse/HDFS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050133#comment-13050133 ] Hudson commented on HDFS-988: - Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2039) TestNameNodeMetrics uses a bad test root path

[ https://issues.apache.org/jira/browse/HDFS-2039?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050122#comment-13050122 ] Hudson commented on HDFS-2039: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2003) Separate FSEditLog reading logic from editLog memory state building logic

[ https://issues.apache.org/jira/browse/HDFS-2003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050134#comment-13050134 ] Hudson commented on HDFS-2003: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2056) Update fetchdt usage

[ https://issues.apache.org/jira/browse/HDFS-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050120#comment-13050120 ] Hudson commented on HDFS-2056: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-1998) make refresh-namodenodes.sh refreshing all namenodes

[ https://issues.apache.org/jira/browse/HDFS-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050135#comment-13050135 ] Hudson commented on HDFS-1998: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2030) Fix the usability of namenode upgrade command

[ https://issues.apache.org/jira/browse/HDFS-2030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050126#comment-13050126 ] Hudson commented on HDFS-2030: -- Integrated in Hadoop-Hdfs-trunk-Commit #746 (See

[jira] [Commented] (HDFS-2018) Move all journal stream management code into one place

[ https://issues.apache.org/jira/browse/HDFS-2018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050141#comment-13050141 ] Todd Lipcon commented on HDFS-2018: --- Hi Ivan. I've been thinking about this patch the

[jira] [Resolved] (HDFS-1952) FSEditLog.open() appears to succeed even if all EDITS directories fail

[ https://issues.apache.org/jira/browse/HDFS-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley resolved HDFS-1952. -- Resolution: Fixed Fix Version/s: 0.23.0 0.22.0 Committed to v22. Thanks,

[jira] [Updated] (HDFS-1692) In secure mode, Datanode process doesn't exit when disks fail.

[ https://issues.apache.org/jira/browse/HDFS-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-1692: -- Status: Patch Available (was: Open) In secure mode, Datanode process doesn't exit when disks

[jira] [Commented] (HDFS-2002) Incorrect computation of needed blocks in getTurnOffTip()

[ https://issues.apache.org/jira/browse/HDFS-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050166#comment-13050166 ] Jakob Homan commented on HDFS-2002: --- Matthias - looks like TestSafeMode is checking the

[jira] [Commented] (HDFS-941) Datanode xceiver protocol should allow reuse of a connection

[ https://issues.apache.org/jira/browse/HDFS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050181#comment-13050181 ] Konstantin Shvachko commented on HDFS-941: -- -1 on committing this without the proof

[jira] [Commented] (HDFS-1692) In secure mode, Datanode process doesn't exit when disks fail.

[ https://issues.apache.org/jira/browse/HDFS-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050182#comment-13050182 ] Hadoop QA commented on HDFS-1692: - -1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-941) Datanode xceiver protocol should allow reuse of a connection

[ https://issues.apache.org/jira/browse/HDFS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050197#comment-13050197 ] stack commented on HDFS-941: @Konstantin Convention is that RM says whats in a release and no

[jira] [Commented] (HDFS-1989) When checkpointing by backup node occurs parallely when a file is being closed by a client then Exception occurs saying no journal streams.

[ https://issues.apache.org/jira/browse/HDFS-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050207#comment-13050207 ] ramkrishna.s.vasudevan commented on HDFS-1989: -- Hi, Yes. the editsLog.close()

[jira] [Commented] (HDFS-941) Datanode xceiver protocol should allow reuse of a connection

[ https://issues.apache.org/jira/browse/HDFS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050219#comment-13050219 ] Kihwal Lee commented on HDFS-941: - Perhaps it's confusing because this Jira is seen as

[jira] [Commented] (HDFS-941) Datanode xceiver protocol should allow reuse of a connection

[ https://issues.apache.org/jira/browse/HDFS-941?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13050231#comment-13050231 ] Todd Lipcon commented on HDFS-941: -- Ran the following benchmark to compare 0.22 before vs