I've traced this down to attempting to prepend to a list field. I was able
to workaround the issue by appending (and then sorting on query).
Prepending seems to build a timeuuid to manage the change, and it's that
step that produces the assertionerror (sometimes).
On Thu, Jan 19, 2017 at 10:56 AM
The first time a client connects to the cluster and sends a bunch of
inserts in parallel I get this assertion error. All subsequent inserts
(including just retrying the first requests) work fine. The only assert in
PrecisionTime is checking if the millis argument is <= the current millis.
What
