Yes, We also plan to upgrade YARN, and we expect to complete the upgrade  in  
Q3-Q4 of 2020 

> 在 2019年12月10日,上午10:23,Weiwei Yang <abvclo...@gmail.com> 写道:
> 
> Awesome! You guys rock!!
> Any plan to upgrade YARN to latest version too?
> 
> --
> Weiwei
> On Dec 9, 2019, 5:20 PM -0800, Hui Fei <feihui.u...@gmail.com>, wrote:
>> Hi Eric,
>> 
>> It's Rolling Upgrade without downtime. We have a cluster with thousands of
>> nodes and 5 namespace, it takes 1 month to do the upgrade. Upgrading
>> Service includes JournalNode, NameNode, ZKFC and DataNode.
>> Related issues of rolling upgrade
>> are HDFS-13596,HDFS-14396,HDFS-14831,HDFS-14509.
>> Watching HDFS-13671 about performance.
>> 
>> Thanks!
>> 
>> Eric Badger <ebad...@verizonmedia.com.invalid> 于2019年12月9日周一 上午11:54写道:
>> 
>>> Hi Runlin,
>>> 
>>> Awesome to hear that you've been able to upgrade! Do you mind sharing some
>>> thoughts on your experience with the upgrade? Did you take a cluster
>>> downtime to do the upgrade? How long did the upgrade take? Did you find any
>>> incompatibilities or issues during or after the upgrade? Do you know if
>>> your performance is better, worse, or similar?
>>> 
>>> Feel free to answer as many or as few of these as you would like.
>>> 
>>> Thanks!
>>> 
>>> Eric
>>> 
>>> On Sun, Dec 8, 2019 at 9:14 PM Runlin zhang <runlin...@gmail.com> wrote:
>>> 
>>>> Hi Folks,
>>>> 
>>>> This is Runlin Zhang from DiDi. I'm glad to announce that our HDFS
>>> has
>>>> just been successfully upgraded from 2.7.2 to 3.2.0, Our cluster has
>>> nearly
>>>> 10,000 nodes,Now the cluster services are stable and we are using new
>>>> features, such as EC, that bring huge benefits! Here I want to thank my
>>>> colleagues for their efforts, Fei Hui, Hu Haiyang, Wang Hongbing, Zhu
>>>> Linhai, Wu Tong; And thanks to the community.
>>>> 
>>>> It is also highly recommended that you upgrade the version to 3.2.1,
>>> If
>>>> you have any problems in the upgrade, you can also communicate and
>>> discuss
>>>> with me.
>>>> 
>>>> 
>>>> Thanks
>>>> Runlin Zhang
>>>> 
>>> 

Reply via email to