Hi, I am facing a problem in scheduling. we are using trident. Initially co-ordinator and emiter scheduled in one worker machine and other bolts in different machines of the cluster.
When Master-Batch-controller of trident goes down or intentionally killed, nimbus bring the MBC up but we are getting so many failures in Storm ui. without scheduling it is working fine but with scheduling we are getting failures. Regards Tarkesh On Mon, May 12, 2014 at 8:56 AM, [email protected] <[email protected]> wrote: > Hi Weide > there is one paper about Scheduler which used in Storm, and they propose a > new algorithm to adjust the default assignment. > http://dl.acm.org/citation.cfm?id=2488267 Adaptive online scheduling in > storm > > ------------------------------ > [email protected] > > > *From:* Weide Zhang <[email protected]> > *Date:* 2014-05-12 00:42 > *To:* user <[email protected]> > *Subject:* storm scheduler behavior > Hi > > Is there any good documentation how storm does resource allocation and how > does it maps a topology to different work process and how was it decided to > group components in one worker process or across worker process ? > > i'm trying to understand what algorithm it uses to partition the topology > and in the meanwhile considering the resource constraint to achieve best > performance if there is something available here ? > > Thanks, > > Weide > >
