Type Members

1.  final case class AllInstanceIndexesInUse(message: String) extends WriterStartupError with Product with Serializable

   We have a upper limit of how many instances can run concurrently (this is defined by how many com.digitalasset.canton.config.DbLockConfig.MAX_SEQUENCER_WRITERS_AVAILABLE are allocated).

   We have a upper limit of how many instances can run concurrently (this is defined by how many com.digitalasset.canton.config.DbLockConfig.MAX_SEQUENCER_WRITERS_AVAILABLE are allocated). We can not start a new sequencer instance if locks for all of these counters are allocated and appear online. However we can keep retrying starting on the chance that one of these will eventually go offline.

2.  final case class BadCommitMode(message: String) extends WriterStartupError with Product with Serializable

   We don't want to run the sequencer with a database commit mode that could lead to data loss, so this is optionally and by default validated upon startup.

3.  final case class DatabaseNotSupported(message: String) extends WriterStartupError with Product with Serializable

   We only support running some features with certain types of databases (locking for HA requires postgres), an enterprise config validation should prevent starting a node with a bad configuration however if we reach creating a Writer with this config this error will be returned.

4.  final case class FailedToCreateExclusiveStorage(message: String) extends WriterStartupError with Product with Serializable

   We failed to create an exclusive storage instance for this writer.

   We failed to create an exclusive storage instance for this writer. Typically this will be caused by contention caused by multiple writers trying to create a lock with the same instance index. This is expected and we can just safely retry as a new free instance index will be assigned.

5.  final case class FailedToInitializeFromSnapshot(message: String) extends WriterStartupError with Product with Serializable

   When creating a separate database sequencer from a snapshot given by another one, there was an error consuming the snapshot to initialize the initial state.

   When creating a separate database sequencer from a snapshot given by another one, there was an error consuming the snapshot to initialize the initial state. If this is a database problem, it can be retried. Other kinds of issues would indicate that the new sequencer does not have a fresh database, which is a fundamental requirement for being able to start a new sequencer fresh from a snapshot.

6.  final case class WatermarkResetError(message: String) extends WriterStartupError with Product with Serializable

   Failed to reset the watermark during the recovery