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 juho.makinen@gmail.com
 designates 209.85.214.44 as permitted sender)
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=ZyisPnbCfxGqxIUiw0fxUp9fPEun70xOLbkBdOAgYxLOHuKFTiEPFO/btP0R97pTCB
         iKhAnhp1T3HqTfnJ8ctIS3IfVC4x7dbKsmW3HkIlcyuSbUBpT7U71EOdLIMpMp+YUDY+
         J3QrNYlhUX6uQiyrlIhproybnXFu/T8C42tI4=
MIME-Version: 1.0
In-Reply-To: <4C32F1C0.4060907@gmail.com>
References: <AANLkTilpi2P9HfR7TAou25zjRMUJyGiixI8B-i80EVWU@mail.gmail.com>
	<4C32F1C0.4060907@gmail.com>
Date: Tue, 6 Jul 2010 13:15:07 +0300
Message-ID: <AANLkTimh1X8dfb3yGLOR_HmYI90hGOZ44Qqpju5FmekE@mail.gmail.com>
Subject: Re: TSocket: Could not write 85 bytes -exception on some get_column
	calls
From: =?ISO-8859-1?Q?Juho_M=E4kinen?= <juho.makinen@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Pieter,

I switched to framed transport but it didn't completely fix the problem.

> PS. i see there is 0.6.3 now available for debian, I'll test that version=
..
> like you said you don't have the issue on 0.6.3 it might be fixed there..

I'm sorry if I didn't tell clearly enough: the problem started at
version 0.6.1, but
updating to 0.6.3 did not fix the problem.

 - Juho M=E4kinen


On Tue, Jul 6, 2010 at 12:05 PM, Pieter Maes <maescool@gmail.com> wrote:
> =A0I'm having a simmular problem, but i get verry random read problems 4
> bytes timouts. (mailed before about this)
>
> The only fix i got/found was, switch to framed transport instead of
> buffered transport, but i still have the same problem (less frequent)
>
> running debian packaged cassandra (0.6.1)
> with phpcassa lib (using thrift)
>
> I have it localhost and external host, so network/switching is not the
> problem..
> I'm afraid there is still something wrong with php thrift.. (even after
> patch https://issues.apache.org/jira/browse/THRIFT-347)
>
> PS. i see there is 0.6.3 now available for debian, I'll test that version=
..
> like you said you don't have the issue on 0.6.3 it might be fixed there..
>
> Pieter Maes
>
> Op 6/07/10 10:14, Juho M=E4kinen schreef:
>> I'm having a strange problem when some of get_column and get_slice calls
>> fails to "TSocket: Could not write 85 bytes paja.dev.pri:9160" exception=
.
>> The problem appears on some but not all calls to get_column and also
>> some times to other calls.
>>
>> I'm using 0.6.3 on a single host (it's a development installation) but
>> the problem appeared on 0.6.1. The client side is done with php using
>> the thrift api.
>>
>> I've turned on TRACE level debugging on the cassandra server and the req=
uests
>> which doesn't fail produce this kind of debug to the logs:
>>
>> DEBUG [pool-1-thread-4] 2010-07-06 11:12:23,438 CassandraServer.java
>> (line 266) get
>> DEBUG [ROW-READ-STAGE:2] 2010-07-06 11:12:23,439 StorageProxy.java
>> (line 755) weakreadlocal reading SliceByNamesReadCommand(table=3D'ig',
>> key=3D'2249', columnParent=3D'QueryPath(columnFamilyName=3D'TalkLastMess=
ages',
>> superColumnName=3D'null', columnName=3D'null')', columns=3D[2582837,])
>>
>> But the requests which fails to the TSocket: Could not write 85 bytes -e=
xception
>> doesn't print anything to the logs. I'm doing the same request all the
>> time with same
>> parameters.
>>
>> How I should debug this issue? All ideas and tips are greatly appreciate=
d.
>>
>> =A0- Juho M=E4kinen
>