# How to replicate the packet to redis hosts?

**URL:** <https://discuss.elastic.co/t/how-to-replicate-the-packet-to-redis-hosts/60371>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 13, 2016, 11:24am UTC](https://discuss.elastic.co/t/how-to-replicate-the-packet-to-redis-hosts/60371 "2016-09-13T11:24:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)\
**Post date:** [September 13, 2016, 11:24am UTC](https://discuss.elastic.co/t/how-to-replicate-the-packet-to-redis-hosts/60371/1 "2016-09-13T11:24:26Z")

</div>

Latest filebeat has ability to loadbalance or send to either redis when multiple redis is configured.

[https://www.elastic.co/guide/en/beats/filebeat/5.x/redis-output.html#\_loadbalance](https://www.elastic.co/guide/en/beats/filebeat/5.x/redis-output.html#_loadbalance)

However, is there any way to **replicate the packets** to all the redis hosts?  
I tried below configuration but packet was only sent to second hosts.

```
output.redis:
  hosts: ["172.30.1.192"]
  password: "redis"
  key: "filebeat"
  db: 0
  timeout: 5
  loadbalance: false

output.redis:
  hosts: ["172.30.1.110"]
  password: "redis"
  key: "filebeat"
  db: 0
  timeout: 5
  loadbalance: false
```

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [September 13, 2016, 8:56pm UTC](https://discuss.elastic.co/t/how-to-replicate-the-packet-to-redis-hosts/60371/2 "2016-09-13T20:56:58Z")

</div>

the settings from second redis section will overwrite the first one, in yaml parser. Unfortunately first section as is will never be presented to filebeat at loading time (config processing would warn and quit here).

What exactly you want replication for?

Replication is not supported on purpose, as users normally ask for replication in order to support sending events to multiple environments. e.g. production and development environments. See [this github discussion](https://github.com/elastic/beats/issues/1035) why this might be a bad idea.

---

<div class="post-metadata">

**Author:** ![YuWatanabe](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuwatanabe/32/13259_2.png) [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)\
**Post date:** [September 13, 2016, 9:06pm UTC](https://discuss.elastic.co/t/how-to-replicate-the-packet-to-redis-hosts/60371/3 "2016-09-13T21:06:37Z")

</div>

@steffens

My goal was to duplicate the events from filebeat , store it to multiple redis and  
**eventually store the events to different clusters of elastisearch**.

But I think below explanation clarifies the concept of shipping events from beats.

> Problem is, when having multiple logstash outputs in beats (doing event routing essentially), these logstash instances implicitly get coupled via beats. If one instance is down or unresponsive, the others won't get any data. A message queue like kafka will help to uncouple these systems as long as kafka is operating.

---

<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:** [October 4, 2016, 11:24am UTC](https://discuss.elastic.co/t/how-to-replicate-the-packet-to-redis-hosts/60371/4 "2016-10-04T11:24:50Z")

</div>

This topic was automatically closed after 21 days. New replies are no longer allowed.