Jenkins jobs in ABORTED status are bad. A lot of times they tend to be
ignored/re-run to get completed results, which is OK, only if the reason
is due to server setup or configuration problems. There's a relatively
recent pattern of o.a.c.cql3.validation test hanging up jobs, and I've
been unable t
The map version of the schema needs to deserialize, serialize, and then
deserialize about 85 times more cells, if your average map has 85
elements. I would assume that's where most of the performance slowdown is
coming from. If you can take the time to run that through a profiler, that
would be u
cassandra-3.9
===
testall: All passed!
===
dtest: 2 failures
repair_tests.repair_test.TestRepair.nonexistent_table_repair_test
CASSANDRA-12578. New failure, looks like a test problem.
cql_tracin
Another couple ABORT examples have presented themselves, tonight, one
that has logs.
Usually we'll see unit tests finish similar to:
01:57:39 [junit] Testsuite:
org.apache.cassandra.cql3.statements.PropertyDefinitionsTest
01:57:39 [junit] Testsuite:
org.apache.cassandra.cql3.statements.Pr
Thanks Tyler!
I wasn't aware of frozen collections - the tracing shows pretty similar
timing characteristics between frozen collection and binary schemas.
Interestingly it's still dog slow while (presumably) doing the
deserialization in python, so although the trace reports good results it's
st
