You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Max Shonichev (JIRA)" <ji...@apache.org> on 2018/05/03 10:56:00 UTC

[jira] [Updated] (IGNITE-8430) implement getCurrentCoordinator method in IgniteMXBean

     [ https://issues.apache.org/jira/browse/IGNITE-8430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Shonichev updated IGNITE-8430:
----------------------------------
    Affects Version/s: 2.5
        Fix Version/s: 2.5
          Description: 
Currently, user can obtain coordinator node id via JMX attribute Coordinator of TcpDiscoverySpi OR ZookeeperDiscoverySpi MBean.

However, to get this attribute, external utility JMX must first understand which discovery SPI implementation is used at current grid, which is inconvenient. Would be much better if that attribute was located in same instance no matter which Disco SPI was configured.

Please, add String CurrentCoordinator attribute to Ignite MX bean with following meaning:
  - for the cases, when node does not know current coordinator (e.g. getCoordinator returns null), attribute should be empty string ''
  - for the case, when node knows current coordinator, return following coordinator properties formatted as string, separated by ',':
   -- Coordinator IP address
   -- Coordinator node ID
   -- Coordinator node order
   -- Coordinator Fully Qualified Domain Name
              Summary: implement getCurrentCoordinator method in IgniteMXBean  (was: gety)

> implement getCurrentCoordinator method in IgniteMXBean
> ------------------------------------------------------
>
>                 Key: IGNITE-8430
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8430
>             Project: Ignite
>          Issue Type: New Feature
>    Affects Versions: 2.5
>            Reporter: Max Shonichev
>            Priority: Major
>             Fix For: 2.5
>
>
> Currently, user can obtain coordinator node id via JMX attribute Coordinator of TcpDiscoverySpi OR ZookeeperDiscoverySpi MBean.
> However, to get this attribute, external utility JMX must first understand which discovery SPI implementation is used at current grid, which is inconvenient. Would be much better if that attribute was located in same instance no matter which Disco SPI was configured.
> Please, add String CurrentCoordinator attribute to Ignite MX bean with following meaning:
>   - for the cases, when node does not know current coordinator (e.g. getCoordinator returns null), attribute should be empty string ''
>   - for the case, when node knows current coordinator, return following coordinator properties formatted as string, separated by ',':
>    -- Coordinator IP address
>    -- Coordinator node ID
>    -- Coordinator node order
>    -- Coordinator Fully Qualified Domain Name



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)