Sure, I got it two times in a row on an initial load (same machine, exact same table). There were two nodes doing an initial load at the same time (not sure if relevant).
I'm not sure how to reproduce it correctly, but this is what the errors on the client side looks like: