[jira] [Commented] (HDFS-5517) Lower the default maximum number of blocks per file

[ https://issues.apache.org/jira/browse/HDFS-5517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13824840#comment-13824840 ] Vinay commented on HDFS-5517: - +1 ATM. Thanks for Jira and patch. Lower the default maximum

[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-tabpanelfocusedCommentId=13824842#comment-13824842 ] Vinay commented on HDFS-5014: - Thanks Chris. Please can someone else too look at the patch. ?

[jira] [Commented] (HDFS-5428) under construction files deletion after snapshot+checkpoint+nn restart leads nn safemode

[ https://issues.apache.org/jira/browse/HDFS-5428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13824844#comment-13824844 ] Vinay commented on HDFS-5428: - +1, latest patch looks good. test failure looks unrelated.

[jira] [Commented] (HDFS-5453) Support fine grain locking in FSNamesystem

[ https://issues.apache.org/jira/browse/HDFS-5453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13824862#comment-13824862 ] Vinay commented on HDFS-5453: - Looks curious Daryn, looking forward for the implementation of

[jira] [Updated] (HDFS-5355) Hsync Metrics error

[ https://issues.apache.org/jira/browse/HDFS-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-5355: -- Component/s: (was: test) datanode Hsync Metrics error

[jira] [Updated] (HDFS-5372) In FSNamesystem, hasReadLock() returns false if the current thread holds the write lock

[ https://issues.apache.org/jira/browse/HDFS-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-5372: Attachment: HDFS-5372.patch uploading a simple patch to 1. remove hasReadOrWriteLock() 2. and returning true for

[jira] [Updated] (HDFS-5372) In FSNamesystem, hasReadLock() returns false if the current thread holds the write lock

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

[jira] [Commented] (HDFS-5355) Hsync Metrics error

[ https://issues.apache.org/jira/browse/HDFS-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13824899#comment-13824899 ] Uma Maheswara Rao G commented on HDFS-5355: --- Thanks for filing JIRA and working

[jira] [Commented] (HDFS-5372) In FSNamesystem, hasReadLock() returns false if the current thread holds the write lock

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

[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-tabpanelfocusedCommentId=13824928#comment-13824928 ] Uma Maheswara Rao G commented on HDFS-5014: --- Thanks for working on this. I think

[jira] [Assigned] (HDFS-5372) In FSNamesystem, hasReadLock() returns false if the current thread holds the write lock

[ https://issues.apache.org/jira/browse/HDFS-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE reassigned HDFS-5372: Assignee: Vinay (was: Tsz Wo (Nicholas), SZE) No problem. I am glad that

[jira] [Updated] (HDFS-5372) In FSNamesystem, hasReadLock() returns false if the current thread holds the write lock

[ https://issues.apache.org/jira/browse/HDFS-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-5372: - Hadoop Flags: Reviewed +1 patch looks good. (Has to go. Will commit this later.

[jira] [Commented] (HDFS-5372) In FSNamesystem, hasReadLock() returns false if the current thread holds the write lock

[ https://issues.apache.org/jira/browse/HDFS-5372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13824932#comment-13824932 ] Uma Maheswara Rao G commented on HDFS-5372: --- Thanks Vinay for the patch and

[jira] [Updated] (HDFS-5355) Hsync Metrics error

[ https://issues.apache.org/jira/browse/HDFS-5355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-5355: -- Status: Open (was: Patch Available) Hsync Metrics error ---

[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-tabpanelfocusedCommentId=13825087#comment-13825087 ] Vinay commented on HDFS-5014: - Thanks Uma for looking at the Jira. I think it should work fine

[jira] [Commented] (HDFS-5372) In FSNamesystem, hasReadLock() returns false if the current thread holds the write lock

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

[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-tabpanelfocusedCommentId=13825118#comment-13825118 ] Vinay commented on HDFS-5014: - Please review and let me know your thoughts.. thanks

[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: Attachment: HDFS-5014-v2.patch Attached HDFS-5014-v2.patch with the suggested approach. registerting to namenode

[jira] [Updated] (HDFS-3987) Support webhdfs over HTTPS

[ https://issues.apache.org/jira/browse/HDFS-3987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai updated HDFS-3987: - Attachment: HDFS-3987.005.patch Support webhdfs over HTTPS --

[jira] [Work stopped] (HDFS-5392) Unify the initialization of the hsftp and swebhdfs clients

[ https://issues.apache.org/jira/browse/HDFS-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-5392 stopped by Haohui Mai. Unify the initialization of the hsftp and swebhdfs clients --

[jira] [Resolved] (HDFS-5392) Unify the initialization of the hsftp and swebhdfs clients

[ https://issues.apache.org/jira/browse/HDFS-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Haohui Mai resolved HDFS-5392. -- Resolution: Duplicate This jira is no longer valid because both HDFS-3987 and HDFS-5502 contain the

[jira] [Work started] (HDFS-5392) Unify the initialization of the hsftp and swebhdfs clients

[ https://issues.apache.org/jira/browse/HDFS-5392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on HDFS-5392 started by Haohui Mai. Unify the initialization of the hsftp and swebhdfs clients --

[jira] [Commented] (HDFS-3987) Support webhdfs over HTTPS

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