You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/17 05:52:00 UTC
[jira] [Commented] (IGNITE-7346) Enable Ignite cache events per
cache
[ https://issues.apache.org/jira/browse/IGNITE-7346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440422#comment-16440422 ]
ASF GitHub Bot commented on IGNITE-7346:
----------------------------------------
Github user alex-plekhanov closed the pull request at:
https://github.com/apache/ignite/pull/3349
> Enable Ignite cache events per cache
> ------------------------------------
>
> Key: IGNITE-7346
> URL: https://issues.apache.org/jira/browse/IGNITE-7346
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Reporter: Denis Magda
> Assignee: Aleksey Plekhanov
> Priority: Major
> Labels: usability
> Fix For: 2.5
>
>
> Whenever a cache event from {{EventType.EVTS_CACHE}}, {{EventType.EVTS_CACHE_REBALANCE}} or {{EventType.EVTS_CACHE_QUERY}} set is enabled and a listener is registered, the cluster will accumulate and send out events for all the deployed caches.
> Such behavior brings down performance especially if hundreds and thousands of caches are used while the user is interested in the monitoring of specific caches.
> Let's add a configuration property like {{CacheConfiguration.setEventsEnabled}} to enable or disable the events per cache. The events will be enabled by default to comply with existing behavior.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)