Install Elasticsearch and enable it in Mastodon #97
Labels
Clear labels
monitoring
bug
design
dev environment
docs
duplicate
enhancement
feature
good first issue
idea
invalid
kredits-1
kredits-2
kredits-3
on hold
ops
question
security
ui/ux
wontfix
service
discourse
Kosmos Community Forums
Infrastructure metrics, alerts, notifications, etc.
service
accounts
Kosmos Accounts
service
drone-ci
Kosmos Drone CI
service
email
mail.kosmos.org
service
garage
S3-compatible object storage
service
gitea
Kosmos Gitea
service
ipfs
Kosmos IPFS
service
mastodon
kosmos.social
service
nostr
Relays, Blossom server, etc.
service
postgres
Database cluster
service
remotestorage
Portable data storage for the Web
service
wiki
Kosmos Wiki
service
xmpp
Kosmos Chat
Something is not working
Graphic/visual design
Config, builds, CI, deployment, etc.
Documentation
This issue or pull request already exists
Improving existing functionality
New functionality
Dive in, and start contributing
Something to consider
Not a bug
Small contribution
Medium contribution
Large contribution
Currently not actionable
Manual IT ops activities
Looking for an answer
release
major
release
minor
release
patch
All your base are belong to us
User interface, process design, etc.
This won't be fixed
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: kosmos/chef#97
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This has been tried in Vagrant and should be good to run on andromeda
Refs #96
Don't we at least want to set a cluster name and a node name as well?
The node name is set automatically from the server's hostname so that is not needed. The default cluster name is
elasticsearch, do you have a suggestion for a name?Never mind then.
utACK. If you want, you can try it on Andromeda. Please just make sure to keep an eye on the resource usage for a bit, because there's some RAM left, but not crazy amounts of it.
I ran into an issue generating the Elasticsearch indices, but I found a PR that was merged into master that's not part of Mastodon 2.9.3 that fixes it: https://github.com/tootsuite/mastodon/pull/11192.
In order to run the importing tasks I have changed the code locally, and I will cherry pick the commit into our production branch
How is something that was merged in June not part of the latest release? I don't quite understand.
It was merged to master but not the stable-2.9 branch. Currently it's 382 commits behind master: https://github.com/tootsuite/mastodon/tree/stable-2.9/app
So what's still missing for merging this now?
This is ready to merge now