You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (JIRA)" <ji...@apache.org> on 2014/12/12 15:54:13 UTC
[jira] [Comment Edited] (CASSANDRA-8458) Don't give out positions
in an sstable beyond its first/last tokens
[ https://issues.apache.org/jira/browse/CASSANDRA-8458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14244219#comment-14244219 ]
Marcus Eriksson edited comment on CASSANDRA-8458 at 12/12/14 2:53 PM:
----------------------------------------------------------------------
attached patch makes checks first/last keys in an sstable to make sure we don't give out positions beyond them
was (Author: krummas):
attached file makes checks first/last keys in an sstable to make sure we don't give out positions beyond them
> Don't give out positions in an sstable beyond its first/last tokens
> -------------------------------------------------------------------
>
> Key: CASSANDRA-8458
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8458
> Project: Cassandra
> Issue Type: Bug
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Fix For: 2.1.3
>
> Attachments: 0001-Make-sure-we-don-t-give-out-positions-from-an-sstabl.patch
>
>
> Looks like we include tmplink sstables in streams in 2.1+, and when we do, sometimes we get this error message on the receiving side: {{java.io.IOException: Corrupt input data, block did not start with 2 byte signature ('ZV') followed by type byte, 2-byte length)}}. I've only seen this happen when a tmplink sstable is included in the stream.
> We can not just exclude the tmplink files when starting the stream - we need to include the original file, which we might miss since we check if the requested stream range intersects the sstable range.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)