[
https://issues.apache.org/jira/browse/HDFS-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14378:
Attachment: HDFS-14378-trunk.002.patch
> Simplify the design of multiple NN and both logic of edit log roll and
>
[
https://issues.apache.org/jira/browse/HDFS-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807719#comment-16807719
]
star commented on HDFS-14378:
-
Initial patch for review. [~xkrogen] would you like to make a review for the
[
https://issues.apache.org/jira/browse/HDFS-14370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807341#comment-16807341
]
star commented on HDFS-14370:
-
[~xkrogen]， agree. Server side handler as limited resource should not be
[
https://issues.apache.org/jira/browse/HDFS-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811584#comment-16811584
]
star commented on HDFS-13596:
-
Maybe another option：we can write new properties after the older ones, so that
[
https://issues.apache.org/jira/browse/HDFS-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811584#comment-16811584
]
star edited comment on HDFS-13596 at 4/6/19 2:34 PM:
-
Maybe another option：we can
[
https://issues.apache.org/jira/browse/HDFS-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811584#comment-16811584
]
star edited comment on HDFS-13596 at 4/6/19 2:35 PM:
-
Maybe another option：we can
[
https://issues.apache.org/jira/browse/HDFS-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806045#comment-16806045
]
star commented on HDFS-14378:
-
first step: make ANN rolling its own log.
last step: make ANN download a
[
https://issues.apache.org/jira/browse/HDFS-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14378:
Attachment: HDFS-14378-trunk.001.patch
> Simplify the design of multiple NN and both logic of edit log roll and
>
[
https://issues.apache.org/jira/browse/HDFS-14276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806918#comment-16806918
]
star commented on HDFS-14276:
-
Maybe we can just sleep 10ms in rpc server side if there are no edit logs. As
[
https://issues.apache.org/jira/browse/HDFS-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14378:
Attachment: (was: HDFS-14378-trunk.002.patch)
> Simplify the design of multiple NN and both logic of edit log
[
https://issues.apache.org/jira/browse/HDFS-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14378:
Attachment: HDFS-14378-trunk.002.patch
> Simplify the design of multiple NN and both logic of edit log roll and
>
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Status: Open (was: Patch Available)
> fullBlockReportLeaseId should be reset after registering to NN
>
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776151#comment-16776151
]
star commented on HDFS-14314:
-
Reuploaded the patch with file format changed.
> fullBlockReportLeaseId
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: HDFS-14314.0.patch
> fullBlockReportLeaseId should be reset after registering to NN
>
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776234#comment-16776234
]
star commented on HDFS-14314:
-
I am confused that tests of TestJournalNodeSync Failed since it has nothing to
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776241#comment-16776241
]
star commented on HDFS-14314:
-
[~hexiaoqiao] Thanks. I will add unit test later.
> fullBlockReportLeaseId
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: HDFS-14314.2.patch
> fullBlockReportLeaseId should be reset after registering to NN
>
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: HDFS-14314-trunk.001.patch
> fullBlockReportLeaseId should be reset after registering to NN
>
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16777692#comment-16777692
]
star commented on HDFS-14314:
-
fix code style and mvn checkstyle passed
> fullBlockReportLeaseId should be
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: HDFS-14314-trunk.001.patch
Status: Patch Available (was: Open)
> fullBlockReportLeaseId
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: HDFS-14314-trunk.002.patch
> fullBlockReportLeaseId should be reset after registering to NN
>
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16778122#comment-16778122
]
star commented on HDFS-14314:
-
[~hexiaoqiao], thanks. new patch updated.
> fullBlockReportLeaseId should be
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16779096#comment-16779096
]
star commented on HDFS-14314:
-
ok, I've run all failed test at local and passed. Code style will be fixed
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: HDFS-14314-trunk.003.patch
> fullBlockReportLeaseId should be reset after registering to NN
>
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: HDFS-14314-trunk.005.patch
> fullBlockReportLeaseId should be reset after registering to NN
>
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: HDFS-14314-trunk.006.patch
> fullBlockReportLeaseId should be reset after registering to NN
>
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16782284#comment-16782284
]
star commented on HDFS-14314:
-
[~jojochuang], thanks for pointing out the mistake. new patch uploaded. Now
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783256#comment-16783256
]
star commented on HDFS-14314:
-
[~jojochuang], could you help review the new patch?
> fullBlockReportLeaseId
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16778907#comment-16778907
]
star commented on HDFS-14314:
-
Still unexpected error ！What's next？
> fullBlockReportLeaseId should be reset
[
https://issues.apache.org/jira/browse/HDFS-14317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16784017#comment-16784017
]
star commented on HDFS-14317:
-
[~ekanth], nice patch.
I am not very clear about 'With in-progress edit log
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: HDFS-14314-branch-2.8.001.patch
> fullBlockReportLeaseId should be reset after registering to NN
>
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16783942#comment-16783942
]
star commented on HDFS-14314:
-
[~jojochuang], append to your sammerization.
2. Afterwards, DN reset its
[
https://issues.apache.org/jira/browse/HDFS-14340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786326#comment-16786326
]
star commented on HDFS-14340:
-
Checking more code, indeed there are inconsistency in those code——write() with
[
https://issues.apache.org/jira/browse/HDFS-14340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786337#comment-16786337
]
star commented on HDFS-14340:
-
[~OneisAll], you can make a patch for the issue.
> Lower the log level when
[
https://issues.apache.org/jira/browse/HDFS-14340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786286#comment-16786286
]
star commented on HDFS-14340:
-
According to the original code, I think:
# There's a warn log before that
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Summary: fullBlockReportLeaseId should be reset after registering to NN
(was: fullBlockReportLeaseId should be
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Fix Version/s: 2.8.4
Affects Version/s: (was: 2.8.0)
2.8.4
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16775981#comment-16775981
]
star commented on HDFS-14314:
-
[~jojochuang] patch available now.
> fullBlockReportLeaseId should be reset
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: HDFS-14314.patch
> fullBlockReportLeaseId should be reset after registering to NN
>
[
https://issues.apache.org/jira/browse/HDFS-14317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16785112#comment-16785112
]
star commented on HDFS-14317:
-
thanks [~ekanth].
> Standby does not trigger edit log rolling when
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: HDFS-14314-trunk.004.patch
> fullBlockReportLeaseId should be reset after registering to NN
>
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16776898#comment-16776898
]
star commented on HDFS-14314:
-
unit test added.
> fullBlockReportLeaseId should be reset after registering
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: HDFS-14314.1.patch
> fullBlockReportLeaseId should be reset after registering to NN
>
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16780153#comment-16780153
]
star commented on HDFS-14314:
-
checkstyle seems not consistent.
Same code ".thenAnswer" at line 1000, 1002,
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Attachment: (was: HDFS-14314.1.patch)
> fullBlockReportLeaseId should be reset after registering to NN
>
star created HDFS-14314:
---
Summary: fullBlockReportLeaseId should be reset after
Key: HDFS-14314
URL: https://issues.apache.org/jira/browse/HDFS-14314
Project: Hadoop HDFS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Description:
since HDFS-7923 ,to rate-limit DN block report, DN will ask for a full
block lease id from
[
https://issues.apache.org/jira/browse/HDFS-14314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14314:
Description:
since HDFS-7923 ,to rate-limit DN block report, DN will ask for a full
block lease id from
[
https://issues.apache.org/jira/browse/HDFS-14349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16794201#comment-16794201
]
star commented on HDFS-14349:
-
The autoroll operation is executed in ANN service, not triggered by SNN.
So
[
https://issues.apache.org/jira/browse/HDFS-14340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16786758#comment-16786758
]
star commented on HDFS-14340:
-
# switch to branch 'trunk'
# edit your code and execute cmd 'git diff >
[
https://issues.apache.org/jira/browse/HDFS-10659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16787947#comment-16787947
]
star commented on HDFS-10659:
-
+1. Recently, our hadoop namenode shutdown when switching active namenode,
[
https://issues.apache.org/jira/browse/HDFS-10659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16788469#comment-16788469
]
star commented on HDFS-10659:
-
[~jojochuang]，if is worth commiting, I would like to fix it to trunk.
>
star created HDFS-14378:
---
Summary: Simplify the design of multiple NN and both logic of edit
log roll and checkpoint
Key: HDFS-14378
URL: https://issues.apache.org/jira/browse/HDFS-14378
Project: Hadoop HDFS
[
https://issues.apache.org/jira/browse/HDFS-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14378:
Description:
HDFS-6440 introduced a mechanism to support more than 2 NNs. It
implements a first-writer-win
[
https://issues.apache.org/jira/browse/HDFS-14349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16795553#comment-16795553
]
star commented on HDFS-14349:
-
Yes, it seems that normal edit log roll will be triggered by multiple SNN. I
[
https://issues.apache.org/jira/browse/HDFS-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793261#comment-16793261
]
star commented on HDFS-14361:
-
Let's go back to original design doc
[
https://issues.apache.org/jira/browse/HDFS-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793276#comment-16793276
]
star commented on HDFS-14361:
-
[~hunhun], what do you mean by 'next code never work',
if sendCheckpoint =
[
https://issues.apache.org/jira/browse/HDFS-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793261#comment-16793261
]
star edited comment on HDFS-14361 at 3/15/19 6:06 AM:
--
Let's go back to
[
https://issues.apache.org/jira/browse/HDFS-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793345#comment-16793345
]
star commented on HDFS-14361:
-
_if another SNN send checkpoint request to ANN successfully_, current SNN will
[
https://issues.apache.org/jira/browse/HDFS-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793295#comment-16793295
]
star commented on HDFS-14361:
-
[~hunhun], _gotcha._
_If there is only one SNN, it make sense for
[
https://issues.apache.org/jira/browse/HDFS-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793366#comment-16793366
]
star commented on HDFS-14361:
-
[~hunhun], right.
> SNN will always upload fsimage
>
[
https://issues.apache.org/jira/browse/HDFS-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793450#comment-16793450
]
star edited comment on HDFS-14361 at 3/15/19 8:30 AM:
--
[~brahmareddy], please wait.
[
https://issues.apache.org/jira/browse/HDFS-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793450#comment-16793450
]
star edited comment on HDFS-14361 at 3/15/19 8:30 AM:
--
[~brahmareddy], please wait.
[
https://issues.apache.org/jira/browse/HDFS-14361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793450#comment-16793450
]
star commented on HDFS-14361:
-
[~brahmareddy], please wait.
Maybe we should reconsider the design doc
[
https://issues.apache.org/jira/browse/HDFS-10477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16815013#comment-16815013
]
star commented on HDFS-10477:
-
[~jojochuang], uploaded patch for branch-2.8.
> Stop decommission a rack of
[
https://issues.apache.org/jira/browse/HDFS-10477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-10477:
Attachment: HDFS-10477.branch-2.8.patch
> Stop decommission a rack of DataNodes caused NameNode fail over to
[
https://issues.apache.org/jira/browse/HDFS-13596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16814975#comment-16814975
]
star commented on HDFS-13596:
-
Sorry for my mistake. Indeed length field is not behaving the way as my
[
https://issues.apache.org/jira/browse/HDFS-14403?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811877#comment-16811877
]
star commented on HDFS-14403:
-
[~xkrogen], Impressive results.
Can you give a detailed information about how
star created HDFS-14424:
---
Summary: NN start beacuse of lossing paxos directory
Key: HDFS-14424
URL: https://issues.apache.org/jira/browse/HDFS-14424
Project: Hadoop HDFS
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDFS-14424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14424:
Summary: NN failover failed beacuse of lossing paxos directory (was: NN
start beacuse of lossing paxos directory)
[
https://issues.apache.org/jira/browse/HDFS-14424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star reassigned HDFS-14424:
---
Assignee: star
> NN failover failed beacuse of lossing paxos directory
>
[
https://issues.apache.org/jira/browse/HDFS-14424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14424:
Description:
Recently, our hadoop namenode shutdown when switching active namenode, just
because of missing paxos
[
https://issues.apache.org/jira/browse/HDFS-10659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16817936#comment-16817936
]
star commented on HDFS-10659:
-
[~hanishakoneru] thanks.
[~jojochuang], patch for trunk uploaded. Mind make a
[
https://issues.apache.org/jira/browse/HDFS-10477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16817908#comment-16817908
]
star commented on HDFS-10477:
-
[~jojochuang], [^HDFS-10477.branch-2.8.patch] is for branch 2.8.
Anything
[
https://issues.apache.org/jira/browse/HDFS-10659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star reassigned HDFS-10659:
---
Assignee: star (was: Hanisha Koneru)
> Namenode crashes after Journalnode re-installation in an HA cluster
[
https://issues.apache.org/jira/browse/HDFS-10659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-10659:
Attachment: HDFS-10659.005.patch
> Namenode crashes after Journalnode re-installation in an HA cluster due to
>
[
https://issues.apache.org/jira/browse/HDFS-10659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16818480#comment-16818480
]
star commented on HDFS-10659:
-
fix check style.
Seems func JNStorage#findFinalizedEditsFile is never used.
[
https://issues.apache.org/jira/browse/HDFS-10659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-10659:
Attachment: HDFS-10659.006.patch
> Namenode crashes after Journalnode re-installation in an HA cluster due to
>
[
https://issues.apache.org/jira/browse/HDFS-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14436:
Description:
When call getTimeDuration like this:
{quote}conf.getTimeDuration("nn.interval", 10,
[
https://issues.apache.org/jira/browse/HDFS-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14436:
Description:
When call getTimeDuration like this:
{quote}conf.getTimeDuration("nn.interval", 10,
[
https://issues.apache.org/jira/browse/HDFS-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14436:
Description:
When call getTimeDuration like this:
{quote}conf.getTimeDuration("nn.interval", 10,
star created HDFS-14436:
---
Summary: Configuration#getTimeDuration is not consistent between
default value and manual settings.
Key: HDFS-14436
URL: https://issues.apache.org/jira/browse/HDFS-14436
Project:
[
https://issues.apache.org/jira/browse/HDFS-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820886#comment-16820886
]
star commented on HDFS-14437:
-
Thanks [~hexiaoqiao] . The table really make the issue clearer.
I've tracking
[
https://issues.apache.org/jira/browse/HDFS-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820950#comment-16820950
]
star commented on HDFS-14437:
-
[~hexiaoqiao], agreed.
{quote}In my opinion, The following code segment in
[
https://issues.apache.org/jira/browse/HDFS-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820886#comment-16820886
]
star edited comment on HDFS-14437 at 4/18/19 9:29 AM:
--
Thanks [~hexiaoqiao] . The
[
https://issues.apache.org/jira/browse/HDFS-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820950#comment-16820950
]
star edited comment on HDFS-14437 at 4/18/19 10:43 AM:
---
[~hexiaoqiao], agreed.
[
https://issues.apache.org/jira/browse/HDFS-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16820886#comment-16820886
]
star edited comment on HDFS-14437 at 4/18/19 9:25 AM:
--
Thanks [~hexiaoqiao] . The
[
https://issues.apache.org/jira/browse/HDFS-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821044#comment-16821044
]
star commented on HDFS-14436:
-
It is a little wired to return only the raw literal number when default time
[
https://issues.apache.org/jira/browse/HDFS-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821045#comment-16821045
]
star commented on HDFS-14436:
-
Maybe I should move it to hadoop-common project.
>
[
https://issues.apache.org/jira/browse/HDFS-14436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star updated HDFS-14436:
Attachment: HDFS-14436.001.patch
> Configuration#getTimeDuration is not consistent between default value and
>
[
https://issues.apache.org/jira/browse/HDFS-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16821092#comment-16821092
]
star commented on HDFS-14437:
-
[~angerszhuuu]. If fsLock ignored, the senario He Xiaoqiao listed could occur
[
https://issues.apache.org/jira/browse/HDFS-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star reassigned HDFS-5853:
--
Assignee: (was: star)
> Add "hadoop.user.group.metrics.percentiles.intervals" to hdfs-default.xml
>
[
https://issues.apache.org/jira/browse/HDFS-5853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star reassigned HDFS-5853:
--
Assignee: star (was: Akira Ajisaka)
> Add "hadoop.user.group.metrics.percentiles.intervals" to
[
https://issues.apache.org/jira/browse/HDFS-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16859250#comment-16859250
]
star commented on HDFS-12914:
-
Few comments about your unit tests.
Following codes bypass lease expiration
[
https://issues.apache.org/jira/browse/HDFS-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16859246#comment-16859246
]
star commented on HDFS-12914:
-
[~hexiaoqiao], I also write a unit test for this issue, mostly similar to
[
https://issues.apache.org/jira/browse/HDFS-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16859246#comment-16859246
]
star edited comment on HDFS-12914 at 6/8/19 3:56 PM:
-
[~hexiaoqiao], I also write a
[
https://issues.apache.org/jira/browse/HDFS-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16859250#comment-16859250
]
star edited comment on HDFS-12914 at 6/8/19 4:09 PM:
-
Few comments about your unit
[
https://issues.apache.org/jira/browse/HDFS-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16859250#comment-16859250
]
star edited comment on HDFS-12914 at 6/8/19 4:10 PM:
-
Few comments about your unit
[
https://issues.apache.org/jira/browse/HDFS-12914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16859272#comment-16859272
]
star commented on HDFS-12914:
-
Yes client refers to datanode. DN get REGISTER command after the startup of NN
[
https://issues.apache.org/jira/browse/HDFS-14424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
star resolved HDFS-14424.
-
Resolution: Duplicate
> NN failover failed beacuse of lossing paxos directory
>
1 - 100 of 149 matches
Mail list logo
