2018-05-08
§
|
20:12 |
<milimetric> |
aborting deployment, will deploy data truncation script too |
[analytics] |
20:08 |
<milimetric> |
deploying refinery to relaunch geoeditors job |
[analytics] |
17:57 |
<joal> |
Mvoe recomputed 2018-03 history snapshot in place of old one (T194075) |
[analytics] |
15:38 |
<joal> |
Try again (last time) to rerun mediawiki-history-druid-wf-2018-04 |
[analytics] |
15:06 |
<ottomata> |
beginnng Kafka upgrade of main-codfw: T167039 |
[analytics] |
08:01 |
<elukey> |
removed cassandra-metrics-collector (graphite) from aqs nodes |
[analytics] |
07:42 |
<joal> |
Rerun mediawiki-history-druid-wf-2018-04 in a non-sync way with mediawiki-reduced |
[analytics] |
06:41 |
<elukey> |
rolling restart of druid-historicals on druid100[456] due to half of the segments not avaiable |
[analytics] |
2018-05-02
§
|
17:33 |
<joal> |
Rerun webrequest-load-wf-text-2018-5-2-15 |
[analytics] |
16:41 |
<joal> |
Manually silence pageview-whitelist alarm overwriting /wmf/refinery/current/static_data/pageview/whitelist/whitelist.tsv |
[analytics] |
16:27 |
<joal> |
2018-05-02T14 webrequest dataloss warnings have been checked and are false positives |
[analytics] |
16:17 |
<joal> |
Restart oozie mediawiki-history-denormalize job after deploy |
[analytics] |
16:14 |
<ottomata> |
bounced eventlogging-consumer@mysql-m4-master-00 after kafka jumbo 1.1.0 upgrade |
[analytics] |
16:05 |
<joal> |
Restart oozie webrequest bundle after deploy |
[analytics] |
15:20 |
<joal> |
Deploying refinery to hadoop |
[analytics] |
14:45 |
<joal> |
Deploying refinery using Scap |
[analytics] |
14:16 |
<joal> |
Refinery-source version 0.0.63 finally released to Archiva! |
[analytics] |
13:49 |
<ottomata> |
beginning upgrade of kafka-jumbo brokers from 1.0.0 -> 1.1.0 : T193495 |
[analytics] |
13:20 |
<elukey> |
restart druid broker on druid100[1-3] to enable druid.sql.enable: true |
[analytics] |