Wikitech-l February 2022

wikitech-l@lists.wikimedia.org

43 participants
37 discussions

Facing a Problem in issue #105
by Ameygupta 05 Feb '22

05 Feb '22

4 5

Re: [Ops] Re: Tendril shutdown
by Daniel Zahn 04 Feb '22

04 Feb '22

Yes, it's much prettier than dbtree. Nice! On Thu, Feb 3, 2022 at 4:48 PM Aaron Schulz <aschulz(a)wikimedia.org> wrote: > > I really like the visual tree on https://orchestrator.wikimedia.org/ . Good work! > > On Tue, Jan 4, 2022 at 3:18 AM Manuel Arostegui <marostegui(a)wikimedia.org> wrote: >> >> Hello, >> >> If you don’t use tendril.wikimedia.org or dbtree.wikimedia.org, feel free to ignore this message. >> >> >> As of today, tendril is now retired and the main page is replaced with a list of replacement for different services tendril used to provide: >> >> >> For checking out our dbtree and replication data: >> >> if you are in the NDA LDAP group, use Orchestrator >> >> otherwise, use the information page on noc.wikimedia.org. For more detail you can also check eqiad.json or codfw.json >> >> If you are looking for slow queries log, go to slow queries dashboard using our standard observability platform (logstash) (NDA required) >> >> >> Tendril has been a great tool for us during the years, but unfortunately it is impossible to maintain with modern MariaDB versions (it uses TokuDB, which is no longer available on MariaDB after 10.1 and needs to be compiled separately) nor its webservice is compatible with modern php versions. Its database is still running on Stretch and on MariaDB 10.1 (which has not been supported for a year already) and it is having serious scalability issues. This would unblock us from removing a lot of legacy home-brew craft and replace them with more modern toolings such as orchestrator. >> >> >> Orchestrator has been in place for a few months now, and provides us with a great way to see and (in the future) manage replication topologies. For now we are using it only for visualization purposes but in the future we’d like it to also help us to handle replication changes (it can be done from the UI or via CLI) and recover topologies automatically if they fail and involve masters or intermediate masters. >> >> >> The slow queries dashboard in logstash offer multiple advantages over tendril. You can set the threshold to see slow queries that took longer to run. You can filter out code paths you’re not interested in or zoom in to relevenet code paths. You can limit it to write queries or read queries only. Also, it provides id of the request making the slow query, so you can cross check it with the rest of logstash or hadoop to identify problematic behavior. >> >> >> If you need it for the transition period, you can still access it in tendril-legacy.wikimedia.org. But it will be shut down in a month. You can follow the work of shutting down tendril in https://phabricator.wikimedia.org/T297605. >> >> >> Thank you. >> >> >> _______________________________________________ >> Ops mailing list -- ops(a)lists.wikimedia.org >> To unsubscribe send an email to ops-leave(a)lists.wikimedia.org > > _______________________________________________ > Ops mailing list -- ops(a)lists.wikimedia.org > To unsubscribe send an email to ops-leave(a)lists.wikimedia.org -- Daniel Zahn <dzahn(a)wikimedia.org> Operations Engineer

1 0

Production Excellence #40: January 2022
by Krinkle 04 Feb '22

04 Feb '22

How’d we do in our strive for operational excellence last month? Read on to find out! Incidents There were no incidents this January. Pfew! Remember to review and schedule Incident Follow-up work <https://phabricator.wikimedia.org/project/view/4758/> in Phabricator. These are preventive measures and tech debt mitigations written down after an incident is concluded. Read about past incidents at Incident status <https://wikitech.wikimedia.org/wiki/Incident_status> on Wikitech. Trends During 2021, I compared us to the median of 4 incidents per month, as measured over the two years prior (2019-2020). I'm glad to announce our median has lowered to 3 per month over the past two years (2020-2021). For more plots and numbers about our incident documentation, refer to Incident stats <https://codepen.io/Krinkle/full/wbYMZK>. Since the previous edition, we resolved 17 tasks from previous months. In January, there were 45 new error reports <https://phabricator.wikimedia.org/maniphest/query/f24Xwi0bGGZU/#R> of which 28 have been resolved within the same month, the remaining 17 have carried over to February. With precisely 17 tasks both closed and added, the workboard remains at the exact total of 298 open tasks, for the third month in a row. That's quite the coincidence. Figure 1: Unresolved error reports by month. <https://phabricator.wikimedia.org/phame/post/view/266/production_excellence…> Take a look at the workboard and look for tasks that could use your help. → https://phabricator.wikimedia.org/tag/wikimedia-production-error/ Thanks! Thank you to everyone who helped by reporting, investigating, or resolving problems in Wikimedia production. Thanks! Until next time, – Timo Tijhof *🎸 Doc Brown <https://en.wikiquote.org/wiki/Back_to_the_Future_Part_II>*: *It could mean that that point in time contains some cosmic significance.., as if it were the temporal junction point of the entire space-time continuum… Or it could just be an amazing coincidence.* 🔗 Share or read later via https://phabricator.wikimedia.org/phame/post/view/266/

