Docs on elasticsearch config
Bug #1714113 reported by
james beedy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Elasticsearch Charm |
Won't Fix
|
Low
|
Unassigned | ||
| Graylog Charm |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
It seems graylog connects to elasticsearch on port 9300, this isn't covered in the set of ports that ufw controls in the elasticsearch charm, so if the elasticsearch config "firewall_
Revision history for this message
| Drew Freiberger (afreiberger) wrote | #1 |
| Changed in elasticsearch-charm: | |
| status: | New → Confirmed |
| status: | Confirmed → New |
| Changed in graylog-charm: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
Revision history for this message
| james beedy (jamesbeedy) wrote | #2 |
| Changed in charm-elasticsearch: | |
| status: | New → Confirmed |
| importance: | Undecided → Low |
| Changed in charm-elasticsearch: | |
| status: | Confirmed → Won't Fix |
| Changed in charm-graylog: | |
| status: | Confirmed → Won't Fix |
To post a comment you must log in.
Looking through the code, elasticsearch-charm sets port 9300 open for it's cluster peers until the cluster is established, then re-closes port 9300. Since graylog expects to be relatively a "peer" with elasticsearch, this current methodology would not work well without logic change.
I believe that both charms would benefit from a more robust external-
Agreed, workaround is to disable the firewall on the ES charm.