To add to Ashwin's diagnosis, assuming you have *properties.xml* setup as described in that tutorial, you need to add to the YARN configuration file *yarn-site.xml* at: */sfw/hadoop/current/etc/hadoop* the following stanza:
*<property><name>yarn.scheduler.minimum-allocation-mb</name><value>128</value></property>* and restart the Hadoop daemons (the easiest way to do this is to simply bounce the sandbox or adapt the script shown in the "*Service Management*" section at: *http://docs.datatorrent.com/sandbox <http://docs.datatorrent.com/sandbox>*/) Ram On Fri, Nov 4, 2016 at 5:18 PM, Ashwin Chandra Putta < [email protected]> wrote: > Dimple, > > Cluster does not have enough resources. Here is the initial container > request set from the log. > > 2016-11-04 15:06:26,901 INFO com.datatorrent.stram.StreamingAppMasterService: > Asking RM for containers: [Capability[<memory:1024, vCores:1>]Priority[0], > Capability[<memory:1224, vCores:1>]Priority[1], Capability[<memory:1024, > vCores:1>]Priority[2], Capability[<memory:1024, vCores:1>]Priority[3], > Capability[<memory:1024, vCores:1>]Priority[4], Capability[<memory:1024, > vCores:1>]Priority[5], Capability[<memory:1024, vCores:1>]Priority[6], > Capability[<memory:1024, vCores:1>]Priority[7], Capability[<memory:1024, > vCores:1>]Priority[8], Capability[<memory:2048, vCores:1>]Priority[9]] > > AM then keeps asking for the following 4 containers every 30 seconds but > never gets. > > 2016-11-04 15:07:01,132 INFO com.datatorrent.stram.StreamingAppMasterService: > Asking RM for containers: [Capability[<memory:1024, vCores:1>]Priority[7], > Capability[<memory:1024, vCores:1>]Priority[8], Capability[<memory:2048, > vCores:1>]Priority[9], Capability[<memory:1024, vCores:1>]Priority[6]] > > Regards, > Ashwin. > > On Fri, Nov 4, 2016 at 3:28 PM, Dimple Patel <[email protected]> > wrote: > >> Hello, >> >> I am trying to run Top N Word application from DataTorrent's >> documentation >> <http://docs.datatorrent.com/tutorials/topnwords/> . >> After running the application on DataTorrent's console, when I monitor it >> in >> dtDashboard, the app's status is running but all my operators are in >> PENDING_DEPLOY state and are not switching to Running state. Attached >> herewith is my AppMaster log. I think the problem is with memory >> allocation >> in all operators as when I run a simple random number generation app, it's >> operators run fine. But I am not entirely sure what exactly the problem >> is. >> >> What is the problem here? >> >> dt.log <http://apache-apex-users-list.78494.x6.nabble.com/file/n111 >> 0/dt.log> >> >> Thanks, >> Dimple >> >> >> >> -- >> View this message in context: http://apache-apex-users-list. >> 78494.x6.nabble.com/Operators-stay-in-PENDING-DEPLOY-state-tp1110.html >> Sent from the Apache Apex Users list mailing list archive at Nabble.com. >> > > > > -- > > Regards, > Ashwin. >
