This is blocking RelEng, and they've called it out as a blocker in scrum-of-scrums. I'm changing the priority to high to get some focus, and I'd appreciate if this could get some attention in our next clinic duty to clear the blocker.

Is this visible in the "Categories" area of the page view? Is there any other user visibility?

So, I've tried this on a couple of wikis and haven't seen it; is the problem related specifically to the language? It doesn't seem to occur in English. And ts uses Latin script (unlike el), so it might not be related to character set.

I've done a first run through the test docs with testwiki, set to multiwrite(redis, kask). It worked fine, which I think is probably what we expect.

@kchapman I wonder if this would be a good task to have Alex help with when she comes onboard?

So, I think this is fixed? I'm going to mark it resolved.

I think we've taken this into account, so I'm going to close this task.

This is done.

It seems like most or all of the components that now use MainStash will instead use WanCache, db-replicated, or db-replicated with a JobQueue. If all of them will, it doesn't make sense to craft a storage solution that is unused. Instead, we could wire MainStash to mcrouter (or db-replicated), and just watch for new extensions or components that use MainStash and make sure that they're not losing too much data.

I'm quitting this job I shouldn't have taken in the first place. I think it'd be a great first task for our soon-to-be-hired tech writer.

For now, I'll take a look to see who on our team can take care of this.

One algorithm for this might be the following:

It would be helpful if @jijiki were able to share their tools or code (if any) that they did for that previous analysis.

For reference, we need more of these!