Elasticsearch reports elasticsearch.ready and elasticsearch.available before all hosts have finished stabalizing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Elasticsearch Charm |
Triaged
|
Low
|
Unassigned |
Bug Description
While deploying elasticsearch rev 67 and graylog rev64, greylog went into an error with a connecting refused to elasticsearch, resulting in a beats-relation-
from the unit-graylog log:
2023-03-03 08:59:57 INFO unit.graylog/
but the elasticsearch.log on units 0 (this unit) and 2 (the master) show that 10.246.64.211 is added to the cluster at the same time (one second later), and unit 1 doesnt even know about .211 yet.
[2023-03-
Elasticsearch probably didnt have time to fully come online before graylog tried to make the request. The other 2 units, one of which is the leader, are both active/idle, its just the third unit that getting configured at the time graylog tries to connect.
In this case graylog 1 gets the error
elastic 0 is executing
elastic 1 is the leader, but doesnt know about 0
and elastic 2 is the master, and knows about 0
you can view the full testrun at:
https:/
the crashdump for this run can be found at:
https:/
1) https:/
tags: | added: bseng-967 |
Changed in charm-elasticsearch: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in charm-elasticsearch: | |
importance: | Medium → Low |