[
https://issues.apache.org/jira/browse/CASSANDRA-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712624#action_12712624
]
Jonathan Ellis commented on CASSANDRA-197:
------------------------------------------
It makes no sense to incur the disadvantages of making your client an add-on to
the server code without going all the way. The server already has perfectly
good connection pooling code; it makes sense to use that instead of creating a
separate pooling mechanism. Nor does it make sense when you are building off
the server jars to go through the extra thrift serialization; make the calls
directly via MessagingService.
The right way to do this is to make the tweaks to the gossip layer necessary to
let a specialized server-client get token ring information with server-level
APIs. I'm strongly against the kludge of doing this at the client layer.
Since the only consumers of that API will necessarily have access to the server
codebase, keeping it in server APIs makes the most sense, and we already have
an server API for distributing token information.
> Expose ring map to client for more direct access
> ------------------------------------------------
>
> Key: CASSANDRA-197
> URL: https://issues.apache.org/jira/browse/CASSANDRA-197
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jun Rao
> Assignee: Jun Rao
> Attachments: issue197.patchv1
>
>
> For certain applications, it would be nice if a read is sent to a node that
> owns the data locally. This saves an extra network hop. To do that, a client
> will need to cache the ring map and use it to figure out the nodes owning a
> row.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
