Skip to content

AzureBlobJournalStorageOptions.MaxMetadataOnlyConflictRetries

MaxMetadataOnlyConflictRetries

getset
View source
public int MaxMetadataOnlyConflictRetries
Gets or sets the maximum number of times a journaling Append, Replace, or Delete operation will refresh its cached WAL ETag and retry in place after observing a metadata-only ETag conflict (for example, a concurrent caller-owned metadata update or generation bump). When the cap is exceeded the storage layer falls back to throwing InconsistentStateException and the journaling layer recovers before retrying. Defaults to 5.