In our production setup we noticed that calling reload after saving changes to a document would often result in the document as it was prior to the changes, because the document would be loaded from one of the secondary nodes. This pull request changes the reload method to always execute with strong consistency to ensure a reload always pulls in the latest version.

I'm not sure how I could modify the tests to verify that strong consistency is used when reloading, the existing specs do still pass of course.