Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of ryan@twitter.com designates
 209.85.214.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=twitter.com; s=google;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=lwqD2VfiZT8l8kERTDczdaHgWAzz+puhOkM7cI+YWb4vwuVlOF3+K1hYoPB3vQQebC
         rCMZiJVpvOPtQ7dH8kPTcQ5LljhYYsr4/t5gxBUUOk8SApkrHuYbUWCDrUatLsaVGwuL
         nfc2auNin+9iAT8Rc15KBklFgXhgnuKqN05D8=
MIME-Version: 1.0
In-Reply-To: <BANLkTimgr3hg4ptsMELQ-TjeYdz6vk0+7g@mail.gmail.com>
References: <BANLkTimgr3hg4ptsMELQ-TjeYdz6vk0+7g@mail.gmail.com>
From: Ryan King <ryan@twitter.com>
Date: Thu, 16 Jun 2011 09:12:52 -0700
Message-ID: <BANLkTimj+Q-OpiGx_JeVmak444Gjo-z6Xg@mail.gmail.com>
Subject: Re: snitch & thrift
To: user@cassandra.apache.org
Content-Type: text/plain; charset=UTF-8

On Thu, Jun 16, 2011 at 6:11 AM, Terje Marthinussen
<tmarthinussen@gmail.com> wrote:
> Hi all!
> Assuming a node ends up in GC land for a while, there is a good chance that
> even though it performs terribly and the dynamic snitching will help you to
> avoid it on the gossip side, it will not really help you much if thrift
> still accepts requests and the thrift interface has choppy performance.
> This makes me wonder if it is a potential idea with thrift only client mode
> nodes.

Those could GC too, albeit to a lesser degree.

> I don't think I have seen that this exists today (or is it possible that I
> have missed a way to configure that?), but it does not seem like a very hard
> thing to make and could maybe be good in some usage patterns for the
> datanode as well as the thrift side.

It might be sometimes useful, but we can't really know without running
some tests.

-ryan