Github user bastiliu commented on the pull request:
https://github.com/apache/storm/pull/838#issuecomment-157255819
@revans2 One of the reasons why we added topology master in JStorm is to
extend the hierarchy of the structrue of collection of HB & metrics to offload
Zookeepr & Nimbus(from "workers->zookeeper->nimbus" to "workers->topology
master->nimbus"). Besides it, the monitor mechanism of Nimbus is easily to
bring the dead topology master up without adding new complex recovery
functionality. Just went through these two solution again and thought about
merging. I think they are not conflicted for merging. As you mentioned above,
pacemaker is designed as a pluggable component used to extend the capablity of
nimbus for future. So, for merging, we can re-direct the reporting from
"topology master->nimbus" to "topology master->pacemaker". That will make the
scalability of processing of metrics better since the num of connections to
pacemaker are reduced significantly (one connection for each topology).
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
