So, apparently I have ElasticSearch now? I had to hard reset my server in the middle of indexing because it ran out of memory and came to a complete halt. (See https://ma.fellr.net/@fell/111375959444602138)
It seems to be working though? I don't care if it hasn't indexed everything as long as it indexes new posts.
@elduvelle@odr_k4tana @feditips
I just encountered a time consuming process on 🦣: a paper I boosted got published and I was hoping to replied to you original booted post so make the information continuous...it took me 30 mins to find the post only becus I had an earlier reply that contain images so I can retrieve from my media tool in #tusky, I had tried #tootfinder and #justmytoots neither of it helped me....and unfortunately my instance cannot afford #elasticsearch.😞
@kofanchen@odr_k4tana@feditips
In any case, I hope your instance can get #ElasticSearch eventually because it is really a game changer, especially for scientists! @jonny got it to work for us and I’m sure they’ll be happy to provide some pointers (or tricks) about it.
Remember: if your server has the new Search enabled, you should decide if you want to be included in it or not (Settings > Public Profile > Privacy & Reach) and tick (or not) the “Include public posts in search results” box.
It’s disabled by default so please enable it to make Mastodon more searchable and useful!! #MastoTip#ElasticSearch
I took some time to work out the exact #formatting that #Elasticsearch demands. If you think this might be useful, go ahead and boost. If you find any errors or would like to suggest additions, please also post a reply!
Hopefully this can help prevent a lot of frustration and trouble people might encounter and give them a better Mastodon experience!
Well, I finally got myself up to #Mastodon v4.1.9, and now to begin the v4.2.0 upgrade. Not going to bother with #Elasticsearch setup for now, though would probably go for #OpenSearch probably anyways.
I'm currently running the Elasticsearch update after upgrading to Mastodon 4.2.0, and it was running really fast until it got to "PublicStatusesIndex" — now it's still importing documents, but it's really slow. It says 406 docs/s, w/ 54M to go, and the ETA keeps getting longer. Anyone else experience this?
I've noticed a lot of chatter about setting up Elasticsearch for Mastodon 4.2's new full text search over the last few days, including what hardware is required, how difficult is it, etc.
So I thought I’d write down my experience, including the hardware I'm running Elasticsearch on for my single user instance:
@enusbaum I went to check if I needed to update #Elasticsearch on my #Mastodon server and then realized that I don't have Elasticsearch on my server because I have 4GB of RAM on my server and Elasticsearch would die on my server.
How to use Elasticsuite to boost the search results by a manually defined sorting relevance? This can be solved just by configuring Elasticsuite, no code adaptions are needed. I've documented the steps in my bitExpert blog post https://blog.bitexpert.de/blog/elasticsuite_sort_relevance_boost
can confirm. The new fulltext search works great, and is awesome! I just searched for "footiMac" which I know only I use and it returned results very very quickly. I can go way back. Including to it's very first mention back in January!
This ability is so very important for the usability and attractiveness of Mastodon!
Unsere #Mastodon Instanz wurde gestern auf die neue Version 4.2.0 aktualisiert. :tux: Es bietet viele Verbesserungen, von der Suche, dem Onboarding-Prozess, bis zur Oberfläche und viele mehr!
Darüber hinaus betreiben wir nun auch #ElasticSearch im Hintergrund, also einen Suchindex. Wir werden deshalb auch bald unserem Server mehr Power geben müssen.
Profilbeschreibungen werden nun auch in der #Suche erfasst, genauso wie eure Posts, wenn ihr dies optional einstellt.
Updated my #Mastodon instances to 4.2.0 this evening. Just awaiting one of them to finish re-indexing things in #ElasticSearch. :docker: :mastodondance: