You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (JIRA)" <ji...@apache.org> on 2016/10/21 11:38:58 UTC
[jira] [Commented] (KARAF-4753) Kafka appender highly uses CPU when
using non existing DNS server name
[ https://issues.apache.org/jira/browse/KARAF-4753?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15594861#comment-15594861 ]
Jean-Baptiste Onofré commented on KARAF-4753:
---------------------------------------------
It could be related to {{ConsumerConfig.WorkerThresholdTimeWindow}} Kafka unset consumer configuration. The {{FailureCounter}} can loop infinitely.
> Kafka appender highly uses CPU when using non existing DNS server name
> ----------------------------------------------------------------------
>
> Key: KARAF-4753
> URL: https://issues.apache.org/jira/browse/KARAF-4753
> Project: Karaf
> Issue Type: Bug
> Components: decanter
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: decanter-1.3.0
>
>
> If you add a DNS name for Kafka for a not existing server, the appender will result in a very high CPU usage (near to 100%).
> This will also be the case, when you define mutliple kafka server locations and if just one of the DNS names are not resolved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)