[jira] [Resolved] (GEODE-3084) Investigate unique client IDs in server connection class

["Bruce Schuchardt (JIRA)" <ji...@apache.org>]

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

Bruce Schuchardt resolved GEODE-3084.
-------------------------------------
       Resolution: Not A Problem
    Fix Version/s: 1.3.0

Alexander's integration with ClientHealthMonitor will provide client IDs that will integrate with the other systems that require these IDs.  In the future we may need to provide a way for a client to identify itself as the owner of multiple socket connections, so that we can associate all of them and determine the load the client is placing on a server, register CQs and interest, etc.

The java client/server interface establishes the clients identity during handshake.  The client uses the tcp/ip port of its first connection to a server to establish, along with its InetSocketAddress, the ID of the client.  It then uses this same ID with each connection it creates to the servers in the cluster.  The new protocol could do something similar in a handshake protobuf message.  At the same time a response from the server could give the client information about the server including, if appropriate, its identity.

> Investigate unique client IDs in server connection class
> --------------------------------------------------------
>
>                 Key: GEODE-3084
>                 URL: https://issues.apache.org/jira/browse/GEODE-3084
>             Project: Geode
>          Issue Type: Sub-task
>          Components: client/server
>            Reporter: Galen O'Sullivan
>             Fix For: 1.3.0
>
>
> Investigate use of unique client IDs in server connection class (see below) -- gather info on complexity/impact that will inform a decision to fix (or not).
> There is some logic around unique client IDs that is used by {{ServerConnection}}. Look at what calls this (outside of the {{Command classes}}, which shouldn't be calling {{NewClientServerConnection}} objects) and determine if we need to make our own {{ClientProxyID}}s or if the interface can be abstracted in a better way.
> This is related to {{ServerConnection}'s {{getSocketHost()}} and {{getSocketPort()}} (see GEODE-3085), which seem to be used mostly for management and reporting.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)