Closed Bug 1561415 Opened 4 months ago Closed 4 months ago

Upgrade instance for treeherder-stage

Categories

(Tree Management :: Treeherder: Infrastructure, task)

task
Not set

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: armenzg, Assigned: dividehex)

References

Details

Attachments

(1 file)

I want to change treeherder-stage (not production) from db.m4.xlarge to db.m5.2xlarge.

I'm happy to self-serve if you would grant that to me OR I can even open PRs if you would like me to.

There's few changes I might need in the near future to improve Treeherder's performance (see bug 1553199). For instance, we might be interested to switch to Amazon Aurora or Postgres.

Flags: needinfo?(jwatkins)

dividehex: Please let me know when you will be able to handle this. I want to make sure I'm around in case we need to revert it.

Attached file GitHub Pull Request
Assignee: nobody → jwatkins
Flags: needinfo?(jwatkins)

(In reply to Armen [:armenzg] from comment #1)

dividehex: Please let me know when you will be able to handle this. I want to make sure I'm around in case we need to revert it.

I'm available anytime this week or next to conduct this upgrade. Just let me know when to pull the trigger.

I've sent an invite for next week Wednesday deploying this.
Thanks Jake!

Via slack, it was requested to start the upgrade anytime...

The upgrade to stage rds is complete.

aws_db_instance.treeherder-stage-rds: Modifying... (ID: treeherder-stage)
instance_class: "db.m4.xlarge" => "db.m5.2xlarge"
...
aws_db_instance.treeherder-stage-rds: Modifications complete after 25m22s (ID: treeherder-stage)

Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → FIXED
Type: defect → task
You need to log in before you can comment on or make changes to this bug.