You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sylvain Pognant (JIRA)" <ji...@apache.org> on 2013/01/16 16:54:14 UTC
[jira] [Comment Edited] (CASSANDRA-4687) Exception:
DecoratedKey(xxx, yyy) != DecoratedKey(zzz, kkk)
[ https://issues.apache.org/jira/browse/CASSANDRA-4687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13555143#comment-13555143 ]
Sylvain Pognant edited comment on CASSANDRA-4687 at 1/16/13 3:53 PM:
---------------------------------------------------------------------
Just been hit by the same issue :
cassandra 1.2.0 cluster with 6 nodes, using vnodes, no write activity from clients, just one client reading a specific row (replication factor 2)
I was randomly stopping/starting nodes to test the client read behavior.
At some point I restarted a node holding the row (the other replicating node was down) and started to get 'unable to seek to position XXXXXX' errors on that node.
- Tried restarting the node : no change
- Removed the content of saved_caches/ : fixed the problem
So, as commented above, the saved cache seems to be invalid.
Note that I always stopped the nodes cleanly.
was (Author: s.pognant@overkiz.com):
Just been hit by the same issue :
cassandra 1.2.0 cluster with 6 nodes, no write activity from clients, just one client reading a specific row (replication factor 2)
I was randomly stopping/starting nodes to test the client read behavior.
At some point I restarted a node holding the row (the other replicating node was down) and started to get 'unable to seek to position XXXXXX' errors on that node.
- Tried restarting the node : no change
- Removed the content of saved_caches/ : fixed the problem
So, as commented above, the saved cache seems to be invalid.
Note that I always stopped the nodes cleanly.
> Exception: DecoratedKey(xxx, yyy) != DecoratedKey(zzz, kkk)
> -----------------------------------------------------------
>
> Key: CASSANDRA-4687
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4687
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: CentOS 6.3 64-bit, Oracle JRE 1.6.0.33 64-bit, single node cluster
> Reporter: Leonid Shalupov
> Assignee: Pavel Yaskevich
> Fix For: 1.2.2
>
> Attachments: 4687-debugging.txt
>
>
> Under heavy write load sometimes cassandra fails with assertion error.
> git bisect leads to commit 295aedb278e7a495213241b66bc46d763fd4ce66.
> works fine if global key/row caches disabled in code.
> {quote}
> java.lang.AssertionError: DecoratedKey(xxx, yyy) != DecoratedKey(zzz, kkk) in /var/lib/cassandra/data/...-he-1-Data.db
> at org.apache.cassandra.db.columniterator.SSTableSliceIterator.<init>(SSTableSliceIterator.java:60)
> at org.apache.cassandra.db.filter.SliceQueryFilter.getSSTableColumnIterator(SliceQueryFilter.java:67)
> at org.apache.cassandra.db.filter.QueryFilter.getSSTableColumnIterator(QueryFilter.java:79)
> at org.apache.cassandra.db.CollationController.collectAllData(CollationController.java:256)
> at org.apache.cassandra.db.CollationController.getTopLevelColumns(CollationController.java:64)
> at org.apache.cassandra.db.ColumnFamilyStore.getTopLevelColumns(ColumnFamilyStore.java:1345)
> at org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1207)
> at org.apache.cassandra.db.ColumnFamilyStore.getColumnFamily(ColumnFamilyStore.java:1142)
> at org.apache.cassandra.db.Table.getRow(Table.java:378)
> at org.apache.cassandra.db.SliceFromReadCommand.getRow(SliceFromReadCommand.java:69)
> at org.apache.cassandra.service.StorageProxy$LocalReadRunnable.runMayThrow(StorageProxy.java:819)
> at org.apache.cassandra.service.StorageProxy$DroppableRunnable.run(StorageProxy.java:1253)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> {quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira