Few ideas about timing and timestamps extraction from the heap dump:
1) Here
https://github.com/apache/cassandra/blob/c1d89c32d27921d1f77f05d29ee248b8922a4c76/src/java/org/apache/cassandra/db/Keyspace.java#L627
you can check the time when the write operation within
"read-hotness-tracker:1" started
Found my issue, it was with the primary key being a combination of uuid
and type. With that fixed, I now have a table with 1.5 million vectors
(768 dimensions) on a 16 node cluster. While I can now execute a CQL
query that includes fields and the order by ANN, it runs too slow. No
query compl
Hi Bowen,
lastSyncedAt is updated by taking pollStarted: lastSyncedAt = pollStarted;
where long pollStarted = clock.now();
the logic uses clock from: SyncRunnable sync = new SyncRunnable(preciseTime)
preciseTime by default is SystemClock
clock.now() -> org.apache.cassandra.utils.Clock.Default#nano
The syncComplete is an instance of WaitQueue, and the syncComplete.queue
is an instance of ConcurrentLinkedQueue. Surprisingly, the queue is
empty. There is no item in the queue's linked list, only the head and
tail nodes, each has item=null.
The usage of the WaitQueue within the AbstractCommi