1 0

Talk to the Search Platform Team—February 2nd, 2022
by Trey Jones 01 Feb '22

01 Feb '22

The Search Platform Team <https://www.mediawiki.org/wiki/Wikimedia_Search_Platform> usually holds an open meeting on the first Wednesday of each month. Come talk to us about anything related to Wikimedia search, Wikidata Query Service, Wikimedia Commons Query Service, etc.! Feel free to add your items to the Etherpad Agenda for the next meeting. Details for our next meeting: Date: Wednesday, February 2nd, 2022 Time: 16:00-17:00 GMT / 08:00-09:00 PST / 11:00-12:00 EST / 17:00-18:00 CET & WAT Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours Google Meet link: https://meet.google.com/vgj-bbeb-uyi Join by phone: https://tel.meet/vgj-bbeb-uyi?pin=8118110806927 Hope to talk to you next week! —Trey Trey Jones Staff Computational Linguist, Search Platform Wikimedia Foundation UTC–5 / EST

1 1

Interested in working with your organization
by Fiza khan 01 Feb '22

01 Feb '22

Hello, I am Fiza Khan, an undergraduate computer science student. I'm new to open source but well acquainted with css, html, javascript, bootstrap framework, c++, ruby on rails. I would love to contribute to your organisation. I don't have any idea how to get started in your organisation. Is there any slack or other channel for further queries? Looking forward to hearing from you Thanks and Regards Fiza Khan

2 1

🕓 Backport window timeslot changes
by Tyler Cipriani 01 Feb '22

01 Feb '22

tl;dr: Backport windows will shift earlier in the (UTC) day starting on Mon, Feb 14th. *Problem* Some backport windows have few deployers, and windows are not evenly distributed for global users—the window times slant US-centric. *Solution* tl;dr: we made a spreadsheet <https://docs.google.com/spreadsheets/d/1-bMfSzzzNxaOswFgqxkGVhfBnTenYL0Rw8X…> (Antoine did, actually). After discussing with backport and train deployers, we're shifting backport window timeslots to: 1. Evenly distribute backport windows – the IST timezone had no good time to deploy 2. Provide better deployer coverage – the late afternoon backport window (which previously happened at 4pm Pacific) often had few deployers (and few users) Here's a schedule that will be live *Mon, Feb 14th *(my Valentine's day present to you all) - 08:00 UTC 🔙 Early Backport - 14:00 UTC 🔙 Afternoon Backport - 21:00 UTC 🔙 Evening Backport Train - 09:00 UTC 🚂 UTC-0 (Antoine) Train - 19:00 UTC 🚂 UTC-7 (US) Train Big(ish) Changes - UTC-7 train is an hour earlier - Swapped with the backport window so backport is now after train - UTC-Early backport is much earlier - UTC-Late backport is pretty early, too <3 Tyler Cipriani (he/him) Engineering Manager, Release Engineering Wikimedia Foundation

2 2

Phabricator monthly statistics - 2022-01
by aklapper＠wikimedia.org 01 Feb '22

01 Feb '22

Hi Community Metrics team, This is your automatic monthly Phabricator statistics mail. Accounts created in (2022-01): 290 Active Maniphest users (any activity) in (2022-01): 1036 Task authors in (2022-01): 547 Users who have closed tasks in (2022-01): 287 Projects which had at least one task moved from one column to another on their workboard in (2022-01): 289 Tasks created in (2022-01): 2176 Tasks closed in (2022-01): 2203 Open and stalled tasks in total: 49069 * Only open tasks in total: 48175 * Only stalled tasks in total: 894 Median age in days of open tasks by priority: Unbreak now: 5 Needs Triage: 739 High: 1061 Normal: 1606 Low: 2238 Lowest: 2326 (How long tasks have been open, not how long they have had that priority) Active Differential users (any activity) in (2022-01): 1 To see the names of the most active task authors: * Go to https://wikimedia.biterg.io/ * Choose "Phabricator > Overview" from the top bar * Adjust the time frame in the upper right corner to your needs * See the author names in the "Submitters" panel TODO: Numbers which refer to closed tasks might not be correct, as described in https://phabricator.wikimedia.org/T1003 . Yours sincerely, Fab Rick Aytor (via community_metrics.sh on phab1001 at Tue 01 Feb 2022 12:00:19 AM UTC)

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l February 2022