Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add known issue for PipelineBusv2 to 8.15.x release notes #16661

Merged
merged 5 commits into from
Nov 11, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 39 additions & 1 deletion docs/static/releasenotes.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -72,6 +72,14 @@ This section summarizes the changes in the following releases:
[[logstash-8-15-4]]
=== Logstash 8.15.4 Release Notes

[[known-issues-8-15-4]]
==== Known issue

**{ls} can fail to shut down under some circumstances when you are using <<pipeline-to-pipeline>>.**
Check out issue https://github.com/elastic/logstash/issues/16657[#16657] for details.
Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`.
This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.
yaauie marked this conversation as resolved.
Show resolved Hide resolved

[[notable-8.15.4]]
==== Notable issues fixed

Expand Down Expand Up @@ -112,6 +120,14 @@ This section summarizes the changes in the following releases:

* Fixed Logstash core compatibility issues with `logstash-input-azure_event_hubs` versions `1.4.8` and earlier https://github.com/elastic/logstash/pull/16485[#16485]

[[known-issues-8-15-3]]
==== Known issue

**{ls} can fail to shut down under some circumstances when you are using <<pipeline-to-pipeline>>.**
Check out issue https://github.com/elastic/logstash/issues/16657[#16657] for details.
Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`.
This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.
yaauie marked this conversation as resolved.
Show resolved Hide resolved

==== Plugins

*Elastic_integration Filter - 0.1.14*
Expand All @@ -137,6 +153,14 @@ This section summarizes the changes in the following releases:

* Fixed a https://github.com/elastic/logstash/issues/16437[regression] from {ls} 8.15.1 in which {ls} removes all quotes from docker env variables, possibly causing {ls} not to start https://github.com/elastic/logstash/pull/16456[#16456]

[[known-issues-8-15-2]]
==== Known issue

**{ls} can fail to shut down under some circumstances when you are using <<pipeline-to-pipeline>>.**
Check out issue https://github.com/elastic/logstash/issues/16657[#16657] for details.
Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`.
This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.
yaauie marked this conversation as resolved.
Show resolved Hide resolved

==== Plugins

*Beats Input - 6.8.4*
Expand Down Expand Up @@ -172,6 +196,12 @@ If this situation occurs, {ls} may fail to start or some plugins may use a malfo
Check out issue https://github.com/elastic/logstash/issues/16437[#16437] for details.
+
Workaround: Downgrade to {ls} 8.15.0, or temporarily avoid using environment and keystore variable references.
* **{ls} can fail to shut down under some circumstances when you are using <<pipeline-to-pipeline>>.**
Check out issue https://github.com/elastic/logstash/issues/16657[#16657] for details.
+
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
+

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this one is necessary because it's in a bulleted list?

Copy link
Contributor

@karenzone karenzone Nov 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggested removing the bullet because it was a single item. When the bullet went away, the + needed to go away, too, to avoid it rendering.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ideally, the + should go, but the line should remain to force rendering into two distinct paragraphs.

Copy link
Contributor

@karenzone karenzone Nov 11, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is what it looks like now. Not the worst, but not the best.

Screen Shot 2024-11-11 at 4 38 12 PM

Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`.
This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.


[[notable-8.15.1]]
==== Performance improvements and notable issues fixed
Expand Down Expand Up @@ -206,6 +236,14 @@ Workaround: Downgrade to {ls} 8.15.0, or temporarily avoid using environment and
[[logstash-8-15-0]]
=== Logstash 8.15.0 Release Notes

[[known-issues-8-15-0]]
==== Known issue

**{ls} can fail to shut down under some circumstances when you are using <<pipeline-to-pipeline>>.**
Check out issue https://github.com/elastic/logstash/issues/16657[#16657] for details.
Workaround: Add `-Dlogstash.pipelinebus.implementation=v1` to `config/jvm.properties`.
This change reverts the `PipelineBus` to `v1`, a version that does not exhibit this issue, but may impact performance in pipeline-to-pipeline scenarios.

[[snmp-ga-8.15.0]]
==== Announcing the new {ls} SNMP integration plugin

Expand Down Expand Up @@ -2579,4 +2617,4 @@ We have added another flag to the Benchmark CLI to allow passing a data file wit
This feature allows users to run the Benchmark CLI in a custom test case with a custom config and a custom dataset. https://github.com/elastic/logstash/pull/12437[#12437]

==== Plugin releases
Plugins align with release 7.14.0
Plugins align with release 7.14.0
Loading