Hi Andrew, At this point, there are no more release blockers including documentations from our side - all work done. But I agree it is too close to the release, after talking with other team members, we are fine to drop this from beta,
And we want to target this for GA. I’m withdrawing this vote and will start afresh vote later for GA. Thanks all who voted this effort ! Thanks, Jian > On Sep 7, 2017, at 3:59 PM, Andrew Wang <andrew.w...@cloudera.com> wrote: > > Hi folks, > > This vote closes today. I see a -1 from Allen on inclusion in beta1. I see > there's active fixing going on, but given that we're one week out from RC0, > I think we should drop this from beta1. > > Allen, Jian, others, is this reasonable? What release should we retarget > this for? I don't have a sense for how much work there is left to do, but > as a reminder, we're planning GA for Nov 1st, and 3.1.0 for January. > > Best, > Andrew > > On Wed, Sep 6, 2017 at 10:19 AM, Jian He <j...@hortonworks.com> wrote: > >>> Please correct me if I’m wrong, but the current summary of the >> branch, post these changes, looks like: >> Sorry for confusion, I was actively writing the formal documentation for >> how to use/how it works etc. and will post soon in a few hours. >> >> >>> On Sep 6, 2017, at 10:15 AM, Allen Wittenauer <a...@effectivemachines.com> >> wrote: >>> >>> >>>> On Sep 5, 2017, at 6:23 PM, Jian He <j...@hortonworks.com> wrote: >>>> >>>>> If it doesn’t have all the bells and whistles, then it shouldn’t >> be on port 53 by default. >>>> Sure, I’ll change the default port to not use 53 and document it. >>>>> *how* is it getting launched on a privileged port? It sounds like >> the expectation is to run “command” as root. *ALL* of the previous >> daemons in Hadoop that needed a privileged port used jsvc. Why isn’t this >> one? These questions matter from a security standpoint. >>>> Yes, it is running as “root” to be able to use the privileged port. The >> DNS server is not yet integrated with the hadoop script. >>>> >>>>> Check the output. It’s pretty obviously borked: >>>> Thanks for pointing out. Missed this when rebasing onto trunk. >>> >>> >>> Please correct me if I’m wrong, but the current summary of the >> branch, post these changes, looks like: >>> >>> * A bunch of mostly new Java code that may or may not have >> javadocs (post-revert YARN-6877, still working out HADOOP-14835) >>> * ~1/3 of the docs are roadmap/TBD >>> * ~1/3 of the docs are for an optional DNS daemon that has >> no end user hook to start it >>> * ~1/3 of the docs are for a REST API that comes from some >> undefined daemon (apiserver?) >>> * Two new, but undocumented, subcommands to yarn >>> * There are no docs for admins or users on how to actually >> start or use this completely new/separate/optional feature >>> >>> How are outside people (e.g., non-branch committers) supposed to >> test this new feature under these conditions? >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: yarn-dev-unsubscr...@hadoop.apache.org >> For additional commands, e-mail: yarn-dev-h...@hadoop.apache.org >> >>
