Updatetimestampscache invalidating space
This could occur if you have a backup node active at the same time as its live node.
Providers will be supplied to the credential store instance.%n Each provider must be installed through java.security file or through service loader from properly packaged jar file on classpath.
This can lead to significant performance problems when performing equality/dirty checking involving this Java type.
Consider registering a custom Java Type Descriptor or at least implementing equals/hash Code.
Ayende, I agree that it would add additional complexity (as a matter of fact the Raven Etag usage is awsome and it pushes the consistency across network to the limits), but the third point nailed it: not working in all the scenarios, that's a pity.
There are more than one servers on the network broadcasting the same node id.