You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2021/04/09 16:55:00 UTC

[jira] [Commented] (IGNITE-12920) Static hierarchy in jmx tree

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

Ignite TC Bot commented on IGNITE-12920:
----------------------------------------

{panel:title=Branch: [pull/8972/head] Base: [master] : No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8972/head] Base: [master] : New Tests (1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#00008b}Basic 1{color} [[tests 1|https://ci.ignite.apache.org/viewLog.html?buildId=5959446]]
* {color:#013220}IgniteBasicTestSuite: GridMBeanSelfTest.testMbeanCreation - PASSED{color}

{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=5959321&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Static hierarchy in jmx tree
> ----------------------------
>
>                 Key: IGNITE-12920
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12920
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Igor Akkuratov
>            Assignee: Igor Akkuratov
>            Priority: Major
>         Attachments: image-2020-04-20-17-05-36-451.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Current jmx tree hierarchy depends on jvm and ignite options and contains classloader by default.
> !image-2020-04-20-17-05-36-451.png!
> Monitoring systems like zabbix use bean path to discover metrics. Classloader is been changing after node restart and monitoring systems rediscover new metrics. If you'll try to disable classloader with option
> {code:java}
> IGNITE_MBEAN_APPEND_CLASS_LOADER_ID=false{code}
> the jmx tree will exclude one level. This behavior excludes an opportunity to create single monitoring template for different deployments. It can also make troubles if you want to start more then one ignite instance in single jvm. In this case you'll have to set {color:#1d1c1d}igniteInstanceName{color} property to add one more level with the name of this instance. It will affect jmx tree hierarchy as well. 
>  I propose to make hierarchy unchangeable and select one of the following values.
> If exist instancename
> else if exist consistantId
>  
> In cases with enabled persistent storage consistent id  would be the same between node restarts, in in-memory cases you will be able to specify instanceName.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)