[
https://issues.apache.org/jira/browse/CASSANDRA-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783831#action_12783831
]
Paul Querna commented on CASSANDRA-569:
---------------------------------------
resetLocalSettings is called from getProcessor, because getProcessor is the
only indication you have from thrift that a *new* client has connected. As far
as I could see, there isnt a way to tell if a client is disconnected either.
Without this resetLocalSettings call, if a client set a low timeout, it
disconnected, and then a new client connected, this new client using the same
thread would have the low timeout -- the reset is there to get all new clients
back to the default timeouts.
>From my quick reading of the Thrift Thread pool server, it does reuse threads,
>not just spawn one new thread per client.
> Add Thrift API to set per-connection settings
> ---------------------------------------------
>
> Key: CASSANDRA-569
> URL: https://issues.apache.org/jira/browse/CASSANDRA-569
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Paul Querna
> Attachments: CASSANDRA-569.patch
>
>
> For thrift API, let you set configuration options per-connection. These
> would be stored thread-local on the server, and when a thrift connection
> dies, they would be reset.
> An example use case is setting the timeout for requests on a per-connection
> basis.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
