Logstash fails to start after upgrade to 9.2.0 if persisted queue max_bytes is >= 2048mb

[redbaron4]

Logstash information:

1. Logstash version (e.g. bin/logstash --version) - 9.2.0
2. Logstash installation source (e.g. built from source, with a package manager: DEB/RPM, expanded from tar or zip archive, docker) - From RPM
3. How is Logstash being run (e.g. as a service/service manager: systemd, upstart, etc. Via command line, docker/kubernetes) - As Service using systemd

OS version (uname -a if on a Unix-like system): Rocky 8 and 9

Description of the problem including expected versus actual behavior:

After upgrade to Logstash 9.2.0 (from 9.1.2), Logstash fails to start if persisted queue is in use and queue.max_bytes is >=2048mb

Steps to reproduce:

1. In logstash.yml set queue.type: persisted and queue.max_bytes: 2048mb
2. Start Logstash
3. Pipeline will fail to start with a RangeError

Provide logs (if relevant):

[2025-10-28T14:18:51,804][ERROR][org.logstash.execution.AbstractPipelineExt][0_main] Logstash failed to create queue.
org.jruby.exceptions.RangeError: (RangeError) too big for int: 2147483648
at org.logstash.ackedqueue.QueueFactoryExt.create(org/logstash/ackedqueue/QueueFactoryExt.java:97) ~[logstash-core.jar:?]
at org.logstash.execution.AbstractPipelineExt.open_queue(org/logstash/execution/AbstractPipelineExt.java:305) ~[logstash-core.jar:?]
at RUBY.finish_initialization(/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:55) ~[?:?]
at RUBY.initialize(/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:50) ~[?:?]
at RUBY.with_logging_thread_context(/usr/share/logstash/logstash-core/lib/logstash/util.rb:60) ~[?:?]
at RUBY.initialize(/usr/share/logstash/logstash-core/lib/logstash/java_pipeline.rb:49) ~[?:?]
at org.jruby.RubyClass.new(org/jruby/RubyClass.java:950) ~[jruby.jar:?]
at RUBY.execute(/usr/share/logstash/logstash-core/lib/logstash/pipeline_action/create.rb:50) ~[?:?]
at RUBY.converge_state(/usr/share/logstash/logstash-core/lib/logstash/agent.rb:431) ~[?:?]

[landon-lengyel]

Experiencing this as well on Debian 13. It is installed through the Elastic repository.

[Elnadrion]

Same here, on:

[robbavey]

Hey folks,

Thanks for reporting. This is a known issue and a fix has been merged that we expect to be available in the next minor release of 9.2

At this time, the best way to resolve the issue is to downgrade to the last previous release in the 9.1 branch, or set the value of queue.max_bytes to 2147483647 bytes or less.