[FOLIO-3074] Confirm the database configuration of the FOLIO Jira Created: 11/Mar/21  Updated: 23/Mar/21  Resolved: 23/Mar/21

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: TBD
Reporter: Peter Murray Assignee: Mike Gorrell
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:
Development Team: None

 Description   

Question: should the FOLIO project use a multi-zone database instance for FOLIO's Jira?

The FOLIO Jira has become crucial to the project's momentum, and the DevOps team has a question about the ideal database configuration.  Jira currently uses an AWS `db.m5.xlarge` instance of MySQL in us-east-1d.  We can make this database instance multi-zone in the AWS us-east-1 region so the database is constantly replicated to another Availability Zone.  In the event of catastrophic failure of `us-east-1d`, we can spin up an EC2 instance in another zone where the MySQL replica is running (e.g., `us-east-1a`).  Automatic snapshots of the Jira application/data EBS volume are made twice daily in the event that the EBS volume in `us-east-1d` can't be reached.

The downside is cost.  Reserved instance contracts for `db.m5.xlarge` instances are $166/month (about $2,000/year).  Making the replicated MySQL instance doubles that cost.

For your information:  In the next year or so, the FOLIO project is going to have to move to cloud-hosted Jira and Confluence due to Atlassian's decision to deprecate the self-hosted instances ( FOLIO-3004 Open ).



 Comments   
Comment by Peter Murray [ 23/Mar/21 ]

Technical Council affirmed the decision to use a multi-AZ RDS for Jira.  The primary motivators were the significant loss of productivity for all corners of the project of missing data in Jira in the gap from the last backup versus the relatively small cost to have the database instantly replicated and available for making it live in another availability zone.

Generated at Thu Feb 08 23:25:25 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.