Persistent queue event ordering constraints during rolling node migrations
Migrating a small Logstash application without downtime typically requires utilizing persistent queues to buffer incoming data during a rolling update. While setting queue.type: persistent ensures that events are written to disk and survive restarts, the behavior under high concurrency remains complex. n When multiple worker threads are configured to process
logstash