As the warning message suggests, you need to check for schema disagreement. My suspicion is that someone made a schema change and possibly dropped the problematic keyspace.
FWIW I suspect the keyspace was dropped because the table isn't new -- CF ID cba90a70-5c46-11e9-9e36-f54fe3235e69 is equivalent to 11 Apr 2019. Check for the existence of the keyspace via cqlsh on other nodes in the cluster (not the node which ran out of disk space). Cheers!
