Notifications Settings
This page covers settings that control behavior related to MinIO AIStor bucket notifications.
You can establish or modify settings by defining:
- an environment variable on the host system prior to starting or restarting the AIStor Server. Refer to your operating system’s documentation for how to define an environment variable.
- a configuration setting using
mc admin config set.
If you define both an environment variable and the similar configuration setting, MinIO AIStor uses the environment variable value.
Some settings have only an environment variable or a configuration setting, but not both.
Sync events
Optional
api sync_events is deprecated.
It still works, but may be removed at any time.
Enables synchronous bucket notifications.
Specify on to direct MinIO AIStor to wait until the remote target returns success on receipt of an event before processing further events.
Defaults to off, or asynchronous bucket notifications where MinIO AIStor does not wait for the remote target to return success on receipt of an event.
Replication event threshold
Bucket event queue
MinIO AIStor holds undelivered bucket events in a global queue. Setting a directory turns the persistent queue on, so that events survive a restart or an unreachable target.
Bucket event queue dir
Specify the directory in which to store undelivered bucket events, such as /opt/minio/events.
Defaults to empty, which keeps the persistent queue off.
Give the minio-user user and group read, write, and list access to the directory.
Bucket event queue dir max size
Specify the maximum size of the queue directory in megabytes (MB).
Defaults to 10000, so plan for up to 10 GB per node when the queue directory is set.
The minimum is 10.
Bucket event queue exclude events
To keep named S3 events out of the queue and its targets, use the bucket_event_queue exclude_events setting.
See Log and Event Stream Filters.
The bucket_event_queue subsystem is dynamic.
A change made with mc admin config set applies without a server restart.