Closed Bug 1178046 Opened 9 years ago Closed 9 years ago

ensure Socorro can handle upcoming leap second

Categories

(Socorro :: Infra, task)

Product:
Socorro
Component:
Infra
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: rhelmer, Assigned: rhelmer)

Details

There will be a leap second inserted on Tuesday June 30, 2015 at 23:59:60 UTC.

Last time there was a leap second, Hadoop clusters (and other Java apps) around the world went down.

Let's make sure all Socorro apps and services can handle this - thinking of ES specifically since it's Java. We should make sure we have all system packages up to date.

Maybe we could roll stage's clocks forward and make sure collection+processing+reporting survives when it ticks over? :)
We didn't get a chance to practice it on stage first, but there were no leap-second-related packages to apply and the leap second has passed without apparent incident.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.