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

Mikhail Petrov updated IGNITE-14675:
------------------------------------
    Description: 
Since IgniteAuthenticationProcessor is not treated as a separate processor, 
it is needed to refactor explicit IgniteAuthenticationProcessor callbacks  from 
other processors. Many of them can be eliminated. 

For example onActivate method can be replaced with 
PartitionsExchangeAware#onDoneBeforeTopologyUnlock
Explicit onLocalJoin method call can be replaced with 
discoMgr.localJoinFuture().listen(fut -> onLocalJoin());

and so on. 

It is also possible that this will require changing the startup order of the 
IgniteAuthenticationProcessor.



  was:
Since IgniteAutthenticationProcessor is not treated as a separate processor, 
it is needed to refactor explicit IgniteAuthenticationProcessor callbacks  from 
other processors. Many of them can be eliminated. 

For example onActivate method can be replaced with 
PartitionsExchangeAware#onDoneBeforeTopologyUnlock
Explicit onLocalJoin method call can be replaced with 
discoMgr.localJoinFuture().listen(fut -> onLocalJoin());

and so on. 

It is also possible that this will require changing the startup order of the 
IgniteAuthenticationProcessor.




> Refactor IgniteAuthenticationProcessor callbacks
> ------------------------------------------------
>
>                 Key: IGNITE-14675
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14675
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Mikhail Petrov
>            Priority: Minor
>
> Since IgniteAuthenticationProcessor is not treated as a separate processor, 
> it is needed to refactor explicit IgniteAuthenticationProcessor callbacks  
> from other processors. Many of them can be eliminated. 
> For example onActivate method can be replaced with 
> PartitionsExchangeAware#onDoneBeforeTopologyUnlock
> Explicit onLocalJoin method call can be replaced with 
> discoMgr.localJoinFuture().listen(fut -> onLocalJoin());
> and so on. 
> It is also possible that this will require changing the startup order of the 
> IgniteAuthenticationProcessor.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to