# High availability

**URL:** <https://discuss.elastic.co/t/high-availability/238097>\
**Category:** Synthetics\
**Created:** [June 22, 2020, 1:45pm UTC](https://discuss.elastic.co/t/high-availability/238097 "2020-06-22T13:45:57Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mohammad\_Etemad](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohammad_etemad/32/42444_2.png) [@Mohammad\_Etemad](https://discuss.elastic.co/u/Mohammad_Etemad)\
**Post date:** [June 22, 2020, 1:45pm UTC](https://discuss.elastic.co/t/high-availability/238097/1 "2020-06-22T13:45:57Z")

</div>

I was wondering if there is a way to have a heartbeat cluster? How can one have HA heratbeat? Is this even possible with heartbeat 7.x?

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [June 25, 2020, 2:16am UTC](https://discuss.elastic.co/t/high-availability/238097/2 "2020-06-25T02:16:05Z")

</div>

We'd love to hear more about your use case.

Heartbeat does support [running in multiple locations](https://www.elastic.co/guide/en/beats/heartbeat/current/heartbeat-geoip.html). You could run multiple heartbeats and tag them as different locations (e.g. `us-west-heartbeat-1` and `us-west-heartbeat-2`).

Alternatively, many users let Kubernetes ensure that at least one heartbeat instance is running at all times. Since heartbeat scales so well it is rare for users to require more than one box.

If either of these options don't work for you we'd love to hear about what you would like!

---

<div class="post-metadata">

**Author:** ![Mohammad\_Etemad](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mohammad_etemad/32/42444_2.png) [@Mohammad\_Etemad](https://discuss.elastic.co/u/Mohammad_Etemad)\
**Post date:** [June 25, 2020, 1:25pm UTC](https://discuss.elastic.co/t/high-availability/238097/3 "2020-06-25T13:25:15Z")

</div>

We are using heartbeat to do tcp checks. But we have an HA system with multiple hosts. So if I put heartbeat on only 1 host, and that host goes down, I will loose heartbeat data. If I put it on 2 hosts, I get duplicate data. I wish there were a clustering mechanism available for HA heartbeat. The heartbeat on our system is living outside of our k8s cluster on the host itself.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 19, 2020, 1:25pm UTC](https://discuss.elastic.co/t/high-availability/238097/4 "2020-07-19T13:25:17Z")

</div>

This topic was automatically closed 24 days after the last reply. New replies are no longer allowed.