Gehel added a comment.

There are 3 issues here, and maybe they should be addressed on different tickets:

  1. isolating updater from blazegraph: this is about reducing the interactions between the 2 components to what is essential, increasing robustness and simplifying investigation into any failure
  2. sharing update workload between different servers: at the moment, update workload is growing linearly with the number of blazegraph servers, both in term of internal workload and in term of induced workload on other components (kafka, wikidata, ...)
  3. optimizing the updater process itself

I think that 1) and 2) have a somewhat strong coupling and should be discussed together, 3) is a fairly different optimization which probably deserves its own ticket.


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

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

To: Gehel
Cc: Smalyshev, Aklapper, Joe, Gehel, Nandana, thifranc, AndyTan, Davinaclare77, Qtn1293, Lahi, Gq86, Lucas_Werkmeister_WMDE, GoranSMilovanovic, Th3d3v1ls, Hfbn0, QZanden, EBjune, merbst, LawExplorer, Zppix, Jonas, Xmlizer, Wong128hk, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, faidon, Mbch331, Jay8g, fgiunchedi
_______________________________________________
Wikidata-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to