[jira] Commented: (HDFS-898) Sequential generation of block ids

[ https://issues.apache.org/jira/browse/HDFS-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803092#action_12803092 ] dhruba borthakur commented on HDFS-898: --- Thanks Konstantin for the explanation. I under

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803090#action_12803090 ] dhruba borthakur commented on HDFS-839: --- I am interested in doing (1) from Konstantin's

[jira] Commented: (HDFS-898) Sequential generation of block ids

[ https://issues.apache.org/jira/browse/HDFS-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803028#action_12803028 ] dhruba borthakur commented on HDFS-898: --- > 1. In case of corrupt blocks, when all gener

[jira] Commented: (HDFS-906) Remove MapReduce jars from raid lib directory

[ https://issues.apache.org/jira/browse/HDFS-906?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802107#action_12802107 ] dhruba borthakur commented on HDFS-906: --- I think this is a duplicate of HDFS-902. Pleas

[jira] Updated: (HDFS-902) TestRaidNode fails

[ https://issues.apache.org/jira/browse/HDFS-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-902: -- Component/s: contrib/raid > TestRaidNode fails > -- > > Key: HDFS

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801985#action_12801985 ] dhruba borthakur commented on HDFS-839: --- > the all-through-the-NN solution can simply

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801973#action_12801973 ] dhruba borthakur commented on HDFS-839: --- Todd: I agree that CPU is not what I am concer

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801705#action_12801705 ] dhruba borthakur commented on HDFS-839: --- > However, if it only synchronizes block repor

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12801701#action_12801701 ] dhruba borthakur commented on HDFS-839: --- > t seems like the network overhead of having

[jira] Commented: (HDFS-898) Sequential generation of block ids

[ https://issues.apache.org/jira/browse/HDFS-898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800978#action_12800978 ] dhruba borthakur commented on HDFS-898: --- >The prehistoric block problem is still releva

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800970#action_12800970 ] dhruba borthakur commented on HDFS-839: --- > what's the rationale for doing so? I am thi

[jira] Commented: (HDFS-822) Appends to already-finalized blocks can rename across volumes

[ https://issues.apache.org/jira/browse/HDFS-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800952#action_12800952 ] dhruba borthakur commented on HDFS-822: --- > But anyway my proposal is to disallow the ac

[jira] Commented: (HDFS-800) The last block of a file under construction may change to the COMPLETE state in response to getAdditionalBlock or completeFileInternal

[ https://issues.apache.org/jira/browse/HDFS-800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800918#action_12800918 ] dhruba borthakur commented on HDFS-800: --- Hi Hairong, can you pl explain (again) what ca

[jira] Commented: (HDFS-822) Appends to already-finalized blocks can rename across volumes

[ https://issues.apache.org/jira/browse/HDFS-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800915#action_12800915 ] dhruba borthakur commented on HDFS-822: --- If there is space in the same volume, then the

[jira] Commented: (HDFS-893) Synchronization other FSNamesystem information to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-893?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800717#action_12800717 ] dhruba borthakur commented on HDFS-893: --- another option is to make the datanode(s) send

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800714#action_12800714 ] dhruba borthakur commented on HDFS-839: --- > Do you think these information should be sen

[jira] Commented: (HDFS-839) The NameNode should forward block reports to BackupNode

[ https://issues.apache.org/jira/browse/HDFS-839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800212#action_12800212 ] dhruba borthakur commented on HDFS-839: --- Hi Wang, thanks for your document. It is very

[jira] Commented: (HDFS-895) Allow hflush/sync to occur in parallel with new writes to the file

[ https://issues.apache.org/jira/browse/HDFS-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799866#action_12799866 ] dhruba borthakur commented on HDFS-895: --- > Do we then allow multiple concurrent sync ca

[jira] Created: (HDFS-895) Allow hflush/sync to occur in parallel with new writes to the file

Allow hflush/sync to occur in parallel with new writes to the file -- Key: HDFS-895 URL: https://issues.apache.org/jira/browse/HDFS-895 Project: Hadoop HDFS Issue Type: Improvem

[jira] Commented: (HDFS-826) Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline

[ https://issues.apache.org/jira/browse/HDFS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799775#action_12799775 ] dhruba borthakur commented on HDFS-826: --- > To clarify by "client" you mean FileContext

[jira] Commented: (HDFS-826) Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline

[ https://issues.apache.org/jira/browse/HDFS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799503#action_12799503 ] dhruba borthakur commented on HDFS-826: --- > If the client gets an error it must close th

[jira] Commented: (HDFS-842) Serialize NN edits log as avro records

[ https://issues.apache.org/jira/browse/HDFS-842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799334#action_12799334 ] dhruba borthakur commented on HDFS-842: --- > 50% increase in writing is simply unacceptab

[jira] Commented: (HDFS-684) Use HAR filesystem to merge parity files

[ https://issues.apache.org/jira/browse/HDFS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799125#action_12799125 ] dhruba borthakur commented on HDFS-684: --- Another issue is that the Har-ing of parity fi

[jira] Updated: (HDFS-684) Use HAR filesystem to merge parity files

[ https://issues.apache.org/jira/browse/HDFS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-684: -- Status: Open (was: Patch Available) I am looking into the hadoop-tools issue. will comment soon.

[jira] Commented: (HDFS-879) FileStatus should have the visible length of the file

[ https://issues.apache.org/jira/browse/HDFS-879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798843#action_12798843 ] dhruba borthakur commented on HDFS-879: --- 2A. I liked this better than 2B. Add a new fil

[jira] Commented: (HDFS-878) FileStatus should have a field "isUnderConstruction"

[ https://issues.apache.org/jira/browse/HDFS-878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798284#action_12798284 ] dhruba borthakur commented on HDFS-878: --- I agree with Eli. We should not change FileSta

[jira] Commented: (HDFS-145) FSNameSystem#addStoredBlock does not handle inconsistent block length correctly

[ https://issues.apache.org/jira/browse/HDFS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797956#action_12797956 ] dhruba borthakur commented on HDFS-145: --- is this a code cleanup issue then? > FSNameSy

[jira] Commented: (HDFS-870) Topology is permanently cached

[ https://issues.apache.org/jira/browse/HDFS-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12797641#action_12797641 ] dhruba borthakur commented on HDFS-870: --- Does your network topology change so frequentl

[jira] Commented: (HDFS-826) Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline

[ https://issues.apache.org/jira/browse/HDFS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12796278#action_12796278 ] dhruba borthakur commented on HDFS-826: --- My thinking is that most hadoop apps should be

[jira] Commented: (HDFS-826) Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline

[ https://issues.apache.org/jira/browse/HDFS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794910#action_12794910 ] dhruba borthakur commented on HDFS-826: --- If we do not introduce Replicable, then applic

[jira] Updated: (HDFS-767) Job failure due to BlockMissingException

[ https://issues.apache.org/jira/browse/HDFS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-767: -- Resolution: Fixed Fix Version/s: 0.22.0 Hadoop Flags: [Reviewed] Status: Re

[jira] Commented: (HDFS-767) Job failure due to BlockMissingException

[ https://issues.apache.org/jira/browse/HDFS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794900#action_12794900 ] dhruba borthakur commented on HDFS-767: --- +1. code looks code. > Job failure due to Blo

[jira] Updated: (HDFS-767) Job failure due to BlockMissingException

[ https://issues.apache.org/jira/browse/HDFS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-767: -- Attachment: HDFS-767_4.txt I changed the name of the config to fs.client.retry.window.base to mat

[jira] Created: (HDFS-855) namenode can save images in parallel to all directories in fs.name.dir

namenode can save images in parallel to all directories in fs.name.dir -- Key: HDFS-855 URL: https://issues.apache.org/jira/browse/HDFS-855 Project: Hadoop HDFS Issue Type:

[jira] Created: (HDFS-854) Datanode should scan devices in parallel to generate block report

Datanode should scan devices in parallel to generate block report - Key: HDFS-854 URL: https://issues.apache.org/jira/browse/HDFS-854 Project: Hadoop HDFS Issue Type: Improvemen

[jira] Commented: (HDFS-853) The HDFS webUI should show a metric that summarizes whether the cluster is balanced regarding disk space usage

[ https://issues.apache.org/jira/browse/HDFS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794584#action_12794584 ] dhruba borthakur commented on HDFS-853: --- I would like a cluster-wide measure that descr

[jira] Assigned: (HDFS-850) Display more memory details on the web ui

[ https://issues.apache.org/jira/browse/HDFS-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur reassigned HDFS-850: - Assignee: Dmytro Molkov > Display more memory details on the web ui > -

[jira] Commented: (HDFS-853) The HDFS webUI should show a metric that summarizes whether the cluster is balanced regarding disk space usage

[ https://issues.apache.org/jira/browse/HDFS-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794473#action_12794473 ] dhruba borthakur commented on HDFS-853: --- We can calculate the variance of space-usage

[jira] Created: (HDFS-853) The HDFS webUI should show a metric that summarizes whether the cluster is balanced regarding disk space usage

The HDFS webUI should show a metric that summarizes whether the cluster is balanced regarding disk space usage -- Key: HDFS-853 URL: https://issues.apache.

[jira] Commented: (HDFS-814) Add an api to get the visible length of a DFSDataInputStream.

[ https://issues.apache.org/jira/browse/HDFS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794446#action_12794446 ] dhruba borthakur commented on HDFS-814: --- > but it has the following issue: Applications

[jira] Updated: (HDFS-767) Job failure due to BlockMissingException

[ https://issues.apache.org/jira/browse/HDFS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-767: -- Status: Open (was: Patch Available) Hi Ning, can we get a few more minor issues fixed: {quote}

[jira] Updated: (HDFS-94) The "Heap Size" in HDFS web ui may not be accurate

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

[jira] Updated: (HDFS-762) Trying to start the balancer throws a NPE

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

[jira] Commented: (HDFS-762) Trying to start the balancer throws a NPE

[ https://issues.apache.org/jira/browse/HDFS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12794261#action_12794261 ] dhruba borthakur commented on HDFS-762: --- The two failed tests are org.apache.hadoop.hd

[jira] Commented: (HDFS-94) The "Heap Size" in HDFS web ui may not be accurate

[ https://issues.apache.org/jira/browse/HDFS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793836#action_12793836 ] dhruba borthakur commented on HDFS-94: -- The failed tests are org.apache.hadoop.hdfs.serv

[jira] Commented: (HDFS-814) Add an api to get the visible length of a DFSDataInputStream.

[ https://issues.apache.org/jira/browse/HDFS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793728#action_12793728 ] dhruba borthakur commented on HDFS-814: --- Code looks good. Can we also enhance DFSClient

[jira] Commented: (HDFS-630) In DFSOutputStream.nextBlockOutputStream(), the client can exclude specific datanodes when locating the next block.

[ https://issues.apache.org/jira/browse/HDFS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793715#action_12793715 ] dhruba borthakur commented on HDFS-630: --- > update versionID in 0.21 and trunk to 53L an

[jira] Assigned: (HDFS-94) The "Heap Size" in HDFS web ui may not be accurate

[ https://issues.apache.org/jira/browse/HDFS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur reassigned HDFS-94: Assignee: Dmytro Molkov > The "Heap Size" in HDFS web ui may not be accurate > ---

[jira] Commented: (HDFS-94) The "Heap Size" in HDFS web ui may not be accurate

[ https://issues.apache.org/jira/browse/HDFS-94?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793702#action_12793702 ] dhruba borthakur commented on HDFS-94: -- Thanks Dmytro for the patch. @Nicholas: please l

[jira] Commented: (HDFS-843) Add HTTP POST/PUT/DELETE support for web servers in datanodes

[ https://issues.apache.org/jira/browse/HDFS-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793701#action_12793701 ] dhruba borthakur commented on HDFS-843: --- Thanks Allen. How will this interact with the

[jira] Commented: (HDFS-843) Add HTTP POST/PUT/DELETE support for web servers in datanodes

[ https://issues.apache.org/jira/browse/HDFS-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793436#action_12793436 ] dhruba borthakur commented on HDFS-843: --- Can you pl post the use-case for this one? >

[jira] Commented: (HDFS-762) Trying to start the balancer throws a NPE

[ https://issues.apache.org/jira/browse/HDFS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793429#action_12793429 ] dhruba borthakur commented on HDFS-762: --- +1. Code looks good. > Trying to start the ba

[jira] Assigned: (HDFS-762) Trying to start the balancer throws a NPE

[ https://issues.apache.org/jira/browse/HDFS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur reassigned HDFS-762: - Assignee: Cristian Ivascu > Trying to start the balancer throws a NPE > ---

[jira] Updated: (HDFS-762) Trying to start the balancer throws a NPE

[ https://issues.apache.org/jira/browse/HDFS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-762: -- Status: Patch Available (was: Open) > Trying to start the balancer throws a NPE > --

[jira] Commented: (HDFS-814) Add an api to get the visible length of a DFSDataInputStream.

[ https://issues.apache.org/jira/browse/HDFS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12793402#action_12793402 ] dhruba borthakur commented on HDFS-814: --- Can this be added to 0.21 as well? > Add an a

[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-tabpanel&focusedCommentId=12793096#action_12793096 ] dhruba borthakur commented on HDFS-347: --- This is turning out to be interesting one! >

[jira] Commented: (HDFS-101) DFS write pipeline : DFSClient sometimes does not detect second datanode failure

[ https://issues.apache.org/jira/browse/HDFS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792677#action_12792677 ] dhruba borthakur commented on HDFS-101: --- +1 Code looks good. The unit test will be diff

[jira] Commented: (HDFS-245) Create symbolic links in HDFS

[ https://issues.apache.org/jira/browse/HDFS-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792590#action_12792590 ] dhruba borthakur commented on HDFS-245: --- Your latest proposal looks good. > Create sy

[jira] Commented: (HDFS-826) Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline

[ https://issues.apache.org/jira/browse/HDFS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792502#action_12792502 ] dhruba borthakur commented on HDFS-826: --- One question that arises is what to return whe

[jira] Updated: (HDFS-826) Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline

[ https://issues.apache.org/jira/browse/HDFS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-826: -- Attachment: ReplicableHdfs.txt Returns the number of valid replicas of block that is currently be

[jira] Commented: (HDFS-101) DFS write pipeline : DFSClient sometimes does not detect second datanode failure

[ https://issues.apache.org/jira/browse/HDFS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792473#action_12792473 ] dhruba borthakur commented on HDFS-101: --- you are right. transferBlocks could take multi

[jira] Commented: (HDFS-101) DFS write pipeline : DFSClient sometimes does not detect second datanode failure

[ https://issues.apache.org/jira/browse/HDFS-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792358#action_12792358 ] dhruba borthakur commented on HDFS-101: --- I am looking at the patch too. Looks good at f

[jira] Created: (HDFS-841) error while checkpointing edits log gets ignored

error while checkpointing edits log gets ignored Key: HDFS-841 URL: https://issues.apache.org/jira/browse/HDFS-841 Project: Hadoop HDFS Issue Type: Bug Components: name-node

[jira] Commented: (HDFS-684) Use HAR filesystem to merge parity files

[ https://issues.apache.org/jira/browse/HDFS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791700#action_12791700 ] dhruba borthakur commented on HDFS-684: --- This part of the code looks good. I will wait

[jira] Commented: (HDFS-826) Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline

[ https://issues.apache.org/jira/browse/HDFS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12791682#action_12791682 ] dhruba borthakur commented on HDFS-826: --- Hi Hairong, would you support creating a new A

[jira] Created: (HDFS-839) The NameNode should forward block reports to BackupNode

The NameNode should forward block reports to BackupNode --- Key: HDFS-839 URL: https://issues.apache.org/jira/browse/HDFS-839 Project: Hadoop HDFS Issue Type: New Feature Componen

[jira] Commented: (HDFS-724) Pipeline close hangs if one of the datanode is not responsive.

[ https://issues.apache.org/jira/browse/HDFS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790424#action_12790424 ] dhruba borthakur commented on HDFS-724: --- +1. I was able to look at the entire code and

[jira] Commented: (HDFS-767) Job failure due to BlockMissingException

[ https://issues.apache.org/jira/browse/HDFS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790415#action_12790415 ] dhruba borthakur commented on HDFS-767: --- Steve: can we leave this patch to continue to

[jira] Commented: (HDFS-767) Job failure due to BlockMissingException

[ https://issues.apache.org/jira/browse/HDFS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790294#action_12790294 ] dhruba borthakur commented on HDFS-767: --- Is there any java Random class that already ta

[jira] Commented: (HDFS-821) Garbage collect datanode tmp dirs

[ https://issues.apache.org/jira/browse/HDFS-821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789966#action_12789966 ] dhruba borthakur commented on HDFS-821: --- what kind of heuristics do you have in mind to

[jira] Commented: (HDFS-822) Appends to already-finalized blocks can rename across volumes

[ https://issues.apache.org/jira/browse/HDFS-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789964#action_12789964 ] dhruba borthakur commented on HDFS-822: --- This looks like a bug that might be good to fi

[jira] Commented: (HDFS-724) Pipeline close hangs if one of the datanode is not responsive.

[ https://issues.apache.org/jira/browse/HDFS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789658#action_12789658 ] dhruba borthakur commented on HDFS-724: --- This is s tough one to review. phew! > Pipeli

[jira] Updated: (HDFS-729) fsck option to list only corrupted files

[ https://issues.apache.org/jira/browse/HDFS-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-729: -- Attachment: badFiles2.txt merged patch with latest trunk > fsck option to list only corrupted fi

[jira] Commented: (HDFS-826) Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline

[ https://issues.apache.org/jira/browse/HDFS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789638#action_12789638 ] dhruba borthakur commented on HDFS-826: --- > Would polling be good enough for your applic

[jira] Commented: (HDFS-826) Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline

[ https://issues.apache.org/jira/browse/HDFS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789636#action_12789636 ] dhruba borthakur commented on HDFS-826: --- Actually, my original proposal might work with

[jira] Commented: (HDFS-826) Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline

[ https://issues.apache.org/jira/browse/HDFS-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788954#action_12788954 ] dhruba borthakur commented on HDFS-826: --- The application is such that it can start writ

[jira] Created: (HDFS-826) Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline

Allow a mechanism for an application to detect that datanode(s) have died in the write pipeline Key: HDFS-826 URL: https://issues.apache.org/jira/browse/HDFS-826

[jira] Commented: (HDFS-808) Implement something like PAR2 support?

[ https://issues.apache.org/jira/browse/HDFS-808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787988#action_12787988 ] dhruba borthakur commented on HDFS-808: --- HDFS-503 has a parity file for every HDFS file

[jira] Commented: (HDFS-811) Additional tests(Unit tests & Functional tests) for HDFS-457.

[ https://issues.apache.org/jira/browse/HDFS-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787986#action_12787986 ] dhruba borthakur commented on HDFS-811: --- another useful thing for a system adminstrator

[jira] Commented: (HDFS-814) Add an api to get the visible length of a DFSDataInputStream.

[ https://issues.apache.org/jira/browse/HDFS-814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787982#action_12787982 ] dhruba borthakur commented on HDFS-814: --- The "visible length" of a file should be the s

[jira] Commented: (HDFS-724) Pipeline close hangs if one of the datanode is not responsive.

[ https://issues.apache.org/jira/browse/HDFS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12787978#action_12787978 ] dhruba borthakur commented on HDFS-724: --- I am still looking at the patch, two comments:

[jira] Commented: (HDFS-788) Datanode behaves badly when one disk is very low on space

[ https://issues.apache.org/jira/browse/HDFS-788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783405#action_12783405 ] dhruba borthakur commented on HDFS-788: --- I agree, Being conservative is better than fai

[jira] Commented: (HDFS-762) Trying to start the balancer throws a NPE

[ https://issues.apache.org/jira/browse/HDFS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781900#action_12781900 ] dhruba borthakur commented on HDFS-762: --- If this is a real problem with the Balancer, t

[jira] Commented: (HDFS-684) Use HAR filesystem to merge parity files

[ https://issues.apache.org/jira/browse/HDFS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781883#action_12781883 ] dhruba borthakur commented on HDFS-684: --- Hi Rodrigo, thanks for the info. I guess it is

[jira] Commented: (HDFS-782) dynamic replication

[ https://issues.apache.org/jira/browse/HDFS-782?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780997#action_12780997 ] dhruba borthakur commented on HDFS-782: --- This is a pretty complex idea and would be har

[jira] Commented: (HDFS-684) Use HAR filesystem to merge parity files

[ https://issues.apache.org/jira/browse/HDFS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780996#action_12780996 ] dhruba borthakur commented on HDFS-684: --- Is there a downside to crearting a HAR for eve

[jira] Issue Comment Edited: (HDFS-684) Use HAR filesystem to merge parity files

[ https://issues.apache.org/jira/browse/HDFS-684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780996#action_12780996 ] dhruba borthakur edited comment on HDFS-684 at 11/21/09 3:23 PM: --

[jira] Updated: (HDFS-780) Revive TestFuseDFS

[ https://issues.apache.org/jira/browse/HDFS-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-780: -- Component/s: contrib/fuse-dfs > Revive TestFuseDFS > -- > > Key:

[jira] Assigned: (HDFS-767) Job failure due to BlockMissingException

[ https://issues.apache.org/jira/browse/HDFS-767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur reassigned HDFS-767: - Assignee: Ning Zhang > Job failure due to BlockMissingException > -

[jira] Updated: (HDFS-763) DataBlockScanner reporting of bad blocks is slightly misleading

[ https://issues.apache.org/jira/browse/HDFS-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-763: -- Resolution: Fixed Fix Version/s: 0.22.0 Hadoop Flags: [Reviewed] Status: Re

[jira] Updated: (HDFS-756) libhdfs unit tests do not run

[ https://issues.apache.org/jira/browse/HDFS-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-756: -- Status: Open (was: Patch Available) Let's use the snapshot jar for now. > libhdfs unit tests do

[jira] Commented: (HDFS-724) Pipeline close hangs if one of the datanode is not responsive.

[ https://issues.apache.org/jira/browse/HDFS-724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778549#action_12778549 ] dhruba borthakur commented on HDFS-724: --- > a heartbeat is sent only if the connection i

[jira] Updated: (HDFS-729) fsck option to list only corrupted files

[ https://issues.apache.org/jira/browse/HDFS-729?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-729: -- Attachment: badFiles.txt This patch allows an API to retrieve the list of files that have blocks

[jira] Updated: (HDFS-596) Memory leak in libhdfs: hdfsFreeFileInfo() in libhdfs does not free memory for mOwner and mGroup

[ https://issues.apache.org/jira/browse/HDFS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-596: -- Resolution: Fixed Fix Version/s: 0.22.0 0.21.0 Hadoop Flags: [Revie

[jira] Commented: (HDFS-596) Memory leak in libhdfs: hdfsFreeFileInfo() in libhdfs does not free memory for mOwner and mGroup

[ https://issues.apache.org/jira/browse/HDFS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778229#action_12778229 ] dhruba borthakur commented on HDFS-596: --- I just committed this. Thanks Eli & Zhang. >

[jira] Assigned: (HDFS-596) Memory leak in libhdfs: hdfsFreeFileInfo() in libhdfs does not free memory for mOwner and mGroup

[ https://issues.apache.org/jira/browse/HDFS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur reassigned HDFS-596: - Assignee: Zhang Bingjun > Memory leak in libhdfs: hdfsFreeFileInfo() in libhdfs does not fr

[jira] Updated: (HDFS-596) Memory leak in libhdfs: hdfsFreeFileInfo() in libhdfs does not free memory for mOwner and mGroup

[ https://issues.apache.org/jira/browse/HDFS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-596: -- Status: Patch Available (was: Open) Triggering HadoopQA tests (mostly a formality for this one).

[jira] Updated: (HDFS-596) Memory leak in libhdfs: hdfsFreeFileInfo() in libhdfs does not free memory for mOwner and mGroup

[ https://issues.apache.org/jira/browse/HDFS-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur updated HDFS-596: -- Status: Open (was: Patch Available) > Memory leak in libhdfs: hdfsFreeFileInfo() in libhdfs does

[jira] Commented: (HDFS-630) In DFSOutputStream.nextBlockOutputStream(), the client can exclude specific datanodes when locating the next block.

[ https://issues.apache.org/jira/browse/HDFS-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778057#action_12778057 ] dhruba borthakur commented on HDFS-630: --- It would be nice to have a patch for trunk and

[jira] Resolved: (HDFS-769) test-c++-libhdfs constantly fails

[ https://issues.apache.org/jira/browse/HDFS-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dhruba borthakur resolved HDFS-769. --- Resolution: Duplicate duplicate of HDFS-756 > test-c++-libhdfs constantly fails >

<    3   4   5   6   7   8   9   10   11   >