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

Brahma Reddy Battula commented on HDFS-15624:
---------------------------------------------

{quote}Wanted to check HDFS-15660 too, but now my namenode isn't starting now 
because of this, and It will take time to sort it. But I am still convinced it 
is different, so no need to hold this, But still I will respect opinions on how 
to go ahead.
{quote}
I think, you can post in mailing list others also can try to help you sort out.

 
{quote}Right now, PR is handling the backward compatibility related issues (due 
to change in StorageType order) and inclusion of new Storage policy, by bumping 
the LayoutVersion and adding check against NVDIMM releated operations to block 
during upgrade.
{quote}
I dn't think bumping the namelayout is best solution, need to check other way. 
( may be like checking the client version during the upgrade.)

 
{quote}HDFS-15660 will be handled soon enough to solve issues of both PROVIDED 
and NVDIMM in a generic way.
{quote}
Yes, I too prefer generic way.
{quote}In any case, if not able to fix any of these by the release time (which 
I think we still have some time), then we can think of revert.
{quote}
 

with provided storage we've given couple of releases, there are alternatives to 
avoid this.

 

 

>  Fix the SetQuotaByStorageTypeOp problem after updating hadoop 
> ---------------------------------------------------------------
>
>                 Key: HDFS-15624
>                 URL: https://issues.apache.org/jira/browse/HDFS-15624
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs
>    Affects Versions: 3.4.0
>            Reporter: YaYun Wang
>            Priority: Major
>              Labels: pull-request-available, release-blocker
>          Time Spent: 6h
>  Remaining Estimate: 0h
>
> HDFS-15025 adds a new storage Type NVDIMM, changes the ordinal() of the enum 
> of StorageType. And, setting the quota by storageType depends on the 
> ordinal(), therefore, it may cause the setting of quota to be invalid after 
> upgrade.



--
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