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
River: A pluggable river (indexer like) support #377
Comments
implemented. |
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
…#377) Revert "Merged in dev/can/MPC-3974-eventbridge-scaling-2021-12-15 (pull request elastic#362)" * Revert "Merged in dev/can/MPC-3974-eventbridge-scaling-2021-12-15 (pull request elastic#362)" This reverts commit 84e3710. Approved-by: Gideon Avida
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
Revert "Merged in dev/can/revert-ems-scaling-2022-12-05 (pull request elastic#377)" * Revert "Merged in dev/can/revert-ems-scaling-2022-12-05 (pull request elastic#377)" This reverts commit 4bfc901. Approved-by: Gideon Avida
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
Add --on-error=abort to night-rally by default. Remove all "on-error": "abort" from race configs. Closes: elastic#377 Closes: elastic#439
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A river is a pluggable entity running within elasticsearch cluster pulling data (or being pushed with data) that is then indexed into the cluster.
A river is composed of a unique name and a type. The type is the type of the river (out of the box, there is the
dummy
river that simply logs that its running). The name uniquely identifies the river within the cluster. For example, one can run an river calledmy_river
with typedummy
.Rivers are singletons within the cluster. They get allocated automatically to one of the nodes and run. If that node fails, an river will be automatically allocated to another node.
River allocation on nodes can be controlled on each node. The
node.river
can be set to_none_
disabling any river allocation to it. Thenode.river
can also include a comma separated list of either river names or types controlling the rivers allowed to run on it. For example:my_river1,my_river2
, ordummy,twitter
.Rivers require both meta data (what type they are, and additional information) that forms the "settings" of the river, and possibly need to store runtime state (indexed up to data X, continue from it in case of failover). Everything is driven by working an internal index called
_river
.In that index (
_river
), each_type
in the index (mapping) corresponds to an river name (do not confuse it with the river type). The_meta
document id is required and includes the settings of that river. It must include at least the river type. In order to delete a river, a simple delete of the mapping type (river name) can be done.With the fact that the river(s) information is stored as an index, it is fully persistent, and allows for very frequent state storage (under one or more documents).
Sounds confusing, but its really simple, here is an example for creating the
dummy
river with the namemy_river
:And deleting the river is:
The text was updated successfully, but these errors were encountered: