[
https://issues.apache.org/jira/browse/IGNITE-8372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16449521#comment-16449521
]
ASF GitHub Bot commented on IGNITE-8372:
----------------------------------------
GitHub user sergey-chugunov-1985 opened a pull request:
https://github.com/apache/ignite/pull/3907
IGNITE-8372 ZookeeperClusterNode was made Externalizable
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8372
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3907.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3907
----
commit 6e37daf2d34ca083f367e982a3db80460ca8de16
Author: Sergey Chugunov <sergey.chugunov@...>
Date: 2018-04-24T09:14:14Z
IGNITE-8372 ZookeeperClusterNode was made Externalizable to preserve
serializing local node's metrics
----
> Cluster metrics are reported incorrectly on joining node with ZK-based
> discovery
> --------------------------------------------------------------------------------
>
> Key: IGNITE-8372
> URL: https://issues.apache.org/jira/browse/IGNITE-8372
> Project: Ignite
> Issue Type: Bug
> Components: zookeeper
> Reporter: Sergey Chugunov
> Assignee: Sergey Chugunov
> Priority: Minor
> Fix For: 2.5
>
>
> When new node joins with ZK discovery it sometimes reports negative number of
> CPUs and incorrect heap size.
> Message in log looks like this:
> {noformat}
> [myid:] - INFO [disco-event-worker-#61:Log4JLogger@495] - Topology snapshot
> [ver=100, servers=100, clients=0, CPUs=-6, heap=0.5GB]
> {noformat}
> There is a race though between this report and ClusterMetricsUpdateMessage:
> if the node receives and process this message first which happens in a
> separate thread correct values are printed to log.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
