Inserts fake unassignmentRequestCounter into the database. These will be overwritten once the unassignment is completed. If the reassignment data has already been inserted, this method will do nothing.

TODO(#16601) Make this method private once PerformUnlessClosing doesn't need it any more

Adds the given offsets to the reassignment data in the store.

The same offset can be added any number of times.

Adds the given com.digitalasset.canton.data.Offset for the reassignment events to the reassignment data in the store, provided that the reassignment data has previously been stored.

The same com.digitalasset.canton.data.Offset can be added any number of times.

Adds the unassignment data to the store.

Calls to this method are idempotent, independent of the order.

Blocks until all earlier tasks have completed and then prevents further tasks from being run.

Marks the reassignment as completed, i.e., an assignment request was committed. If the reassignment has already been completed then a ReassignmentStore.ReassignmentAlreadyCompleted is reported, and the com.digitalasset.canton.data.CantonTimestamp of the completion is not changed from the old value.

Removes all completions of reassignments that have been triggered by requests with at least the given timestamp. This method must not be called concurrently with completeReassignment, but may be called concurrently with addUnassignmentData.

Therefore, this method need not be linearizable w.r.t. completeReassignment. For example, if two requests at ts1 and ts2 complete two reassignments while deleteCompletionsSince is running for some ts <= ts1, ts2, then there are no guarantees which of the completions at ts1 and ts2 remain.

Removes the reassignment from the store, when the unassignment request is rejected or the reassignment is pruned.

Find utility to look for in-flight reassignments. Reassignments are ordered by the tuple (request timestamp, source synchronizer id), ie reassignments are ordered by request timestamps and ties are broken with lexicographic ordering on synchronizer ids.

The ordering here has been chosen to allow a participant to fetch all the pending reassignments. The ordering has to be consistent accross calls and uniquely identify a pending reassignment, but is otherwise arbitrary.

Queries the reassignment ids for the given contract ids. Optional filtering by unassignment and completion (assignment) timestamps, and by source synchronizer.

Find utility to look for the earliest incomplete reassignment w.r.t. the ledger end. If an incomplete reassignment exists, the method returns the global offset of the incomplete reassignment for either the unassignment or the assignment, whichever of these is not null, the reassignment id and the target synchronizer id. It returns None if there is no incomplete reassignment (either because all reassignments are complete or are in-flight, or because there are no reassignments), or the reassignment table is empty.

Find utility to look for incomplete reassignments. Reassignments are ordered by global offset.

A reassignment t is considered as incomplete at offset validAt if only one of the two reassignment events was emitted on the indexer at validAt. That is, one of the following hold:

1. Only unassignment was emitted
   • t.unassignmentGlobalOffset is smaller or equal to validAt
   • t.assignmentGlobalOffset is null or greater than validAt 2. Only assignment was emitted
   • t.assignmentGlobalOffset is smaller or equal to validAt
   • t.unassignmentGlobalOffset is null or greater than validAt

In particular, for a reassignment to be considered incomplete at validAt, then exactly one of the two offsets (unassignmentGlobalOffset, assignmentGlobalOffset) is not null and smaller or equal to validAt.

Check whether we're closing. Susceptible to race conditions; unless you're using this as a flag to the retry lib or you really know what you're doing, prefer performUnlessClosing and friends.

Set this to true to get detailed information about all futures that did not complete during shutdown.

Looks up the given in-flight reassignment and returns the data associated with the reassignment.

Use this method to create a PromiseUnlessShutdown that will automatically be cancelled when the close context is closed. This allows proper clean up of stray promises when the node is transitioning to a passive state.

Note: you should *not* invoke success on the returned promise but rather use trySuccess. The reason is that the call to success may fail in case of shutdown.

Blocks until all earlier tasks have completed and then prevents further tasks from being run.

TODO(#16601) Make this method private once PerformUnlessClosing doesn't need it any more

Schedules the given task to be run upon closing.

Register a task to run when closing is initiated, or run it immediately if closing is already ongoing. Unlike runOnClose, this method does not guarantee that this task will have run by the time the LifeCycleManager's closeAsync method completes or AutoCloseable's close returns. This is because the task is run immediately if the component has already been closed.

Variant of runOnOrAfterClose that does not return a com.digitalasset.canton.lifecycle.LifeCycleRegistrationHandle.

Runs the computation f only if the component is not yet closing. If so, the component will delay releasing its resources until f has completed (as defined by the com.digitalasset.canton.util.Thereafter instance) or the synchronizeWithClosingPatience has elapsed.

DO NOT CALL this.close as part of f, because it will result in a deadlock. DO NOT PUT retries, especially indefinite ones, inside f.

Convenience method for synchronizing on Futures instead of FutureUnlessShutdowns. Equivalent to

synchronizeWithClosing(name)(FutureUnlessShutdown.outcomeF(f))

Runs the computation f only if the component is not yet closing. If so, the component will delay releasing its resources until f has finished or the synchronizeWithClosingPatience has elapsed.

DO NOT CALL this.close as part of f, because it will result in a deadlock. DO NOT PUT retries, especially indefinite ones, inside f.

Runs the computation f only if the component is not yet closing. If so, the component will delay releasing its resources until f has completed (as defined by the com.digitalasset.canton.util.Thereafter instance) or the synchronizeWithClosingPatience has elapsed.

DO NOT CALL this.close as part of f, because it will result in a deadlock. DO NOT PUT retries, especially indefinite ones, inside f.

Runs the computation fa unless isClosing returns true.

This method does not delay the closing while fa is running, unlike the methods in HasSynchronizeWithClosing. Accordingly, this method is useful for intermittent checks whether the result of the computation is still relevant.