# Metricbeats output.redis excessiv DNS Querries when redis down

**URL:** https://discuss.elastic.co/t/metricbeats-output-redis-excessiv-dns-querries-when-redis-down/269021
**Category:** Beats
**Tags:** metricbeat
**Created:** [April 1, 2021, 10:56am UTC](https://discuss.elastic.co/t/metricbeats-output-redis-excessiv-dns-querries-when-redis-down/269021 "2021-04-01T10:56:48Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![brockp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brockp/32/92708_2.png) [@brockp](https://discuss.elastic.co/u/brockp)
#### Post date: [April 1, 2021, 10:56am UTC](https://discuss.elastic.co/t/metricbeats-output-redis-excessiv-dns-querries-when-redis-down/269021/1 "2021-04-01T10:56:48Z")

</div>

We have metricbeats sending data to redis and on to ES. When redis is down metricbeats CPU jumps to 100% and 4 hosts easily create 20,000 DNS requests/second for the list of hosts running redis. Kinda odd it's not cached at all.

Any way to address this? Kind makes it unsafe in our lab.

```auto
#-------------------------- Redis output -------------------------------
output.redis:
    hosts: ["<list of redis hosts>"]
    key: "metricbeat"
    db: 0
    timeout: 5

```

---

<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: [April 29, 2021, 12:57pm UTC](https://discuss.elastic.co/t/metricbeats-output-redis-excessiv-dns-querries-when-redis-down/269021/2 "2021-04-29T12:57:10Z")

</div>

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