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

Posted to issues@ignite.apache.org by "Artem Shutak (JIRA)" <ji...@apache.org> on 2016/01/11 17:18:39 UTC

[jira] [Updated] (IGNITE-2350) Make IGNITE_UPDATE_NOTIFIER per cluster setting

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

Artem Shutak updated IGNITE-2350:
---------------------------------
    Priority: Critical  (was: Major)

> Make IGNITE_UPDATE_NOTIFIER per cluster setting
> -----------------------------------------------
>
>                 Key: IGNITE-2350
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2350
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Yakov Zhdanov
>            Assignee: Artem Shutak
>            Priority: Critical
>             Fix For: 1.6
>
>
> We need to refactor update notification behavior to make it more transparent.
> # The first node (topVer=1) should behave in accordance to its local settings
> # The first node should set cluster-wide default which should survive its (first node) exit.
> # Further nodes should ignore local setting and respect cluster wide value set on cluster start



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)