Myron, What approach did you use initially to initialize the node local map? IgniteNode is considered to be fully functional as soon as Ignition.start() method returns control, so any operations done on NodeLocalMap after the node start should be considered to be run concurrently with EntryProcessors invocations. If this is a requirement for you, you can put a simple CountDown latch to the NodeLocalMap, wait for it in an EntryProcessor and release it once the NodeLocalMap is in a consistent state.
It is safe to initialize the NodeLocalMap synchronously from LifecycleBean's BEFORE_NODE_START event since the event notification is run at the moment when the discovery SPI is not started yet and no other nodes "know" about this starting node. As for the EntryProcessor resource injection, you can track this ticket [1]. Looks like it is almost ready and will be merged to master pretty soon. -- AG [1] https://issues.apache.org/jira/browse/IGNITE-2560
