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

Backport to 6.3: Doc changes (#7883 #7889 #7950) #8013

Merged
merged 3 commits into from
Aug 27, 2018

Conversation

dedemorton
Copy link
Contributor

Cherry-picks the following changes into the 6.3 branch:

#7883
#7889
#7950

@@ -514,7 +514,7 @@ configured. The default value is 2.
deprecated[5.0.0]

The default port to use if the port number is not given in <<hosts,`hosts`>>. The default port number
is 10200.
is 5044.
Copy link
Member

Choose a reason for hiding this comment

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

Whas this change included in cherry-picked PRs?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@jsoriano Not sure exactly what you are asking here. I have backported this change to 6.3, 6.4, and 6.x. The change is relevant to earlier releases, too, but we don't usually backport all doc fixes to all releases where the docs are wrong because that would be really time consuming. Does that answer your question? Note that the default was changed here: eefdbd6

Copy link
Member

Choose a reason for hiding this comment

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

O, I see, yes, I meant that I couldn't find the change on the default port, it LGTM then, thanks!

@jsoriano jsoriano merged commit a020d83 into elastic:6.3 Aug 27, 2018
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…elastic#8013)

* Add missing config options to Logstash section of reference.yml (elastic#7883)
* Add safeguard related statements for max_backoff setting (elastic#7889)
* Add recommendation to avoid harvesting symlinks when dealing with file rotation (elastic#7950)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants