Skip to content
This repository has been archived by the owner on Mar 23, 2023. It is now read-only.

Develop an HA plan for the batch submitter service #1390

Open
7 tasks done
CLEckhardt opened this issue Apr 21, 2022 · 0 comments
Open
7 tasks done

Develop an HA plan for the batch submitter service #1390

CLEckhardt opened this issue Apr 21, 2022 · 0 comments
Assignees
@CLEckhardt
Labels
5 Time estimate Epic: Batch Tracking

Comments

@CLEckhardt
Copy link
Contributor

CLEckhardt commented Apr 21, 2022 •
edited

Develop a plan and design doc for a high-availability deployment of the batch submitter service.

To do

  • Determine overall HA approach
  • Determine and demonstrate that we can/cannot safely make atomic updates with postgres (i.e. can implement a concurrency-safe job queue with locks on service_ids)
  • Determine and demonstrate that we do/do not need some form of down detection
  • Write up concurrency options and tradeoffs (determine database load)
  • Map out the queries and data model related to instance coordination
  • Determine the impact of using SQLite in an HA configuration
  • Map out the impact of an HA configuration to the queuer, submitter, and DLT monitor
@CLEckhardt CLEckhardt self-assigned this Apr 21, 2022
@CLEckhardt CLEckhardt added this to Ready in Grid Apr 21, 2022
@CLEckhardt CLEckhardt moved this from Ready to In progress in Grid Apr 22, 2022
@shannynalayna shannynalayna added the 5 Time estimate label May 2, 2022
@CLEckhardt CLEckhardt moved this from In progress to In Review in Grid Jul 12, 2022
@ryjones ryjones removed this from In Review in Grid Mar 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@CLEckhardt CLEckhardt

Labels
5 Time estimate Epic: Batch Tracking
Milestone
No milestone
Development

No branches or pull requests
2 participants
@shannynalayna @CLEckhardt