[ 
https://issues.apache.org/jira/browse/HDFS-15287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17094722#comment-17094722
 ] 

Chen Liang edited comment on HDFS-15287 at 4/28/20, 5:42 PM:
-------------------------------------------------------------

Thanks for the update [~kihwal]. Will follow up on HDFS-15293, the issue to 
resolve there should be relatively though. Issue mentioned in HDFS-15293 is not 
a consistently happening issue and can lead to missing at most one periodical 
image upload.

And just to clarify though, the improvement from HDFS-15036 is not specific to 
Observer. It was for multiple SBN in general. Even without Observer, as long as 
there are multiple SBN, there can be frequent image upload. While even with 
Observer, if there is only one SBN, frequent upload would not be an issue.

Regarding making this configurable, would like to have [~shv]'s thoughts here, 
as Konstantin was opposing adding this new config.


was (Author: vagarychen):
Thanks for the update [~kihwal]. Will follow up on HDFS-15293, the issue to 
resolve there should be relatively though. Issue mentioned in HDFS-15293 is not 
a consistently happening issue and can lead to missing at most one periodical 
image upload.

And just to clarify though, the improvement from HDFS-15036 is not specific to 
Observer. It was for multiple SBN in general. Even without Observer, as long as 
there are multiple SBN, there can be frequent image upload. While even with 
Observer, if there is only one SBN, frequent upload would not be an issue.

> HDFS rollingupgrade prepare never finishes
> ------------------------------------------
>
>                 Key: HDFS-15287
>                 URL: https://issues.apache.org/jira/browse/HDFS-15287
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.10.0, 3.3.0
>            Reporter: Kihwal Lee
>            Priority: Blocker
>
> After HDFS-12979, the prepare step of rolling upgrade does not work. This is 
> because it added additional check for sufficient time passing since last 
> checkpoint. Since RU rollback image creation and upload can happen any time, 
> uploading of rollback image never succeeds. For a new cluster deployed for 
> testing, it might work since it never checkpointed before.
> It was found that this check is disabled for unit tests, defeating the very 
> purpose of testing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to