[jira] [Commented] (HDFS-3107) HDFS truncate

[ https://issues.apache.org/jira/browse/HDFS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14161021#comment-14161021 ] dhruba borthakur commented on HDFS-3107: Thanks for the clarification Milind. I was

[jira] [Commented] (HDFS-3107) HDFS truncate

[ https://issues.apache.org/jira/browse/HDFS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14159278#comment-14159278 ] dhruba borthakur commented on HDFS-3107: Thanks KonstantinS. I get it now. Just to

[jira] [Commented] (HDFS-3107) HDFS truncate

[ https://issues.apache.org/jira/browse/HDFS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14156265#comment-14156265 ] dhruba borthakur commented on HDFS-3107: Hi KonstantinS, I have been following this

[jira] [Commented] (HDFS-3107) HDFS truncate

[ https://issues.apache.org/jira/browse/HDFS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14151051#comment-14151051 ] dhruba borthakur commented on HDFS-3107: The design-doc looks cool. And thanks for

[jira] [Commented] (HDFS-3107) HDFS truncate

[ https://issues.apache.org/jira/browse/HDFS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14150789#comment-14150789 ] dhruba borthakur commented on HDFS-3107: hi konstantin, is it possible to wait for

[jira] [Comment Edited] (HDFS-3107) HDFS truncate

[ https://issues.apache.org/jira/browse/HDFS-3107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14150789#comment-14150789 ] dhruba borthakur edited comment on HDFS-3107 at 9/27/14 9:56 PM:

[jira] [Commented] (HDFS-1245) Plugable block id generation

[ https://issues.apache.org/jira/browse/HDFS-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13551863#comment-13551863 ] dhruba borthakur commented on HDFS-1245: Great to see progress on this old JIRA!

[jira] [Commented] (HDFS-487) HDFS should expose a fileid to uniquely identify a file

[ https://issues.apache.org/jira/browse/HDFS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13435637#comment-13435637 ] dhruba borthakur commented on HDFS-487: --- as far as i know, nobody is working on this

[jira] [Commented] (HDFS-1783) Ability for HDFS client to write replicas in parallel

[ https://issues.apache.org/jira/browse/HDFS-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13283170#comment-13283170 ] dhruba borthakur commented on HDFS-1783: Hi Lars, the code is in

[jira] [Commented] (HDFS-3429) DataNode reads checksums even if client does not need them

[ https://issues.apache.org/jira/browse/HDFS-3429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13276537#comment-13276537 ] dhruba borthakur commented on HDFS-3429: For the records, if you switch-on local

[jira] [Commented] (HDFS-234) Integration with BookKeeper logging system

[ https://issues.apache.org/jira/browse/HDFS-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13270691#comment-13270691 ] dhruba borthakur commented on HDFS-234: --- Hi Uma, while it is true that we are

[jira] [Commented] (HDFS-3092) Enable journal protocol based editlog streaming for standby namenode

[ https://issues.apache.org/jira/browse/HDFS-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13265110#comment-13265110 ] dhruba borthakur commented on HDFS-3092: we might continue to invest in making

[jira] [Commented] (HDFS-3092) Enable journal protocol based editlog streaming for standby namenode

[ https://issues.apache.org/jira/browse/HDFS-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13259394#comment-13259394 ] dhruba borthakur commented on HDFS-3092: I am trying to digest the meat of this

[jira] [Commented] (HDFS-2246) Shortcut a local client reads to a Datanodes files directly

[ https://issues.apache.org/jira/browse/HDFS-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13102234#comment-13102234 ] dhruba borthakur commented on HDFS-2246: I see, is there a reason why we should not

[jira] [Commented] (HDFS-2246) Shortcut a local client reads to a Datanodes files directly

[ https://issues.apache.org/jira/browse/HDFS-2246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13102009#comment-13102009 ] dhruba borthakur commented on HDFS-2246: Todd: this patch seems to be the best way

[jira] [Updated] (HDFS-1779) After NameNode restart , Clients can not read partial files even after client invokes Sync.

[ https://issues.apache.org/jira/browse/HDFS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-1779: --- Fix Version/s: 0.20.205.0 Maybe we need to include this for the upcoming 0.20.205+ release

[jira] [Commented] (HDFS-1623) High Availability Framework for HDFS NN

[ https://issues.apache.org/jira/browse/HDFS-1623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070643#comment-13070643 ] dhruba borthakur commented on HDFS-1623: Hi Yang, The zk heartbeats and delivery of

[jira] [Commented] (HDFS-2179) HA: namenode fencing mechanism

[ https://issues.apache.org/jira/browse/HDFS-2179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13070658#comment-13070658 ] dhruba borthakur commented on HDFS-2179: Awesome, +1 to the proposal listed above.

[jira] [Commented] (HDFS-1783) Ability for HDFS client to write replicas in parallel

[ https://issues.apache.org/jira/browse/HDFS-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13067545#comment-13067545 ] dhruba borthakur commented on HDFS-1783: Thanks for the ping, Sanjay. This patch is

[jira] [Commented] (HDFS-347) DFS read performance suboptimal when client co-located on nodes with data

[ https://issues.apache.org/jira/browse/HDFS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13064158#comment-13064158 ] dhruba borthakur commented on HDFS-347: --- My observation has been that it is the high

[jira] [Commented] (HDFS-347) DFS read performance suboptimal when client co-located on nodes with data

[ https://issues.apache.org/jira/browse/HDFS-347?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13064352#comment-13064352 ] dhruba borthakur commented on HDFS-347: --- we do not run with HDFS-941. I will post

[jira] [Commented] (HDFS-503) Implement erasure coding as a layer on HDFS

[ https://issues.apache.org/jira/browse/HDFS-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060975#comment-13060975 ] dhruba borthakur commented on HDFS-503: --- 1. Raid has no impact on dfsadmin -report

[jira] [Created] (HDFS-2128) Support for pluggable Trash policies

Support for pluggable Trash policies Key: HDFS-2128 URL: https://issues.apache.org/jira/browse/HDFS-2128 Project: Hadoop HDFS Issue Type: Improvement Reporter: dhruba borthakur

[jira] [Updated] (HDFS-2128) Support for pluggable Trash policies

[ https://issues.apache.org/jira/browse/HDFS-2128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-2128: --- Component/s: name-node Support for pluggable Trash policies

[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-tabpanelfocusedCommentId=13059671#comment-13059671 ] dhruba borthakur commented on HDFS-2123: +1, sounds good to me. 1073: Checkpoint

[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-tabpanelfocusedCommentId=13059162#comment-13059162 ] dhruba borthakur commented on HDFS-2123: +1, code looks good. what happens if

[jira] [Commented] (HDFS-1580) Add interface for generic Write Ahead Logging mechanisms

[ https://issues.apache.org/jira/browse/HDFS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13058708#comment-13058708 ] dhruba borthakur commented on HDFS-1580: 1. it would be nice to get rid of mark()

[jira] [Commented] (HDFS-395) DFS Scalability: Incremental block reports

[ https://issues.apache.org/jira/browse/HDFS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13058782#comment-13058782 ] dhruba borthakur commented on HDFS-395: --- When the block invalidate command comes to

[jira] [Commented] (HDFS-395) DFS Scalability: Incremental block reports

[ https://issues.apache.org/jira/browse/HDFS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13058833#comment-13058833 ] dhruba borthakur commented on HDFS-395: --- The reason block deletion is async is because

[jira] [Commented] (HDFS-395) DFS Scalability: Incremental block reports

[ https://issues.apache.org/jira/browse/HDFS-395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13058854#comment-13058854 ] dhruba borthakur commented on HDFS-395: --- from my earlier experience with developing

[jira] [Commented] (HDFS-929) DFSClient#getBlockSize is unused

[ https://issues.apache.org/jira/browse/HDFS-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13054988#comment-13054988 ] dhruba borthakur commented on HDFS-929: --- any motivation for doing this? Since this is

[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=13050726#comment-13050726 ] dhruba borthakur commented on HDFS-941: --- My experience with TestDFSIO has been that

[jira] [Commented] (HDFS-503) Implement erasure coding as a layer on HDFS

[ https://issues.apache.org/jira/browse/HDFS-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13043211#comment-13043211 ] dhruba borthakur commented on HDFS-503: --- source code in

[jira] [Commented] (HDFS-988) saveNamespace can corrupt edits log, apparently due to race conditions

[ https://issues.apache.org/jira/browse/HDFS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13041962#comment-13041962 ] dhruba borthakur commented on HDFS-988: --- we should not logSync after a

[jira] [Commented] (HDFS-1982) Null pointer exception is thrown when NN restarts with a block lesser in size than the block that is present in DN1 but the generation stamp is greater in the NN

[ https://issues.apache.org/jira/browse/HDFS-1982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13041236#comment-13041236 ] dhruba borthakur commented on HDFS-1982: Theoretically, this seems plausible. are

[jira] [Commented] (HDFS-2006) ability to support storing extended attributes per file

[ https://issues.apache.org/jira/browse/HDFS-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13040357#comment-13040357 ] dhruba borthakur commented on HDFS-2006: @Konstantin: This feature can be used in a

[jira] [Created] (HDFS-2006) ability to support storing extended attributes per file

ability to support storing extended attributes per file --- Key: HDFS-2006 URL: https://issues.apache.org/jira/browse/HDFS-2006 Project: Hadoop HDFS Issue Type: Improvement

[jira] [Assigned] (HDFS-2006) ability to support storing extended attributes per file

[ https://issues.apache.org/jira/browse/HDFS-2006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur reassigned HDFS-2006: -- Assignee: dhruba borthakur ability to support storing extended attributes per file

[jira] [Commented] (HDFS-1779) After NameNode restart , Clients can not read partial files even after client invokes Sync.

[ https://issues.apache.org/jira/browse/HDFS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13037012#comment-13037012 ] dhruba borthakur commented on HDFS-1779: if the namenode restarts, the datanode

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

[ https://issues.apache.org/jira/browse/HDFS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13035233#comment-13035233 ] dhruba borthakur commented on HDFS-988: --- yes, they should all be using RWLock,

[jira] [Commented] (HDFS-1627) Fix NullPointerException in Secondary NameNode

[ https://issues.apache.org/jira/browse/HDFS-1627?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13032591#comment-13032591 ] dhruba borthakur commented on HDFS-1627: +1, looks good to me. Fix

[jira] [Commented] (HDFS-487) HDFS should expose a fileid to uniquely identify a file

[ https://issues.apache.org/jira/browse/HDFS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13030856#comment-13030856 ] dhruba borthakur commented on HDFS-487: --- Hi Tigran, thanks for doing this. As you

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

[ https://issues.apache.org/jira/browse/HDFS-988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13029783#comment-13029783 ] dhruba borthakur commented on HDFS-988: --- 1. we should not throw an exception is unable

[jira] [Commented] (HDFS-1865) Share LeaseChecker thread among DFSClients

[ https://issues.apache.org/jira/browse/HDFS-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026883#comment-13026883 ] dhruba borthakur commented on HDFS-1865: Ok, got it. Share LeaseChecker thread

[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=13026847#comment-13026847 ] dhruba borthakur commented on HDFS-1052: +1. although the benchmarks are single

[jira] [Commented] (HDFS-1580) Add interface for generic Write Ahead Logging mechanisms

[ https://issues.apache.org/jira/browse/HDFS-1580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026852#comment-13026852 ] dhruba borthakur commented on HDFS-1580: Nice document. can you pl describe the

[jira] [Commented] (HDFS-1865) Share LeaseChecker thread among DFSClients

[ https://issues.apache.org/jira/browse/HDFS-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026857#comment-13026857 ] dhruba borthakur commented on HDFS-1865: hi nicholas, I do not undertand your

[jira] [Commented] (HDFS-1848) Datanodes should shutdown when a critical volume fails

[ https://issues.apache.org/jira/browse/HDFS-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026858#comment-13026858 ] dhruba borthakur commented on HDFS-1848: Hi Koji, I am fine implementing more

[jira] [Commented] (HDFS-1865) Share LeaseChecker thread among DFSClients

[ https://issues.apache.org/jira/browse/HDFS-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026861#comment-13026861 ] dhruba borthakur commented on HDFS-1865: Oh ok, can you also explain the usecase

[jira] [Commented] (HDFS-1848) Datanodes should shutdown when a critical volume fails

[ https://issues.apache.org/jira/browse/HDFS-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026121#comment-13026121 ] dhruba borthakur commented on HDFS-1848: Point #1 is limited to allowing an admin

[jira] [Commented] (HDFS-1848) Datanodes should shutdown when a critical volume fails

[ https://issues.apache.org/jira/browse/HDFS-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026127#comment-13026127 ] dhruba borthakur commented on HDFS-1848: Would something like mapreduce's

[jira] [Commented] (HDFS-1846) Don't fill preallocated portion of edits log with 0x00

[ https://issues.apache.org/jira/browse/HDFS-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026130#comment-13026130 ] dhruba borthakur commented on HDFS-1846: +1 Don't fill preallocated portion of

[jira] [Commented] (HDFS-1865) Share LeaseChecker thread among DFSClients

[ https://issues.apache.org/jira/browse/HDFS-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13026131#comment-13026131 ] dhruba borthakur commented on HDFS-1865: why not share the DFSClient itself?

[jira] [Updated] (HDFS-1391) Exiting safemode takes a long time when there are lots of blocks in the HDFS

[ https://issues.apache.org/jira/browse/HDFS-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-1391: --- Status: Open (was: Patch Available) Have to fix review comments. Exiting safemode takes a

[jira] [Updated] (HDFS-1391) Exiting safemode takes a long time when there are lots of blocks in the HDFS

[ https://issues.apache.org/jira/browse/HDFS-1391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-1391: --- Attachment: excessReplicas5.txt Addressed Review comments. Exiting safemode takes a long

[jira] [Commented] (HDFS-1848) Datanodes should shutdown when a critical volume fails

[ https://issues.apache.org/jira/browse/HDFS-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13023527#comment-13023527 ] dhruba borthakur commented on HDFS-1848: Thanks Eli for the explanation. It seems

[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=13023529#comment-13023529 ] dhruba borthakur commented on HDFS-1295: Code looks good to me, +1 Improve

[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and bump it's default value

[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13023530#comment-13023530 ] dhruba borthakur commented on HDFS-1861: maybe do it in a backward-compatible way

[jira] [Commented] (HDFS-1861) Rename dfs.datanode.max.xcievers and bump it's default value

[ https://issues.apache.org/jira/browse/HDFS-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13023611#comment-13023611 ] dhruba borthakur commented on HDFS-1861: apologies, patch looks good. +1 Rename

[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=13022685#comment-13022685 ] dhruba borthakur commented on HDFS-1295: hi suresh, the block-report creation time

[jira] [Commented] (HDFS-1848) Datanodes should shutdown when a critical volume fails

[ https://issues.apache.org/jira/browse/HDFS-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022686#comment-13022686 ] dhruba borthakur commented on HDFS-1848: I too am not clear why the datanode

[jira] [Commented] (HDFS-1846) Don't fill preallocated portion of edits log with 0x00

[ https://issues.apache.org/jira/browse/HDFS-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022687#comment-13022687 ] dhruba borthakur commented on HDFS-1846: The idea of preallocation is to somehow

[jira] [Commented] (HDFS-1848) Datanodes should shutdown when a critical volume fails

[ https://issues.apache.org/jira/browse/HDFS-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022840#comment-13022840 ] dhruba borthakur commented on HDFS-1848: thanks Eli/Koji for the explanation. are

[jira] [Commented] (HDFS-1846) Don't fill preallocated portion of edits log with 0x00

[ https://issues.apache.org/jira/browse/HDFS-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13022843#comment-13022843 ] dhruba borthakur commented on HDFS-1846: Is your point that we should figure out

[jira] [Commented] (HDFS-1825) Remove thriftfs contrib

[ https://issues.apache.org/jira/browse/HDFS-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019219#comment-13019219 ] dhruba borthakur commented on HDFS-1825: +1 Remove thriftfs contrib

[jira] [Commented] (HDFS-1804) Modify or add a new block-volume device choosing policy that looks at free space

[ https://issues.apache.org/jira/browse/HDFS-1804?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019221#comment-13019221 ] dhruba borthakur commented on HDFS-1804: Hi doug, I think just a biased round-robin

[jira] [Commented] (HDFS-1371) One bad node can incorrectly flag many files as corrupt

[ https://issues.apache.org/jira/browse/HDFS-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019658#comment-13019658 ] dhruba borthakur commented on HDFS-1371: I agree with Jitendra. I think a good

[jira] [Commented] (HDFS-1822) Editlog opcodes overlap between 20 security and later releases

[ https://issues.apache.org/jira/browse/HDFS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13019664#comment-13019664 ] dhruba borthakur commented on HDFS-1822: I think Konstantin's proposal seems to be

[jira] [Commented] (HDFS-1822) Editlog opcodes overlap between 20 security and later releases

[ https://issues.apache.org/jira/browse/HDFS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13018510#comment-13018510 ] dhruba borthakur commented on HDFS-1822: What is the problem in adding handling of

[jira] [Commented] (HDFS-1822) Editlog opcodes overlap between 20 security and later releases

[ https://issues.apache.org/jira/browse/HDFS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13017892#comment-13017892 ] dhruba borthakur commented on HDFS-1822: No, Apache has not made a release off

[jira] [Commented] (HDFS-1630) Checksum fsedits

[ https://issues.apache.org/jira/browse/HDFS-1630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13017592#comment-13017592 ] dhruba borthakur commented on HDFS-1630: +1, code looks good to me. Checksum

[jira] [Commented] (HDFS-1822) Editlog opcodes overlap between 20 security and later releases

[ https://issues.apache.org/jira/browse/HDFS-1822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13017685#comment-13017685 ] dhruba borthakur commented on HDFS-1822: We need to make sure, any op code added

[jira] [Commented] (HDFS-744) Support hsync in HDFS

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13016678#comment-13016678 ] dhruba borthakur commented on HDFS-744: --- @Nicholas: yeah, machines were hard-rebooted

[jira] [Commented] (HDFS-744) Support hsync in HDFS

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13016258#comment-13016258 ] dhruba borthakur commented on HDFS-744: --- We need this functionality for HBase

[jira] [Commented] (HDFS-1070) Speedup NameNode image loading and saving by storing local file names

[ https://issues.apache.org/jira/browse/HDFS-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015716#comment-13015716 ] dhruba borthakur commented on HDFS-1070: hi nicholas, when we use compression to

[jira] [Commented] (HDFS-1070) Speedup NameNode image loading and saving by storing local file names

[ https://issues.apache.org/jira/browse/HDFS-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015749#comment-13015749 ] dhruba borthakur commented on HDFS-1070: Completely agree with you Nicholas that

[jira] [Commented] (HDFS-1798) saveNamespace should background the writing of the FSImage files when in SafeMode

[ https://issues.apache.org/jira/browse/HDFS-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13015764#comment-13015764 ] dhruba borthakur commented on HDFS-1798: In another ira, it is proposed that the NN

[jira] [Resolved] (HDFS-1392) Improve namenode scalability by prioritizing datanode heartbeats over block reports

[ https://issues.apache.org/jira/browse/HDFS-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur resolved HDFS-1392. Resolution: Duplicate duplicate of HDFS-1541 Improve namenode scalability by prioritizing

[jira] [Commented] (HDFS-1790) review use of synchronized methods in FSNamesystem

[ https://issues.apache.org/jira/browse/HDFS-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011753#comment-13011753 ] dhruba borthakur commented on HDFS-1790: incVolumeFailure(), isInSafeMode() and

[jira] [Commented] (HDFS-1779) After NameNode restart , Clients can not read partial files even after client invokes Sync.

[ https://issues.apache.org/jira/browse/HDFS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011584#comment-13011584 ] dhruba borthakur commented on HDFS-1779: If the app has invoked sync/hflush (as

[jira] [Commented] (HDFS-1120) Make DataNode's block-to-device placement policy pluggable

[ https://issues.apache.org/jira/browse/HDFS-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011526#comment-13011526 ] dhruba borthakur commented on HDFS-1120: Looks like a reasonable start. can we make

[jira] [Commented] (HDFS-1790) review use of synchronized methods in FSNamesystem

[ https://issues.apache.org/jira/browse/HDFS-1790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011564#comment-13011564 ] dhruba borthakur commented on HDFS-1790: The setting of safemode should be done

[jira] [Commented] (HDFS-1779) After NameNode restart , Clients can not read partial files even after client invokes Sync.

[ https://issues.apache.org/jira/browse/HDFS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011565#comment-13011565 ] dhruba borthakur commented on HDFS-1779: This seems to be a valid bug, would you

[jira] [Commented] (HDFS-1772) atime and mtime are different from hdfs:// and hftp://

[ https://issues.apache.org/jira/browse/HDFS-1772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011566#comment-13011566 ] dhruba borthakur commented on HDFS-1772: This is really mysterious. Is the first

[jira] [Commented] (HDFS-1779) After NameNode restart , Clients can not read partial files even after client invokes Sync.

[ https://issues.apache.org/jira/browse/HDFS-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13011567#comment-13011567 ] dhruba borthakur commented on HDFS-1779: Wait a minute, can you pl provide some

[jira] [Commented] (HDFS-1780) reduce need to rewrite fsimage on statrtup

[ https://issues.apache.org/jira/browse/HDFS-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13010794#comment-13010794 ] dhruba borthakur commented on HDFS-1780: There is another piece of work being done

[jira] [Created] (HDFS-1783) Ability for HDFS client to write replicas in parallel

Ability for HDFS client to write replicas in parallel - Key: HDFS-1783 URL: https://issues.apache.org/jira/browse/HDFS-1783 Project: Hadoop HDFS Issue Type: Improvement

[jira] [Commented] (HDFS-1783) Ability for HDFS client to write replicas in parallel

[ https://issues.apache.org/jira/browse/HDFS-1783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13010955#comment-13010955 ] dhruba borthakur commented on HDFS-1783: I have a HBase workload that has the hot

[jira] [Commented] (HDFS-1148) Convert FSDataset to ReadWriteLock

[ https://issues.apache.org/jira/browse/HDFS-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009940#comment-13009940 ] dhruba borthakur commented on HDFS-1148: I too have figured out lately that for

[jira] [Commented] (HDFS-1767) Delay second Block Reports until after cluster finishes startup, to improve startup times

[ https://issues.apache.org/jira/browse/HDFS-1767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009022#comment-13009022 ] dhruba borthakur commented on HDFS-1767: good stuff. This patch look good. In the

[jira] [Commented] (HDFS-1766) Datanode is marked dead, but datanode process is alive and verifying blocks

[ https://issues.apache.org/jira/browse/HDFS-1766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13009023#comment-13009023 ] dhruba borthakur commented on HDFS-1766: Yes, catching Throwable might be better.

[jira] Commented: (HDFS-1172) Blocks in newly completed files are considered under-replicated too quickly

[ https://issues.apache.org/jira/browse/HDFS-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13008665#comment-13008665 ] dhruba borthakur commented on HDFS-1172: putting it in pendingReplication means

[jira] Commented: (HDFS-1751) Intrinsic limits for HDFS files, directories

[ https://issues.apache.org/jira/browse/HDFS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13007802#comment-13007802 ] dhruba borthakur commented on HDFS-1751: can somebody pl explain the use-case why

[jira] Commented: (HDFS-1751) Intrinsic limits for HDFS files, directories

[ https://issues.apache.org/jira/browse/HDFS-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13007096#comment-13007096 ] dhruba borthakur commented on HDFS-1751: is there a way to integrate this into the

[jira] Commented: (HDFS-1594) When the disk becomes full Namenode is getting shutdown and not able to recover

[ https://issues.apache.org/jira/browse/HDFS-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13006527#comment-13006527 ] dhruba borthakur commented on HDFS-1594: @Devaraj: ur proposal to make the NN go

[jira] Commented: (HDFS-1594) When the disk becomes full Namenode is getting shutdown and not able to recover

[ https://issues.apache.org/jira/browse/HDFS-1594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13006335#comment-13006335 ] dhruba borthakur commented on HDFS-1594: another question related to this one. Can

[jira] Commented: (HDFS-1742) Provide hooks / callbacks to execute some code based on events happening in HDFS (file / directory creation, opening, closing, etc)

[ https://issues.apache.org/jira/browse/HDFS-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13006148#comment-13006148 ] dhruba borthakur commented on HDFS-1742: I agree that this is a useful feature, we

[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=13003809#comment-13003809 ] dhruba borthakur commented on HDFS-1295: Good stuf Matt, thanks for doing this.

[jira] Commented: (HDFS-1696) HDFS Federation: when build version doesn't match - datanode should wait (keep connecting) untill NN comes up with the right version

[ https://issues.apache.org/jira/browse/HDFS-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13003035#comment-13003035 ] dhruba borthakur commented on HDFS-1696: what if we get rid of the build version

[jira] Commented: (HDFS-1667) Consider redesign of block report processing

[ https://issues.apache.org/jira/browse/HDFS-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13003083#comment-13003083 ] dhruba borthakur commented on HDFS-1667: Hi Matt, if the namenode can do most of

  1   2   3   4   5   6   7   8   9   >