Skip to main content

Compare-Exchange Configuration

Cluster.CompareExchangeExpiredDeleteFrequencyInSec​

Time (in seconds) between cleanup of expired compare-exchange items.

  • Type: int
  • Default: 60
  • Scope: Server-wide only

Cluster.CompareExchangeTombstonesCleanupIntervalInMin​

  • Compare-exchange tombstones are created when compare-exchange items are deleted.
    These tombstones are not removed immediately - RavenDB uses an internal cleaner task to periodically remove tombstones that are eligible for deletion.

  • This configuration option sets the interval, in minutes, between each cleanup run.

  • At each interval, the cleaner will only remove tombstones that are ready for removal - meaning their deletion has already been processed by all relevant subscribers. Subscribers are internal RavenDB processes that need to observe or react to compare-exchange deletions, such as indexes, ETL tasks, subscriptions, etc.
    Tombstones become eligible for removal only after all such processes have handled the deletion.

  • Type: int
  • Default: 10
  • Scope: Server-wide only

Cluster.MaxClusterTransactionCompareExchangeTombstoneCheckIntervalInMin​

EXPERT ONLY:

  • This configuration sets the interval (in minutes) between checks for compare-exchange tombstones that can be marked for deletion by the cluster-wide transaction mechanism on the node. This is separate from checks performed by other subscribers (such as indexes, subscriptions, or ETL tasks).

  • Normally, whenever a cluster-wide transaction command is processed, the cluster-wide transaction mechanism checks for compare-exchange tombstones that can be marked as eligible for deletion. If no cluster-wide transaction command occurs within the specified interval, the mechanism will automatically perform this check after the configured time has elapsed.

  • Any tombstones that have been fully handled by the cluster-wide transaction mechanism will be marked for deletion, making them eligible for cleanup by the tombstone cleaner task.

  • Type: int
  • Default: 5
  • Scope: Server-wide only

Cluster.DisableAtomicDocumentWrites​

EXPERT ONLY:
Disable automatic atomic writes with cluster write transactions.
If set to true, will only consider explicitly added compare exchange values to validate cluster wide transactions.

  • Type: bool
  • Default: false
  • Scope: Server-wide or per database