[
https://issues.apache.org/jira/browse/IGNITE-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anton Vinogradov updated IGNITE-4641:
-------------------------------------
Fix Version/s: (was: 1.9)
2.0
FixVersion changed to 2.0.
In case issue can be done till Feb 17 please rollback this change.
> 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: 2.0
>
>
> 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)
