So we both used http://www.exogeni.net/2015/04/enabling-site-aware- scheduling-for-apache-storm-in-exogeni/ tutorial. Then I guess we are facing the problem due to the version.
I think, we should try this our own until help arrives and if any of us figured it out, let us inform each other. Cheers, Regards, Eranga Heshan *Undergraduate* Computer Science & Engineering University of Moratuwa Mobile: +94 71 138 2686 <%2B94%2071%20552%202087> Email: [email protected] <[email protected]> <https://www.facebook.com/erangaheshan> <https://twitter.com/erangaheshan> <https://www.linkedin.com/in/erangaheshan> On Tue, Nov 29, 2016 at 5:07 PM, Ohad Edelstein <[email protected]> wrote: > I used this tutorial: > > http://www.exogeni.net/2015/04/enabling-site-aware- > scheduling-for-apache-storm-in-exogeni/ > > > https://github.com/xumingming/storm-lib/blob/master/src/jvm/ > storm/DemoScheduler.java > > But its for storm 0.9.3 > > From: Eranga Heshan <[email protected]> > Date: Tuesday, 29 November 2016 at 13:13 > To: Ohad Edelstein <[email protected]> > > Subject: Re: Schedule a Bolt/Spout to a Predefined Node > > Hi Ohad, > > Yeah, it works when I remove that meta data part from the storm.yaml. I > thought about that also. Could you please set "supervisor.scheduler.meta" > to "supervisor.meta" and see it works. However, it did not work for me. But > in someplace I saw it like that. > > I am working with storm-1.0.2. > > Let us both win at once 😉 > > Cheers, > Regard, > > > Eranga Heshan > *Undergraduate* > Computer Science & Engineering > University of Moratuwa > Mobile: +94 71 138 2686 <%2B94%2071%20552%202087> > Email: [email protected] <[email protected]> > <https://www.facebook.com/erangaheshan> > <https://twitter.com/erangaheshan> > <https://www.linkedin.com/in/erangaheshan> > > On Tue, Nov 29, 2016 at 4:37 PM, Ohad Edelstein <[email protected]> wrote: > >> I guess you added the meta data part to the storm.yaml in the supervisors… >> I think that when ever the code has a problem with one of the params you >> add there, it cause the workers not to start >> When you remove the meta data the problem will go away. >> My guess is that I am not writing the meta part correctly… >> When I set a different parameter that was suppose to be array to a simple >> string, it did the same thing… >> >> With what version of storm are you working with? And what instructions >> are you following? >> Thanks >> >> From: Eranga Heshan <[email protected]> >> Reply-To: "[email protected]" <[email protected]> >> Date: Tuesday, 29 November 2016 at 12:55 >> >> To: "[email protected]" <[email protected]> >> Subject: Re: Schedule a Bolt/Spout to a Predefined Node >> >> Hi Ohad, >> >> My supervisors are running. But inside them, the workers are not working. >> That is what I think the issue is. Do you have the same issue? >> >> >> Eranga Heshan >> *Undergraduate* >> Computer Science & Engineering >> University of Moratuwa >> Mobile: +94 71 138 2686 <%2B94%2071%20552%202087> >> Email: [email protected] <[email protected]> >> <https://www.facebook.com/erangaheshan> >> <https://twitter.com/erangaheshan> >> <https://www.linkedin.com/in/erangaheshan> >> >> On Tue, Nov 29, 2016 at 3:23 PM, Ohad Edelstein <[email protected]> >> wrote: >> >>> Hi, I am having the same problem on storm 1.0.1 >>> I would love if you can share the information again, >>> I also had the same problem that Eranga is having. >>> The problem he has is that the supervisor can’t start because of >>> configuration problem… >>> >>> From: Eranga Heshan <[email protected]> >>> Reply-To: "[email protected]" <[email protected]> >>> Date: Tuesday, 29 November 2016 at 11:00 >>> To: "[email protected]" <[email protected]> >>> Subject: Re: Schedule a Bolt/Spout to a Predefined Node >>> >>> Hi, >>> >>> Thanks for the info. I implemented a custom scheduler according to the >>> link you suggested. I changed "getAvailableWorkerSlots" in the original >>> code to "getAvailableSlots". However when I submit my topology it shows on >>> the Storm UI. But when I click on it and look for more information I see >>> nothing. All the tables are emplty. >>> >>> I am here attaching the inside view of my topology. Could you please >>> look into that and say what I might have done wrong? >>> >>> Thanks, >>> Regards, >>> >>> ​ >>> >>> >>> Eranga Heshan >>> *Undergraduate* >>> Computer Science & Engineering >>> University of Moratuwa >>> Mobile: +94 71 138 2686 <%2B94%2071%20552%202087> >>> Email: [email protected] <[email protected]> >>> <https://www.facebook.com/erangaheshan> >>> <https://twitter.com/erangaheshan> >>> <https://www.linkedin.com/in/erangaheshan> >>> >>> On Mon, Nov 28, 2016 at 9:54 AM, anshu shukla <[email protected]> >>> wrote: >>> >>>> you have to use custom site aware scheduler for that . Or use ntp to >>>> sync clocks for all VMs . >>>> >>>> On Mon, Nov 28, 2016 at 9:49 AM, Eranga Heshan <[email protected]> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I have a cluster of four nodes. There is a benchmark I need to run on >>>>> cluster. Hovever I need to run "input bolt" and "output bolt" on the same >>>>> node in order to calculate the latency properly. >>>>> >>>>> Is there a way that I could run both the bols on the same node? >>>>> >>>>> Thanks, >>>>> Regards, >>>>> >>>>> Eranga Heshan >>>>> *Undergraduate* >>>>> Computer Science & Engineering >>>>> University of Moratuwa >>>>> Mobile: +94 71 138 2686 <%2B94%2071%20552%202087> >>>>> Email: [email protected] <[email protected]> >>>>> <https://www.facebook.com/erangaheshan> >>>>> <https://twitter.com/erangaheshan> >>>>> <https://www.linkedin.com/in/erangaheshan> >>>>> >>>> >>>> >>>> >>>> -- >>>> Thanks & Regards, >>>> Anshu Shukla >>>> >>> >>> >> >
