incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ian Holsman <...@holsman.net>
Subject Re: Best way to use a Cassandra Client in a multi-threaded environment?
Date Thu, 16 Jul 2009 01:13:49 GMT
ugh.
if this is a byproduct of thrift, we should have another way of  
getting to the backend.
serialization is *not* a desired feature for most people ;-0

On 16/07/2009, at 11:06 AM, Jonathan Ellis wrote:

> What I mean is, if you have
>
> client.rpc1()
> <block for rpc1 to finish>
>
> it doesn't really matter if you can do
>
> client.rpc2()
> <block for rpc1, then rpc2>
>
> from another thread or not, since it's dumb. :)
>
> On Wed, Jul 15, 2009 at 7:41 PM, Ian Holsman<ian@holsman.net> wrote:
>>
>> On 16/07/2009, at 10:35 AM, Jonathan Ellis wrote:
>>
>>> IIRC thrift makes no effort to generate threadsafe code.
>>>
>>> which makes sense in an rpc-oriented protocol really.
>>
>> hmm.. not really. you can have a webserver calling a thrift backend  
>> quite
>> easily, and then you would have 100+ threads all calling the same  
>> code.
>>>
>>> On Wed, Jul 15, 2009 at 7:25 PM, Joel Meyer<joel.meyer@gmail.com>  
>>> wrote:
>>>>
>>>> Hello,
>>>> Are there any recommendations on how to use Cassandra Clients in a
>>>> multi-threaded front-end application (java)? Is the Client thread- 
>>>> safe or
>>>> is
>>>> it best to do a client per thread (or object pool of some sort)?
>>>> Thanks,
>>>> Joel
>>
>> --
>> Ian Holsman
>> Ian@Holsman.net
>>
>>
>>
>>

--
Ian Holsman
Ian@Holsman.net




Mime
View raw message