Hi folks, Thanks again for the testing help with the RC. Here's our dashboard for the 3.0.0 release:
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329849 Right now we're tracking three blockers: * HADOOP-15058 is the create-release fix, I just put up a patch which needs reviews. It's the worst timing, but I'm hoping Allen could give it a quick sanity check. * HADOOP-15059 is the MR rolling upgrade issue that Junping found, needs triage and an assignee. I asked Ray to look at what we've done with our existing rolling upgrade testing, since it does run an MR job. * HDFS-12480 is an EC issue that Eddy would like to get in if we're rolling another RC, looks close. Is there anything else from this thread that needs to be addressed? I rely on the dashboard to track blockers, so please file a JIRA and prioritize if so. Best, Andrew On Tue, Nov 21, 2017 at 2:08 PM, Vrushali C <vrushalic2...@gmail.com> wrote: > Hi Vinod, > > bq. (b) We need to figure out if this V1 TimelineService should even be > support given ATSv2. > > Yes, I am following this discussion. Let me chat with Rohith and Varun > about this and we will respond on this thread. As such, my preliminary > thoughts are that we should continue to support Timeline Service V1 till we > have the detailed entity level ACLs in V2 and perhaps also a proposal > around upgrade/migration paths from TSv1 to TSv2. > > But in any case, we do need to work towards phasing out Timeline Service > V1. > > thanks > Vrushali > > > On Tue, Nov 21, 2017 at 1:16 PM, Vinod Kumar Vavilapalli < > vino...@apache.org > > wrote: > > > >> - $HADOOP_YARN_HOME/sbin/yarn-daemon.sh start historyserver doesn't > > even work. Not just deprecated in favor of timelineserver as was > advertised. > > > > > > This works for me in trunk and the bash code doesn’t appear to > > have changed in a very long time. Probably something local to your > > install. (I do notice that the deprecation message says “starting” which > > is awkward when the stop command is given though.) Also: is the > > deprecation message even true at this point? > > > > > > Sorry, I mischaracterized the problem. > > > > The real issue is that I cannot use this command line when the MapReduce > > JobHistoryServer is already started on the same machine. > > > > ~/tmp/yarn$ $HADOOP_YARN_HOME/sbin/yarn-daemon.sh start historyserver > > WARNING: Use of this script to start YARN daemons is deprecated. > > WARNING: Attempting to execute replacement "yarn --daemon start" instead. > > DEPRECATED: Use of this command to start the timeline server is > deprecated. > > Instead use the timelineserver command for it. > > Starting the History Server anyway... > > historyserver is running as process 86156. Stop it first. > > > > So, it looks like in shell-scripts, there can ever be only one daemon of > a > > given name, irrespective of which daemon scripts are invoked. > > > > We need to figure out two things here > > (a) The behavior of this command. Clearly, it will conflict with the > > MapReduce JHS - only one of them can be started on the same node. > > (b) We need to figure out if this V1 TimelineService should even be > > support given ATSv2. > > > > @Vrushani / @Rohith / @Varun Saxena et.al, if you are watching, please > > comment on (b). > > > > Thanks > > +Vinod >
