You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Oleksandr Diachenko (JIRA)" <ji...@apache.org> on 2013/06/03 12:52:26 UTC
[jira] [Created] (AMBARI-2250) Create a service check for YARN
Oleksandr Diachenko created AMBARI-2250:
-------------------------------------------
Summary: Create a service check for YARN
Key: AMBARI-2250
URL: https://issues.apache.org/jira/browse/AMBARI-2250
Project: Ambari
Issue Type: New Feature
Components: agent, controller
Affects Versions: 1.4.0
Reporter: Oleksandr Diachenko
Assignee: Oleksandr Diachenko
Fix For: 1.4.0
Assuming we are running this off a node that has the yarn client jars, we can run the distributed shell application.
{code}
bin/hadoop jar <path to yarn-applications-distributedshell*.jar> -appname yarnservicecheck -master_memory 512 -container_memory 128 -num_containers 2 -shell_command "ls" -jar <path to yarn-applications-distributedshell*.jar>
{code}
Before running this, we can running basic sanity tests by verify that the resource manager is up by either using the webservice and also use the webservice to ensure that the required NMs have connected to the RM via <RM node:RM web port>/ws/v1/cluster and /ws/v1/cluster/nodes
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira