Uploaded image for project: 'Usage Metrics'
  1. Usage Metrics
  2. UMETRICS-34

AWS server performance

    XMLWordPrintable

Details

    • Pain point
    • Resolution: Fixed
    • Neutral
    • None
    • None
    • server
    • None

    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.

      Attachments

        Activity

          People

            mmichel Maxime Michel
            mmichel Maxime Michel
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: