[
https://issues.apache.org/jira/browse/IGNITE-6667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216662#comment-16216662
]
Alexei Scherbakov edited comment on IGNITE-6667 at 10/24/17 1:57 PM:
---------------------------------------------------------------------
[~sboikov]
I've implemented flexible strategy for disco cache reuse, please take a look.
TC: https://ci.ignite.apache.org/viewQueued.html?itemId=909093 (still in queue)
was (Author: ascherbakov):
[~sboikov]
I've implemented flexible strategy for disco cache reuse, please take a look.
TC: https://ci.ignite.apache.org/viewQueued.html?itemId=906993 (still in queue)
> Allow discovery cache instance reuse if only minor topology change has
> occured.
> -------------------------------------------------------------------------------
>
> Key: IGNITE-6667
> URL: https://issues.apache.org/jira/browse/IGNITE-6667
> Project: Ignite
> Issue Type: Improvement
> Security Level: Public(Viewable by anyone)
> Affects Versions: 2.2
> Reporter: Alexei Scherbakov
> Assignee: Alexei Scherbakov
> Fix For: 2.4
>
>
> Currently we always recreating DiscoCache instance even if only minor
> topology change has occured and cache may be reused.
> Profiling shows what initialization of such object tooks up tens of millis
> which adds to ring latency delay and especially sensitive for large
> topologies.
> Solution: reuse current discovery cache instance whenever possible.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
