Docs: Add a note about rollover issues #33679
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6.4 has a bad bug where it won't if any of the shards on the node have been rolled over. This documents that in the known issues for 6.4.0 and links to the fix in the bug fixes section of 6.4.1. Relates to elastic#33394
jasontedor
requested changes
Sep 13, 2018
|
|
||
| Rollover:: | ||
| {es} can once again start if any shards on the node have been | ||
| <<indices-rollover-index, rolled over>>. {pull}33394[#33394] |
There was a problem hiding this comment.
I think this needs to wait to be added until 6.4.1 release time?
There was a problem hiding this comment.
We're already generated 6.4.1 release notes with a "coming in 6.4.1" note. I think it is ok to add this to that page.
| @@ -70,6 +74,11 @@ coming[6.4.1] | |||
| [float] | |||
| === Known issues | |||
|
|
|||
| Rollover:: | |||
| {es} can't start if any of the shards on the node have been | |||
| <<indices-rollover-index, rolled over>>. (issue: {issue}33316[#33316]) | |||
There was a problem hiding this comment.
I think that we need to highlight this more loudly (and the existing known issue for 6.4.0). Please see #32135 for how I think this should be done.
| @@ -170,15 +177,15 @@ Java High Level REST Client:: | |||
| * Rest High Level client: Add List Tasks {pull}29546[#29546] (issue: {issue}27205[#27205]) | |||
|
|
|||
| Machine learning:: | |||
| * Detectors now support {stack-ov}/ml-rules.html[custom rules] that enable the | |||
| user to improve machine learning results by providing some domain-specific | |||
| * Detectors now support {stack-ov}/ml-rules.html[custom rules] that enable the | |||
There was a problem hiding this comment.
Would you avoid the formatting changes?
|
@jasontedor I've pushed an update. Could you have another look? |
lcawl
approved these changes
Sep 13, 2018
|
Thanks for all of your suggestions @jasontedor and @lcawl! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
6.4 has a bad bug where it won't if any of the shards on the node have
been rolled over. This documents that in the known issues for 6.4.0 and
links to the fix in the bug fixes section of 6.4.1.
Relates to #33394