In T313731#9498030, @Ladsgroup wrote:

Yes, That's how other pruning of old rows works in mediawiki (RC, CU, etc.) and for the sake of simplicity of architecture, it should just reuse the same concepts if not the same code.

Jan 30 2024, 10:08 PM · MW-1.43-notes (1.43.0-wmf.21; 2024-09-03), Patch-For-Review, MW-Interfaces-Team, ApiFeatureUsage, Platform Engineering, Discovery-Search

Ladsgroup added a comment to T313731: Long term plan for reducing maintenance workload on the Search Platform team of supporting APIFeatureUsage.

In T313731#9496949, @aaron wrote:

Even for simple idempotent events like pruning some oldest X expired rows with a limit, where even some divergence would be temporary and not matter in terms of data-integrity?

Yes. It's not just replication, there are many more pieces in our infra.

In any case, I'm fine with having periodic pruning on the INSERT/UPDATE. My main preference is to not have it tied to the special page SELECT.

Yes, That's how other pruning of old rows works in mediawiki (RC, CU, etc.) and for the sake of simplicity of architecture, it should just reuse the same concepts if not the same code.

Jan 30 2024, 11:31 AM · MW-1.43-notes (1.43.0-wmf.21; 2024-09-03), Patch-For-Review, MW-Interfaces-Team, ApiFeatureUsage, Platform Engineering, Discovery-Search

Ladsgroup added a comment to T313731: Long term plan for reducing maintenance workload on the Search Platform team of supporting APIFeatureUsage.

Not to mention we just had a page due to the switchover.

Jan 30 2024, 8:24 AM · MW-1.43-notes (1.43.0-wmf.21; 2024-09-03), Patch-For-Review, MW-Interfaces-Team, ApiFeatureUsage, Platform Engineering, Discovery-Search

• Marostegui added a comment to T313731: Long term plan for reducing maintenance workload on the Search Platform team of supporting APIFeatureUsage.

In T313731#9496949, @aaron wrote:

In T313731#9488510, @Ladsgroup wrote:

The circular replication is quite a snowflake and has caused issues before, I'd avoid it if possible.

I'm curious what those issues are, since we use it for the mainstash DB on x2. Are there tasks that mention them?

Jan 30 2024, 8:20 AM · MW-1.43-notes (1.43.0-wmf.21; 2024-09-03), Patch-For-Review, MW-Interfaces-Team, ApiFeatureUsage, Platform Engineering, Discovery-Search

aaron added a comment to T313731: Long term plan for reducing maintenance workload on the Search Platform team of supporting APIFeatureUsage.

In T313731#9488510, @Ladsgroup wrote:

The circular replication is quite a snowflake and has caused issues before, I'd avoid it if possible.

Jan 30 2024, 1:30 AM · MW-1.43-notes (1.43.0-wmf.21; 2024-09-03), Patch-For-Review, MW-Interfaces-Team, ApiFeatureUsage, Platform Engineering, Discovery-Search

Jan 25 2024

aaron added a project to T313731: Long term plan for reducing maintenance workload on the Search Platform team of supporting APIFeatureUsage: MW-Interfaces-Team.

Jan 25 2024, 5:38 PM · MW-1.43-notes (1.43.0-wmf.21; 2024-09-03), Patch-For-Review, MW-Interfaces-Team, ApiFeatureUsage, Platform Engineering, Discovery-Search

Ladsgroup added a comment to T313731: Long term plan for reducing maintenance workload on the Search Platform team of supporting APIFeatureUsage.

In T313731#9487392, @aaron wrote:

I'd rather not have the writes be cross-datacenter, tying up the working thread in the post-send stage of web requests, especially given the potential for spikes. If there was some aggregation service in the middle (batching/flushing counter updates), that would less risky, though more complex.

Maybe this could use circular replication similar like x2? It probably could just use x2, given the modest traffic there similar needs. The AUTOINCREMENT column would have to be removed. The write queries would use an "INSERT ON DUPLICATE KEY UPDATE" that would naturally merge any conflicting updates from different replication sources.

Jan 25 2024, 2:08 PM · MW-1.43-notes (1.43.0-wmf.21; 2024-09-03), Patch-For-Review, MW-Interfaces-Team, ApiFeatureUsage, Platform Engineering, Discovery-Search

aaron added a comment to T313731: Long term plan for reducing maintenance workload on the Search Platform team of supporting APIFeatureUsage.

I'd rather not have the writes be cross-datacenter, tying up the working thread in the post-send stage of web requests, especially given the potential for spikes. If there was some aggregation service in the middle (batching/flushing counter updates), that would less risky, though more complex.

