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

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

Return the current configuration of the pool.

Obtain all the connections present in the pool.

Obtain a number of connections from the pool. The set of returned connections has the following properties:

• it contains at most one connection per sequencer ID
• the sequencer IDs represented are picked at random at every call
• it may contain less than the requested number of connections if the current pool contents cannot satisfy the requirements
• it excludes connections for sequencer IDs provided in exclusions
• when the pool contains multiple connections for the same sequencer ID, the connection returned for that sequencer ID is chosen via round-robin

Obtain a single connection for each different sequencer ID present in the pool.

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.

Determine whether the connection pool can still reach the given threshold, ignoring the ignored connections and considering an additional extraUndecided number of undecided connections.

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

Return the number of connections present in the pool (>= nbSequencers).

Return the number of different sequencerIds present in the pool (connections for the same sequencerId count for 1).

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

Return the synchronizer ID to which the connections in the pool are connected. Empty if the pool has not yet reached enough validated connections to initialize.

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.

Start the connection pool. This will start all the configured connections and begin validating them.

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.

Dynamically update the pool configuration. Changing the expected synchronizer ID is not supported and requires a node restart.