You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@metron.apache.org by "Meenakshi.S" <me...@inspirisys.com> on 2019/04/16 12:16:34 UTC

MAAS -- not starting

Hi , 

 

I tried to start the maas service using the command

1.  $METRON_HOME/bin/maas_service.sh -zq node1:2181

I am seeing this in the console and after that it is displayed as killed in
the yarn gui.

 

 

19/04/16 16:49:21 INFO service.Client: Got application report from ASM for,
appId=2, clientToAMToken=null, appDiagnostics=[Tue Apr 16 16:39:25 +0530
2019] Application is added to the scheduler and is not yet activated.
Skipping AM assignment as cluster resource is empty.  Details : AM Partition
= <DEFAULT_PARTITION>; AM Resource Request = <memory:1024, vCores:1>; Queue
Resource Limit for AM = <memory:0, vCores:0>; User AM Resource Limit of the
queue = <memory:0, vCores:0>; Queue AM Resource Usage = <memory:0,
vCores:0>; , appMasterHost=N/A, appQueue=default, appMasterRpcPort=-1,
appStartTime=1555412965701, yarnAppState=ACCEPTED,
distributedFinalState=UNDEFINED,
appTrackingUrl=http://node1:8088/proxy/application_1555334168692_0002/,
appUser=metron

19/04/16 16:49:21 INFO service.Client: Reached client specified timeout for
application. Killing application

19/04/16 16:49:22 INFO impl.YarnClientImpl: Killed application
application_1555334168692_0002

19/04/16 16:49:22 ERROR service.Client: Application failed to complete
successfully

 

 

 

Any help please .

 

Regards,

Meenakshi


RE: MAAS -- not starting

Posted by babar siddique <ba...@abcdata.org>.
Hi Meenakshi.S,

I think there is issue in FQDN of your cluster where there is node1:2181 in place of node1 type your cluster hostname and then try again. 
1. $METRON_HOME/bin/maas_service.sh -zq <your_cluster_hostname>:2181


Regards,
Babar Siddique


From: Meenakshi.S
Sent: Tuesday, April 16, 2019 5:17 PM
To: user@metron.apache.org
Subject: MAAS -- not starting 

Hi , 

I tried to start the maas service using the command
2. $METRON_HOME/bin/maas_service.sh -zq node1:2181
I am seeing this in the console and after that it is displayed as killed in the yarn gui.


19/04/16 16:49:21 INFO service.Client: Got application report from ASM for, appId=2, clientToAMToken=null, appDiagnostics=[Tue Apr 16 16:39:25 +0530 2019] Application is added to the scheduler and is not yet activated. Skipping AM assignment as cluster resource is empty.  Details : AM Partition = <DEFAULT_PARTITION>; AM Resource Request = <memory:1024, vCores:1>; Queue Resource Limit for AM = <memory:0, vCores:0>; User AM Resource Limit of the queue = <memory:0, vCores:0>; Queue AM Resource Usage = <memory:0, vCores:0>; , appMasterHost=N/A, appQueue=default, appMasterRpcPort=-1, appStartTime=1555412965701, yarnAppState=ACCEPTED, distributedFinalState=UNDEFINED, appTrackingUrl=http://node1:8088/proxy/application_1555334168692_0002/, appUser=metron
19/04/16 16:49:21 INFO service.Client: Reached client specified timeout for application. Killing application
19/04/16 16:49:22 INFO impl.YarnClientImpl: Killed application application_1555334168692_0002
19/04/16 16:49:22 ERROR service.Client: Application failed to complete successfully



Any help please …

Regards,
Meenakshi