# Filebeat redis output doesn't support redis cluster mode **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [July 14, 2017, 3:50am UTC](https://discuss.elastic.co/t/filebeat-redis-output-doesnt-support-redis-cluster-mode/93108 "2017-07-14T03:50:00Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![cjuroz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cjuroz/32/20059_2.png) [@cjuroz](https://discuss.elastic.co/u/cjuroz)\ **Post date:** [July 14, 2017, 3:50am UTC](https://discuss.elastic.co/t/filebeat-redis-output-doesnt-support-redis-cluster-mode/93108/1 "2017-07-14T03:50:00Z")
I am using filebeat `5.4.0` with redis output and I noticed filebeat doesn't support access to **redis cluster configuration endpoint**. I am using AWS redis cluster mode on (engine `3.2.4`) and filebeat is not able to handle MOVED events ([https://redis.io/docs/reference/cluster-spec/](https://redis.io/topics/cluster-spec#moved-redirection)). This is the error I get from `filebeat logs`: > 2017-07-14T02:35:51Z ERR Failed to RPUSH event to list with MOVED 6715 x.x.x.x:6379 and here my `filebeat.yml` output.redis section: > output.redis: > hosts: ["[xxxx.xxxx.clustercfg.usw2.cache.amazonaws.com:6379](http://xxxx.xxxx.clustercfg.usw2.cache.amazonaws.com:6379)"] > datatype: "list" > key: "filebeat:%{[environment]}" As per my understanding, filebeat should be aware of this and implement corresponding logic to redirect PUSH to node returned by MOVED (redis-cli, for instance do it). Note: **logstash** should act in the same way. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 11, 2017, 3:50am UTC](https://discuss.elastic.co/t/filebeat-redis-output-doesnt-support-redis-cluster-mode/93108/2 "2017-08-11T03:50:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.