CFS.truncateBlocking relies on sleep

ColumnFamilyStore.truncateBlocking uses Uninterruptibles.sleepUninterruptibly(1, TimeUnit.MILLISECONDS); to ensure that truncatedAt does not compete with a deletedAt.
System.currentTimeMillis() usually (it's not guaranteed) works as expected on Linux and OSX - but especially on Windows it may stall (update the System.currentTimeMillis() at non-regular intervals).

I don't think this is a major issue as it just affects the truncate operation, which is a DDL operation, which should never be used in application code (IMO).