Gehel added a comment.

The tricky part here is that once we deploy the change, we'd need to reload immediately (since the dictionary would be incompatible). But we don't want to take all servers down at the same time. So we need a way to run server with different configs for a while. @Gehel, do you have any ideas how to do it best?

Is it different config or different code? As I read https://gerrit.wikimedia.org/r/#/c/383777/, I understand that the new vocabulary is deployed as part of Blazegraph code. We might be using different definitions of "config"... In my vocabulary, config is something deployed externally to balzegraph, and that shoudl be deployed with Puppet, and can easily be parameterized for each server, via hiera (yes, I simplify a bit).

In this case, if I understand correctly, we need something like:

for each server n:

  • depool server n
  • update code
  • data reimport import
  • pool server n

And we can probably parallelize eqiad and codfw.

This should not be an issue, we can restrict scap to deploy to only a subset of servers...


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

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

To: Gehel
Cc: gerritbot, Gehel, Aklapper, Smalyshev, Gq86, Lordiis, Lucas_Werkmeister_WMDE, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, EBjune, merbst, Avner, Lewizho99, Maathavan, debt, Jonas, FloNight, Xmlizer, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, Mbch331
_______________________________________________
Wikidata-bugs mailing list
Wikidata-bugs@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs

Reply via email to