River: Failure to reallocate river to another node on rivers node failure #850
Comments
williamrandolph
pushed a commit
to williamrandolph/elasticsearch
that referenced
this issue
Jun 4, 2020
… reading from multiple types. - Moved Field parsing logic into it's own class. - Add ability to merge mappings from multiple types together into a resolved view. - Convert most of the usages of the Field class to the new Mapping class. - Moved a handful of utility functions into the Mapping class since there's a logical place for those functions to live now. This is WIP since the tests are not building entirely yet with the changes. - Convert tests over to new mapping api. - Adding tests to ensure that the multi-mapping support works fixes elastic#938, fixes elastic#850
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
…(pull request elastic#850) Increase test22.tfvars recorder asg to 50 from 20 * Increase test22.tfvars recorder asg to 50 from 20 Approved-by: Can Yildiz
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a node that a river is running on fails, the river is not allocated to a different node.
The text was updated successfully, but these errors were encountered: