Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 98435 invoked from network); 16 Jul 2009 00:36:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 16 Jul 2009 00:36:19 -0000 Received: (qmail 74869 invoked by uid 500); 16 Jul 2009 00:36:29 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 74839 invoked by uid 500); 16 Jul 2009 00:36:29 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 74830 invoked by uid 99); 16 Jul 2009 00:36:29 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jul 2009 00:36:29 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates 209.85.219.224 as permitted sender) Received: from [209.85.219.224] (HELO mail-ew0-f224.google.com) (209.85.219.224) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 16 Jul 2009 00:36:20 +0000 Received: by ewy23 with SMTP id 23so4248549ewy.12 for ; Wed, 15 Jul 2009 17:35:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=vhZguXO2dYlsxt1oGJT2rRssJBL5qZ3cpFg2BDQb9dE=; b=uOTS4RPAen9boT6SzVOZLiixTG0qnk+8+960seMRpMPbuhyTuYt39f2S9lxXIOO6ut H2eIcI85VLm+lefOVRTOHdVN8DN4gcMmIqO5ZiaE9YqEMvMoDSpZAVc/pwJM/NbKcoBW S63gsB1Gt1PwjupTPnTDYmmW0NwcHjp5FHKKo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=eJVXSoCQlNCdzbZE/SsO1jd/yW7Tcq83kBn6DYYBbaXuLaHmW8vl32dfZep/1JFdg8 Ex9DvAPkTqDswvYF9yFw+uEzWAGmL0K6bYqvz+lxrj6/Fl7DhwFaYMr8CARkt49ZCsMT Nfwq8EqD31NtPAWWRP2nfW9O4/u2hqjuESZMM= MIME-Version: 1.0 Received: by 10.216.71.13 with SMTP id q13mr2194073wed.190.1247704559573; Wed, 15 Jul 2009 17:35:59 -0700 (PDT) In-Reply-To: <5e50457d0907151725j1542232cp2f8b698ae007a1af@mail.gmail.com> References: <5e50457d0907151725j1542232cp2f8b698ae007a1af@mail.gmail.com> Date: Wed, 15 Jul 2009 19:35:59 -0500 Message-ID: Subject: Re: Best way to use a Cassandra Client in a multi-threaded environment? From: Jonathan Ellis To: cassandra-user@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org IIRC thrift makes no effort to generate threadsafe code. which makes sense in an rpc-oriented protocol really. On Wed, Jul 15, 2009 at 7:25 PM, Joel Meyer 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