[jira] [Commented] (HDFS-3194) DataNode block scanner is running too frequently

[ https://issues.apache.org/jira/browse/HDFS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286337#comment-13286337 ] amith commented on HDFS-3194: - Hi Eli Thanks for looking into this issue This issue may be in

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

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286270#comment-13286270 ] Eli Collins commented on HDFS-744: -- We're still not out of alpha for 2.0, IMO this seems re

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

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286255#comment-13286255 ] Tsz Wo (Nicholas), SZE commented on HDFS-744: - For backporting it to 1.0, it req

[jira] [Commented] (HDFS-3479) backport HDFS-3335 (check for edit log corruption at the end of the log) to branch-1

[ https://issues.apache.org/jira/browse/HDFS-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286250#comment-13286250 ] Tsz Wo (Nicholas), SZE commented on HDFS-3479: -- Why UNCHECKED_REGION_LENGTH is

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13286227#comment-13286227 ] Tsz Wo (Nicholas), SZE commented on HDFS-3456: -- > I haven't done the analysis

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13286223#comment-13286223 ] Tsz Wo (Nicholas), SZE commented on HDFS-3456: -- > Well, I was going by > http

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13286200#comment-13286200 ] Andy Isaacson commented on HDFS-3456: - {quote}2**53 milliseconds is thousands of years.

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13286192#comment-13286192 ] Colin Patrick McCabe commented on HDFS-3456: Well, I was going by http://docs.

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13286178#comment-13286178 ] Tsz Wo (Nicholas), SZE commented on HDFS-3456: -- > 2**53 milliseconds is thousa

[jira] [Commented] (HDFS-3194) DataNode block scanner is running too frequently

[ https://issues.apache.org/jira/browse/HDFS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286132#comment-13286132 ] Eli Collins commented on HDFS-3194: --- I see this on branch-2 as well. > D

[jira] [Created] (HDFS-3480) Multiple SLF4J binding warning

Eli Collins created HDFS-3480: - Summary: Multiple SLF4J binding warning Key: HDFS-3480 URL: https://issues.apache.org/jira/browse/HDFS-3480 Project: Hadoop HDFS Issue Type: Bug Componen

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13286126#comment-13286126 ] Colin Patrick McCabe commented on HDFS-3456: Thanks, Andy. I came up with this

[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.004.patch Here is a simple patch that just fixes the immediate p

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13286118#comment-13286118 ] Andy Isaacson commented on HDFS-3456: - .003.patch uses nextDouble, which does not provi

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13286117#comment-13286117 ] Colin Patrick McCabe commented on HDFS-3456: I have a feeling that people will

[jira] [Commented] (HDFS-3194) DataNode block scanner is running too frequently

[ https://issues.apache.org/jira/browse/HDFS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286108#comment-13286108 ] Eli Collins commented on HDFS-3194: --- Here's the DN log from a recent trunk build with jus

[jira] [Updated] (HDFS-3194) DataNode block scanner is running too frequently

[ https://issues.apache.org/jira/browse/HDFS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-3194: -- Summary: DataNode block scanner is running too frequently (was: Continuous block scanning at DN side)

[jira] [Commented] (HDFS-3194) Continuous block scanning at DN side

[ https://issues.apache.org/jira/browse/HDFS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286089#comment-13286089 ] Eli Collins commented on HDFS-3194: --- Hi Amith, I think the current behavior (rolling the

[jira] [Commented] (HDFS-3479) backport HDFS-3335 (check for edit log corruption at the end of the log) to branch-1

[ https://issues.apache.org/jira/browse/HDFS-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286080#comment-13286080 ] Colin Patrick McCabe commented on HDFS-3479: Hi Nicholas, In the patch it says

[jira] [Updated] (HDFS-3194) Continuous block scanning at DN side

[ https://issues.apache.org/jira/browse/HDFS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-3194: -- Status: Open (was: Patch Available) > Continuous block scanning at DN side > --

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

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286067#comment-13286067 ] Lars Hofhansl commented on HDFS-744: I agree. Or at least Hadoop 2.0.x.

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

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286062#comment-13286062 ] Zhihong Yu commented on HDFS-744: - Backport to hadoop 1.0 would be nice. >

[jira] [Commented] (HDFS-3479) backport HDFS-3335 (check for edit log corruption at the end of the log) to branch-1

[ https://issues.apache.org/jira/browse/HDFS-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286051#comment-13286051 ] Tsz Wo (Nicholas), SZE commented on HDFS-3479: -- Why there is a UNCHECKED_REGIO

[jira] [Updated] (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:all-tabpanel ] Lars Hofhansl updated HDFS-1783: Attachment: HDFS-1783-trunk-v2.patch Patch rebased for HDFS-744. * Added a first simple test * Fixed

[jira] [Commented] (HDFS-3479) backport HDFS-3335 (check for edit log corruption at the end of the log) to branch-1

[ https://issues.apache.org/jira/browse/HDFS-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286009#comment-13286009 ] Hadoop QA commented on HDFS-3479: - -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-tabpanel&focusedCommentId=13285995#comment-13285995 ] Hudson commented on HDFS-3462: -- Integrated in Hadoop-Mapreduce-trunk-Commit #2320 (See [https

[jira] [Commented] (HDFS-3468) Make BKJM-ZK session timeout configurable.

[ https://issues.apache.org/jira/browse/HDFS-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285994#comment-13285994 ] Hudson commented on HDFS-3468: -- Integrated in Hadoop-Mapreduce-trunk-Commit #2320 (See [https

[jira] [Commented] (HDFS-3476) Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462

[ https://issues.apache.org/jira/browse/HDFS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285993#comment-13285993 ] Hudson commented on HDFS-3476: -- Integrated in Hadoop-Mapreduce-trunk-Commit #2320 (See [https

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

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285992#comment-13285992 ] Hudson commented on HDFS-744: - Integrated in Hadoop-Mapreduce-trunk-Commit #2320 (See [https://

[jira] [Updated] (HDFS-3479) backport HDFS-3335 (check for edit log corruption at the end of the log) to branch-1

[ https://issues.apache.org/jira/browse/HDFS-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-3479: --- Status: Patch Available (was: Open) > backport HDFS-3335 (check for edit log corr

[jira] [Updated] (HDFS-3479) backport HDFS-3335 (check for edit log corruption at the end of the log) to branch-1

[ https://issues.apache.org/jira/browse/HDFS-3479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Colin Patrick McCabe updated HDFS-3479: --- Attachment: HDFS-3335-b1.005.patch * fix the way we do pre-allocation (formerly, we we

[jira] [Created] (HDFS-3479) backport HDFS-3335 (check for edit log corruption at the end of the log) to branch-1

Colin Patrick McCabe created HDFS-3479: -- Summary: backport HDFS-3335 (check for edit log corruption at the end of the log) to branch-1 Key: HDFS-3479 URL: https://issues.apache.org/jira/browse/HDFS-3479

[jira] [Commented] (HDFS-3468) Make BKJM-ZK session timeout configurable.

[ https://issues.apache.org/jira/browse/HDFS-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285964#comment-13285964 ] Hudson commented on HDFS-3468: -- Integrated in Hadoop-Common-trunk-Commit #2303 (See [https://

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

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285963#comment-13285963 ] Lars Hofhansl commented on HDFS-744: Thanks Nicholas! > Support hsync i

[jira] [Updated] (HDFS-3468) Make BKJM-ZK session timeout configurable.

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

[jira] [Commented] (HDFS-3475) Make the replication monitor multipliers configurable

[ https://issues.apache.org/jira/browse/HDFS-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285943#comment-13285943 ] Aaron T. Myers commented on HDFS-3475: -- I'm +1 to making these configurable.

[jira] [Commented] (HDFS-3468) Make BKJM-ZK session timeout configurable.

[ https://issues.apache.org/jira/browse/HDFS-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285942#comment-13285942 ] Hudson commented on HDFS-3468: -- Integrated in Hadoop-Hdfs-trunk-Commit #2375 (See [https://bu

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

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285940#comment-13285940 ] Hudson commented on HDFS-744: - Integrated in Hadoop-Hdfs-trunk-Commit #2375 (See [https://build

[jira] [Commented] (HDFS-3474) Cleanup Exception handling in BookKeeper journal manager

[ https://issues.apache.org/jira/browse/HDFS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285939#comment-13285939 ] Hudson commented on HDFS-3474: -- Integrated in Hadoop-Mapreduce-trunk-Commit #2319 (See [https

[jira] [Resolved] (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:all-tabpanel ] Aaron T. Myers resolved HDFS-3463. -- Resolution: Duplicate > DFSTestUtil.waitCorruptReplicas() should not use file reading time a

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

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285936#comment-13285936 ] Hudson commented on HDFS-744: - Integrated in Hadoop-Common-trunk-Commit #2302 (See [https://bui

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

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-744: Resolution: Fixed Fix Version/s: 3.0.0 Hadoop Flags: Reviewed S

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

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285926#comment-13285926 ] Tsz Wo (Nicholas), SZE commented on HDFS-744: - If Todd is not around, then I wil

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=13285916#comment-13285916 ] Tsz Wo (Nicholas), SZE commented on HDFS-3456: -- -1 on the patch: - all use of

[jira] [Commented] (HDFS-3476) Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462

[ https://issues.apache.org/jira/browse/HDFS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285915#comment-13285915 ] Eli Collins commented on HDFS-3476: --- +1 patch looks good > Correct the d

[jira] [Updated] (HDFS-3478) -setQuota, -setSpaceQuota Issues with Long.Max_Value

[ https://issues.apache.org/jira/browse/HDFS-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-3478: -- Component/s: name-node Affects Version/s: 2.0.0-alpha Labels: newbie (was: ) A

[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.003.patch * fix bug where low bits might not be randomized by th

[jira] [Commented] (HDFS-3476) Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462

[ https://issues.apache.org/jira/browse/HDFS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285901#comment-13285901 ] Hudson commented on HDFS-3476: -- Integrated in Hadoop-Common-trunk-Commit #2301 (See [https://

[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-tabpanel&focusedCommentId=13285902#comment-13285902 ] Hudson commented on HDFS-3462: -- Integrated in Hadoop-Common-trunk-Commit #2301 (See [https://

[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-tabpanel&focusedCommentId=13285898#comment-13285898 ] Hudson commented on HDFS-3462: -- Integrated in Hadoop-Hdfs-trunk-Commit #2374 (See [https://bu

[jira] [Commented] (HDFS-3476) Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462

[ https://issues.apache.org/jira/browse/HDFS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285897#comment-13285897 ] Hudson commented on HDFS-3476: -- Integrated in Hadoop-Hdfs-trunk-Commit #2374 (See [https://bu

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

[ https://issues.apache.org/jira/browse/HDFS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285895#comment-13285895 ] Eli Collins commented on HDFS-744: -- @Lars, Todd is on vacation this week, might take him so

[jira] [Updated] (HDFS-3474) Cleanup Exception handling in BookKeeper journal manager

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

[jira] [Commented] (HDFS-3474) Cleanup Exception handling in BookKeeper journal manager

[ https://issues.apache.org/jira/browse/HDFS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285885#comment-13285885 ] Hudson commented on HDFS-3474: -- Integrated in Hadoop-Common-trunk-Commit #2300 (See [https://

[jira] [Updated] (HDFS-3476) Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462

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

[jira] [Commented] (HDFS-3474) Cleanup Exception handling in BookKeeper journal manager

[ https://issues.apache.org/jira/browse/HDFS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285884#comment-13285884 ] Hudson commented on HDFS-3474: -- Integrated in Hadoop-Hdfs-trunk-Commit #2373 (See [https://bu

[jira] [Created] (HDFS-3478) -setQuota, -setSpaceQuota Issues with Long.Max_Value

Sujay Rau created HDFS-3478: --- Summary: -setQuota, -setSpaceQuota Issues with Long.Max_Value Key: HDFS-3478 URL: https://issues.apache.org/jira/browse/HDFS-3478 Project: Hadoop HDFS Issue Type: Bug

[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-tabpanel&focusedCommentId=13285849#comment-13285849 ] Hadoop QA commented on HDFS-3473: - -1 overall. Here are the results of testing the latest

[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 ] Andy Isaacson updated HDFS-3473: Attachment: hadoop-8447.patch Updated patch, fixes null-value problem. > DN logs ba

[jira] [Commented] (HDFS-3469) start-dfs.sh will start zkfc, but stop-dfs.sh will not stop zkfc similarly.

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

[jira] [Commented] (HDFS-3477) FormatZK and ZKFC startup can fail due to zkclient connection establishment delay

[ https://issues.apache.org/jira/browse/HDFS-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285699#comment-13285699 ] Rakesh R commented on HDFS-3477: ActiveStandbyElector is missing the checks for SyncConnect

[jira] [Updated] (HDFS-3477) FormatZK and ZKFC startup can fail due to zkclient connection establishment delay

[ https://issues.apache.org/jira/browse/HDFS-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] suja s updated HDFS-3477: - Description: Format and ZKFC startup flows continue further after creation of zkclient connection without waiting

[jira] [Updated] (HDFS-3477) FormatZK and ZKFC startup can fail due to zkclient connection establishment delay

[ https://issues.apache.org/jira/browse/HDFS-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-3477: -- Component/s: auto-failover Target Version/s: 2.0.1-alpha, 3.0.0 Affects Ve

[jira] [Updated] (HDFS-3477) FormatZK and ZKFC startup can fail due to zkclient connection establishment delay

[ https://issues.apache.org/jira/browse/HDFS-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] suja s updated HDFS-3477: - Description: Format and ZKFC startup flows continue further after creation of zkclient connection without waiting

[jira] [Updated] (HDFS-3469) start-dfs.sh will start zkfc, but stop-dfs.sh will not stop zkfc similarly.

[ https://issues.apache.org/jira/browse/HDFS-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Uma Maheswara Rao G updated HDFS-3469: -- Target Version/s: 2.0.1-alpha, 3.0.0 (was: 3.0.0) Fix Version/s: (was: 3.0.0)

[jira] [Assigned] (HDFS-3477) FormatZK and ZKFC startup can fail due to zkclient connection establishment delay

[ https://issues.apache.org/jira/browse/HDFS-3477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rakesh R reassigned HDFS-3477: -- Assignee: Rakesh R > FormatZK and ZKFC startup can fail due to zkclient connection establishment >

[jira] [Created] (HDFS-3477) FormatZK and ZKFC startup can fail due to zkclient connection establishment delay

suja s created HDFS-3477: Summary: FormatZK and ZKFC startup can fail due to zkclient connection establishment delay Key: HDFS-3477 URL: https://issues.apache.org/jira/browse/HDFS-3477 Project: Hadoop HDFS

[jira] [Updated] (HDFS-3469) start-dfs.sh will start zkfc, but stop-dfs.sh will not stop zkfc similarly.

[ https://issues.apache.org/jira/browse/HDFS-3469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-3469: Fix Version/s: 3.0.0 Status: Patch Available (was: Open) > start-dfs.sh will start zkfc, but stop-df

[jira] [Commented] (HDFS-3476) Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462

[ https://issues.apache.org/jira/browse/HDFS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285688#comment-13285688 ] Hadoop QA commented on HDFS-3476: - +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-tabpanel&focusedCommentId=13285676#comment-13285676 ] Hudson commented on HDFS-3462: -- Integrated in Hadoop-Mapreduce-trunk #1095 (See [https://buil

[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-tabpanel&focusedCommentId=13285675#comment-13285675 ] Hudson commented on HDFS-3452: -- Integrated in Hadoop-Mapreduce-trunk #1095 (See [https://buil

[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-tabpanel&focusedCommentId=13285674#comment-13285674 ] Hudson commented on HDFS-3398: -- Integrated in Hadoop-Mapreduce-trunk #1095 (See [https://buil

[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-tabpanel&focusedCommentId=13285659#comment-13285659 ] Ivan Kelly commented on HDFS-3441: -- the code of the patch looks good. I think the test sho

[jira] [Commented] (HDFS-3474) Cleanup Exception handling in BookKeeper journal manager

[ https://issues.apache.org/jira/browse/HDFS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285651#comment-13285651 ] Rakesh R commented on HDFS-3474: +1 patch looks nice. > Cleanup Exception

[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-tabpanel&focusedCommentId=13285627#comment-13285627 ] Hadoop QA commented on HDFS-3441: - +1 overall. Here are the results of testing the latest

[jira] [Updated] (HDFS-3476) Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462

[ https://issues.apache.org/jira/browse/HDFS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-3476: -- Attachment: HDFS-3476.patch Attached patch changes the default and also cleans up line width violations from be

[jira] [Updated] (HDFS-3476) Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462

[ https://issues.apache.org/jira/browse/HDFS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J updated HDFS-3476: -- Status: Patch Available (was: Open) > Correct the default used in TestDFSClientRetries.busyTest() after HDF

[jira] [Assigned] (HDFS-3476) Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462

[ https://issues.apache.org/jira/browse/HDFS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Harsh J reassigned HDFS-3476: - Assignee: Harsh J > Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462 >

[jira] [Commented] (HDFS-3476) Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462

[ https://issues.apache.org/jira/browse/HDFS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285616#comment-13285616 ] Harsh J commented on HDFS-3476: --- Konstantin's comment from HDFS-3462: {quote} {code} +in

[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-tabpanel&focusedCommentId=13285613#comment-13285613 ] Harsh J commented on HDFS-3462: --- Konstantin, I thought it to be fine for that test case but I

[jira] [Created] (HDFS-3476) Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462

Harsh J created HDFS-3476: - Summary: Correct the default used in TestDFSClientRetries.busyTest() after HDFS-3462 Key: HDFS-3476 URL: https://issues.apache.org/jira/browse/HDFS-3476 Project: Hadoop HDFS

[jira] [Commented] (HDFS-3474) Cleanup Exception handling in BookKeeper journal manager

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

[jira] [Created] (HDFS-3475) Make the replication monitor multipliers configurable

Harsh J created HDFS-3475: - Summary: Make the replication monitor multipliers configurable Key: HDFS-3475 URL: https://issues.apache.org/jira/browse/HDFS-3475 Project: Hadoop HDFS Issue Type: Improve

[jira] [Commented] (HDFS-3194) Continuous block scanning at DN side

[ https://issues.apache.org/jira/browse/HDFS-3194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285602#comment-13285602 ] Hadoop QA commented on HDFS-3194: - -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-tabpanel&focusedCommentId=13285594#comment-13285594 ] Hudson commented on HDFS-3462: -- Integrated in Hadoop-Hdfs-trunk #1061 (See [https://builds.ap

[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-tabpanel&focusedCommentId=13285592#comment-13285592 ] Hudson commented on HDFS-3398: -- Integrated in Hadoop-Hdfs-trunk #1061 (See [https://builds.ap

[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-tabpanel&focusedCommentId=13285593#comment-13285593 ] Hudson commented on HDFS-3452: -- Integrated in Hadoop-Hdfs-trunk #1061 (See [https://builds.ap

[jira] [Commented] (HDFS-3474) Cleanup Exception handling in BookKeeper journal manager

[ https://issues.apache.org/jira/browse/HDFS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285583#comment-13285583 ] Uma Maheswara Rao G commented on HDFS-3474: --- +1 lgtm > Cleanup E

[jira] [Updated] (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:all-tabpanel ] Uma Maheswara Rao G updated HDFS-3441: -- Target Version/s: 2.0.1-alpha, 3.0.0 Fix Version/s: (was: 3.0.0)

[jira] [Updated] (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:all-tabpanel ] Rakesh R updated HDFS-3441: --- Fix Version/s: 2.0.0-alpha 3.0.0 Affects Version/s: 2.0.0-alpha S

[jira] [Updated] (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:all-tabpanel ] Rakesh R updated HDFS-3441: --- Attachment: HDFS-3441.1.patch Thanks Ivan and Uma. Updated the patch by addressing the comments. Please revie

[jira] [Commented] (HDFS-3423) BookKeeperJournalManager: NN startup is failing, when tries to recoverUnfinalizedSegments() a bad inProgress_ ZNodes

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

[jira] [Updated] (HDFS-3474) Cleanup Exception handling in BookKeeper journal manager

[ https://issues.apache.org/jira/browse/HDFS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-3474: - Attachment: HDFS-3474.diff Fixed typo. > Cleanup Exception handling in BookKeeper journal

[jira] [Commented] (HDFS-3470) [Log Improvement]: Error logs logged at the time of switch which is misleading

[ https://issues.apache.org/jira/browse/HDFS-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285567#comment-13285567 ] Ivan Kelly commented on HDFS-3470: -- This occurs because of the way we open ledgers in book

[jira] [Updated] (HDFS-3470) [Log Improvement]: Error logs logged at the time of switch which is misleading

[ https://issues.apache.org/jira/browse/HDFS-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-3470: - Issue Type: Bug (was: Sub-task) Parent: (was: HDFS-3399) > [Log Improvement]: Error logs

[jira] [Commented] (HDFS-3474) Cleanup Exception handling in BookKeeper journal manager

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

[jira] [Commented] (HDFS-3474) Cleanup Exception handling in BookKeeper journal manager

[ https://issues.apache.org/jira/browse/HDFS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285564#comment-13285564 ] Uma Maheswara Rao G commented on HDFS-3474: --- Thanks a lot Ivan, for cleaning up t

[jira] [Commented] (HDFS-3468) Make BKJM-ZK session timeout configurable.

[ https://issues.apache.org/jira/browse/HDFS-3468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285563#comment-13285563 ] Ivan Kelly commented on HDFS-3468: -- lgtm +1 > Make BKJM-ZK session timeo

[jira] [Updated] (HDFS-3423) BookKeeperJournalManager: NN startup is failing, when tries to recoverUnfinalizedSegments() a bad inProgress_ ZNodes

[ https://issues.apache.org/jira/browse/HDFS-3423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-3423: - Attachment: HDFS-3423.diff Rebased on trunk. This patch clashes with HDFS-3474, so which ever goes in fir

[jira] [Updated] (HDFS-3474) Cleanup Exception handling in BookKeeper journal manager

[ https://issues.apache.org/jira/browse/HDFS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Kelly updated HDFS-3474: - Attachment: HDFS-3474.diff Patch to replace "catch (Exception e)" with specific exceptions

  1   2   >