Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Thu, 9 Feb 2017 16:04:42 +0000 (UTC)
From: "Dmitry Karachentsev (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.13039617.1485986695000.39485.1486656282636@Atlassian.JIRA>
In-Reply-To: <JIRA.13039617.1485986695000@Atlassian.JIRA>
References: <JIRA.13039617.1485986695000@Atlassian.JIRA> <JIRA.13039617.1485986695036@jira-lw-us.apache.org>
Subject: [jira] [Assigned] (IGNITE-4641) Refresh client attributes during
 reconnect
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 09 Feb 2017 16:04:50 -0000


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

Dmitry Karachentsev reassigned IGNITE-4641:
-------------------------------------------

    Assignee: Dmitry Karachentsev

> Refresh client attributes during reconnect
> ------------------------------------------
>
>                 Key: IGNITE-4641
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4641
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: 1.8
>            Reporter: Valentin Kulichenko
>            Assignee: Dmitry Karachentsev
>             Fix For: 1.9
>
>
> Currently, when client disconnects and reconnects, it is forced to do that with the exact same set of attributes. However, there can be a component that wants to update attribute(s) in {{onDisconnected}} method, so that node reconnects with new attributes. To make sure this happens we need to refresh attributes before reconnecting. Most likely this should happen in {{TcpDiscoveryNode.clientReconnectNode()}} method which should acquire attributes via {{GridKernalContext.nodeAttributes()}}.
> Typical use case is a security token that can expire. Security processor implementation may want to refresh the token in case of disconnect, but this is not possible now.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)