You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitry Karachentsev (JIRA)" <ji...@apache.org> on 2017/02/09 16:04:42 UTC
[jira] [Assigned] (IGNITE-4641) Refresh client attributes during
reconnect
[ 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)