under higher sets per second clients dont get all view results after observing for all mutations

We have just recently found that under load, doing a series of writes, waiting until they're durable, and then querying a view with stale=false gives incorrect results. I should note that this is definitely tied to throughput load. Under minimal load, it works fine. Under a lot of load, we see the incorrect results. This could be a client issue, but I admit that it sounds more like a server side issue at the moment. We're going to try to reproduce it with another client before raising a server issue. It's JCBC-142 at the moment.