Page MenuHomePhabricator

Investigate "no content returned" errors
Closed, ResolvedPublic

Description

There's a non-zero amount of No Content Returned message in RESTBase logs. Seem to be mostly for update requests, but without a clear pattern regarding individual requests - page size/complexity or content type doesn't seem to matter.

Event Timeline

Pchelolo moved this task from doing to next on the Services board.
Pchelolo edited projects, added Services (next); removed Services (doing).

I my experience, this is typically Parsoid not returning anything. This could potentially be how a recently-deceased Parsoid worker looks to us.

GWicke renamed this task from No content returned errors to Investigate "no content returned" errors.Jul 12 2017, 10:07 PM
GWicke added subscribers: ssastry, Arlolra.

Looking through the pages triggering these errors, they mostly seem to be huge and complex. An example showing up multiple times is https://commons.wikimedia.org/api/rest_v1/page/html/Emoji.

I am inclined to attribute this to Parsoid workers being killed after failing the watchdog checks. @Arlolra @ssastry @Pchelolo, any objections to doing so?

I am inclined to attribute this to Parsoid workers being killed after failing the watchdog checks. @Arlolra @ssastry @Pchelolo, any objections to doing so?

+1. Just encountered this error in the logs for https://www.wikidata.org/wiki/User:Pasleim/Items_for_deletion/Page_deleted so I'm inclined to draw the same conclusion.

Wasn't really happening a lot lately.