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