Log spam when data change counter is being used

When data change counter is configured to count changes in the topology, the log files start to be spammed with OptimisticLockFailed exceptions whenever any updates are received. The amount of this log spam is about 2MB per 1k routes, reducing the usability of logging a lot when log rotation is configured (pushing 10k of routes generated 20MB of spam which essentially flushes the logs on the default settings.