You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2017/06/15 06:25:00 UTC

[jira] [Resolved] (IGNITE-5272) Try get rid of custom discovery message for client cache start

     [ https://issues.apache.org/jira/browse/IGNITE-5272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Semen Boikov resolved IGNITE-5272.
----------------------------------
    Resolution: Fixed
      Assignee:     (was: Semen Boikov)

> 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
>            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)