[
https://issues.apache.org/jira/browse/IGNITE-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Semen Boikov resolved IGNITE-2350.
----------------------------------
Resolution: Fixed
Assignee: Sergey Kozlov (was: Semen Boikov)
During implementation we found that approach with utility cache is not reliable
(e.g. when daemon or client node starts first utility cache is not available).
I implemented passing update notifier status in discovery data (commit 7175a42).
Sergey, could you please verify this fix?
Thanks
> 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: Sergey Kozlov
> Priority: Critical
> Labels: important
> 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)
