ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stanislav Lukyanov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8776) Eviction policy MBeans are never registered if evictionPolicyFactory is used
Date Wed, 04 Jul 2018 12:35:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-8776?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532698#comment-16532698

Stanislav Lukyanov commented on IGNITE-8776:

[~kcheng.mvp] thanks for looking into this!

Yes, it seems that moving all responsibility for the eviction policy to the `GridCacheEvictionManager`
would be the best.
Roughly speaking, having a `prepare()` method in GridCacheEvictionManager same as the one
in the `GridCacheProcessor` seems alright.

> Eviction policy MBeans are never registered if evictionPolicyFactory is used
> ----------------------------------------------------------------------------
>                 Key: IGNITE-8776
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8776
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.5
>            Reporter: Stanislav Lukyanov
>            Assignee: kcheng.mvp
>            Priority: Minor
>              Labels: newbie
> Eviction policy MBeans, such as LruEvictionPolicyMBean, are never registered if evictionPolicyFactory
is set instead of evictionPolicy (the latter is deprecated).
> This happens because GridCacheProcessor::registerMbean attempts to find either an *MBean
interface or IgniteMBeanAware interface on the passed object. It works for LruEvictionPolicy
but not for LruEvictionPolicyFactory (which doesn't implement these interfaces).
> The code needs to be adjusted to handle factories correctly.
> New tests are needed to make sure that all standard beans are registered (IgniteKernalMbeansTest
does that for kernal mbeans - need the same for cache beans).

This message was sent by Atlassian JIRA

View raw message