Database hiccup

At approximately 7:30am PDT, EZID’s database in the Amazon cloud infrastructure suffered a brief outage.  3 operations were affected.  The database has been operately normally since then.

Advertisements

Server hiccup

The server hung on a routine software update and had to be restarted, resulting in an outage of a few seconds.  There were a few requests being processed at the time, and those likely failed.

Excessive usage encountered

EZID suffered a brief interruption when it was restarted to ban a particular user.  We’re unsure whether the user was malicious, or just being over-enthusiastic in their stress testing.

N2T resolver backlog

Due to heavy activity, there is a backlog in registering ARK identifiers with the N2T resolver.  The backlog should clear in about a day.

The backlog has cleared. DOI registrations will be reflected in the Handle System with their normal delay, a few seconds to a few minutes.

There is a backlog in DOI registrations, which will be finished in about 4 hours. (Written at 09:30 PST)

Database upgrade completed

The database upgrade ended up taking about 60min, but is completed.

Database upgrade

During this morning’s maintenance window we’re going to be upgrading EZID’s database.  Based on upgrades of similar systems, we expect EZID to be down for approximately 20 minutes.

Higher-than-normal DOI activity

EZID is encountering higher-than-normal DOI activity.  It may take up to a day for a newly-registered DOI to appear in the Handle System.  We expect the activity to subside within the next couple days.  In the meantime, we’re working with DataCite to see if there’s a way we can push requests through faster.

N2T problem resolved

The N2T database problem has been resolved and EZID and N2T are again connected.  New ARK identifiers will resolve.  ARK identifiers created during the outage are being back-registered into N2T now; that process will complete in about 4 hours.