Page MenuHomePhabricator

Elasticsearch, a CirrusSearch dependency, is switching to SSPL/Custom licence
Closed, ResolvedPublic

Description

According to their blogpost (https://www.elastic.co/blog/licensing-change):

Starting with the upcoming Elastic 7.11 release, we will be moving the Apache 2.0-licensed code of Elasticsearch and Kibana to be dual licensed under SSPL and the Elastic License, giving users the choice of which license to apply.

Their FAQ on 2021 License Change : https://www.elastic.co/pricing/faq/licensing

Considering this is happening:

  1. WIll CirrusSearch rely on ElasticSearch in the near future (say on version 7.x)?
  2. Will CirrusSearch rely on ElasticSearch in long-term?
  3. According to task T213996, the switch from MongoDB had happened because it was removed in Debian and therefore will be unsuitable for long-term use., and therefore it was unclear if a precedent was achieved. Are there any policy change or clarification if another dependency announced to switch to a license that may not be suitable for MediaWiki?

Context on proprietary relicensing:
https://sfconservancy.org/blog/2020/jan/06/copyleft-equality/

Existing alternative venues:
https://opendistro.github.io/for-elasticsearch/contribute.html ("distribution" or "fork" depending who you ask, no CLA)

Some announced forks:
https://aws.amazon.com/blogs/opensource/stepping-up-for-a-truly-open-source-elasticsearch/
https://logz.io/blog/open-source-elasticsearch-doubling-down/

Related Objects

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Gacelperfinian renamed this task from Elasticsearch will switch to SSPL to Elasticsearch, a CirrusSearch dependency, is switching to SSPL/Custom licence.Jan 15 2021, 1:22 AM

WIll CirrusSearch rely on ElasticSearch in the near future (say on version 7.x)?

Yes. CirrusSearch is currently on 6.5.4. It will likely upgrade to 6.8.x soon. These versions are EOL and stopped receiving security updates from elastic in Nov 2020.

Will CirrusSearch rely on ElasticSearch in long-term?

Yes? No? Maybe? It will take months to figure this out.

According to task T213996, the switch from MongoDB had happened because it was removed in Debian and therefore will be unsuitable for long-term use., and therefore it was unclear if a precedent was achieved. Are there any policy change or clarification if another dependency announced to switch to a license that may not be suitable for MediaWiki?

The rule of thumb, it may or may not be a strict rule somewhere, is that WMF deploy's software with OSI approved licenses. There is at least some mention under development policys that new services must be licensed under an OSI-approved license.

Also for notetaking: Kibana will also be affected by this change, but I am not sure if WMF stack uses Kibana in some way (if there is any, this should be on another task anyways).

The Translate extension also uses ElasticSearch.

Nemo_bis renamed this task from Elasticsearch, a CirrusSearch dependency, is switching to SSPL/Custom licence to Elasticsearch is going proprietary with a SSPL/custom licence; forks coming.Jan 24 2021, 4:47 PM

This isn't the task for the Logstash or Translate issues. Please see T272238: Elasticsearch and Kibana are switching to non-OSI-approved SSPL licence for the former and create a new task for the latter, as implied above.

Jdforrester-WMF renamed this task from Elasticsearch is going proprietary with a SSPL/custom licence; forks coming to Elasticsearch, a CirrusSearch dependency, is switching to SSPL/Custom licence.Jan 24 2021, 6:11 PM
Gehel claimed this task.
Gehel subscribed.

For the moment, we're staying on Elasticsearch 7.x (once we've migrated from 6.x to 7.x), but we're blocked on upgrading past 7.10.2 because of licensing. There is a larger question of what exactly are the needs in term of Search that needs to be resolved.

There isn't a clear acceptance criteria on this task, so closing it for now. Feel free to re-open as needed.

Legoktm subscribed.

For the moment, we're staying on Elasticsearch 7.x (once we've migrated from 6.x to 7.x), but we're blocked on upgrading past 7.10.2 because of licensing. There is a larger question of what exactly are the needs in term of Search that needs to be resolved.

There isn't a clear acceptance criteria on this task, so closing it for now. Feel free to re-open as needed.

I don't think staying on Elasticsearch 7.x is a long-term solution, is it? I think we can consider this ticket resolved once CirrusSearch has moved to using something that is properly open source under an OSI license.

@Legoktm, see T272238 and T280482 - it seems OpenSearch is the relevant replacement in the future, and this task can be left closed.

Gehel removed Gehel as the assignee of this task.Apr 15 2024, 2:00 PM

Regarding Elastic as used for Logstash:

In T272238#7706582, @lmata wrote on 14 Feb 2022:

[..] The Observability team identified two potential options: OpenSearch and Grafana Loki.

[..] In conclusion, the team recommended moving forward with OpenSearch [..].

After this evaluation, we implemented a testing environment in beta [..], followed by deployments to production [..]. Both codfw and eqiad have been migrated to OpenSearch, thus removing the observability stack of scope for SSPL concerns.

Regarding Elastic for MediaWiki search:

In T280482#9760984, @bking wrote on 1 May 2024:

Based on discussions with @dcausse and @EBernhardson last week, I believe we (as in Search Platform team) have decided that Opensearch is our only choice to replace Elasticsearch. [..]

In T370147#10125422, @Gehel wrote on 6 Sep 2024:

Given the recent changes to Elasticsearch license to AGPL, we are likely going to stay on Elasticsearch and upgrade to latest version. Final decision to come...

In T370661#10220958, @dr0ptp4kt wrote on 11 Oct 2024:

Update: Search Platform has reviewed further, and it intends to stick with its decision to migrate to OpenSearch. https://www.mediawiki.org/wiki/Wikimedia_Search_Platform/Decision_Records/Search_backend_replacement_technology has been updated.

[…]

In T370147#10459323, @bking wrote on 14 Jan 2025:

Following up on Gehel 's last comment. Search Platform team (along with stakeholders) has officially decided to migrate to Opensearch. See T370661 for more details about how any why we made that decision.

Krinkle claimed this task.
Krinkle added a subscriber: dr0ptp4kt.