Jan 25 2024, 5:14 AM · MW-1.43-notes (1.43.0-wmf.21; 2024-09-03), Patch-For-Review, MW-Interfaces-Team, ApiFeatureUsage, Platform Engineering, Discovery-Search

Jan 8 2024

Krinkle added a comment to T313731: Long term plan for reducing maintenance workload on the Search Platform team of supporting APIFeatureUsage.

The ApiFeatureUsage extension, or more specifically the SpecialPage frontend and Action API module, ultimately just need a table with incrementing counters.

Jan 8 2024, 7:42 PM · MW-1.43-notes (1.43.0-wmf.21; 2024-09-03), Patch-For-Review, MW-Interfaces-Team, ApiFeatureUsage, Platform Engineering, Discovery-Search

Dec 3 2023

Theknightwho created T352612: Purging pages with API now requires a POST request.

Dec 3 2023, 6:31 AM · MediaWiki-Page-derived-data

Oct 8 2023

RKemper created T348418: Reboot apifeatureusage* hosts.

Oct 8 2023, 10:46 PM · Data-Platform-SRE

Sep 18 2023

Umherirrender closed T346482: Update ApiFeatureUsage to use the new HookContainer/HookRunner system as Resolved.

Sep 18 2023, 5:52 PM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Core Platform Team Initiatives (New Hook System), ApiFeatureUsage

ReleaseTaggerBot added a project to T346482: Update ApiFeatureUsage to use the new HookContainer/HookRunner system: MW-1.41-notes (1.41.0-wmf.27; 2023-09-19).

Sep 18 2023, 11:00 AM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Core Platform Team Initiatives (New Hook System), ApiFeatureUsage

Maintenance_bot removed a project from T346482: Update ApiFeatureUsage to use the new HookContainer/HookRunner system: Patch-For-Review.

Sep 18 2023, 10:33 AM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Core Platform Team Initiatives (New Hook System), ApiFeatureUsage

gerritbot added a comment to T346482: Update ApiFeatureUsage to use the new HookContainer/HookRunner system.

Change 958021 merged by jenkins-bot:

[mediawiki/extensions/ApiFeatureUsage@master] Use HookHandlers for core hook

https://gerrit.wikimedia.org/r/958021

Sep 18 2023, 10:20 AM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Core Platform Team Initiatives (New Hook System), ApiFeatureUsage

Sep 16 2023

Umherirrender claimed T346482: Update ApiFeatureUsage to use the new HookContainer/HookRunner system.

Sep 16 2023, 10:02 PM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Core Platform Team Initiatives (New Hook System), ApiFeatureUsage

Umherirrender added a parent task for T346482: Update ApiFeatureUsage to use the new HookContainer/HookRunner system: T263353: Update all Wikimedia production extensions to use the new HookContainer/HookRunner system.

Sep 16 2023, 10:01 PM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Core Platform Team Initiatives (New Hook System), ApiFeatureUsage

gerritbot added a project to T346482: Update ApiFeatureUsage to use the new HookContainer/HookRunner system: Patch-For-Review.

Sep 16 2023, 9:43 PM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Core Platform Team Initiatives (New Hook System), ApiFeatureUsage

gerritbot added a comment to T346482: Update ApiFeatureUsage to use the new HookContainer/HookRunner system.

Change 958021 had a related patch set uploaded (by Umherirrender; author: Umherirrender):

[mediawiki/extensions/ApiFeatureUsage@master] Use HookHandlers for core hook

https://gerrit.wikimedia.org/r/958021

Sep 16 2023, 9:43 PM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Core Platform Team Initiatives (New Hook System), ApiFeatureUsage

Umherirrender created T346482: Update ApiFeatureUsage to use the new HookContainer/HookRunner system.

Sep 16 2023, 9:43 PM · MW-1.41-notes (1.41.0-wmf.27; 2023-09-19), Core Platform Team Initiatives (New Hook System), ApiFeatureUsage

Jul 18 2023

lmata moved T325880: Figure out who owns apifeatureusage[12]001 servers from Inbox to Radar on the observability board.

Jul 18 2023, 11:09 PM · Discovery-Search, User-bd808, Platform Engineering, ApiFeatureUsage, SRE Observability, observability

Jul 11 2023

Aklapper changed the edit policy for ApiFeatureUsage.

Jul 11 2023, 6:45 PM

Jun 15 2023

thiemowmde renamed T186849: ApiFeatureUsage extension has no PHPUnit tests from ApiFeatureUsage extension has no tests to ApiFeatureUsage extension has no PHPUnit tests.

Jun 15 2023, 9:31 AM · Test-Coverage, Technical-Debt, ApiFeatureUsage