cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Branimir Lambov (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11960) Hints are not seekable
Date Mon, 20 Jun 2016 15:06:05 GMT


Branimir Lambov commented on CASSANDRA-11960:

Is it possible to save both the file offset (from {{getSourcePosition}}) as well as the buffer
offset? This would let us resume from exactly where we stopped, wouldn't it?

I believe the reason I removed the seeking was because I saw it can't work correctly for compressed
files (as we store uncompressed offset but don't have a way to map it to compressed chunk
and offset), and after that I wasn't very thorough in checking that it's not actually used.

> Hints are not seekable
> ----------------------
>                 Key: CASSANDRA-11960
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Robert Stupp
>            Assignee: Stefan Podkowinski
> Got the following error message on trunk. No idea how to reproduce. But the only thing
the (not overridden) seek method does is throwing this exception.
> {code}
> ERROR [HintsDispatcher:2] 2016-06-05 18:51:09,397 - Exception
in thread Thread[HintsDispatcher:2,1,main]
> java.lang.UnsupportedOperationException: Hints are not seekable.
> 	at ~[main/:na]
> 	at ~[main/:na]
> 	at org.apache.cassandra.hints.HintsDispatchExecutor$DispatchHintsTask.deliver(
> 	at org.apache.cassandra.hints.HintsDispatchExecutor$DispatchHintsTask.dispatch(
> 	at org.apache.cassandra.hints.HintsDispatchExecutor$DispatchHintsTask.dispatch(
> 	at org.apache.cassandra.hints.HintsDispatchExecutor$
> 	at java.util.concurrent.Executors$ ~[na:1.8.0_91]
> 	at ~[na:1.8.0_91]
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker( ~[na:1.8.0_91]
> 	at java.util.concurrent.ThreadPoolExecutor$ [na:1.8.0_91]
> 	at [na:1.8.0_91]
> {code}

This message was sent by Atlassian JIRA

View raw message