[jira] [Updated] (HDFS-233) Support for snapshots

[ https://issues.apache.org/jira/browse/HDFS-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arun C Murthy updated HDFS-233: --- Comment: was deleted (was: I will return to the office on January 17th. For urgent matters, please con

[jira] [Commented] (HDFS-233) Support for snapshots

[ https://issues.apache.org/jira/browse/HDFS-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182058#comment-13182058 ] Philip Zeyliger commented on HDFS-233: -- I will return to the office on January 17th. F

[jira] [Commented] (HDFS-233) Support for snapshots

[ https://issues.apache.org/jira/browse/HDFS-233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182056#comment-13182056 ] Joe Kraska commented on HDFS-233: - Reviewing the comments and noting the dataware housing fe

[jira] [Commented] (HDFS-2764) HA: TestBackupNode is failing

[ https://issues.apache.org/jira/browse/HDFS-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182051#comment-13182051 ] Aaron T. Myers commented on HDFS-2764: -- I don't have time just this moment, but I'll t

[jira] [Commented] (HDFS-2764) HA: TestBackupNode is failing

[ https://issues.apache.org/jira/browse/HDFS-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182049#comment-13182049 ] Uma Maheswara Rao G commented on HDFS-2764: --- I ran this tests several times, for

[jira] [Assigned] (HDFS-2764) HA: TestBackupNode is failing

[ https://issues.apache.org/jira/browse/HDFS-2764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G reassigned HDFS-2764: - Assignee: Uma Maheswara Rao G > HA: TestBackupNode is failing > --

[jira] [Created] (HDFS-2768) BackupNode stop can not close proxy connections because it is not a proxy instance.

BackupNode stop can not close proxy connections because it is not a proxy instance. --- Key: HDFS-2768 URL: https://issues.apache.org/jira/browse/HDFS-2768 Project: Hadoo

[jira] [Commented] (HDFS-1960) dfs.*.dir should not default to /tmp (or other typically volatile storage)

[ https://issues.apache.org/jira/browse/HDFS-1960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182041#comment-13182041 ] Harsh J commented on HDFS-1960: --- Another perhaps-working default could probably be a relative

[jira] [Commented] (HDFS-2592) HA: Balancer support for HA namenodes

[ https://issues.apache.org/jira/browse/HDFS-2592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182037#comment-13182037 ] Uma Maheswara Rao G commented on HDFS-2592: --- Balancer HA support completed for Cl

[jira] [Updated] (HDFS-1273) Handle disk failure when writing new blocks on datanode

[ https://issues.apache.org/jira/browse/HDFS-1273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-1273: -- Resolution: Duplicate Status: Resolved (was: Patch Available) Resolving based on Uma's comment above.

[jira] [Commented] (HDFS-252) Export the HDFS file system through a NFS protocol

[ https://issues.apache.org/jira/browse/HDFS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182035#comment-13182035 ] Brock Noland commented on HDFS-252: --- I wrote a NFS4 proxy for HDFS which seems to work wel

[jira] [Commented] (HDFS-583) HDFS should enforce a max block size

[ https://issues.apache.org/jira/browse/HDFS-583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182034#comment-13182034 ] Harsh J commented on HDFS-583: -- We should cap the DFSClient as well, as it'd help save an RPC c

[jira] [Created] (HDFS-2767) HA: ConfiguredFailoverProxyProvider should support NameNodeProtocol

HA: ConfiguredFailoverProxyProvider should support NameNodeProtocol --- Key: HDFS-2767 URL: https://issues.apache.org/jira/browse/HDFS-2767 Project: Hadoop HDFS Issue Type: Sub-

[jira] [Updated] (HDFS-664) Add a way to efficiently replace a disk in a live datanode

[ https://issues.apache.org/jira/browse/HDFS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-664: - Resolution: Duplicate Status: Resolved (was: Patch Available) Dupe of HDFS-1362, per comments above.

[jira] [Resolved] (HDFS-1863) When all data directory volumes pulled out in DataNode, Its better to shutdown.

[ https://issues.apache.org/jira/browse/HDFS-1863?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-1863. --- Resolution: Cannot Reproduce This doesn't seem to be a problem on 0.23 given Bharath's work (see comments abo

[jira] [Updated] (HDFS-583) HDFS should enforce a max block size

[ https://issues.apache.org/jira/browse/HDFS-583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-583: - Component/s: (was: data-node) name-node Summary: HDFS should enforce a max block size

[jira] [Commented] (HDFS-891) DataNode.instantiateDataNode calls system.exit(-1) if conf.get("dfs.network.script") != null

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

[jira] [Commented] (HDFS-739) "Go to parent directory" link broken running on windows

[ https://issues.apache.org/jira/browse/HDFS-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182024#comment-13182024 ] Harsh J commented on HDFS-739: -- I think using File API for that is a bad idea. We should use Pa

[jira] [Resolved] (HDFS-1724) Can not browse the Data Node blocks from NameNode UI if there is no Data Node hostname mappings in clients.

[ https://issues.apache.org/jira/browse/HDFS-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G resolved HDFS-1724. --- Resolution: Not A Problem Release Note: Clients should have host mappings configu

[jira] [Commented] (HDFS-1724) Can not browse the Data Node blocks from NameNode UI if there is no Data Node hostname mappings in clients.

[ https://issues.apache.org/jira/browse/HDFS-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182017#comment-13182017 ] Harsh J commented on HDFS-1724: --- I'd argue that this is a client-end/environment issue, and t

[jira] [Resolved] (HDFS-1587) JVM crash under writes: ExceptionMark destructor expects no pending exceptions

[ https://issues.apache.org/jira/browse/HDFS-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-1587. --- Resolution: Not A Problem This looked to be cause jars were updated during the runtime. The mail thread http:

[jira] [Commented] (HDFS-1564) Make dfs.datanode.du.reserved configurable per volume

[ https://issues.apache.org/jira/browse/HDFS-1564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13182009#comment-13182009 ] Harsh J commented on HDFS-1564: --- I wonder if this still makes sense to have, and if we should

[jira] [Resolved] (HDFS-973) DataNode.setDataNode() considered dangerous

[ https://issues.apache.org/jira/browse/HDFS-973?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-973. -- Resolution: Cannot Reproduce This does not seem to be a problem in 0.23+, reading the DataNode instantiation cod

[jira] [Updated] (HDFS-891) DataNode.instantiateDataNode calls system.exit(-1) if conf.get("dfs.network.script") != null

[ https://issues.apache.org/jira/browse/HDFS-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-891: - Attachment: HDFS-891.patch I think we can do away with this check. It is a wrong prop name today, and even if it d

[jira] [Updated] (HDFS-891) DataNode.instantiateDataNode calls system.exit(-1) if conf.get("dfs.network.script") != null

[ https://issues.apache.org/jira/browse/HDFS-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-891: - Target Version/s: 0.24.0, 0.23.1 Status: Patch Available (was: Open) > DataNode.instantiateDataN

[jira] [Commented] (HDFS-2709) HA: Appropriately handle error conditions in EditLogTailer

[ https://issues.apache.org/jira/browse/HDFS-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181975#comment-13181975 ] Hudson commented on HDFS-2709: -- Integrated in Hadoop-Hdfs-HAbranch-build #40 (See [https://bu

[jira] [Commented] (HDFS-2349) DN should log a WARN, not an INFO when it detects a corruption during block transfer

[ https://issues.apache.org/jira/browse/HDFS-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181957#comment-13181957 ] Hudson commented on HDFS-2349: -- Integrated in Hadoop-Mapreduce-trunk #951 (See [https://build

[jira] [Commented] (HDFS-1314) dfs.blocksize accepts only absolute value

[ https://issues.apache.org/jira/browse/HDFS-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181958#comment-13181958 ] Hudson commented on HDFS-1314: -- Integrated in Hadoop-Mapreduce-trunk #951 (See [https://build

[jira] [Commented] (HDFS-2729) Update BlockManager's comments regarding the invalid block set

[ https://issues.apache.org/jira/browse/HDFS-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181953#comment-13181953 ] Hudson commented on HDFS-2729: -- Integrated in Hadoop-Mapreduce-trunk #951 (See [https://build

[jira] [Commented] (HDFS-554) BlockInfo.ensureCapacity may get a speedup from System.arraycopy()

[ https://issues.apache.org/jira/browse/HDFS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181959#comment-13181959 ] Hudson commented on HDFS-554: - Integrated in Hadoop-Mapreduce-trunk #951 (See [https://builds.a

[jira] [Commented] (HDFS-2726) "Exception in createBlockOutputStream" shouldn't delete exception stack trace

[ https://issues.apache.org/jira/browse/HDFS-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181956#comment-13181956 ] Hudson commented on HDFS-2726: -- Integrated in Hadoop-Mapreduce-trunk #951 (See [https://build

[jira] [Commented] (HDFS-1314) dfs.blocksize accepts only absolute value

[ https://issues.apache.org/jira/browse/HDFS-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181949#comment-13181949 ] Hudson commented on HDFS-1314: -- Integrated in Hadoop-Mapreduce-0.23-Build #153 (See [https://

[jira] [Commented] (HDFS-2349) DN should log a WARN, not an INFO when it detects a corruption during block transfer

[ https://issues.apache.org/jira/browse/HDFS-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181948#comment-13181948 ] Hudson commented on HDFS-2349: -- Integrated in Hadoop-Mapreduce-0.23-Build #153 (See [https://

[jira] [Commented] (HDFS-554) BlockInfo.ensureCapacity may get a speedup from System.arraycopy()

[ https://issues.apache.org/jira/browse/HDFS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181950#comment-13181950 ] Hudson commented on HDFS-554: - Integrated in Hadoop-Mapreduce-0.23-Build #153 (See [https://bui

[jira] [Commented] (HDFS-2729) Update BlockManager's comments regarding the invalid block set

[ https://issues.apache.org/jira/browse/HDFS-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181944#comment-13181944 ] Hudson commented on HDFS-2729: -- Integrated in Hadoop-Mapreduce-0.23-Build #153 (See [https://

[jira] [Commented] (HDFS-2726) "Exception in createBlockOutputStream" shouldn't delete exception stack trace

[ https://issues.apache.org/jira/browse/HDFS-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181947#comment-13181947 ] Hudson commented on HDFS-2726: -- Integrated in Hadoop-Mapreduce-0.23-Build #153 (See [https://

[jira] [Updated] (HDFS-2762) TestCheckpoint is timing out

[ https://issues.apache.org/jira/browse/HDFS-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-2762: -- Attachment: HDFS-2762.patch > TestCheckpoint is timing out > ---

[jira] [Commented] (HDFS-2762) TestCheckpoint is timing out

[ https://issues.apache.org/jira/browse/HDFS-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181941#comment-13181941 ] Uma Maheswara Rao G commented on HDFS-2762: --- Here is the fix for testMultipleSeco

[jira] [Commented] (HDFS-554) BlockInfo.ensureCapacity may get a speedup from System.arraycopy()

[ https://issues.apache.org/jira/browse/HDFS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181939#comment-13181939 ] Hudson commented on HDFS-554: - Integrated in Hadoop-Hdfs-trunk #918 (See [https://builds.apache

[jira] [Commented] (HDFS-2349) DN should log a WARN, not an INFO when it detects a corruption during block transfer

[ https://issues.apache.org/jira/browse/HDFS-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181937#comment-13181937 ] Hudson commented on HDFS-2349: -- Integrated in Hadoop-Hdfs-trunk #918 (See [https://builds.apa

[jira] [Commented] (HDFS-1314) dfs.blocksize accepts only absolute value

[ https://issues.apache.org/jira/browse/HDFS-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181938#comment-13181938 ] Hudson commented on HDFS-1314: -- Integrated in Hadoop-Hdfs-trunk #918 (See [https://builds.apa

[jira] [Commented] (HDFS-2726) "Exception in createBlockOutputStream" shouldn't delete exception stack trace

[ https://issues.apache.org/jira/browse/HDFS-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181936#comment-13181936 ] Hudson commented on HDFS-2726: -- Integrated in Hadoop-Hdfs-trunk #918 (See [https://builds.apa

[jira] [Commented] (HDFS-2729) Update BlockManager's comments regarding the invalid block set

[ https://issues.apache.org/jira/browse/HDFS-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181933#comment-13181933 ] Hudson commented on HDFS-2729: -- Integrated in Hadoop-Hdfs-trunk #918 (See [https://builds.apa

[jira] [Commented] (HDFS-554) BlockInfo.ensureCapacity may get a speedup from System.arraycopy()

[ https://issues.apache.org/jira/browse/HDFS-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181931#comment-13181931 ] Hudson commented on HDFS-554: - Integrated in Hadoop-Hdfs-0.23-Build #131 (See [https://builds.a

[jira] [Commented] (HDFS-2349) DN should log a WARN, not an INFO when it detects a corruption during block transfer

[ https://issues.apache.org/jira/browse/HDFS-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181929#comment-13181929 ] Hudson commented on HDFS-2349: -- Integrated in Hadoop-Hdfs-0.23-Build #131 (See [https://build

[jira] [Commented] (HDFS-1314) dfs.blocksize accepts only absolute value

[ https://issues.apache.org/jira/browse/HDFS-1314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181930#comment-13181930 ] Hudson commented on HDFS-1314: -- Integrated in Hadoop-Hdfs-0.23-Build #131 (See [https://build

[jira] [Commented] (HDFS-2729) Update BlockManager's comments regarding the invalid block set

[ https://issues.apache.org/jira/browse/HDFS-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181925#comment-13181925 ] Hudson commented on HDFS-2729: -- Integrated in Hadoop-Hdfs-0.23-Build #131 (See [https://build

[jira] [Commented] (HDFS-2726) "Exception in createBlockOutputStream" shouldn't delete exception stack trace

[ https://issues.apache.org/jira/browse/HDFS-2726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181928#comment-13181928 ] Hudson commented on HDFS-2726: -- Integrated in Hadoop-Hdfs-0.23-Build #131 (See [https://build

[jira] [Resolved] (HDFS-851) NPE in FSDir.getBlockInfo

[ https://issues.apache.org/jira/browse/HDFS-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J resolved HDFS-851. -- Resolution: Duplicate This was fixed by Bharat's recent work on moving all calls to the FileUtil.listFiles wrapp

[jira] [Commented] (HDFS-2762) TestCheckpoint is timing out

[ https://issues.apache.org/jira/browse/HDFS-2762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13181902#comment-13181902 ] Uma Maheswara Rao G commented on HDFS-2762: --- Thanks Aaron for filing the JIRA. To