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

License expiring #110

Closed
sweco-sefild opened this issue Jun 17, 2019 · 2 comments · Fixed by #111
Closed

License expiring #110

sweco-sefild opened this issue Jun 17, 2019 · 2 comments · Fixed by #111

Comments

@sweco-sefild
Copy link

sweco-sefild commented Jun 17, 2019

Started my elastic-container, running pelias/elasticsearch:5.6.12, and got the following in the log:

(I deleted #'s before each row to calm markdown a bit)


 License [will expire] on [Thursday, June 27, 2019]. If you have a new license, please update it.
 Otherwise, please reach out to your support contact.
 
 Commercial plugins operate with reduced functionality on license expiration:
 - security
  - Cluster health, cluster stats and indices stats operations are blocked
  - All data operations (read and write) continue to work
 - watcher
  - PUT / GET watch APIs are disabled, DELETE watch API continues to work
  - Watches execute and write to the history
  - The actions of the watches don't execute
 - monitoring
  - The agent will stop collecting cluster and indices metrics
  - The agent will stop automatically cleaning indices older than [xpack.monitoring.history.duration]
 - graph
  - Graph explore APIs are disabled
 - ml
  - Machine learning APIs are disabled
 - deprecation
  - Deprecation APIs are disabled
 - upgrade
  - Upgrade API is disabled

I don't think I've seen it before - is this anything one should be worried about?

@missinglink
Copy link
Member

missinglink commented Jun 17, 2019

This seems to be related to x-pack which we don't use.
https://medium.com/@ospaarmann/tidbits-solving-the-elasticsearch-x-pack-license-issue-in-docker-d15bb22d82fd

@orangejulius where's best to disable x-pack? via packer or via env vars in the docker-compose.yml files?

orangejulius added a commit that referenced this issue Jun 18, 2019
The X-Pack extensions to Elasticsearch are proprietary addons for
additional functionality, none of which is needed by Pelias.

In the past, we've made due with disabling some of them by environment
variable, however that still leaves them present to emit scary warnings
about licenses. These warnings probably are ok to ignore, again since
Pelias does not use any X-Pack features.

However, its best to avoid scary warnings where possible, so this change
removes the X-Pack plugin completely.

Fixes #110
@orangejulius
Copy link
Member

Hi @sweco-sefild thanks for reporting this, we totally hadn't noticed.

I have no idea if there would actually be any impact to Pelias users come June 27th (mine showed June 10th), but it's not worth waiting to find out.

I just opened #111 to remove the X-Pack extension from our docker images completely.

calpb pushed a commit to sorelle/docker that referenced this issue Mar 29, 2021
The X-Pack extensions to Elasticsearch are proprietary addons for
additional functionality, none of which is needed by Pelias.

In the past, we've made due with disabling some of them by environment
variable, however that still leaves them present to emit scary warnings
about licenses. These warnings probably are ok to ignore, again since
Pelias does not use any X-Pack features.

However, its best to avoid scary warnings where possible, so this change
removes the X-Pack plugin completely.

Fixes pelias#110
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 a pull request may close this issue.

3 participants