[
https://issues.apache.org/jira/browse/BIGTOP-1274?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evans Ye updated BIGTOP-1274:
-----------------------------
Attachment: BIGTOP-1274.1.patch
> yarn ResourceManager should be started before starting NodeManagers
> -------------------------------------------------------------------
>
> Key: BIGTOP-1274
> URL: https://issues.apache.org/jira/browse/BIGTOP-1274
> Project: Bigtop
> Issue Type: Bug
> Components: Deployment
> Affects Versions: 0.7.0
> Reporter: Evans Ye
> Assignee: Evans Ye
> Priority: Minor
> Fix For: 0.8.0
>
> Attachments: BIGTOP-1274.1.patch
>
>
> Yarn NodeManager failed to start up while using bigtop-puppet to deploy a
> hadoop cluster with yarn required:
> {code}
> debug: Service[hadoop-yarn-nodemanager](provider=redhat): Executing
> '/sbin/service hadoop-yarn-nodemanager start'
> err:
> /Stage[main]/Hadoop_worker_node/Hadoop::Nodemanager[nodemanager]/Service[hadoop-yarn-nodemanager]/ensure:
> change from stopped to running failed: Could not start
> Service[hadoop-yarn-nodemanager]: Execution of '/sbin/service
> hadoop-yarn-nodemanager start' returned 1: at
> /tmp/vagrant-puppet/modules-0/hadoop/manifests/init.pp:530
> {code}
> This is caused by starting up NodeMangers before ResourceManager gets ready.
> The reproduce steps can completely leverage the
> [vagrant-puppet|https://github.com/apache/bigtop/tree/master/bigtop-deploy/vm/vagrant-puppet]
> snippets delivered in BIGTOP-1178:
> 1.) Add components you would like to have by modifying provision.sh
> {code}
> ...
> jdk_package_name,java-1.7.0-openjdk-devel.x86_64
> components,hadoop,hbase,yarn,mapred-app
> EOF
> ...
> {code}
> 2.) Spin up the cluster
> {code}
> $ ./startup.sh --cluster
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
