Page MenuHomePhabricator

reload wdqs1006 from other server
Closed, ResolvedPublic

Description

Looks like wdqs1006 also has very low free allocator number (210 now) which suggests it is about to suffer the same fate as wdqs100[78]. We should reload its database from any of the other servers to prevent it. Good ones to use may be: wdqs100[34578].

Event Timeline

Restricted Application added a project: Wikidata. · View Herald TranscriptJan 10 2019, 12:51 AM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Smalyshev triaged this task as Unbreak Now! priority.
Restricted Application added subscribers: Liuxinyu970226, TerraCodes. · View Herald TranscriptJan 10 2019, 12:52 AM
Smalyshev assigned this task to Gehel.Jan 10 2019, 12:52 AM

Mentioned in SAL (#wikimedia-operations) [2019-01-10T11:54:16Z] <onimisionipe> starting data transfer from wdqs1003 -> wdqs1006 - T213361

Mentioned in SAL (#wikimedia-operations) [2019-01-10T12:34:33Z] <onimisionipe> starting data transfer from wdqs1003 -> wdqs1006 - T213361 - aborted (nodes are in different cluster)

Mentioned in SAL (#wikimedia-operations) [2019-01-10T12:42:32Z] <onimisionipe> starting data transfer from wdqs1004 -> wdqs1006 - T213361

Mentioned in SAL (#wikimedia-operations) [2019-01-10T16:41:45Z] <onimisionipe> data transfer from wdqs1004 -> wdqs1006 completed! - T213361

Mathew.onipe lowered the priority of this task from Unbreak Now! to Normal.Jan 10 2019, 4:42 PM
Smalyshev closed this task as Resolved.Jan 10 2019, 8:54 PM