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].
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Smalyshev | T213210 WDQS is hitting allocator limit on Blazegraph | |||
Resolved | Gehel | T213361 reload wdqs1006 from other server |
Event Timeline
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2019-01-10T11:54:16Z] <onimisionipe> starting data transfer from wdqs1003 -> wdqs1006 - T213361
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2019-01-10T12:34:33Z] <onimisionipe> starting data transfer from wdqs1003 -> wdqs1006 - T213361 - aborted (nodes are in different cluster)
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2019-01-10T12:42:32Z] <onimisionipe> starting data transfer from wdqs1004 -> wdqs1006 - T213361
Comment Actions
Mentioned in SAL (#wikimedia-operations) [2019-01-10T16:41:45Z] <onimisionipe> data transfer from wdqs1004 -> wdqs1006 completed! - T213361