ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Evgeniy Ignatiev <yevgeniy.ignat...@gmail.com>
Subject Re: IGNITE-5123
Date Tue, 04 Jul 2017 14:06:45 GMT
As it is explicitly stated in Javadoc of PluginProvider#onIgniteStart 
that all internal components should be started before this method is 
called, which is not true, as internal component callbacks are called 
right after the PluginProvider#onIgniteStart.

On 7/2/2017 12:58 PM, Evgeniy Ignatiev wrote:
> Hello, Igniters.
> Looking at the ticket 
> https://issues.apache.org/jira/browse/IGNITE-5123, the 
> IgniteKernal#start notifies plugin providers, calling 
> PluginProvider#onIgniteStart, before components are notified, when 
> caches are created in GridCacheProcessor#onIgniteStart. Does it make 
> sense to move plugin providers notification after components are 
> notified, probably right before lifecycle beans notification, so to 
> ensure that caches are started before PluginProvider#onIgniteStart 
> method is called?

View raw message