Regarding partition map exchange triggers

[VeenaMithare <v....@cmcmarkets.com>]

Hi , 


I can see the triggers for PME initiation here : 
https://cwiki.apache.org/confluence/display/IGNITE/%28Partition+Map%29+Exchange+-+under+the+hood

Triggers
Events which causes exchange

Topology events:

Node Join (EVT_NODE_JOINED) - new node discovered and joined topology
(exchange is done after a node is included into the ring). This event
doesn't trigger the PME if a thick client connects the cluster and an Ignite
version is 2.8 or later. 
/*-- This means in ignite 2.8 or higher, this is triggered only if nodes
that participate in the baseline topology are added ?*/
Node Left (EVT_NODE_LEFT) - correct shutdown with call ignite.close. This
event doesn't trigger the PME in Ignite 2.8 and later versions if a node
belonging to an existing baseline topology leaves.
/*-- This means this is not triggered at all 2.8.1 or higher if shutdown
cleanly ? i.e. if this is called : Ignition.stop(false) */
Node Failed (EVT_NODE_FAILED) - detected unresponsive node, probably crashed
and is considered failed
/*-- This means this is  triggered at all 2.8.1 or higher for baseline nodes
or any thick client node ?*/

Custom events:

Activation / Deactivation / Baseline topology set - ChangeGlobalStateMessage 
Dynamic cache start / Dynamic cache stop - DynamicCacheChangeBatch
/* for the end user , is this invoked when we do ignite.getOrCreate( xx )
and ignite.cache(xx )*/

Snapshot create / restore - SnapshotDiscoveryMessage
Global WAL enable / disable - WalStateAbstractMessage
Late affinity assignment - CacheAffinityChangeMessage


regards,
Veena.




--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/