Hi, My all tasks are affinity tasks, so they are always submitted to primary node. How setting DIGNITE_READ_LOAD_BALANCING to false help in this case ? Even if it is true it will always read the values from primary node as the task is landed on primary node.
Thanks, Prasad On Fri, Feb 28, 2020 at 4:45 PM Alexey Goncharuk <[email protected]> wrote: > Prasad, > > The current version in the entry is checked agains the version which was > read from the very same entry, so with absence of concurrent updates the > version will be the same. > > From your description, I think there might be a concurrent read for the > key that you clear which loads the value on primary node with a different > version. Then, the read happening inside transaction always reads the value > from backup which leads to a permanent version mismatch; I reproduced this > scenario locally. The -DIGNITE_READ_LOAD_BALANCING=false fixes the issue at > a price of disabling read load balancing. > > I will create a ticket for the issue shortly, perhaps someone from the > community will pick it up. >
