[jira] [Updated] (HDFS-2654) Make BlockReaderLocal not extend RemoteBlockReader2

[ https://issues.apache.org/jira/browse/HDFS-2654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-2654: - Target Version/s: 0.23.1, 0.24.0, 1.1.0 (was: 0.23.1, 1.1.0) Fix Version/s: 1.1.0 fixed

[jira] [Updated] (HDFS-2617) Replaced Kerberized SSL for image transfer and fsck with SPNEGO-based solution

[ https://issues.apache.org/jira/browse/HDFS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-2617: - Fix Version/s: 2.0.1-alpha make FixedVersion consistent with commits. Replaced

[jira] [Updated] (HDFS-2617) Replaced Kerberized SSL for image transfer and fsck with SPNEGO-based solution

[ https://issues.apache.org/jira/browse/HDFS-2617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-2617: - Target Version/s: 2.0.0-alpha, 1.1.0 (was: 1.1.0) Replaced Kerberized SSL for image transfer and

[jira] [Updated] (HDFS-2637) The rpc timeout for block recovery is too low

[ https://issues.apache.org/jira/browse/HDFS-2637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-2637: - Fix Version/s: 1.1.0 make FixedVersion consistent with commits. The rpc timeout for

[jira] [Updated] (HDFS-2638) Improve a block recovery log

[ https://issues.apache.org/jira/browse/HDFS-2638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-2638: - Fix Version/s: 1.1.0 Eli, please update FixedVersion field to be consistent with TargetVersion, when

[jira] [Updated] (HDFS-3078) 2NN https port setting is broken

[ https://issues.apache.org/jira/browse/HDFS-3078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-3078: - Fix Version/s: 1.1.0 change FixedVersion to match commits. 2NN https port setting is

[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=13284655#comment-13284655 ] Lars Hofhansl commented on HDFS-1783: - Will wait for HDFS-744 to be committed, since

[jira] [Commented] (HDFS-3457) Number of UnderReplicated blocks and Number of Files in the cluster, displayed in UI and Fsck report is different

[ https://issues.apache.org/jira/browse/HDFS-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284725#comment-13284725 ] J.Andreina commented on HDFS-3457: -- yes Ashish you are right, UI report displays the count

[jira] [Commented] (HDFS-3452) BKJM:Switch from standby to active fails and NN gets shut down due to delay in clearing of lock

[ https://issues.apache.org/jira/browse/HDFS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284727#comment-13284727 ] Ivan Kelly commented on HDFS-3452: -- The new patch looks almost ready to go. I have a

[jira] [Updated] (HDFS-3459) Fix the tests FSMainOperationsBaseTest.java and F ileContextMainOperationsBaseTest.java to avoid potential test failure

[ https://issues.apache.org/jira/browse/HDFS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-3459: -- Target Version/s: 3.0.0 Affects Version/s: 3.0.0 Hadoop Flags: Reviewed Status:

[jira] [Updated] (HDFS-3462) TestDFSClientRetries.busyTest() should restore default xceiver count in the config.

[ https://issues.apache.org/jira/browse/HDFS-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-3462: -- Hadoop Flags: Reviewed Status: Patch Available (was: Open) +1 pending Jenkins. Thanks!

[jira] [Commented] (HDFS-3459) Fix the tests FSMainOperationsBaseTest.java and F ileContextMainOperationsBaseTest.java to avoid potential test failure

[ https://issues.apache.org/jira/browse/HDFS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284742#comment-13284742 ] Hadoop QA commented on HDFS-3459: - +1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-3452) BKJM:Switch from standby to active fails and NN gets shut down due to delay in clearing of lock

[ https://issues.apache.org/jira/browse/HDFS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284765#comment-13284765 ] Uma Maheswara Rao G commented on HDFS-3452: --- Hi Ivan, Thanks a lot for taking a

[jira] [Commented] (HDFS-2964) No notice in any logs if dfs.datanode.du.reserved is greater than available disk space

[ https://issues.apache.org/jira/browse/HDFS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284789#comment-13284789 ] Harsh J commented on HDFS-2964: --- Thanks for the patch! Can you make sure to follow all code

[jira] [Commented] (HDFS-2964) No notice in any logs if dfs.datanode.du.reserved is greater than available disk space

[ https://issues.apache.org/jira/browse/HDFS-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284792#comment-13284792 ] Harsh J commented on HDFS-2964: --- Perhaps message can be better too: Disk capacity is lower

[jira] [Commented] (HDFS-3462) TestDFSClientRetries.busyTest() should restore default xceiver count in the config.

[ https://issues.apache.org/jira/browse/HDFS-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284795#comment-13284795 ] Hadoop QA commented on HDFS-3462: - +1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-3452) BKJM:Switch from standby to active fails and NN gets shut down due to delay in clearing of lock

[ https://issues.apache.org/jira/browse/HDFS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284805#comment-13284805 ] Ivan Kelly commented on HDFS-3452: -- For #1, what you have is good.

[jira] [Commented] (HDFS-3453) HDFS does not use ClientProtocol in a backward-compatible way

[ https://issues.apache.org/jira/browse/HDFS-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284819#comment-13284819 ] Suresh Srinivas commented on HDFS-3453: --- Finally got some time spend on this and

[jira] [Updated] (HDFS-3453) HDFS does not use ClientProtocol in a backward-compatible way

[ https://issues.apache.org/jira/browse/HDFS-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kihwal Lee updated HDFS-3453: - Attachment: hdfs-3453-branch-1.patch New patch: comments added as Suresh suggested.

[jira] [Commented] (HDFS-3453) HDFS does not use ClientProtocol in a backward-compatible way

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

[jira] [Updated] (HDFS-3453) HDFS does not use ClientProtocol in a backward-compatible way

[ https://issues.apache.org/jira/browse/HDFS-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Suresh Srinivas updated HDFS-3453: -- Resolution: Fixed Target Version/s: 1.1.0 Hadoop Flags: Reviewed

[jira] [Resolved] (HDFS-3001) dfsadmin -refreshServiceAcl fails Kerb authentication with valid Kerb ticket, other subcommands succeed

[ https://issues.apache.org/jira/browse/HDFS-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John George resolved HDFS-3001. --- Resolution: Cannot Reproduce Pat, I am going to close this as not-reproducible anymore. If you

[jira] [Updated] (HDFS-3452) BKJM:Switch from standby to active fails and NN gets shut down due to delay in clearing of lock

[ https://issues.apache.org/jira/browse/HDFS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-3452: -- Attachment: HDFS-3452-2.patch Updated the patch by addressing the Ivan comments.

[jira] [Updated] (HDFS-3462) TestDFSClientRetries.busyTest() should restore default xceiver count in the config.

[ https://issues.apache.org/jira/browse/HDFS-3462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-3462: -- Resolution: Fixed Fix Version/s: 3.0.0 Target Version/s: (was: 3.0.0) Status:

[jira] [Commented] (HDFS-3452) BKJM:Switch from standby to active fails and NN gets shut down due to delay in clearing of lock

[ https://issues.apache.org/jira/browse/HDFS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284902#comment-13284902 ] Hadoop QA commented on HDFS-3452: - +1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-3462) TestDFSClientRetries.busyTest() should restore default xceiver count in the config.

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

[jira] [Commented] (HDFS-3462) TestDFSClientRetries.busyTest() should restore default xceiver count in the config.

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

[jira] [Commented] (HDFS-3452) BKJM:Switch from standby to active fails and NN gets shut down due to delay in clearing of lock

[ https://issues.apache.org/jira/browse/HDFS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284939#comment-13284939 ] Ivan Kelly commented on HDFS-3452: -- lgtm +1 BKJM:Switch from standby to

[jira] [Commented] (HDFS-3462) TestDFSClientRetries.busyTest() should restore default xceiver count in the config.

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

[jira] [Updated] (HDFS-3049) During the normal loading NN startup process, fall back on a different EditLog if we see one that is corrupt

[ https://issues.apache.org/jira/browse/HDFS-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-3049: --- Attachment: HDFS-3049.026.patch * rebase on trunk During the normal

[jira] [Commented] (HDFS-3442) Incorrect count for Missing Replicas in FSCK report

[ https://issues.apache.org/jira/browse/HDFS-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284990#comment-13284990 ] Andrew Wang commented on HDFS-3442: --- New patch with test case for # of missing replicas.

[jira] [Updated] (HDFS-3442) Incorrect count for Missing Replicas in FSCK report

[ https://issues.apache.org/jira/browse/HDFS-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-3442: -- Attachment: HDFS-3442-2.patch Incorrect count for Missing Replicas in FSCK report

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13284995#comment-13284995 ] Alejandro Abdelnur commented on HDFS-3466: -- It is an unnecessary flexibility

[jira] [Commented] (HDFS-3442) Incorrect count for Missing Replicas in FSCK report

[ https://issues.apache.org/jira/browse/HDFS-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285000#comment-13285000 ] Aaron T. Myers commented on HDFS-3442: -- Latest patch looks pretty good to me, Andrew.

[jira] [Updated] (HDFS-140) When a file is deleted, its blocks remain in the blocksmap till the next block report from Datanode

[ https://issues.apache.org/jira/browse/HDFS-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Foley updated HDFS-140: Target Version/s: (was: 1.1.0) When a file is deleted, its blocks remain in the blocksmap till the

[jira] [Updated] (HDFS-3452) BKJM:Switch from standby to active fails and NN gets shut down due to delay in clearing of lock

[ https://issues.apache.org/jira/browse/HDFS-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-3452: -- Resolution: Fixed Fix Version/s: 3.0.0 2.0.1-alpha Hadoop

[jira] [Commented] (HDFS-3452) BKJM:Switch from standby to active fails and NN gets shut down due to delay in clearing of lock

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

[jira] [Commented] (HDFS-3441) Race condition between rolling logs at active NN and purging at standby

[ https://issues.apache.org/jira/browse/HDFS-3441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285024#comment-13285024 ] Uma Maheswara Rao G commented on HDFS-3441: --- HDFS-3058 and HDFS-3452 committed.

[jira] [Commented] (HDFS-3452) BKJM:Switch from standby to active fails and NN gets shut down due to delay in clearing of lock

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

[jira] [Commented] (HDFS-3049) During the normal loading NN startup process, fall back on a different EditLog if we see one that is corrupt

[ https://issues.apache.org/jira/browse/HDFS-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285049#comment-13285049 ] Hadoop QA commented on HDFS-3049: - +1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-3442) Incorrect count for Missing Replicas in FSCK report

[ https://issues.apache.org/jira/browse/HDFS-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285051#comment-13285051 ] Hadoop QA commented on HDFS-3442: - +1 overall. Here are the results of testing the latest

[jira] [Commented] (HDFS-3398) Client will not retry when primaryDN is down once it's just got pipeline

[ https://issues.apache.org/jira/browse/HDFS-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285055#comment-13285055 ] Uma Maheswara Rao G commented on HDFS-3398: --- I have just committed this to trunk

[jira] [Updated] (HDFS-3398) Client will not retry when primaryDN is down once it's just got pipeline

[ https://issues.apache.org/jira/browse/HDFS-3398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-3398: -- Resolution: Fixed Fix Version/s: 3.0.0 2.0.1-alpha Hadoop

[jira] [Commented] (HDFS-3398) Client will not retry when primaryDN is down once it's just got pipeline

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

[jira] [Commented] (HDFS-3398) Client will not retry when primaryDN is down once it's just got pipeline

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

[jira] [Commented] (HDFS-3452) BKJM:Switch from standby to active fails and NN gets shut down due to delay in clearing of lock

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

[jira] [Updated] (HDFS-3371) EditLogFileInputStream: be more careful about closing streams when we're done with them.

[ https://issues.apache.org/jira/browse/HDFS-3371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-3371: --- Attachment: HDFS-3371.002.patch * rebase EditLogFileInputStream: be

[jira] [Commented] (HDFS-3457) Number of UnderReplicated blocks and Number of Files in the cluster, displayed in UI and Fsck report is different

[ https://issues.apache.org/jira/browse/HDFS-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285088#comment-13285088 ] Aaron T. Myers commented on HDFS-3457: -- So shall we resolve this as invalid ?

[jira] [Commented] (HDFS-3463) DFSTestUtil.waitCorruptReplicas() should not use file reading time as a timeout measure.

[ https://issues.apache.org/jira/browse/HDFS-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285090#comment-13285090 ] Aaron T. Myers commented on HDFS-3463: -- Hey Konstantin, this seems like a duplicate of

[jira] [Assigned] (HDFS-3266) DFSTestUtil#waitCorruptReplicas doesn't sleep between checks

[ https://issues.apache.org/jira/browse/HDFS-3266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aaron T. Myers reassigned HDFS-3266: Assignee: (was: Aaron T. Myers) DFSTestUtil#waitCorruptReplicas doesn't sleep

[jira] [Commented] (HDFS-3398) Client will not retry when primaryDN is down once it's just got pipeline

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

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285102#comment-13285102 ] Alejandro Abdelnur commented on HDFS-3466: -- Also, it does not seem correct using

[jira] [Commented] (HDFS-3453) HDFS does not use ClientProtocol in a backward-compatible way

[ https://issues.apache.org/jira/browse/HDFS-3453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285139#comment-13285139 ] Tsz Wo (Nicholas), SZE commented on HDFS-3453: -- Merged to branch-1.1.

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285147#comment-13285147 ] Arpit Gupta commented on HDFS-3466: --- {quote} It is an unnecessary flexibility (adding

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285155#comment-13285155 ] Aaron T. Myers commented on HDFS-3466: -- bq. We need to do this because as soon as you

[jira] [Commented] (HDFS-3371) EditLogFileInputStream: be more careful about closing streams when we're done with them.

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

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285167#comment-13285167 ] Arpit Gupta commented on HDFS-3466: --- @Aaron Thanks for the info. I wil try these out.

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285186#comment-13285186 ] Aaron T. Myers commented on HDFS-3466: -- Happy to help. If these work for you, would

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285190#comment-13285190 ] Arpit Gupta commented on HDFS-3466: --- @Aaron I still feel that this flexibility is good

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285201#comment-13285201 ] Aaron T. Myers commented on HDFS-3466: -- bq. I still feel that this flexibility is good

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285230#comment-13285230 ] Arpit Gupta commented on HDFS-3466: --- @Aaron The reason i think it will be easier is

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285248#comment-13285248 ] Alejandro Abdelnur commented on HDFS-3466: -- regarding key change, we can deprecate

[jira] [Commented] (HDFS-3466) The SPNEGO filter for the NameNode should come out of the web keytab file

[ https://issues.apache.org/jira/browse/HDFS-3466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285290#comment-13285290 ] Aaron T. Myers commented on HDFS-3466: -- bq. The reason i think it will be easier is

[jira] [Updated] (HDFS-3442) Incorrect count for Missing Replicas in FSCK report

[ https://issues.apache.org/jira/browse/HDFS-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Wang updated HDFS-3442: -- Attachment: HDFS-3442-3.patch New patch addressing ATM's comments. Incorrect count

[jira] [Updated] (HDFS-3456) blockReportInterval is long value but when we take the random value it uses getRandom().nextInt,it is causing frequently BR

[ https://issues.apache.org/jira/browse/HDFS-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-3456: --- Attachment: HDFS-3456.002.patch * fix bugs in RandomUtils.nextRandomLong * add unit

[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=13285343#comment-13285343 ] Kang Xiao commented on HDFS-1783: - Hi Dhrubas, is there any latency test on this patch or

[jira] [Commented] (HDFS-3157) Error in deleting block is keep on coming from DN even after the block report and directory scanning has happened

[ https://issues.apache.org/jira/browse/HDFS-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285368#comment-13285368 ] Ashish Singhi commented on HDFS-3157: - I forgot to mention that, I have used {code}+

[jira] [Updated] (HDFS-3457) Number of UnderReplicated blocks displayed in UI and Fsck report is different

[ https://issues.apache.org/jira/browse/HDFS-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] J.Andreina updated HDFS-3457: - Description: Scenario: = Write an HDFS application with the following sequence of operations 1.

[jira] [Commented] (HDFS-3157) Error in deleting block is keep on coming from DN even after the block report and directory scanning has happened

[ https://issues.apache.org/jira/browse/HDFS-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285372#comment-13285372 ] Ashish Singhi commented on HDFS-3157: - Mistake. {quote} In System.arraycopy it will

[jira] [Commented] (HDFS-3457) Number of UnderReplicated blocks displayed in UI and Fsck report is different

[ https://issues.apache.org/jira/browse/HDFS-3457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13285374#comment-13285374 ] J.Andreina commented on HDFS-3457: -- Hi Aaron, Thanks for looking into this defect.

[jira] [Commented] (HDFS-3442) Incorrect count for Missing Replicas in FSCK report

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

[jira] [Created] (HDFS-3472) initializeSharedEdits should warn if a shared edits dir is not configured

Eli Collins created HDFS-3472: - Summary: initializeSharedEdits should warn if a shared edits dir is not configured Key: HDFS-3472 URL: https://issues.apache.org/jira/browse/HDFS-3472 Project: Hadoop HDFS

[jira] [Updated] (HDFS-3473) DN logs backtrace when running under jsvc and /jmx is loaded

[ https://issues.apache.org/jira/browse/HDFS-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-3473: -- Target Version/s: 2.0.1-alpha DN logs backtrace when running under jsvc and /jmx is loaded

[jira] [Moved] (HDFS-3473) DN logs backtrace when running under jsvc and /jmx is loaded

[ https://issues.apache.org/jira/browse/HDFS-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins moved HADOOP-8447 to HDFS-3473: --- Affects Version/s: (was: 2.0.0-alpha) 2.0.0-alpha

[jira] [Commented] (HDFS-3473) DN logs backtrace when running under jsvc and /jmx is loaded

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