Fs Gateway: Add (native) file lock to ensure two nodes in a split brain are not updating same gateway #481
Labels
Comments
|
Fs Gateway: Add (native) file lock to ensure two nodes in a split brain are not updating same gateway, closed by 6b952f6. |
medcl
pushed a commit
to medcl/elasticsearch
that referenced
this issue
Jul 1, 2011
…in are not updating same gateway, closes elastic#481.
williamrandolph
pushed a commit
to williamrandolph/elasticsearch
that referenced
this issue
Jun 4, 2020
Spark 1.4 relies on a case insensitive match that forbiding the use of camel case options Update documentation relates elastic#481
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
…#481) MPC-4694: added lisa sandbox * added lisa sandbox Approved-by: fabien
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
Currently, all fields named `message` are mapped to be excluded from the `.keyword` and `.raw`. This is rather strict, and need only be applied to the top-level `message` field. All nested `**.*.message` fields should be treated like any old field. Fixes elastic#481
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add file lock to gateway to ensure two nodes in a split brain are not updating same gateway. This should be able to prevent index corruption with two clusters split brained trying to write to same gateway.
In order to disable it, set
gateway.fs.snapshot_locktofalse.The text was updated successfully, but these errors were encountered: