# Load balancing messages traffic

**URL:** <https://community.graylog.org/t/load-balancing-messages-traffic/11438>\
**Category:** Graylog Central (peer support)\
**Created:** [August 1, 2019, 9:05am UTC](https://community.graylog.org/t/load-balancing-messages-traffic/11438 "2019-08-01T09:05:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![maniel](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/maniel/32/58_2.png) [@maniel](https://community.graylog.org/u/maniel)\
**Post date:** [August 1, 2019, 9:05am UTC](https://community.graylog.org/t/load-balancing-messages-traffic/11438/1 "2019-08-01T09:05:13Z")

</div>

Hi  
We’re planning to move on from single node deployment. I plan to have two graylog nodes for redundancy, three es nodes and three mongo nodes to avoid split brain problem (am i right here?). Not planning to load balance graylog’s web interface, we don’t need it.

1. Balancing the messages traffic is a must though (not because of performance but HA is needed here), is nginx the only solution here?

2. I’m aware of udp load balancing problems when using GELF for example, but only thing we use udp for is syslog, does it have similar fragmentation related problems?

also:

- is there any caching on this level possible?
- where do you place a load balancer to maximize HA? outside of the whole cluster?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\
**Post date:** [August 15, 2019, 9:05am UTC](https://community.graylog.org/t/load-balancing-messages-traffic/11438/2 "2019-08-15T09:05:15Z")

</div>

Closed on August 15, 2019, 9:05am UTC

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