Skip to content

Add a lock_cluster command ? #71

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.

Sign up for GitHub

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

Jump to bottom
Closed
clintongormley opened this issue Mar 18, 2010 · 2 comments
Closed

Add a lock_cluster command ? #71

clintongormley opened this issue Mar 18, 2010 · 2 comments

Comments

@clintongormley
Copy link
Contributor

Just an idea, how about being able to lock the cluster to prevent writes and or reads.

For instance, when the cluster is starting up and restoring from the gateway, it may take a few seconds to load all of the data. It'd be nice to say:

lock the cluster until cluster_health is green

Also, when changing a mapping, (thus forcing a reindex), we could do something like:

  • generate new index
  • lock cluster
  • rename the indices
  • flush index
  • unlock cluster when cluster_health is green

ta

clint
@kimchy
Copy link
Member

kimchy commented Mar 19, 2010

regarding the first point, the APIs will simply wait (until the timeout) if the cluster can't fullfil the requests yet.

An index level lock is interesting (mainly, I guess, to disallow dirty operations).

@clintongormley
Copy link
Contributor Author

This seems to be handled nicely in recent releases

@bluelu bluelu mentioned this issue Dec 11, 2014
Closed
dadoonet added a commit that referenced this issue Jun 5, 2015
@dadoonet
Update settings filter and remove component settings from AbstractCom…
cd7b8d4 
…ponent

Update settings filter to match #9748
Remove component settings from AbstractComponent as seen in #9919

Closes #71.
Closes #72.
@makeyang makeyang mentioned this issue Sep 7, 2015
Closed
@maxcom maxcom mentioned this issue Feb 3, 2017
Closed
maabernethy pushed a commit to maabernethy/elasticsearch that referenced this issue Mar 20, 2017
@kblincoe
Merge pull request elastic#71 from wsimf/patch-2
38a7963 
Claimed the issue 23436
@adeshp adeshp mentioned this issue Aug 15, 2018
Closed
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
@danielmitterdorfer
Query more data for daily indices (elastic#71)
fa89c7a 
With this commit we first fix the index pattern so queries can actually
match data. We also change the queries so we don't run any redundant
ones and modify them to retrieve more data. Finally, we modify the
Kibana runner so it stores some metadata about the query results (number
of total hits and the maximum value of `took` across all msearch
responses).
@jacksmith15 jacksmith15 mentioned this issue Aug 19, 2021
Open
@herrBez herrBez mentioned this issue Apr 15, 2022
Open
@mlyczek mlyczek mentioned this issue Sep 8, 2022
Closed
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
@danielmitterdorfer
Update Rally config file template
272f693 
With this commit we update the Rally config file template so it does not
include any JDK references. With elastic/rally#518 we will resolve JDK
versions using the `JAVAx_HOME` environment variables.

Relates elastic/rally#518
Closes elastic#70
Relates elastic#71
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kimchy @clintongormley