Well, this makes me wonder how varints are compared in java vs python because the problem may be there.
I'd suggest getting the token, to know which server contains the missing data. Go there and convert sstables to json, find the record and see what's there as the tnt_id. You could also use the thrift client to list it and see how it looks on disk and see if there's something wrong. If the data is there and looks fine, probably there's a problem managing varints somewhere in the read path. Regarfds Carlos Alonso | Software Engineer | @calonso <https://twitter.com/calonso> On 23 November 2015 at 13:55, Ramon Rockx <ra...@iqnomy.com> wrote: > Hello Prem, > > On Mon, Nov 23, 2015 at 2:36 PM, Prem Yadav <ipremya...@gmail.com> wrote: > >> Can you run the trace again for the query "select * " without any >> conditions and see if you are getting results for tnt_id=5? >> <http://www.iqnomy.com/> > > > Of course, here are the results, with trace: > > cqlsh> tracing on > Now tracing requests. > cqlsh> select * from mls.te limit 330; > > period | tnt_id | evt_id | > evt_type | data > > -------------+------------+--------------------------------------+----------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > ...8<... > 62013120356 | 5 | c16bb2a0-5c1b-11e3-bf53-402d20524153 | 0 > | > {"v":1383387,"s":2052457,"r":95257,"pvs":3610247,"u":" > http://www.example.com"} > 62013120356 | 5 | 9f6cb1e0-5c1b-11e3-bf53-402d20524153 | > 0 | > {"v":1383387,"s":2052457,"r":95257,"pvs":3610246,"u":" > http://www.example.com"} > 62013120356 | 5 | 3f33f950-5c1b-11e3-bf53-402d20524153 | > 0 | > {"v":1383387,"s":2052457,"r":95257,"pvs":3610245,"u":" > http://www.example.com"} > 62013120356 | 5 | ec15e5d0-5c1a-11e3-bf53-402d20524153 | > 0 | > {"v":1383387,"s":2052457,"r":95257,"pvs":3610243,"u":" > http://www.example.com"} > 62015032164 | 2063819251 | 63d5c920-cfdb-11e4-85e9-000c2981ebb4 | > 0 > | > {"v":1451223,"s":2130306,"r":104667,"u":"http://www.example.com"} > 62015032164 | 2063819251 | 111ce010-cfdb-11e4-85e9-000c2981ebb4 | > 0 > | > {"v":1451222,"s":2130305,"r":104769,"u":"http://www.example.com"} > 62015032164 | 2063819251 | 105e7210-cfdb-11e4-85e9-000c2981ebb4 | > 0 > | > {"v":1451221,"s":2130304,"r":104769,"u":"http://www.example.com"} > 62015061055 | 2147429759 | 35b97470-0f68-11e5-8cc3-000c2981ebb4 | > 1 > | > {"v":1453821,"s":2134354,"r":105462,"q":"13082ede-0843-47ee-8126-ba3767eae547"} > 62015061055 | 2147429759 | 35a0bc50-0f68-11e5-8cc3-000c2981ebb4 | > 0 > | > {"v":1453821,"s":2134354,"r":105462,"u":"http://www.example.com"} > > > Tracing session: 5bf98eb0-91e8-11e5-9612-6783eab735d4 > > activity > | timestamp | source | source_elapsed > > ------------------------------------------------------------------------------------------------+--------------+---------------+---------------- > > execute_cql3_query | 14:44:46,620 | 192.168.0.210 | 0 > Parsing select * > from mls.te limit 330; | 14:44:46,621 | 192.168.0.210 | 526 > > Preparing statement | 14:44:46,621 | 192.168.0.210 | 990 > > Determining replicas to query | 14:44:46,621 | 192.168.0.210 | > 1174 > Enqueuing > request to /192.168.0.212 | 14:44:46,622 | 192.168.0.210 | 1661 > Sending > message to /192.168.0.212 | 14:44:46,622 | 192.168.0.210 | 1832 > Message > received from /192.168.0.210 | 14:44:46,631 | 192.168.0.212 | > 25 > Executing seq scan across 2 sstables for [min(-1), > max(2517740252400273538161079278238384398)] | 14:44:46,631 | 192.168.0.212 > | 476 > Seeking to partition > beginning in data file | 14:44:46,665 | 192.168.0.212 | 33929 > Read 6 live > and 0 tombstoned cells | 14:44:46,665 | 192.168.0.212 | 34013 > Seeking to partition > beginning in data file | 14:44:46,665 | 192.168.0.212 | 34027 > Read 2 live > and 0 tombstoned cells | 14:44:46,665 | 192.168.0.212 | 34039 > Seeking to partition > beginning in data file | 14:44:46,665 | 192.168.0.212 | 34047 > Read 6 live > and 0 tombstoned cells | 14:44:46,665 | 192.168.0.212 | 34065 > Seeking to partition > beginning in data file | 14:44:46,665 | 192.168.0.212 | 34073 > Read 1 live > and 0 tombstoned cells | 14:44:46,665 | 192.168.0.212 | 34083 > Seeking to partition > beginning in data file | 14:44:46,665 | 192.168.0.212 | 34090 > Read 74 live > and 0 tombstoned cells | 14:44:46,665 | 192.168.0.212 | 34249 > Seeking to partition > beginning in data file | 14:44:46,665 | 192.168.0.212 | 34257 > Read 1 live > and 0 tombstoned cells | 14:44:46,665 | 192.168.0.212 | 34267 > Seeking to partition > beginning in data file | 14:44:46,665 | 192.168.0.212 | 34274 > Read 1 live > and 0 tombstoned cells | 14:44:46,665 | 192.168.0.212 | 34284 > Seeking to partition > beginning in data file | 14:44:46,665 | 192.168.0.212 | 34293 > Read 2 live > and 0 tombstoned cells | 14:44:46,665 | 192.168.0.212 | 34304 > Seeking to partition > beginning in data file | 14:44:46,665 | 192.168.0.212 | 34311 > Read 3 live > and 0 tombstoned cells | 14:44:46,665 | 192.168.0.212 | 34324 > Seeking to partition > beginning in data file | 14:44:46,665 | 192.168.0.212 | 34331 > Read 3 live > and 0 tombstoned cells | 14:44:46,665 | 192.168.0.212 | 34345 > Seeking to partition > beginning in data file | 14:44:46,665 | 192.168.0.212 | 34352 > Read 4 live > and 0 tombstoned cells | 14:44:46,665 | 192.168.0.212 | 34366 > Seeking to partition > beginning in data file | 14:44:46,665 | 192.168.0.212 | 34373 > Read 32 live > and 0 tombstoned cells | 14:44:46,667 | 192.168.0.212 | 36300 > Seeking to partition > beginning in data file | 14:44:46,667 | 192.168.0.212 | 36313 > Read 11 live > and 0 tombstoned cells | 14:44:46,667 | 192.168.0.212 | 36342 > Seeking to partition > beginning in data file | 14:44:46,667 | 192.168.0.212 | 36350 > Read 3 live > and 0 tombstoned cells | 14:44:46,667 | 192.168.0.212 | 36363 > Seeking to partition > beginning in data file | 14:44:46,667 | 192.168.0.212 | 36371 > Read 2 live > and 0 tombstoned cells | 14:44:46,667 | 192.168.0.212 | 36383 > Seeking to partition > beginning in data file | 14:44:46,667 | 192.168.0.212 | 36391 > Read 17 live > and 0 tombstoned cells | 14:44:46,667 | 192.168.0.212 | 36429 > Seeking to partition > beginning in data file | 14:44:46,667 | 192.168.0.212 | 36437 > Read 42 live > and 0 tombstoned cells | 14:44:46,667 | 192.168.0.212 | 36524 > Seeking to partition > beginning in data file | 14:44:46,667 | 192.168.0.212 | 36532 > Read 8 live > and 0 tombstoned cells | 14:44:46,667 | 192.168.0.212 | 36553 > Seeking to partition > beginning in data file | 14:44:46,667 | 192.168.0.212 | 36561 > Read 1 live > and 0 tombstoned cells | 14:44:46,667 | 192.168.0.212 | 36571 > Seeking to partition > beginning in data file | 14:44:46,667 | 192.168.0.212 | 36578 > Read 1 live > and 0 tombstoned cells | 14:44:46,667 | 192.168.0.212 | 36587 > Seeking to partition > beginning in data file | 14:44:46,667 | 192.168.0.212 | 36595 > Read 2 live > and 0 tombstoned cells | 14:44:46,667 | 192.168.0.212 | 36607 > Seeking to partition > beginning in data file | 14:44:46,667 | 192.168.0.212 | 36614 > Read 83 live > and 0 tombstoned cells | 14:44:46,667 | 192.168.0.212 | 36794 > Seeking to partition > beginning in data file | 14:44:46,667 | 192.168.0.212 | 36801 > Read 20 live > and 0 tombstoned cells | 14:44:46,667 | 192.168.0.212 | 36844 > Seeking to partition > beginning in data file | 14:44:46,667 | 192.168.0.212 | 36853 > Read 3 live > and 0 tombstoned cells | 14:44:46,668 | 192.168.0.212 | 36866 > Seeking to partition > beginning in data file | 14:44:46,668 | 192.168.0.212 | 36874 > Read 3 live > and 0 tombstoned cells | 14:44:46,668 | 192.168.0.212 | 36886 > Seeking to partition > beginning in data file | 14:44:46,668 | 192.168.0.212 | 36893 > Read 1 live > and 0 tombstoned cells | 14:44:46,668 | 192.168.0.212 | 36902 > Scanned > 25 rows and matched 25 | 14:44:46,668 | 192.168.0.212 | 36986 > Enqueuing > response to /192.168.0.210 | 14:44:46,668 | 192.168.0.212 | 37005 > Sending > message to /192.168.0.210 | 14:44:46,668 | 192.168.0.212 | 37122 > Message > received from /192.168.0.212 | 14:44:46,672 | 192.168.0.210 | > 52230 > Processing > response from /192.168.0.212 | 14:44:46,678 | 192.168.0.210 | > 57312 > > Request complete | 14:44:46,696 | 192.168.0.210 | 76395 > > > As you can see there are still rows with tnt_id 5 in it. > > Regards, > Ramon > >
