Skip to content
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

Better ES settings on docker-compose #6439

Merged
merged 2 commits into from Dec 11, 2019
Merged

Conversation

humitos
Copy link
Member

@humitos humitos commented Dec 5, 2019

  • Disable check for allocation which is not needed on development
  • Set a better name to the node

This avoid the cluster going read-only mode because not "enough" space on disk,

search_1     | [2019-12-05T16:38:02,390][WARN ][o.e.c.r.a.DiskThresholdMonitor] [1qOjoH7] flood stage disk watermark [95%] exceeded on [1qOjoH7qRX2hXuMCo80xOg][1qOjoH7][/usr/share/elasticsearch/data/nodes/0] free: 4.2gb[4.7%], all indices on this node will be marked read-only

@humitos humitos requested a review from ericholscher Dec 5, 2019
@humitos
Copy link
Member Author

@humitos humitos commented Dec 9, 2019

If you are already experimenting this problem, this command makes the index to be non read-only again (execute from web container):

curl -H'Content-Type: application/json' -XPUT search:9200/_all/_settings?pretty -d'
{
    "index": {
        "blocks.read_only": false
    }
}'

@ericholscher ericholscher merged commit fd9a132 into master Dec 11, 2019
3 checks passed
@ericholscher ericholscher deleted the humitos/better-es-settings branch Dec 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants