[
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-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=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=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=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=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 commented on HDFS-14361:
-
Let's go back to original design doc
[
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.
>
[
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-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-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=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=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-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-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-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=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: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: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: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: 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: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: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: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-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: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: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: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
> 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.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: (was: 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=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=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: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=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:
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: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: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-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:
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: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:
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
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
101 - 149 of 149 matches
Mail list logo
