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/01/10 12:01: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=16320136#comment-16320136 ]
ASF GitHub Bot commented on IGNITE-7346:
----------------------------------------
GitHub user alex-plekhanov opened a pull request:
https://github.com/apache/ignite/pull/3349
IGNITE-7346: Enable Ignite cache events per cache
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/alex-plekhanov/ignite ignite-7346
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3349.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3349
----
commit 0ec834d8f463c9338cce7cfadcd63540f2321129
Author: Aleksey Plekhanov <pl...@...>
Date: 2018-01-09T08:56:24Z
IGNITE-7346 Enable Ignite cache events (EventType.EVTS_CACHE, EventType.EVTS_CACHE_REBALANCE) per cache
commit 636bb2988f7711a742f1d1c53cbdbbe411b696f9
Author: Aleksey Plekhanov <pl...@...>
Date: 2018-01-09T10:07:09Z
IGNITE-7346 Enable Ignite cache events (EventType.EVTS_CACHE_REBALANCE) per cache
commit 8d3bdec1ad82179b912fdbb14cc08a908cfb46c7
Author: Aleksey Plekhanov <pl...@...>
Date: 2018-01-09T13:30:04Z
IGNITE-7346 Enable Ignite cache events (EventType.EVTS_CACHE_QUERY) per cache
----
> 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
> Labels: usability
> Fix For: 2.4
>
>
> 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
(v6.4.14#64029)