Re: Understanding tombstone WARN log output

2014-12-19 Thread Jens Rantil
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 

Understanding tombstone WARN log output

2014-12-18 Thread Jens Rantil
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=