Our application can operate with either ReplicatedEnvironments (HA) or standard Environments (non-HA). We have just noticed that our application, when running in HA mode, violates the rule stated in the javdoc for Cursor#getNext() and others that "In a replicated environment, an explicit transaction must have been specified when opening the cursor, unless read-uncommitted isolation is specified via the CursorConfig or LockMode parameter". We are inadvertently calling #getNext() and #getSearchKey() on cursors from ReplicatedEnvironments without a transaction and in lock modes other than read-uncommitted. The application has seemingly been working without error for many years despite this problem.
We intend to fix the application immediately but need to formulate a response for our existing user base.
What harmful effects can we expect from this mistake? The model of our application is such that it does not actually read from an HA node until it is made master (in other words, the replica nodes are dormant, from an application perspective, until they are awoken by the election result).
We are using 5.0.104.
Thanks in advance for any advice.