[
https://issues.apache.org/jira/browse/IGNITE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16282082#comment-16282082
]
Aleksey Plekhanov commented on IGNITE-369:
------------------------------------------
Where in the public API is the best place for a methods to enable/disable
statistics?
At the moment, there is a method
{{org.apache.ignite.cache.CacheManager#enableStatistics}}, that
enables/disables statistics locally, but it also register or unregister new
MXBean (for JSR-107 compatibility, as I understand it). I can change this
method to enable/disable statistics globally, but for each cache additional
MXBeans will be registered when this method will be used to enable statistics.
Also I can implement a new method in {{CacheManager}} (something like
{{enableStatisticsGlobally}}), but, perhaps, API will become inconsistent
(public methods which are not declared in {{javax.cache.CacheManager}}).
Another proposal was to implement new methods in {{IgniteCluster}}, but for now
it contains mostly methods for topology management.
Which way to choose? Are there any other proposals?
> Cache manager should switch cache statisticsEnabled property globaly
> --------------------------------------------------------------------
>
> Key: IGNITE-369
> URL: https://issues.apache.org/jira/browse/IGNITE-369
> Project: Ignite
> Issue Type: Task
> Affects Versions: sprint-2
> Reporter: Alexey Kuznetsov
> Assignee: Aleksey Plekhanov
>
> Also you should take care about new nodes that joining grid.
> New node could have statisticsEnabled with opposite value that nodes in grid.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
