You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Jungtaek Lim (JIRA)" <ji...@apache.org> on 2015/06/18 23:31:01 UTC

[jira] [Comment Edited] (STORM-885) Heartbeat Server (Pacemaker)

    [ https://issues.apache.org/jira/browse/STORM-885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14592539#comment-14592539 ] 

Jungtaek Lim edited comment on STORM-885 at 6/18/15 9:30 PM:
-------------------------------------------------------------

Is Pacemaker already implemented? Or it is in progress?

I've posted STORM-872 and thinking about how to realize.
(Actually my approach was giving a chance to replace ZK for worker heartbeat to Redis Cluster or Couchbase, or other in-memory NoSQL, which can scale well. It could be also heartbeat server / client when we extract interface well.)

But if pacemaker is implemented (or will be implemented in a short time), and it is pretty easy to install / use for end-users, we can close STORM-872 as duplicated.


was (Author: kabhwan):
Is Pacemaker already implemented? Or it is in progress?

I've posted https://issues.apache.org/jira/browse/STORM-872 and thinking about how to realize.
(Actually my approach was giving a chance to replace ZK for worker heartbeat to Redis or Couchbase, or other in-memory NoSQL, which can scale well. It could be heartbeat server / client when we extract interface well.)

But if pacemaker is implemented (or will be implemented in a short time), and it is pretty easy to install / use for end-users, we can close STORM-872 as duplicated.

> Heartbeat Server (Pacemaker)
> ----------------------------
>
>                 Key: STORM-885
>                 URL: https://issues.apache.org/jira/browse/STORM-885
>             Project: Apache Storm
>          Issue Type: Improvement
>            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)