[
https://issues.apache.org/jira/browse/IGNITE-5579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexey Goncharuk updated IGNITE-5579:
-------------------------------------
Fix Version/s: (was: 2.5)
2.6
> Make sure identical binary metadata updates from the same node do not happen
> twice
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-5579
> URL: https://issues.apache.org/jira/browse/IGNITE-5579
> Project: Ignite
> Issue Type: Improvement
> Components: cache
> Affects Versions: 1.7
> Reporter: Alexey Goncharuk
> Priority: Major
> Fix For: 2.6
>
>
> It is possible that multiple user threads attempt identical binary metadata
> update concurrently. In this case, a node will just increase contention on
> the cache key, but once the lock is acquired there will be nothing changed.
> On large topologies, this may lead to nodes waiting for the metadata update
> for hours (!).
> We should work out a way to identify identical metadata updates and allow
> only one thread to proceed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
