You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Helena Bales (JIRA)" <ji...@apache.org> on 2018/08/03 00:57:00 UTC

[jira] [Resolved] (GEODE-5157) ClientHealthStats may not be propagated when system has a hostname

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

Helena Bales resolved GEODE-5157.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 1.8.0

> ClientHealthStats may not be propagated when system has a hostname
> ------------------------------------------------------------------
>
>                 Key: GEODE-5157
>                 URL: https://issues.apache.org/jira/browse/GEODE-5157
>             Project: Geode
>          Issue Type: Bug
>          Components: cq, jmx
>            Reporter: Jens Deppe
>            Assignee: Helena Bales
>            Priority: Major
>             Fix For: 1.8.0
>
>
> For CQs, the client publishes stats from {{ClientStatsManager.publishClientStats}}. Here the client memberId is used as a key for putting the stats into an admin region. If the client has a valid hostname then the memberId contains the hostname. If there is no valid hostname, then the memberId is just the IP address.
> On the server side, clientIDs are determined from {{CacheClientProxy}} objects - see {{CacheServerBridge.getUniqueClientIds}}. It appears that these IDs are always IP-address based.
> Thus if there is this mismatch then ClientHealthStats are not published correctly.



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