[
https://issues.apache.org/jira/browse/CASSANDRA-4000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13223526#comment-13223526
]
Sylvain Lebresne commented on CASSANDRA-4000:
---------------------------------------------
I hesitate on that one, but in fact I think that this case can realistically
happen when:
# either the user requested 1 or 2 columns (like in this ticket). Asking for +1
or *2 doesn't change much.
# the row has been deleted but one node didn't got the tombstone yet (or at
all). In that case, you mostly want for the RR to send the missed tombstone to
the node missing it. However, we can't be sure the retry will arrive after the
RR (i.e. we may need a third retry if we're unlucky), and so asking for twice
more data from that one node may be less efficient.
I mean, clearly there is no need to over-think this and I'm good with either +1
and *2 but I'm not really convinced one will be better (nor really worse) than
the other in general.
> Division by zero on get_slice
> -----------------------------
>
> Key: CASSANDRA-4000
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4000
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.8
> Environment: We start getting this exception after upgrading from
> 1.0.1 -> 1.0.8.
> 4 nodes cluster on Cassandra v1.0.8. RF = 3.
> Hector v0.8.0-3.
> Reporter: Sergey B
> Assignee: Sylvain Lebresne
> Fix For: 1.0.9
>
> Attachments: 4000.txt
>
>
> We have a column family with String row keys and Long column keys.
> Our WideEntityService is trying to get the first column in the range from 0
> to Long.MAX. It's a batch operation performed for every row in the CF (rows
> count is approximately tens of thousands and each row contains from 0 to 1000
> columns).
> After processing each row we are removing some of the columns we have
> queried. Also, at the same time we are writing in this CF in another threads
> but somewhat less intensive.
> An error rises approximately for a one of 100 rows.
> Exception itself:
> [05-Mar-2012 18:47:25,247] ERROR [http-8095-1 WideEntityServiceImpl.java:142]
> - get: key1 - {type=RANGE, start=0, end=9223372036854775807, orderDesc=false,
> limit=1}
> me.prettyprint.hector.api.exceptions.HCassandraInternalException: Cassandra
> encountered an internal error processing this request: TApplicationError
> type: 6 message:Internal error processing get_slice
> at
> me.prettyprint.cassandra.service.ExceptionsTranslatorImpl.translate(ExceptionsTranslatorImpl.java:31)
> at
> me.prettyprint.cassandra.service.KeyspaceServiceImpl$7.execute(KeyspaceServiceImpl.java:285)
> at
> me.prettyprint.cassandra.service.KeyspaceServiceImpl$7.execute(KeyspaceServiceImpl.java:268)
> at
> me.prettyprint.cassandra.service.Operation.executeAndSetResult(Operation.java:101)
> at
> me.prettyprint.cassandra.connection.HConnectionManager.operateWithFailover(HConnectionManager.java:233)
> at
> me.prettyprint.cassandra.service.KeyspaceServiceImpl.operateWithFailover(KeyspaceServiceImpl.java:131)
> at
> me.prettyprint.cassandra.service.KeyspaceServiceImpl.getSlice(KeyspaceServiceImpl.java:289)
> at
> me.prettyprint.cassandra.model.thrift.ThriftSliceQuery$1.doInKeyspace(ThriftSliceQuery.java:53)
> at
> me.prettyprint.cassandra.model.thrift.ThriftSliceQuery$1.doInKeyspace(ThriftSliceQuery.java:49)
> at
> me.prettyprint.cassandra.model.KeyspaceOperationCallback.doInKeyspaceAndMeasure(KeyspaceOperationCallback.java:20)
> at
> me.prettyprint.cassandra.model.ExecutingKeyspace.doExecute(ExecutingKeyspace.java:85)
> at
> me.prettyprint.cassandra.model.thrift.ThriftSliceQuery.execute(ThriftSliceQuery.java:48)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
