Planned labs maintenance on tools-db: Puppetization + log file change
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	yuvipanda
	Apr 1 2015, 12:33 AM

Description

Why is being done

For T88234 to be completed, https://dev.mysql.com/doc/refman/5.5/en/innodb-data-log-reconfiguration.html needs to be done. Since this also has other changes being bundled in, a small window of planned maintenance would be appropriate.

What is going to be affected?

tools-db on labsdb1005. Would be down for a small amount of time.

How is this being done?

https://dev.mysql.com/doc/refman/5.5/en/innodb-data-log-reconfiguration.html will be followed by hand.

When is this planned?

2015-04-16 02:00 UTC

Possible to roll back / stop mid way? Recovery plan if it goes belly up?

I guess we could just put the old config back, disable puppet, and start it back up? {{citationneeded}}

Related Objects
Search...

Status	Assigned	Task
Resolved	coren	T88234 Puppetize & fix tools-db
Resolved	yuvipanda	T94643 Planned labs maintenance on tools-db: Puppetization + log file change
Resolved	• jcrespo	T88718 Make sure tools-db is replicated somewhere

Event Timeline

yuvipanda created this task.Apr 1 2015, 12:33 AM

yuvipanda raised the priority of this task from to Needs Triage.

yuvipanda updated the task description. (Show Details)

yuvipanda added projects: Cloud-Services, Toolforge.

yuvipanda added subscribers: yuvipanda, coren, • Springle.

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptApr 1 2015, 12:33 AM

yuvipanda mentioned this in T94608: Create a simple checklist to follow for announcing / doing planned maintenance (on labs).Apr 1 2015, 12:33 AM

yuvipanda updated the task description. (Show Details)Apr 1 2015, 12:37 AM

yuvipanda set Security to None.

yuvipanda updated the task description. (Show Details)Apr 1 2015, 12:44 AM

yuvipanda updated the task description. (Show Details)Apr 1 2015, 1:03 AM

yuvipanda added a parent task: T88234: Puppetize & fix tools-db.Apr 1 2015, 1:38 AM

coren added a subtask: T88718: Make sure tools-db is replicated somewhere.Apr 1 2015, 8:38 PM

Yes, the recovery plan can be as simple as put-the-old-config-back.

Since there is no replication slave (right?) for tools-db, we should dump the data first.

In T94643#1172810, @Springle wrote:

Since there is no replication slave (right?

That's Phase II. :-)

Should we schedule this tentatively for Thursday next?

scfc triaged this task as Medium priority.Apr 6 2015, 11:03 AM

scfc moved this task from Backlog to Ready to be worked on on the Toolforge board.

scfc subscribed.

@Springle: Ping? It's now too late to schedule this for this Thursday if you expect any outage at all given we have decided on a week's notice - can you okay a window for next week, then?

I just spoke to @Springle on IRC and he said coming Thursday (16th April) 0200 UTC is good for him.

@coren can you mail out a notice?

Notice mail't

jeremyb-phone added a subscriber: jeremyb.Apr 10 2015, 2:56 PM

coren updated the task description. (Show Details)Apr 10 2015, 5:37 PM

Ricordisamoa subscribed.Apr 11 2015, 11:40 AM