Magnus added a comment.

I haven't had time for a detailed look yet. Yuvi updated WDQ to the latest 
dump, which is where the timestamp comes from. He says both VMs are running 1 
CPU at 100%, but don't reply to queries. That sounds like they try to update to 
the live state via the API, but got stuck in a loop.

A quick patch could be to disable incremental updates; then, the VMs would be 
stuck at the current timestamp, but at least answer to queries. Then we'd have 
to figure out where the updating fails. Not sure when I'll have time.


TASK DETAIL
  https://phabricator.wikimedia.org/T89583

REPLY HANDLER ACTIONS
  Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign 
<username>.

EMAIL PREFERENCES
  https://phabricator.wikimedia.org/settings/panel/emailpreferences/

To: Magnus
Cc: Johansen.fred, Mushroom, Shonagon, yuvipanda, Magnus, Aklapper, Multichill, 
Wikidata-bugs, Jdouglas, aude, Gryllida, scfc



_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to