You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Alex Volkov (JIRA)" <ji...@apache.org> on 2018/12/24 11:04:00 UTC

[jira] [Created] (IGNITE-10802) Documentation for option IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE

Alex Volkov created IGNITE-10802:
------------------------------------

             Summary: Documentation for option IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE
                 Key: IGNITE-10802
                 URL: https://issues.apache.org/jira/browse/IGNITE-10802
             Project: Ignite
          Issue Type: Task
          Components: documentation
    Affects Versions: 2.8
            Reporter: Alex Volkov


After implementation  -IGNITE-10172- it's not clear how cluster should behave in some cases.

For example, if I have cluster with option 

IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE=True and one additional node with flag 

IGNITE_DISCOVERY_DISABLE_CACHE_METRICS_UPDATE=False comes to this cluster. What behaviour should I expect from the cluster?

In general, please provide documentation for this option.



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