Page MenuHomePhabricator

ContentTranslationError event logging table is not receiving new events
Closed, ResolvedPublic

Event Timeline

Nikerabbit raised the priority of this task from to High.
Nikerabbit updated the task description. (Show Details)
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptMay 12 2015, 10:14 AM
Nemo_bis set Security to None.
Nemo_bis edited subscribers, added: Nemo_bis; removed: Analytics-EventLogging.
Nemo_bis added a subscriber: Ottomata.
mforns added a subscriber: mforns.May 12 2015, 3:27 PM

A recent deployment to optimize mysql insertion is buffering events by schema until they reach a number of 100 before inserting to the db.

I can see that this schema has a low traffic, so it is possible that the event that you logged is still in the mysql-consumer buffer waiting to be inserted to the db.

We have a patch for EL in CR that reduces the time-to-insert for low traffic schemas down to 5 minutes. I guess this will be deployed in short. I'll let you know when this happens.

And also we are currently working on improving the whole architecture of EL to avoid scaling problems and other issues.

I looked into this this morning, this schema hasn't had 100 events since May 1st, that's the problem as Marcel guessed.

Milimetric moved this task from Next Up to In Progress on the Analytics-Kanban board.
ggellerman moved this task from In Progress to Paused on the Analytics-Kanban board.

Just FYI: we're trying to deploy the new patch that makes this problem better early next week.

Milimetric closed this task as Resolved.May 20 2015, 5:34 PM

The patch to improve batch inserts was deployed Monday, so this issue should be fixed. Events will still not be inserted right away because of the low throughput, but the *second* event since the last insert will be inserted in at worst 5 minutes. Please let us know if you have questions.