[
https://issues.apache.org/jira/browse/IGNITE-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050047#comment-16050047
]
Semen Boikov commented on IGNITE-5272:
--------------------------------------
Changed client cache start/close to do not use synchronous discovery event and
'client only' exchage (thus minor topology version is not incremented). Instead
client cache is started locally (still in exchange thread to avoid races with
cache start/destory), and discovery event is sent asynchrnously just to notify
cluster (multiple client cache starts/closes can be batched in single event).
> Try get rid of custom discovery message for client cache start
> --------------------------------------------------------------
>
> Key: IGNITE-5272
> URL: https://issues.apache.org/jira/browse/IGNITE-5272
> Project: Ignite
> Issue Type: Task
> Components: cache
> Reporter: Semen Boikov
> Assignee: Semen Boikov
> Priority: Critical
> Labels: important
> Fix For: 2.1
>
>
> Currently both server and client caches are started in the same way - using
> custom discovery message. Most probably for client caches we do not need
> strong ordering guarentees which discovery messages provide.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
