Skip to content

Update to v8.19.6#1122

Merged
docker-elk-updater[bot] merged 2 commits intorelease-8.xfrom
update/release-8.x
Oct 29, 2025
Merged

Update to v8.19.6#1122
docker-elk-updater[bot] merged 2 commits intorelease-8.xfrom
update/release-8.x

Conversation

@docker-elk-updater
Copy link
Copy Markdown
Contributor

Automated changes by create-pull-request GitHub action

@antoineco
Copy link
Copy Markdown
Collaborator

The pipeline is failing because we are hitting the 90% disk watermark even before the setup is able to complete, so we don't even get a chance to disable the behavior in the workflow:

{"@timestamp":"2025-10-27T07:10:43.630Z", "log.level": "WARN", "message":"high disk watermark [90%] exceeded on [qQNPG8zuQfaFmCPEalPSkA][elasticsearch][/usr/share/elasticsearch/data] free: 6.5gb[9%], shards will be relocated away from this node; currently relocating away shards totalling [0] bytes; the node is expected to continue to exceed the high disk watermark when these relocations are complete", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[elasticsearch][masterService#updateTask][T#4]","log.logger":"org.elasticsearch.cluster.routing.allocation.DiskThresholdMonitor","elasticsearch.cluster.uuid":"dSjyc7yfTL6MkdJ8X2e_Pw","elasticsearch.node.id":"qQNPG8zuQfaFmCPEalPSkA","elasticsearch.node.name":"elasticsearch","elasticsearch.cluster.name":"docker-cluster"}
{"@timestamp":"2025-10-27T07:10:45.886Z", "log.level":"ERROR", "message":"failed to retrieve password hash for reserved user [elastic]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[elasticsearch][transport_worker][T#1]","log.logger":"org.elasticsearch.xpack.security.authc.esnative.ReservedRealm","elasticsearch.cluster.uuid":"dSjyc7yfTL6MkdJ8X2e_Pw","elasticsearch.node.id":"qQNPG8zuQfaFmCPEalPSkA","elasticsearch.node.name":"elasticsearch","elasticsearch.cluster.name":"docker-cluster","error.type":"org.elasticsearch.action.UnavailableShardsException","error.message":"at least one primary shard for the index [.security-7] is unavailable","error.stack_trace":"org.elasticsearch.action.UnavailableShardsException: at least one primary shard for the index [.security-7] is unavailable\n"}

# Elasticsearch's high disk watermark gets regularly exceeded on GitHub Actions runners.
# https://www.elastic.co/guide/en/elasticsearch/reference/current/fix-watermark-errors.html
- name: Disable Elasticsearch disk allocation decider
run: .github/workflows/scripts/disable-disk-alloc-decider.sh

@antoineco antoineco force-pushed the update/release-8.x branch 2 times, most recently from 8053866 to c087540 Compare October 29, 2025 18:21
antoineco and others added 2 commits October 29, 2025 19:40
When all images are pre-cached, we get dangerously close to
Elasticsearch's 90% disk watermark even before the setup is able to
complete.

Cherry-picked from b90c23a9c4e764fd4589e8af27c62e7628e35fa4.
@docker-elk-updater docker-elk-updater Bot merged commit bfc0251 into release-8.x Oct 29, 2025
1 check passed
@github-actions github-actions Bot deleted the update/release-8.x branch October 29, 2025 18:47
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.

1 participant