ok yeah, i've been running some more repairs cause i wanted to fix things. definitely just an issue of some of the new DB nodes not having an accurate picture of some of the data and since we're not using quorum for read-only API requests, we don't have a chance to automatically heal via row-repairs
All reads in service of write requests are quorum reads but that doesn't really help in this particular case. I _think_ the repairs I'm running should resolve the issues though.
Comments