Thanks Andrew for the hard driving!! I downloaded the source tar bao and built it successfully on a MacOS. I haven't got the chance to try it yet, so mynon-binding +1. Regards,Kai ------------------------------------------------------------------发件人：John Zhuge <[email protected]>发送时间：2017年12月14日(星期四) 11:06收件人：Vinod Kumar Vavilapalli <[email protected]>抄 送：Andrew Wang <[email protected]>; Junping Du <[email protected]>; Robert Kanter <[email protected]>; Arun Suresh <[email protected]>; Lei Xu <[email protected]>; Wei-Chiu Chuang <[email protected]>; Ajay Kumar <[email protected]>; Xiao Chen <[email protected]>; Aaron T. Myers <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>主 题：Re: [VOTE] Release Apache Hadoop 3.0.0 RC1 Thanks Andrew for the great effort! Here is my late vote.
+1 (binding) - Verified checksums and signatures of tarballs - Built source with native, Oracle Java 1.8.0_152 on Mac OS X 10.13.2 - Verified cloud connectors: - S3A integration tests (perf tests skipped) - Deployed both binary and built source to a pseudo cluster, passed the following sanity tests in insecure and SSL mode: - HDFS basic and ACL - DistCp basic - MapReduce wordcount - KMS and HttpFS basic - Balancer start/stop On Wed, Dec 13, 2017 at 6:12 PM, Vinod Kumar Vavilapalli <[email protected] > wrote: > Yes, JIRAs will be filed, the wiki-page idea from YARN meetup is to record > all combinations of testing that need to be done and correspondingly > capture all the testing that someone in the community has already done and > record it for future perusal. > > From what you are saying, I guess we haven't advertised to the public yet > on rolling upgrades, but in our meetups etc so far, you have been saying > that rolling upgrades is supported - so I assumed we did put it in our > messaging. > > The important question is if we are or are not allowed to make potentially > incompatible changes to fix bugs in the process of supporting 2.x to 3.x > upgrades whether rolling or not. > > +Vinod > > > On Dec 13, 2017, at 1:05 PM, Andrew Wang <[email protected]> > wrote: > > > > I'm hoping we can address YARN-7588 and any remaining rolling upgrade > issues in 3.0.x maintenance releases. Beyond a wiki page, it would be > really great to get JIRAs filed and targeted for tracking as soon as > possible. > > > > Vinod, what do you think we need to do regarding caveating rolling > upgrade support? We haven't advertised rolling upgrade support between > major releases outside of dev lists and JIRA. As a new major release, our > compat guidelines allow us to break compatibility, so I don't think it's > expected by users. > > > > -- John
