[UMETRICS-34] AWS server performance Created: 17/Sep/21  Updated: 22/Sep/21  Resolved: 22/Sep/21

Status: Closed
Project: Usage Metrics
Component/s: server
Affects Version/s: None
Fix Version/s: None

Type: Pain point Priority: Neutral
Reporter: Maxime Michel Assignee: Maxime Michel
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File es-meeting.md    
Template:

 Description   

In recent months, the cheap AWS instance we use has died on us twice, losing all not backed up data in the process. Yesterday had and I had a meeting in which we identified a couple of short/mid-term solutions. I am documenting them here in the case the issue happens again in the future:

  1. m3 single data node
  2. t2 master + t2 data
  3. t2 master + m3 data
  4. t2 master + 2 cheap data nodes

I suggest to go with #1 for now and keep an eye on how it evolves. I will also try setting up CloudWatch emails if simple enough.

I am also including the notes over which we iterated during the meeting. Other solutions were considered, but they were discarded because too expensive changes.


Generated at Mon Feb 12 11:09:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.