Hi Nikhil, While Nimbus would be a best place to hook the information of assignment and record, but Nimbus doesn't provide the hook (if I'm not missing here). As you already stated, you could leverage IWorkerHook to record the start of worker which looks enough on your case. It only records when worker is successfully launched. If there's some cases which worker continuously fails to launch, the assignment will not be recorded. Please note that shutdown is not guaranteed to be called.
Thanks, Jungtaek Lim (HeartSaVioR) 2018년 2월 28일 (수) 오전 3:37, Nikhil Bafna <[email protected]>님이 작성: > Would implementiong IWorkerHook be more appropriate? > > On Tue, Feb 27, 2018 at 11:19 PM, Nikhil Bafna <[email protected]> > wrote: > > > > > Hello, > > > > I want to build a centralised history that looks like > > > > timestamp : topology_name : component_name : topology_id : component_id > : VM hostname : VM IP : Worker port > > > > What would be the best to go about it in Storm? I can think of > > > > 1. Reporting this from prepare() method of a spout/bolt > > 2. Write a custom scheduler that reports the assignments > > > > I had explore event hook, but that doesn't have an event for > > worker/executor task assignment. The UI only reports the current > > assignments. I can devise a poll based mechanism from the REST API, but > > it's not guaranteed to not miss events. > > > > -- > > Nikhil Bafna > > > > > > -- > Nikhil Bafna >
