pub struct Config {Show 23 fields
pub durable_name: Option<String>,
pub name: Option<String>,
pub description: Option<String>,
pub deliver_policy: DeliverPolicy,
pub ack_policy: AckPolicy,
pub ack_wait: Duration,
pub max_deliver: i64,
pub filter_subject: String,
pub filter_subjects: Vec<String>,
pub replay_policy: ReplayPolicy,
pub rate_limit: u64,
pub sample_frequency: u8,
pub max_waiting: i64,
pub max_ack_pending: i64,
pub headers_only: bool,
pub max_batch: i64,
pub max_bytes: i64,
pub max_expires: Duration,
pub inactive_threshold: Duration,
pub num_replicas: usize,
pub memory_storage: bool,
pub metadata: HashMap<String, String>,
pub backoff: Vec<Duration>,
}Fields§
§durable_name: Option<String>Setting durable_name to Some(...) will cause this consumer
to be “durable”. This may be a good choice for workloads that
benefit from the JetStream server or cluster remembering the
progress of consumers for fault tolerance purposes. If a consumer
crashes, the JetStream server or cluster will remember which
messages the consumer acknowledged. When the consumer recovers,
this information will allow the consumer to resume processing
where it left off. If you’re unsure, set this to Some(...).
Setting durable_name to None will cause this consumer to
be “ephemeral”. This may be a good choice for workloads where
you don’t need the JetStream server to remember the consumer’s
progress in the case of a crash, such as certain “high churn”
workloads or workloads where a crashed instance is not required
to recover.
name: Option<String>A name of the consumer. Can be specified for both durable and ephemeral consumers.
description: Option<String>A short description of the purpose of this consumer.
deliver_policy: DeliverPolicyAllows for a variety of options that determine how this consumer will receive messages
ack_policy: AckPolicyHow messages should be acknowledged
ack_wait: DurationHow long to allow messages to remain un-acknowledged before attempting redelivery
max_deliver: i64Maximum number of times a specific message will be delivered. Use this to avoid poison pill messages that repeatedly crash your consumer processes forever.
filter_subject: StringWhen consuming from a Stream with many subjects, or wildcards, this selects only specific incoming subjects. Supports wildcards.
filter_subjects: Vec<String>server_2_10 only.Fulfills the same role as Config::filter_subject, but allows filtering by many subjects.
replay_policy: ReplayPolicyWhether messages are sent as quickly as possible or at the rate of receipt
rate_limit: u64The rate of message delivery in bits per second
sample_frequency: u8What percentage of acknowledgments should be samples for observability, 0-100
max_waiting: i64The maximum number of waiting consumers.
max_ack_pending: i64The maximum number of unacknowledged messages that may be in-flight before pausing sending additional messages to this consumer.
headers_only: boolOnly deliver headers without payloads.
max_batch: i64Maximum size of a request batch
max_bytes: i64Maximum value of request max_bytes
max_expires: DurationMaximum value for request expiration
inactive_threshold: DurationThreshold for consumer inactivity
num_replicas: usizeNumber of consumer replicas
memory_storage: boolForce consumer to use memory storage.
metadata: HashMap<String, String>server_2_10 only.backoff: Vec<Duration>Custom backoff for missed acknowledgments.