﻿---
title: Logstash known issues
description: Known issues are significant defects or limitations that may impact your implementation. These issues are actively being worked on and will be addressed...
url: https://www.elastic.co/elastic/docs-builder/docs/2532/release-notes/logstash/known-issues
products:
  - Logstash
---

# Logstash known issues
Known issues are significant defects or limitations that may impact your implementation.
These issues are actively being worked on and will be addressed in a future release.
Review known issues to help you make informed decisions, such as upgrading to a new version.

## 9.2.0

**Logstash will not start if a Persistent Queue has been defined with a size greater than 2 GiB**
Applies to: Logstash 9.2.0
<dropdown title="Details">
  Attempts to start Logstash when `queue.max_bytes` has been set to `2147483648` bytes or greater will fail. There is currently no workaround for this issue other than downgrading to a previous version of Logstash. Therefore we recommend that any Logstash users with a Persistent Queue greater than size not upgrade to Logstash `9.2.0`.Details of the bug are included in [this PR fixing the issue](https://github.com/elastic/logstash/pull/18366), which will be included in a future version of Logstash.
</dropdown>

**BufferedTokenizer may silently drop data when oversize input has no delimiters**
Applies to: Logstash 9.2.0
<dropdown title="Details">
  The `decode_size_limit_bytes` setting for Logstash plugins that use the `json_lines` codec is behaving differently than expected. When the size limit exceeds the specified limit without a separator in the data, the size grows beyond the limit.
  This occurs because size validation happens after the token is fully accumulated, which does not occur if no trailing separator is detected.Logstash plugins that use the `json_lines` codec include `input-stdin` `input-http`, `input-tcp` `integration-logstash` and `input-elastic_serverless_forwarder`.Best practice: Do not set `decode_size_limit_bytes` manually.Details for this issue and the details for future behavior are being tracked in [#18321](https://github.com/elastic/logstash/issues/18321)
</dropdown>


## 9.0.0

None at this time