Redistribute distribution events occurred after snapshot was taken · Issue #31871 · camunda/camunda · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the time when the snapshot is being taken, some distribution events may have been processed by the engine. They will not be part of the newly created snapshot and they are necessary for the correct processing in the new partition.
Implementation
Partition 1 - PartitionManagerImpl
When the snapshot is completed, we need to:
append a command to save the reservation_id of the snapshot in the state (hint: RedistributionState it's probably a good place)
there's no unique id that identifies the current scale up operation, but desiredPartitionCount should be enough
append a command to redistribute events from snapshot_idx to now.
When all events are redistributed [To be clarified if it needs to be done after the events are redistributed or after sending the command]:
append a follow-up event to include the new partition in the RoutingState used for regular distribution
Motivation
During the time when the snapshot is being taken, some distribution events may have been processed by the engine. They will not be part of the newly created snapshot and they are necessary for the correct processing in the new partition.
Implementation
Partition 1 -
PartitionManagerImpl
When the snapshot is completed, we need to:
RedistributionState
it's probably a good place)desiredPartitionCount
should be enoughWhen all events are redistributed [To be clarified if it needs to be done after the events are redistributed or after sending the command]:
Dependencies:
The text was updated successfully, but these errors were encountered: