[jira] [Updated] (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:all-tabpanel ] J.Andreina updated HDFS-3457: - Attachment: (was: UI screenshots.docx) > Number of UnderReplicated blocks and Number of Files in t

[jira] [Updated] (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:all-tabpanel ] J.Andreina updated HDFS-3457: - Attachment: UI screenshots.docx Attached the screenshot for UI report > Number of UnderRe

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

J.Andreina created HDFS-3457: Summary: Number of UnderReplicated blocks and Number of Files in the cluster, displayed in UI and Fsck report is different Key: HDFS-3457 URL: https://issues.apache.org/jira/browse/HDFS-3

[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-tabpanel&focusedCommentId=13281404#comment-13281404 ] amith commented on HDFS-3442: - Here I guess calculation it self is wrong, since by the definiti

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

Brahma Reddy Battula created HDFS-3456: -- Summary: blockReportInterval is long value but when we take the random value it uses getRandom().nextInt,it is causing frequently BR Key: HDFS-3456 URL: https://issues

[jira] [Commented] (HDFS-3415) During NameNode starting up, it may pick wrong storage directory inspector when the layout versions of the storage directories are different

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

[jira] [Commented] (HDFS-3415) During NameNode starting up, it may pick wrong storage directory inspector when the layout versions of the storage directories are different

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

[jira] [Commented] (HDFS-3415) During NameNode starting up, it may pick wrong storage directory inspector when the layout versions of the storage directories are different

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

[jira] [Updated] (HDFS-3415) During NameNode starting up, it may pick wrong storage directory inspector when the layout versions of the storage directories are different

[ https://issues.apache.org/jira/browse/HDFS-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-3415: - Resolution: Fixed Fix Version/s: 2.0.1 Status: Resolved (was: Pa

[jira] [Commented] (HDFS-3415) During NameNode starting up, it may pick wrong storage directory inspector when the layout versions of the storage directories are different

[ https://issues.apache.org/jira/browse/HDFS-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281284#comment-13281284 ] Brandon Li commented on HDFS-3415: -- Manually tested it. It works as expected: throws excep

[jira] [Updated] (HDFS-3454) Balancer unconditionally logs InterruptedException at INFO level on shutdown if security is enabled

[ https://issues.apache.org/jira/browse/HDFS-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-3454: - Hadoop Flags: Reviewed +1 > Balancer unconditionally logs Interru

[jira] [Commented] (HDFS-3415) During NameNode starting up, it may pick wrong storage directory inspector when the layout versions of the storage directories are different

[ https://issues.apache.org/jira/browse/HDFS-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281264#comment-13281264 ] Tsz Wo (Nicholas), SZE commented on HDFS-3415: -- Hi Brandon, since there is no

[jira] [Updated] (HDFS-3415) During NameNode starting up, it may pick wrong storage directory inspector when the layout versions of the storage directories are different

[ https://issues.apache.org/jira/browse/HDFS-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-3415: - Hadoop Flags: Reviewed +1 patch looks good. > During NameNode sta

[jira] [Commented] (HDFS-3454) Balancer unconditionally logs InterruptedException at INFO level on shutdown if security is enabled

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

[jira] [Moved] (HDFS-3455) Add docs for NameNode initializeSharedEdits and bootstrapStandby commands

[ https://issues.apache.org/jira/browse/HDFS-3455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins moved MAPREDUCE-4132 to HDFS-3455: -- Component/s: (was: documentation) docume

[jira] [Updated] (HDFS-3454) Balancer unconditionally logs InterruptedException at INFO level on shutdown if security is enabled

[ https://issues.apache.org/jira/browse/HDFS-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-3454: -- Attachment: hdfs-3454.txt Patch attached, just bumps the log to debug level. > Balancer

[jira] [Updated] (HDFS-3454) Balancer unconditionally logs InterruptedException at INFO level on shutdown if security is enabled

[ https://issues.apache.org/jira/browse/HDFS-3454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eli Collins updated HDFS-3454: -- Status: Patch Available (was: Open) > Balancer unconditionally logs InterruptedException at INFO le

[jira] [Created] (HDFS-3454) Balancer unconditionally logs InterruptedException at INFO level on shutdown if security is enabled

Eli Collins created HDFS-3454: - Summary: Balancer unconditionally logs InterruptedException at INFO level on shutdown if security is enabled Key: HDFS-3454 URL: https://issues.apache.org/jira/browse/HDFS-3454

[jira] [Commented] (HDFS-3436) adding new datanode to existing pipeline fails in case of Append/Recovery

[ https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281177#comment-13281177 ] Vinay commented on HDFS-3436: - Hi Nicholas, I am working on it. Thanks. > addi

[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-tabpanel&focusedCommentId=13281167#comment-13281167 ] Kihwal Lee commented on HDFS-3453: -- Manually ran test-patch {noformat} [exec] -1 over

[jira] [Commented] (HDFS-3436) adding new datanode to existing pipeline fails in case of Append/Recovery

[ https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281149#comment-13281149 ] Tsz Wo (Nicholas), SZE commented on HDFS-3436: -- The patch file is corrupted. {

[jira] [Commented] (HDFS-3368) Missing blocks due to bad DataNodes comming up and down.

[ https://issues.apache.org/jira/browse/HDFS-3368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281146#comment-13281146 ] Tsz Wo (Nicholas), SZE commented on HDFS-3368: -- Patch looks good but the faile

[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-tabpanel&focusedCommentId=13281139#comment-13281139 ] Andrew Wang commented on HDFS-3442: --- Clarifying question: what should be the correct perc

[jira] [Commented] (HDFS-3153) For HA, a logical name is visible in URIs - add an explicit logical name

[ https://issues.apache.org/jira/browse/HDFS-3153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281129#comment-13281129 ] Tsz Wo (Nicholas), SZE commented on HDFS-3153: -- Hi Eli, I have some ideas. Wi

[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-tabpanel&focusedCommentId=13280989#comment-13280989 ] Kihwal Lee commented on HDFS-3453: -- I successfully ran smoke and commit on my desktop. No

[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=13280987#comment-13280987 ] Ivan Kelly commented on HDFS-3441: -- Patch looks good to me. It would be good to have some

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

[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-tabpanel&focusedCommentId=13280984#comment-13280984 ] Kihwal Lee commented on HDFS-3453: -- The attached patch changes how namenode.create() is ca

[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: - Status: Patch Available (was: Open) > HDFS does not use ClientProtocol in a backward-compatible way >

[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 > HDFS does not use ClientProtocol in a backward-compatible way >

[jira] [Commented] (HDFS-3394) Do not use generic in INodeFile.getLastBlock()

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

[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=13280967#comment-13280967 ] Ivan Kelly commented on HDFS-3423: -- How would you change it though? I don't see a clean wa

[jira] [Commented] (HDFS-3386) BK JM : Namenode is not deleting his lock entry '/ledgers/lock/lock-0000X', when fails to acquire the lock

[ https://issues.apache.org/jira/browse/HDFS-3386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280964#comment-13280964 ] Ivan Kelly commented on HDFS-3386: -- HDFS-3452 will make this unnecessary.

[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=13280956#comment-13280956 ] Ivan Kelly commented on HDFS-3452: -- Moved to HDFS. I've thought about this a bit more. Yo

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

Kihwal Lee created HDFS-3453: Summary: HDFS does not use ClientProtocol in a backward-compatible way Key: HDFS-3453 URL: https://issues.apache.org/jira/browse/HDFS-3453 Project: Hadoop HDFS Issu

[jira] [Commented] (HDFS-3394) Do not use generic in INodeFile.getLastBlock()

[ https://issues.apache.org/jira/browse/HDFS-3394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280892#comment-13280892 ] Hudson commented on HDFS-3394: -- Integrated in Hadoop-Hdfs-trunk #1053 (See [https://builds.ap

[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 ] Ivan Kelly updated HDFS-3452: - Issue Type: Sub-task (was: Bug) Parent: HDFS-3399 > BKJM:Switch from standby to active fails

[jira] [Moved] (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 ] Ivan Kelly moved BOOKKEEPER-253 to HDFS-3452: - Component/s: (was: bookkeeper-client) Target Version/s: 2.0.0,

[jira] [Commented] (HDFS-3368) Missing blocks due to bad DataNodes comming up and down.

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

[jira] [Commented] (HDFS-3058) HA: Bring BookKeeperJournalManager up to date with HA changes

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

[jira] [Commented] (HDFS-3436) adding new datanode to existing pipeline fails in case of Append/Recovery

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

[jira] [Commented] (HDFS-2914) HA: Standby should not enter safemode when resources are low

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

[jira] [Updated] (HDFS-2914) HA: Standby should not enter safemode when resources are low

[ https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-2914: Fix Version/s: 2.0.1 Target Version/s: 0.24.0, 2.0.1 (was: 0.24.0) Affects Version/s: 2.0.1 Ha

[jira] [Updated] (HDFS-2914) HA: Standby should not enter safemode when resources are low

[ https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-2914: Attachment: HDFS-2914-2.0.1.patch > HA: Standby should not enter safemode when resources are low > -

[jira] [Updated] (HDFS-2914) HA: Standby should not enter safemode when resources are low

[ https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-2914: Attachment: (was: HDFS-2914.patch) > HA: Standby should not enter safemode when resources are low >

[jira] [Updated] (HDFS-3436) adding new datanode to existing pipeline fails in case of Append/Recovery

[ https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-3436: Attachment: HDFS-3436.patch Attaching the Patch for same > adding new datanode to existing pipelin

[jira] [Updated] (HDFS-2914) HA: Standby should not enter safemode when resources are low

[ https://issues.apache.org/jira/browse/HDFS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-2914: Attachment: HDFS-2914.patch Attaching patch for movement of NNRM from CommonService to ActiveService

[jira] [Updated] (HDFS-3436) adding new datanode to existing pipeline fails in case of Append/Recovery

[ https://issues.apache.org/jira/browse/HDFS-3436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinay updated HDFS-3436: Fix Version/s: 2.0.1 Hadoop Flags: Reviewed Status: Patch Available (was: In Progress) > adding

[jira] [Commented] (HDFS-3058) HA: Bring BookKeeperJournalManager up to date with HA changes

[ https://issues.apache.org/jira/browse/HDFS-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280759#comment-13280759 ] Rakesh R commented on HDFS-3058: Hi Ivan, Its great work and good to see the hot standby f