cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13899) Streaming of compressed partition fails
Date Tue, 03 Oct 2017 19:27:00 GMT


Jason Brown commented on CASSANDRA-13899:

[~pauloricardomg] do you think you can finish up the review on this soonish?

> Streaming of compressed partition fails 
> ----------------------------------------
>                 Key: CASSANDRA-13899
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Paulo Motta
>            Assignee: Jason Brown
>             Fix For: 4.0
>         Attachments: largepartition.yaml
> Streaming a single partition with ~100K rows fails with the following exception:
> {noformat}
> ERROR [Stream-Deserializer-/] 2017-09-21 04:03:41,237
- [Stream #c2e5b640-9eab-11e7-99c0-e9864ca8da8e] Streaming error occurred on session with
> org.apache.cassandra.streaming.StreamReceiveException: java.lang.RuntimeException: Last
written key DecoratedKey(-1000328290821038380) >= current key DecoratedKey(-1055007227842125139)
 writing into /home/paulo/.ccm/test/node2/data0/stresscql/typestest-482ac7b09e8d11e787cf85d073c
> 8e037/na-1-big-Data.db
>         at org.apache.cassandra.streaming.messages.IncomingFileMessage$1.deserialize(
>         at org.apache.cassandra.streaming.messages.IncomingFileMessage$1.deserialize(
>         at org.apache.cassandra.streaming.messages.StreamMessage.deserialize(
>         at org.apache.cassandra.streaming.async.StreamingInboundHandler$
>         at [na:1.8.0_121]
> {noformat}
> Reproduction steps:
>  * Create CCM cluster with 2 nodes
> * Start only first node, disable hinted handoff
>  * Run stress with the attached yaml: {{tools/bin/cassandra-stress "user profile=largepartition.yaml
n=10K ops(insert=1) no-warmup -node whitelist -mode native cql3 compression=lz4
-rate threads=4 -insert visits=FIXED(100K) revisit=FIXED(100K)"}}
> * Start second node, run repair on {{stresscql}} table - the exception above will be
> I investigated briefly and haven't found anything suspicious. This seems to be related
to CASSANDRA-12229 as I tested the steps above in a branch without that and the repair completed
successfully. I haven't tested with a smaller number of rows per partition to see at which
point it starts to be a problem.
> We should probably add a regression dtest to stream large partitions to catch similar
problems in the future.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message