You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@karaf.apache.org by "Oliver Wulff (Jira)" <ji...@apache.org> on 2020/05/05 21:49:00 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=17100276#comment-17100276 ] 

Oliver Wulff commented on KARAF-4753:
-------------------------------------

Hi JB

We had several incidents because of this and we think the root cause is that too many events are queued by EventAdmin and can't be sent to Kafka because it's not available (should not happen but can in case of maintenance or other reasons). At some stage (all heap is used by the event admin queue) thus the GC is busy in freeing up memory which is not possible of course.

Is there a way to purge all events in EventAdmin in such cases or better limit the size of it?

I've attached the export from Eclipse Memory Analyzer of the heap dump.

Thanks

Oli

> 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
>
> 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
(v8.3.4#803005)