You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Michael Dodge (JIRA)" <ji...@apache.org> on 2018/03/08 23:59:00 UTC
[jira] [Commented] (GEODE-3694) New protocol should create unique
client IDs
[ https://issues.apache.org/jira/browse/GEODE-3694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392135#comment-16392135 ]
Michael Dodge commented on GEODE-3694:
--------------------------------------
It seems like {{TcpServer.handleProtobufConnection()}} is the place to associate a client ID with a socket. However, I do not see any interaction with handshaking from whence a client ID might come. Maybe {{ProtobufStreamProcessor}} is a better place to associate a client ID with a socket connection.
> New protocol should create unique client IDs
> --------------------------------------------
>
> Key: GEODE-3694
> URL: https://issues.apache.org/jira/browse/GEODE-3694
> Project: Geode
> Issue Type: Improvement
> Components: client/server
> Reporter: Brian Baynes
> Priority: Major
>
> As a dev/admin using the new protocol, I'd like to be able to see client connection/socket use in the aggregate -- for example, if I have a single client opening many more sockets than others, this info may help me figure out if there's a problem. Just knowing the kind of load a particular client may be introducing would also be valuable.
> Implement unique client IDs for new protocol clients so we can associate multiple connections from the same client with one another.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)