{"action":"created","issue":{"url":"https://api.github.com/repos/elastic/beats/issues/1924","repository_url":"https://api.github.com/repos/elastic/beats","labels_url":"https://api.github.com/repos/elastic/beats/issues/1924/labels{/name}","comments_url":"https://api.github.com/repos/elastic/beats/issues/1924/comments","events_url":"https://api.github.com/repos/elastic/beats/issues/1924/events","html_url":"https://github.com/elastic/beats/issues/1924","id":162702893,"number":1924,"title":"Abnormal CPU activity when filebeat can't connect to Redis instance","user":{"login":"jwadolowski","id":6334715,"avatar_url":"https://avatars.githubusercontent.com/u/6334715?v=3","gravatar_id":"","url":"https://api.github.com/users/jwadolowski","html_url":"https://github.com/jwadolowski","followers_url":"https://api.github.com/users/jwadolowski/followers","following_url":"https://api.github.com/users/jwadolowski/following{/other_user}","gists_url":"https://api.github.com/users/jwadolowski/gists{/gist_id}","starred_url":"https://api.github.com/users/jwadolowski/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jwadolowski/subscriptions","organizations_url":"https://api.github.com/users/jwadolowski/orgs","repos_url":"https://api.github.com/users/jwadolowski/repos","events_url":"https://api.github.com/users/jwadolowski/events{/privacy}","received_events_url":"https://api.github.com/users/jwadolowski/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-06-28T14:40:19Z","updated_at":"2016-06-28T15:13:52Z","closed_at":"2016-06-28T15:13:52Z","body":"Filebeat version: \r\n\r\n```\r\n$ filebeat -version\r\nfilebeat version 1.2.3 (amd64)\r\n```\r\n\r\nOS: \r\n\r\n```\r\n$ cat /etc/redhat-release \r\nRed Hat Enterprise Linux Server release 6.8 (Santiago)\r\n```\r\n\r\nFilebeat config file:\r\n\r\n```\r\n$ cat /etc/filebeat/filebeat.yml \r\nfilebeat:\r\n  prospectors: []\r\n  registry_file: \"/var/lib/filebeat/registry\"\r\n  config_dir: \"/etc/filebeat/conf.d\"\r\noutput:\r\n  redis:\r\n    host: redis.service.consul\r\n    port: 6379\r\nlogging:\r\n  to_syslog: false\r\n  to_files: true\r\n  level: info\r\n  files:\r\n    path: \"/opt/logs/filebeat\"\r\n    name: filebeat.log\r\n    rotateeverybytes: 256000000\r\n    keepfiles: 4\r\n```\r\n\r\nWhen `filebeat` can't connect to defined Redis instance the following warning is printed in logs over and over again:\r\n\r\n```\r\n2016-06-28T15:19:43+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n2016-06-28T15:19:44+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n2016-06-28T15:19:45+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n2016-06-28T15:19:46+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n2016-06-28T15:19:47+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n2016-06-28T15:19:48+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n2016-06-28T15:19:49+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n2016-06-28T15:19:50+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n2016-06-28T15:19:51+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n2016-06-28T15:19:52+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n2016-06-28T15:19:53+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n2016-06-28T15:19:54+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n2016-06-28T15:19:55+01:00 WARN Error connecting to Redis (dial tcp: lookup redis.service.consul on 127.0.0.1:53: no such host). Retrying in 1s\r\n```\r\n\r\nAt the same time CPU load significantly increased. Even though retry was set to 1s it shouldn't affect server performance that much. Please find CPU load diagram and `glances` command output below:\r\n\r\n![filebeat_abnormal_load_zbx](https://cloud.githubusercontent.com/assets/6334715/16419601/9d8d7190-3d4e-11e6-9832-00164d3c213c.png)\r\n\r\n![filebeat_abnormal_load_glances](https://cloud.githubusercontent.com/assets/6334715/16419602/9f74781e-3d4e-11e6-88b6-4ce400653604.png)\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/elastic/beats/issues/comments/229080751","html_url":"https://github.com/elastic/beats/issues/1924#issuecomment-229080751","issue_url":"https://api.github.com/repos/elastic/beats/issues/1924","id":229080751,"user":{"login":"urso","id":75886,"avatar_url":"https://avatars.githubusercontent.com/u/75886?v=3","gravatar_id":"","url":"https://api.github.com/users/urso","html_url":"https://github.com/urso","followers_url":"https://api.github.com/users/urso/followers","following_url":"https://api.github.com/users/urso/following{/other_user}","gists_url":"https://api.github.com/users/urso/gists{/gist_id}","starred_url":"https://api.github.com/users/urso/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/urso/subscriptions","organizations_url":"https://api.github.com/users/urso/orgs","repos_url":"https://api.github.com/users/urso/repos","events_url":"https://api.github.com/users/urso/events{/privacy}","received_events_url":"https://api.github.com/users/urso/received_events","type":"User","site_admin":false},"created_at":"2016-06-28T15:13:52Z","updated_at":"2016-06-28T15:13:52Z","body":"related discuss topic: https://discuss.elastic.co/t/what-would-happend-if-filebeat-couldnt-reach-elasticsearch/53871/4\r\n\r\ntl;dr do not use redis output with filebeat 1.x releases. filebeat+redis requires 5.0alpha3 at least."}}
{"actor":{"display_login":"urso"}}