ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-2350) Make IGNITE_UPDATE_NOTIFIER per cluster setting
Date Mon, 11 Jan 2016 15:33:39 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-2350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092130#comment-15092130

ASF GitHub Bot commented on IGNITE-2350:

GitHub user ashutakGG opened a pull request:


    IGNITE-2350: Make IGNITE_UPDATE_NOTIFIER per cluster setting


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ashutakGG/incubator-ignite ignite-2350-upd-notif

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #395
commit cc1883f6ee792515699e2cb54bea046baac154f5
Author: ashutak <ashutak@gridgain.com>
Date:   2016-01-11T15:10:02Z

    ignite-2350: Make IGNITE_UPDATE_NOTIFIER per cluster setting


> 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
>             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)
> # Further nodes should ignore local setting and respect cluster wide value set on cluster

This message was sent by Atlassian JIRA

View raw message