Install Elasticsearch and enable it in Mastodon #97

Manually merged
raucao merged 4 commits from feature/96-elasticsearch_mastodon into master 2019-09-11 11:44:07 +00:00
Owner

This has been tried in Vagrant and should be good to run on andromeda

Refs #96

This has been tried in Vagrant and should be good to run on andromeda Refs #96
raucao reviewed 2019-09-09 10:19:04 +00:00
Owner

Don't we at least want to set a cluster name and a node name as well?

Don't we at least want to set a cluster name and a node name as well?
greg reviewed 2019-09-09 12:50:11 +00:00
Author
Owner

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?

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?
raucao reviewed 2019-09-09 15:24:18 +00:00
Owner

Never mind then.

Never mind then.
Owner

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.

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.
Author
Owner

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

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
Owner

How is something that was merged in June not part of the latest release? I don't quite understand.

How is something that was merged in June not part of the latest release? I don't quite understand.
Author
Owner

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

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
Owner

So what's still missing for merging this now?

So what's still missing for merging this now?
Author
Owner

This is ready to merge now

This is ready to merge now
raucao closed this pull request 2019-09-11 11:44:06 +00:00
raucao closed this pull request 2019-09-11 11:44:07 +00:00
raucao deleted branch feature/96-elasticsearch_mastodon 2019-09-11 11:44:12 +00:00
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: kosmos/chef#97
No description provided.