Hi again,
A follow-up question (to my yet unanswered question):
How come the first localDeletion is Integer.MAX_VALUE above? Should it be?
Cheers,
Jens
———
Jens Rantil
Backend engineer
Tink AB
Email: jens.ran...@tink.se
Phone: +46 708 84 18 32
Web: www.tink.se
Facebook Linkedin Twitter
On Thu, Dec 18, 2014 at 2:48 PM, Jens Rantil wrote:
> Hi,
> I am occasionally seeing:
> WARN [ReadStage:9576] 2014-12-18 11:16:19,042 SliceQueryFilter.java (line
> 225) Read 756 live and 17027 tombstoned cells in mykeyspace.mytable (see
> tombstone_warn_threshold). 5001 columns was requested,
> slices=[73c31274-f45c-4ba5-884a-6d08d20597e7:myfield-],
> delInfo={deletedAt=-9223372036854775808, localDeletion=2147483647,
> ranges=[73f0b59e-7525-4a18-a84f-d2a2f0505503-73f0b59e-7525-4a18-a84f-d2a2f0505503:!,
> deletedAt=141872018676,
> localDeletion=1418720186][74374d72-2688-4e64-bb0b-f51a956b0529-74374d72-2688-4e64-bb0b-f51a956b0529:!,
> deletedAt=1418720184675000, localDeletion=1418720184] ...
> in system.log. My primary key is ((userid uuid), id uuid). Is it possible
> for me to see from this output which partition key and/or ranges that has
> all of these tombstones?
> Thanks,
> Jens
> --
> Jens Rantil
> Backend engineer
> Tink AB
> Email: jens.ran...@tink.se
> Phone: +46 708 84 18 32
> Web: www.tink.se
> Facebook Linkedin
>
> Twitter
