If it¹s talking to the resource manager my guess is it¹s either (a) not pushing through there b/c of the queue size; and or (b) the capacity on the batch stub.
Try upping the batch stub capacity in resmgr/policy/nodes.xml. Maybe make it equal to the max # of jobs you want it running at a time? Cheers, Chris ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Adjunct Associate Professor, Computer Science Department University of Southern California Los Angeles, CA 90089 USA Email: [email protected] WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -----Original Message----- From: Zichuan Wang <[email protected]> Date: Sunday, November 9, 2014 at 7:02 AM To: Chris Mattmann <[email protected]> Subject: Re: Problem with OODT Workflow RSUBMIT > > > > >Here is a screenshot of OODT monitor. My wild guess is workflow is >running sequentially, instead of parallelly. Really got no idea what I >could do to make it faster... > >‹ >Zichuan Wang >Department of Computer Science, USC > > >On Sun, Nov 9, 2014 at 5:06 AM, Zichuan Wang <[email protected]> wrote: > > >Dear Professor, > > >I followed your advise on enlarge workflow manager¹s min pool size, and >now jobs no longer hang in queues, instead, they are marked as ³RSUBMIT². >Could you please give me another advise on how to speed workflow manager >in this case? > >‹ >Zichuan Wang >Department of Computer Science, USC > > > >
