RoutingUpdate event.

checkpointing succeed.

checkpointing suceeded for vb.

When a source mutation is translated into multiple target mutations for different target namespaces.

data failed conflict resolution on source cluster side due to optimistic replication.

data is filtered out by the component.

Data merged and send to and acknowledged by source bucket.

Data not replicated due to broken collection mapping NOTE: This event is only supposed to be raised after ensuring the data will be re-replicated later in another backfill.

Unable to get recycled data from datapool.

data is processed by the componentand passed down to the downstream.

data received by the component.

data sent to and acknowledged by the target system.

data sent failed because of Cas change.

data sending is throttled due to bandwidth usage limit being reached.

data sending is throttled due to throughput limit being reached.

data is unable to be successfully parsed to be filtered.

fatal error encountered by the component.

Expiry field has been stripped.

When previously broken mappings have been fixed and should be backfilled.

response received from target cluster for subdoc_multi_lookup for XATTR and document body.

get meta response received from target cluster, or if custom CR, subdoc_multi_lookup for XATTR received.

When a backfill pipeline ends, throughSeqnoTrackerSvc will raise this once the last seen DCP seqno has been processed.

set merge result failed because source Cas changed.

DCP may send OSO snapshot marker if XDCR requested only one collection.

received snapshot marker from dcp.

generic stats update event for the component.

data streaming ends.

data streaming starts.

When DCP sends down a system event.

data skipped because it is from target.

error encountered in a particular vb by the component.

AsyncComponentEventListener is a subtype of ComponentEventListener which processes events asynchonously.

ComponentEventListener abstracts anybody who is interested in an event of a component.

Connectable abstracts the step that can be connected to one or more downstream steps.

Connector abstracts the logic which moves data from one processing steps to another.

Nozzle models the openning that data streaming out of the source systemand the outlet where the data flowing into the target system.

interface for Pipeline.

PipelineRuntimeContext manages all the services that attaches to the feed.

PipelineService can be any component that monitors, does logging, keeps state for the pipelineEach PipelineService is a goroutine that run parallelly.

Components that can be supervised, e.g., parts, replication manager, etc.

Handler for failures reported by Supervisor.

ComponentEventType is the common event type that Component can raise during its lifecycleIt is not required for Component to raise all those event.