Hey all,
</br>
</br>
Versions: 2.1 & 2.3-SNAPSHOT</br>
Setup: 1 client, 1+ servers
</br>
</br>
I found an issue with Near Caching. When a topology change occurs the
GridNearCacheEntry.valid method will update the GridNearCacheEntry.topVer to
None. This version then never gets "reset". Causing the state of the
GridNearCacheEntry.valid to always be false because the None check is done
before the update of the version. This will cause all future request to miss
the near cache and make a remote call to the cluster
</br></br>
>From what i can see, the the AffinityTopologyVersion get set in a few spots
so i was unsure where to patch this. For testing i added a compare check to
the GridNearCacheEntry.loadedValue which set the topVer to the latest.
</br></br>
This is fairly large issue for us, as the performance goes from <1
millisecond to +40 milliseconds.
</br></br>
Let me know if you have questions.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
