MediaWiki and Phabricator supports Elasticsearch.
While we have no firm plan to implement it, elasticsearch seems to be a good stuff. Maybe we can (in the future) use it for high-traffic wikis and Phabricator.
MediaWiki and Phabricator supports Elasticsearch.
While we have no firm plan to implement it, elasticsearch seems to be a good stuff. Maybe we can (in the future) use it for high-traffic wikis and Phabricator.
Status | Assigned | Task | ||
---|---|---|---|---|
Declined | Southparkfan | T2482 Have a look at Elasticsearch | ||
Declined | John | T2742 Requesting extensions CirrusSearch and Elastica for Podpedia |
I think the best course of action in this case would be to expand our current parsoid1 server and make it a misc3. We could host Elasticsearch and Collection there.
Parsoid, Collection and ES are all memory/cpu heavy services. Hosting them all on a small memory server seems a) unwise b) unreliable.
We looked at ES originally and decided resources v gain was little so unless the gain has increased in usage, I doubt the resources are there for it.
I'm still not convinced about the benefits of this. For new infrastructure there should be an identified benefit and identified user base and I don't think this really has either.
Search index in db* seems fine, disk intensive but fine.
@Southparkfan will probably have his yes/no on this fairly quickly.