Page MenuHomePhabricator

Database locked error while publishing article using CX
Closed, DuplicatePublic

Description

While analysing CX article creation logs, following error was noted

'2', 'en', 'es', 'Pitchi.com', '{\"servedby\":\"mw####\",\"error\":{\"code\":\"readonly\",\"info\":\"The wiki is currently in read-only mode\",\"readonlyreason\":\"The database has been automatically locked while the slave database servers ', '20150809221918', 'Mirek Alcest'

But I see that https://es.wikipedia.org/wiki/Pitchi.com was indeed created. Source language was en, target language is es. But the contenttranslation tag was not added to the article.

@aaron, any clue on how this can happen? or how to prevent it.

I saw only one instance of this error so far .

Related Objects

View Standalone Graph
This task is connected to more than 200 other tasks. Only direct parents and subtasks are shown here. Use View Standalone Graph to show more of the graph.

Event Timeline

santhosh raised the priority of this task from to Medium.
santhosh updated the task description. (Show Details)
santhosh added subscribers: santhosh, Aklapper, aaron.

Further analysis showed that from August 6th onwards(last deployment date), contenttranslation tags were not added to several articles published. For all such articles, while publishing, following error is reported

{"xhr":{"readyState":4,"responseText":"","status":200,"statusText":"OK"},"textStatus":"parsererror","exception":{}}

AFAIK, this indicate the api returned something that the jquery ajax could not parse. All of such articles was published, just that the tag is missing.

Amire80 subscribed.

I saw only one instance of this error so far .

The title sounds scary, but it was indeed only once, then it's Normal prio. Should be raised if it happens more frequently.

Has this happened again? If it only happened once, I'm inclined to closing it or making the priority lowest.

Any slave lag spikes will cause this. Avoiding those is T95501.