> When I manually inspected this byte array, it seems hold all details
> correctly, except the super-column name, causing it to fetch the entire wide
> row.
What is the CF definition and what is the exact query you are sending?
There does not appear to be anything obvious in the QueryPath serde
VM Settings are
-javaagent:./../lib/jamm-0.2.5.jar -XX:+UseThreadPriorities
-XX:ThreadPriorityPolicy=42 -Xms8G -Xmx8G -Xmn800M
-XX:+HeapDumpOnOutOfMemoryError -XX:+UseParNewGC -XX:+UseConcMarkSweepGC
-XX:+CMSParallelRemarkEnabled -XX:SurvivorRatio=8
-XX:MaxTenuringThreshold=1 -XX:CMSInitiatingOccup
> We started receiving OOMs in our cassandra grid and took a heap dump
What are the JVM settings ?
What was the error stack?
> I am pasting the serialized byte array of SliceByNamesReadCommand, which
> seems to be corrupt on issuing certain digest queries.
Sorry I don't follow what you are sayi
We started receiving OOMs in our cassandra grid and took a heap dump. We
are running version 1.0.7 with LOCAL_QUORUM from both reads/writes.
After some analysis, we kind of identified the problem, with
SliceByNamesReadCommand, involving a single Super-Column. This seems to be
happening only in dig
