trait TopologyTransactionProcessingSubscriber extends TopologyTransactionProcessingSubscriberCommon
- Alphabetic
- By Inheritance
- TopologyTransactionProcessingSubscriber
- TopologyTransactionProcessingSubscriberCommon
- AnyRef
- Any
- Hide All
- Show All
- Public
- Protected
Abstract Value Members
- abstract def observed(sequencedTimestamp: SequencedTime, effectiveTimestamp: EffectiveTime, sequencerCounter: SequencerCounter, transactions: Seq[SignedTopologyTransaction[TopologyChangeOp]])(implicit traceContext: TraceContext): FutureUnlessShutdown[Unit]
Concrete Value Members
- def updateHead(effectiveTimestamp: EffectiveTime, approximateTimestamp: ApproximateTime, potentialTopologyChange: Boolean)(implicit traceContext: TraceContext): Unit
Move the most known timestamp ahead in future based of newly discovered information
Move the most known timestamp ahead in future based of newly discovered information
We don't know the most recent timestamp directly. However, we can guess it from two sources: What was the timestamp of the latest topology transaction added? And what was the last processing timestamp. We need to know both such that we can always deliver the latest valid set of topology information, and don't use old snapshots. Therefore, we expose the updateHead function on the public interface for initialisation purposes.
- effectiveTimestamp
sequencer timestamp + epsilon(sequencer timestamp)
- approximateTimestamp
our current best guess of what the "best" timestamp is to get a valid current topology snapshot
- potentialTopologyChange
if true, the time advancement is related to a topology change that might have occurred or become effective
- Definition Classes
- TopologyTransactionProcessingSubscriberCommon