cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alon Peer (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4209) Randomly getting "Invalid bytes remaining after an end-of-component at component1" exceptions
Date Wed, 02 May 2012 12:58:50 GMT


Alon Peer commented on CASSANDRA-4209:

I did:, but their response time isn't that great.

I'll post your thoughts on this there too. But how can this be reproduced in your opinion?
I only saw this happening on our production environment, with thousands of concurrent requests.
I wasn't able to reproduce this permanently on dev environment.
> Randomly getting "Invalid bytes remaining after an end-of-component at component1" exceptions
> ---------------------------------------------------------------------------------------------
>                 Key: CASSANDRA-4209
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.9
>         Environment: Linux version (
>            Reporter: Alon Peer
> I have a CF with composite column sort:
> {noformat}
> ColumnFamily: MyCF
>   Key Validation Class: org.apache.cassandra.db.marshal.UTF8Type
>   Default column value validator: org.apache.cassandra.db.marshal.UTF8Type
>   Columns sorted by: org.apache.cassandra.db.marshal.CompositeType(org.apache.cassandra.db.marshal.AsciiType,org.apache.cassandra.db.marshal.IntegerType)
>   Row cache size / save period in seconds / keys to save : 0.0/0/all
>   Row Cache Provider: org.apache.cassandra.cache.SerializingCacheProvider
>   Key cache size / save period in seconds: 200000.0/14400
>   GC grace seconds: 864000
>   Compaction min/max thresholds: 4/32
>   Read repair chance: 0.1
>   Replicate on write: true
>   Bloom Filter FP chance: default
>   Built indexes: []
>   Compaction Strategy: org.apache.cassandra.db.compaction.SizeTieredCompactionStrategy
>   Compression Options:
>     chunk_length_kb: 64
>     sstable_compression:
> {noformat}
> I'm using [phpcassa|] to communicate with my Cassandra
> I'm getting the following exception from time to time while reading/writing to this CF:
> {noformat}
> exception 'cassandra_InvalidRequestException' with message
> 'Invalid bytes remaining after an end-of-component at component1' in /phpcassa/thrift/packages/cassandra/Cassandra.php:256\nStack
> #0 /phpcassa/thrift/packages/cassandra/Cassandra.php(256): thrift_protocol_read_binary(Object(TBinaryProtocolAccelerated),
'cassandra_Cassa...', false)
> #1 /phpcassa/thrift/packages/cassandra/Cassandra.php(229): CassandraClient->recv_get_slice()
> #2 [internal function]: CassandraClient->get_slice('6034-28141406', Object(cassandra_ColumnParent),
Object(cassandra_SlicePredicate), 2)
> ...
> {noformat}
> I've thoroughly checked my code, I'm always sending the same parameters to Cassandra,
and there's no format error. My column name request is always AsciiType:IntegerType.
> The weird part is that this is completely random. If I run a get() query once, I get
the exception, but the following request with the same parameters succeeds.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message