You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2018/04/18 07:40:00 UTC
[jira] [Resolved] (CAMEL-12418) camel-consul - High CPU load on
events watching
[ https://issues.apache.org/jira/browse/CAMEL-12418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-12418.
---------------------------------
Resolution: Fixed
Assignee: Claus Ibsen
Fix Version/s: 2.21.1
Thanks for reporting and the PR
> camel-consul - High CPU load on events watching
> -----------------------------------------------
>
> Key: CAMEL-12418
> URL: https://issues.apache.org/jira/browse/CAMEL-12418
> Project: Camel
> Issue Type: Bug
> Components: camel-consul
> Affects Versions: 2.21.0
> Reporter: Viachaslau Tsikhanovich
> Assignee: Claus Ibsen
> Priority: Major
> Fix For: 2.21.1, 2.22.0
>
>
> Camel-Consul library expects EventClient to block requests and [passes number of seconds to block request to EventClient|https://github.com/apache/camel/blob/camel-2.21.0/components/camel-consul/src/main/java/org/apache/camel/component/consul/endpoint/ConsulEventConsumer.java#L59].
> However Event HTTP Endpoint [does not support Blocking Queries|https://www.consul.io/api/event.html] and EventClient [ignores passed queryOptions|https://github.com/rickfast/consul-client/blob/1.1.1/src/main/java/com/orbitz/consul/EventClient.java#L164].
> This results in high CPU usage because ConsulEventConsumer constantly makes requests to Consul without any delay or blocking.
> Maybe some _Thread.sleep_ could be added to _EventWatcher.watch(EventClient client)_ before _client.listEvents_ call or any other fix to introduce delay between _listEvents_ requests.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)