Page History

...

1. Configure Ignite to enable OnlineCDC.
2. Configure ignite-cdc process (set BACKUP mode in CdcConfiguration)
3. Start Ignite cluster in ACTIVE_READ_ONLY mode.
4. Start background process ignite-cdc in BACKUP mode.
1. ./ignite-cdc.sh cdc-config.xml
5. Explicit start OnlineCDC on Ignite:
1. ./control.sh –cdc online –start
6. Move Ignite cluster to ACTIVE state.
   

Note, that ignite-cdc.sh can be run in 2 modes - BACKUP, ACTIVE (default):

1. BACKUP is used as backup process for OnlineCDC, and then such process may fetch CDC configuration from IgniteConfiguration. Case is async replication between master and stand-by clusters.
2. ACTIVE is used as independent process that doesn’t rely on OnlineCDC, has its own configuration. Case is filling a cold data lake.
   

...

1. CdcConfiguration#mode - ACTIVE, BACKUP (default ACTIVE if OnlineCDC is not configured, and BACKUP otherwise)
2. Logs: 
   1. clearing cdc dir, switch state.
3. Metrics:
   1. current state.

...

1. If DataRegionConfiguration#cdcMode == ONLINE, then create CdcProcessor.
2. CdcProcessor read from the Metastorage the last persisted CdcConsumerState.
1. CdcState#enabled is false then skip initialization.
2. If CdcState == null OR CdcState#enabled is false then skip initializationthen initialize.
3. Initialization - collect logical updates from the CdcState#committedPtr until the end of WAL. See GridCacheDatabaseSharedManager#performBinaryMemoryRestore.

...