[
https://issues.apache.org/jira/browse/STORM-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012526#comment-15012526
]
ASF GitHub Bot commented on STORM-885:
--------------------------------------
Github user ptgoetz commented on the pull request:
https://github.com/apache/storm/pull/838#issuecomment-157914621
@knusbaum Nice documentation! Thank you.
Some thoughts on documentation improvements (please correct me if I'm
wrong):
1. Since pacemaker is a single node service, what happens in the event it
goes down or gets separated by a network partition?
2. How does it compare to the default zookeeper-backed implementation
(performance, fault tolerance, how requirements, etc.).
Documentation can make or break adoption of a new feature/API/etc.
I'm +1 for merging this with the current documentation. +2 if the points
above are addresses or a follow-up JIRA is created.
> Heartbeat Server (Pacemaker)
> ----------------------------
>
> Key: STORM-885
> URL: https://issues.apache.org/jira/browse/STORM-885
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-core
> Reporter: Robert Joseph Evans
> Assignee: Kyle Nusbaum
>
> Large highly connected topologies and large clusters write a lot of data into
> ZooKeeper. The heartbeats, that make up the majority of this data, do not
> need to be persisted to disk. Pacemaker is intended to be a secure
> replacement for storing the heartbeats without changing anything within the
> heartbeats. In the future as more metrics are added in, we may want to look
> into switching it over to look more like Heron, where a metrics server is
> running for each node/topology. And can be used to aggregate/per-aggregate
> them in a more scalable manor.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
