Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SPIKE: Investigate how ElasticPress could gracefully fallback when ES times out or errors #524

Open
5 of 20 tasks
owaincuvelier opened this issue Aug 13, 2024 · 1 comment
Labels
could have Could be done, or nice to have, low priority for now
Milestone

Comments

@owaincuvelier
Copy link
Contributor

owaincuvelier commented Aug 13, 2024

Currently, if your ES cluster goes down, this can cause the entire request to fail or timeout.
Ideally, the request to ES would time out in isolation and fallback to MySQL.

This needs to consider both standard front end queries, admin queries, updates, etc.
Edges cases should be covered and documented.

Check with 10Up, on their plans/approach for resiliency.

Potentially produce a simple Proof of Concept.


Acceptance Criteria

  • A documented response from 10Up
  • An outline of any potential approach
  • A plan for implementation

TimeBox: 2 days


For Altis Team Use

Ready for Work Checklist

Is this ticket ready to be worked on? See
the Play Book Definition of Ready

  • Is the title clear?
  • Is the description clear and detailed enough?
  • Are acceptance criteria listed?
  • Have any dependencies been identified? (Optional)
  • Have any documentation/playbook changes been identified? (Optional)
  • Is an estimate or time box assigned?
  • Is a priority label assigned?
  • Is this ticket added to a milestone?
  • Is this ticket added to an epic? (Optional)

Completion Checklist

Is this ticket done? See
the Play Book Definition of Done

  • Has the acceptance criteria been met?
  • Is the documentation updated (including README)?
  • Do any code/documentation changes meet project standards?
  • Are automatic tests in place to verify the fix or new functionality?
    • Or are manual tests documented (at least on this ticket)?
  • Are any Playbook/Handbook pages updated?
  • Has a new module release (patch/minor) been created/scheduled?
  • Have the appropriate backport labels been added to the PR?
@owaincuvelier owaincuvelier added could have Could be done, or nice to have, low priority for now to refine Issues needing refinement. labels Aug 13, 2024
@mikelittle mikelittle added this to the Altis v21 milestone Aug 14, 2024
@mikelittle mikelittle changed the title Catch timeout and fall back SPIKE: Investigate how ElasticPRess could Gracefully fallback when ES times out or errors Aug 14, 2024
@mikelittle mikelittle changed the title SPIKE: Investigate how ElasticPRess could Gracefully fallback when ES times out or errors SPIKE: Investigate how ElasticPress could gracefully fallback when ES times out or errors Aug 14, 2024
@mikelittle
Copy link
Contributor

Hey team! Please add your planning poker estimate with Zenhub @jerico @kovshenin

@mikelittle mikelittle removed the to refine Issues needing refinement. label Aug 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
could have Could be done, or nice to have, low priority for now
Projects
None yet
Development

No branches or pull requests

2 participants