ES Release Plan

Unknown
edited April 2021 in Support Agents

Quick reference for us to determine who is on Elastic and who isn't:

Before we go nuts and start flipping the Elastic switch, we will want to make sure that we have our customer's content indexed with Elastic Search. On the following dates, Ops will begin the indexing process in the background, without enabling Elastic Search. 

March 30th: Ops will begin the indexing process for Public clusters (cl300xx & cl400xx)

April 6th: Ops will begin the indexing process for Enterprise clusters (cl500xx)

Once indexing has been completed Ops will begin enabling Elastic Search.

April 8th: Elastic Search will be enabled by default on all dev & staging clusters (cl100xx & cl200xx)

April 8th: BETA Customers will have Elastic Search enabled on production. 

April 13th: Elastic Search will be enabled by default on all public clusters (cl300xx & cl400xx)

April 21st: Elastic Search will be enabled by default on all Enterprise clusters (cl500xx)


Rollout Schedule. <-- Link

Comments

  • Unknown
    edited April 2021

    Note from Francis:

    Here some information that could potentially help support over the weekend or even the next few weeks if search issues arise. We started rolling out ES as many of you already know. You can track progress here: https://github.com/vanilla/dev-inter-ops/issues/88#issuecomment-816002691 (if you do not have access to the repo I’m sharing a screenshot of the state right now with this message). Please ask questions if you are unsure about something.


    ES add-on means the add-on is enabled and we’ve began/complete indexing on their cluster/sites

    ES Active means elastic search is the search driver we use when making searches on that cluster/sites

    SX Disable means sphinx isn’t enable anymore (We aren’t there yet but mentioning it for next few weeks)


    That being said if search issues arise and you believe ES could be the problem (on the clusters/sites where ES is running) you can revert the site back to sphinx by setting that configuration in the site config: Vanilla.Search.Driver = sphinx . Obviously this requires the sphinx add-on to be enabled. I encourage you to, please, share the above with anyone who this can be relevant too. Thank you.


    To reiterate a note from Tim, disabling ES should be a last resort. If you feel you have to do it, make sure the issue is well documented.