Skip to content

Instantly share code, notes, and snippets.

@gregblake

gregblake/elastic_search_upgrade.md

Last active February 14, 2020 17:09
Show Gist options
  • Save gregblake/b4acd852492747f9db77e53eeea420ee to your computer and use it in GitHub Desktop.
Save gregblake/b4acd852492747f9db77e53eeea420ee to your computer and use it in GitHub Desktop.
Download ZIP
ElasticSearch Upgrade Notes
Raw
elastic_search_upgrade.md

Steps to Upgrading

  1. Upgraded cluster
  2. Upgrade gems from 2.0.
  3. Audit application for breaking changes, and update them accordingly.
  4. Refresh indices (?)

Other Considerations

  • It looks like we can only upgrade to v6, and not v7 yet. See compatibility chart for the elasticsearch-rails gem.
  • Is the messages table being indexed in production now? If so, will this be compatible after the upgrade? Will we need to refresh the index?
  • Indices are currently updated as part of the ActiveRecord lifecycle. Does this need to happen as part of a background task instead? Curious how this might impact performance (in particular, with the notifications server).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment