wdqs200 failed to update when encountering invalid JSON response from Blazegraph: https://logstash.wikimedia.org/goto/6bf10387447fed74b0b86093196d21c8 and did not recover. This is related to T192768 but different.
Here the solution is not clear. If Blazegraph is having problems, Updater can't do much about it. Retrying in this case probably won't help much as if Blazegraph is stuck on some OOM problem, it will remain stuck at least short term (within our retry horizon). I could see whether we can make bad JSON follow the same path as connection error, etc. but ultimately if Blazegraph does not recover very quickly, there's nothing Updater can do...