[jira] [Updated] (HDFS-4851) Deadlock in pipeline recovery

[ https://issues.apache.org/jira/browse/HDFS-4851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-4851: -- Resolution: Duplicate Status: Resolved (was: Patch Available) Dupe on commit of HDFS-5016, fixe

[jira] [Commented] (HDFS-5036) Namenode safemode is on and is misleading on webpage

[ https://issues.apache.org/jira/browse/HDFS-5036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720445#comment-13720445 ] Suresh Srinivas commented on HDFS-5036: --- If this is not happening on an Apache releas

[jira] [Updated] (HDFS-5016) Deadlock in pipeline recovery causes Datanode to be marked dead

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

[jira] [Created] (HDFS-5036) Namenode safemode is on and is misleading on webpage

Raghu C Doppalapudi created HDFS-5036: - Summary: Namenode safemode is on and is misleading on webpage Key: HDFS-5036 URL: https://issues.apache.org/jira/browse/HDFS-5036 Project: Hadoop HDFS

[jira] [Commented] (HDFS-5016) Deadlock in pipeline recovery causes Datanode to be marked dead

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720427#comment-13720427 ] Hadoop QA commented on HDFS-5016: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (HDFS-2906) NullPointerExeception in BlockReceiver on DataNode restart.

[ https://issues.apache.org/jira/browse/HDFS-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-2906: Attachment: HDFS-2906.patch Simple patch to avoid NPE. Instead throwing IOException > NullPointerEx

[jira] [Commented] (HDFS-5035) getFileLinkStatus and rename do not correctly check permissions of symlinks

[ https://issues.apache.org/jira/browse/HDFS-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720404#comment-13720404 ] Hadoop QA commented on HDFS-5035: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Updated] (HDFS-5016) Deadlock in pipeline recovery causes Datanode to be marked dead

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-5016: -- Summary: Deadlock in pipeline recovery causes Datanode to be marked dead (was: Deadlock in pipe

[jira] [Updated] (HDFS-5016) Deadlock in pipeline recovery causes Datanodes to be marked dead

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-5016: -- Summary: Deadlock in pipeline recovery causes Datanodes to be marked dead (was: Heartbeating th

[jira] [Commented] (HDFS-4953) enable HDFS local reads via mmap

[ https://issues.apache.org/jira/browse/HDFS-4953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720384#comment-13720384 ] Tsuyoshi OZAWA commented on HDFS-4953: -- This work is very interesting to increase the

[jira] [Commented] (HDFS-5016) Heartbeating thread blocks under some failure conditions leading to loss of datanodes

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720374#comment-13720374 ] Andrew Wang commented on HDFS-5016: --- +1 LGTM. It'd be great if you dupe HDFS-4851 too whe

[jira] [Updated] (HDFS-5016) Heartbeating thread blocks under some failure conditions leading to loss of datanodes

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-5016: -- Attachment: HDFS-5016.3.patch Updated patch to address the comments. > Heartbea

[jira] [Commented] (HDFS-5016) Heartbeating thread blocks under some failure conditions leading to loss of datanodes

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720364#comment-13720364 ] Hadoop QA commented on HDFS-5016: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (HDFS-5035) getFileLinkStatus and rename do not correctly check permissions of symlinks

[ https://issues.apache.org/jira/browse/HDFS-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-5035: -- Target Version/s: 2.1.0-beta Status: Patch Available (was: Open) > getFileLinkStatus

[jira] [Updated] (HDFS-5035) getFileLinkStatus and rename do not correctly check permissions of symlinks

[ https://issues.apache.org/jira/browse/HDFS-5035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-5035: -- Attachment: hdfs-5035-1.patch Patch attached, pretty simple impl since it reuses what I did for HDFS-476

[jira] [Created] (HDFS-5035) getFileLinkStatus and rename do not correctly check permissions of symlinks

Andrew Wang created HDFS-5035: - Summary: getFileLinkStatus and rename do not correctly check permissions of symlinks Key: HDFS-5035 URL: https://issues.apache.org/jira/browse/HDFS-5035 Project: Hadoop HDF

[jira] [Commented] (HDFS-5016) Heartbeating thread blocks under some failure conditions leading to loss of datanodes

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720360#comment-13720360 ] Andrew Wang commented on HDFS-5016: --- bq. Can you explain why it is not a good idea? I th

[jira] [Updated] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-4979: -- Resolution: Fixed Fix Version/s: 2.1.0-beta Status: Resolved (was: Patch Avail

[jira] [Commented] (HDFS-5016) Heartbeating thread blocks under some failure conditions leading to loss of datanodes

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720337#comment-13720337 ] Suresh Srinivas commented on HDFS-5016: --- bq. We probably don't want to stick the enti

[jira] [Commented] (HDFS-5016) Heartbeating thread blocks under some failure conditions leading to loss of datanodes

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720329#comment-13720329 ] Andrew Wang commented on HDFS-5016: --- Patch looks good, and I agree we can just close out

[jira] [Updated] (HDFS-5025) Record ClientId and CallId in EditLog to enable rebuilding retry cache in case of HA failover

[ https://issues.apache.org/jira/browse/HDFS-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-5025: Attachment: HDFS-5025.001.patch Update the patch: 1. Add the functionality to rebuild retry cache based on e

[jira] [Updated] (HDFS-5016) Heartbeating thread blocks under some failure conditions leading to loss of datanodes

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-5016: -- Attachment: HDFS-5016.2.patch New patch adds an undocumented configuration for xceiver thread st

[jira] [Commented] (HDFS-5016) Heartbeating thread blocks under some failure conditions leading to loss of datanodes

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720279#comment-13720279 ] Suresh Srinivas commented on HDFS-5016: --- bq. I agree with Todd, this looks like the s

[jira] [Updated] (HDFS-5013) Improve HDFS HA document

[ https://issues.apache.org/jira/browse/HDFS-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated HDFS-5013: -- Attachment: HDFS-5013.patch > Improve HDFS HA document > > >

[jira] [Updated] (HDFS-5013) Improve HDFS HA document

[ https://issues.apache.org/jira/browse/HDFS-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated HDFS-5013: -- Attachment: (was: HDFS-5013.patch) > Improve HDFS HA document >

[jira] [Commented] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720203#comment-13720203 ] Suresh Srinivas commented on HDFS-4979: --- BTW, yesterday I meant to post this comment,

[jira] [Comment Edited] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720203#comment-13720203 ] Suresh Srinivas edited comment on HDFS-4979 at 7/25/13 11:08 PM:

[jira] [Commented] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720202#comment-13720202 ] Suresh Srinivas commented on HDFS-4979: --- bq. Also I don't think CacheEntry#state need

[jira] [Commented] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720192#comment-13720192 ] Jing Zhao commented on HDFS-4979: - bq. Also I don't think CacheEntry#state needs to be vola

[jira] [Updated] (HDFS-5013) Improve HDFS HA document

[ https://issues.apache.org/jira/browse/HDFS-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated HDFS-5013: -- Attachment: HDFS-5013.patch > Improve HDFS HA document > > >

[jira] [Updated] (HDFS-5013) Improve HDFS HA document

[ https://issues.apache.org/jira/browse/HDFS-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated HDFS-5013: -- Attachment: HDFS-5013.patch > Improve HDFS HA document > > >

[jira] [Updated] (HDFS-5013) Improve HDFS HA document

[ https://issues.apache.org/jira/browse/HDFS-5013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Siddharth Wagle updated HDFS-5013: -- Attachment: (was: HDFS-5013.patch) > Improve HDFS HA document >

[jira] [Commented] (HDFS-4019) FSShell should support creating symlinks

[ https://issues.apache.org/jira/browse/HDFS-4019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720101#comment-13720101 ] Arpit Agarwal commented on HDFS-4019: - Hi Colin, It looks like with this patch {{FileC

[jira] [Commented] (HDFS-5021) FileSystem#delete and FileSystem#rename should operate on symlinks, not their targets

[ https://issues.apache.org/jira/browse/HDFS-5021?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720099#comment-13720099 ] Andrew Wang commented on HDFS-5021: --- Hey Colin, These cases are covered by our existing

[jira] [Updated] (HDFS-5034) Remove debug prints from getFileLinkInfo

[ https://issues.apache.org/jira/browse/HDFS-5034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-5034: -- Attachment: hdfs-5034-1.patch Trivial patch attached. > Remove debug prints from getFil

[jira] [Created] (HDFS-5034) Remove debug prints from getFileLinkInfo

Andrew Wang created HDFS-5034: - Summary: Remove debug prints from getFileLinkInfo Key: HDFS-5034 URL: https://issues.apache.org/jira/browse/HDFS-5034 Project: Hadoop HDFS Issue Type: Improvement

[jira] [Commented] (HDFS-3302) Review and improve HDFS trash documentation

[ https://issues.apache.org/jira/browse/HDFS-3302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720015#comment-13720015 ] David Ongaro commented on HDFS-3302: Why is this "Major" priority and still open? The c

[jira] [Commented] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719944#comment-13719944 ] Colin Patrick McCabe commented on HDFS-4979: I'm still concerned about the magi

[jira] [Updated] (HDFS-5033) Bad error message for fs -put/copyFromLocal if user doesn't have permissions to read the source

[ https://issues.apache.org/jira/browse/HDFS-5033?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-5033: -- Labels: noob (was: ) > Bad error message for fs -put/copyFromLocal if user doesn't have permissions

[jira] [Created] (HDFS-5033) Bad error message for fs -put/copyFromLocal if user doesn't have permissions to read the source

Karthik Kambatla created HDFS-5033: -- Summary: Bad error message for fs -put/copyFromLocal if user doesn't have permissions to read the source Key: HDFS-5033 URL: https://issues.apache.org/jira/browse/HDFS-5033

[jira] [Commented] (HDFS-4882) Namenode LeaseManager checkLeases() runs into infinite loop

[ https://issues.apache.org/jira/browse/HDFS-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719847#comment-13719847 ] Shrijeet Paliwal commented on HDFS-4882: Just wanted to report that we have been hi

[jira] [Commented] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719829#comment-13719829 ] Suresh Srinivas commented on HDFS-4979: --- [~cmccabe] Please look at this patch and HAD

[jira] [Commented] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719827#comment-13719827 ] Suresh Srinivas commented on HDFS-4979: --- Given that this is a change that should go i

[jira] [Commented] (HDFS-4979) Implement retry cache on the namenode

[ https://issues.apache.org/jira/browse/HDFS-4979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719824#comment-13719824 ] Jing Zhao commented on HDFS-4979: - The new patch looks pretty good to me. +1 for the patch.

[jira] [Commented] (HDFS-5027) On startup, DN should scan volumes in parallel

[ https://issues.apache.org/jira/browse/HDFS-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719809#comment-13719809 ] Aaron T. Myers commented on HDFS-5027: -- Thanks, Kihwal. > On startup,

[jira] [Commented] (HDFS-5027) On startup, DN should scan volumes in parallel

[ https://issues.apache.org/jira/browse/HDFS-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719806#comment-13719806 ] Kihwal Lee commented on HDFS-5027: -- I started reviewing it but sidetracked. I will get bac

[jira] [Commented] (HDFS-5027) On startup, DN should scan volumes in parallel

[ https://issues.apache.org/jira/browse/HDFS-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719722#comment-13719722 ] Aaron T. Myers commented on HDFS-5027: -- Thanks for the comment, Kihwal. If you have ti

[jira] [Commented] (HDFS-5014) BPOfferService#processCommandFromActor() synchronization on namenode RPC call delays IBR to Active NN, if Stanby NN is unstable

[ https://issues.apache.org/jira/browse/HDFS-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719691#comment-13719691 ] Hadoop QA commented on HDFS-5014: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Created] (HDFS-5032) Write pipeline failures caused by slow or busy disk may not be handled properly.

Kihwal Lee created HDFS-5032: Summary: Write pipeline failures caused by slow or busy disk may not be handled properly. Key: HDFS-5032 URL: https://issues.apache.org/jira/browse/HDFS-5032 Project: Hadoop

[jira] [Commented] (HDFS-5031) BlockScanner scans the block multiple times and on restart scans everything

[ https://issues.apache.org/jira/browse/HDFS-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719666#comment-13719666 ] Hadoop QA commented on HDFS-5031: - {color:green}+1 overall{color}. Here are the results of

[jira] [Updated] (HDFS-4927) CreateEditsLog creates inodes with an invalid inode ID, which then cannot be loaded by a namenode.

[ https://issues.apache.org/jira/browse/HDFS-4927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-4927: -- Fix Version/s: 2.1.0-beta 3.0.0 > CreateEditsLog creates inodes w

[jira] [Commented] (HDFS-5027) On startup, DN should scan volumes in parallel

[ https://issues.apache.org/jira/browse/HDFS-5027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719622#comment-13719622 ] Kihwal Lee commented on HDFS-5027: -- At this stage of datanode startup, it is mostly I/O bo

[jira] [Updated] (HDFS-5014) BPOfferService#processCommandFromActor() synchronization on namenode RPC call delays IBR to Active NN, if Stanby NN is unstable

[ https://issues.apache.org/jira/browse/HDFS-5014?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5014: Affects Version/s: 3.0.0 Status: Patch Available (was: Open) > BPOfferService#processCommandFrom

[jira] [Updated] (HDFS-5031) BlockScanner scans the block multiple times and on restart scans everything

[ https://issues.apache.org/jira/browse/HDFS-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5031: Attachment: HDFS-5031.patch Attached the patch > BlockScanner scans the block multiple times and on

[jira] [Updated] (HDFS-5031) BlockScanner scans the block multiple times and on restart scans everything

[ https://issues.apache.org/jira/browse/HDFS-5031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5031: Status: Patch Available (was: Open) > BlockScanner scans the block multiple times and on restart scans everythi

[jira] [Created] (HDFS-5031) BlockScanner scans the block multiple times and on restart scans everything

Vinay created HDFS-5031: --- Summary: BlockScanner scans the block multiple times and on restart scans everything Key: HDFS-5031 URL: https://issues.apache.org/jira/browse/HDFS-5031 Project: Hadoop HDFS

[jira] [Commented] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid

[ https://issues.apache.org/jira/browse/HDFS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719501#comment-13719501 ] Hadoop QA commented on HDFS-4325: - {color:red}-1 overall{color}. Here are the results of t

[jira] [Updated] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid

[ https://issues.apache.org/jira/browse/HDFS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Binglin Chang updated HDFS-4325: Attachment: HDFS-4325.v1.patch Because ClientProtocol is in RPC and param dirPerm is defined as "req

[jira] [Commented] (HDFS-5016) Heartbeating thread blocks under some failure conditions leading to loss of datanodes

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719407#comment-13719407 ] Tsz Wo (Nicholas), SZE commented on HDFS-5016: -- > ... I think the timrout sho

[jira] [Updated] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid

[ https://issues.apache.org/jira/browse/HDFS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Binglin Chang updated HDFS-4325: Status: Patch Available (was: Open) > ClientProtocol.createSymlink parameter dirPerm invalid >

[jira] [Updated] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid

[ https://issues.apache.org/jira/browse/HDFS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Binglin Chang updated HDFS-4325: Target Version/s: 2.1.0-beta (was: 2.0.3-alpha) Affects Version/s: (was: 2.0.2-alpha)

[jira] [Commented] (HDFS-5016) Heartbeating thread blocks under some failure conditions leading to loss of datanodes

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719356#comment-13719356 ] Nicolas Liochon commented on HDFS-5016: --- nice analysis. as Devaraj, I think the timro

[jira] [Commented] (HDFS-5016) Heartbeating thread blocks under some failure conditions leading to loss of datanodes

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719342#comment-13719342 ] Suresh Srinivas commented on HDFS-5016: --- I considered it and decided against it. It i

[jira] [Commented] (HDFS-5016) Heartbeating thread blocks under some failure conditions leading to loss of datanodes

[ https://issues.apache.org/jira/browse/HDFS-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719332#comment-13719332 ] Tsz Wo (Nicholas), SZE commented on HDFS-5016: -- > ... only minor nit is that w