[ensembl-dev] Error 503 GRCh37

[Johann Lieberwirth]

Hi Dan and Kirill,

thank you for your kind responses and the hint with the retry loop. I will try to implement this in my future requests.

Best wishes,
Johann

> Am 06.10.2020 um 15:52 schrieb Kirill Tsukanov <ktsukanov at ebi.ac.uk>:
> 
> Hi Johann,
> 
> To add to what Dan said, here's an example of the implementation of the backoff-then-retry loop which he mentioned in our Python package: [1]. Perhaps this could be useful.
> 
> [1] https://github.com/EBIvariation/eva-opentargets/blob/7bca316956066f8a79b6c7e931c62efec91be2d2/vep-mapping-pipeline/vep_mapping_pipeline/consequence_mapping.py#L54 <https://github.com/EBIvariation/eva-opentargets/blob/7bca316956066f8a79b6c7e931c62efec91be2d2/vep-mapping-pipeline/vep_mapping_pipeline/consequence_mapping.py#L54>
> Best wishes, Kirill
> Kirill Tsukanov | Senior Bioinformatician
> European Variation Archive, EMBL-EBI
> 
> On 05/10/2020 18:56, Dan Sheppard wrote:
>> Hi Johann,
>> 
>> Thanks for your message. We've noticed a higher than normal error rate
>> both on GRCh37 REST, and also on certain main REST endpoints; it has
>> set off a number of monitoring alarms. We have been looking into the
>> errors and these seem to be caused by recent increases in data volume,
>> meaning that we need to re-tweak some resource settings to maintain
>> adequate throughput. We should have this completed within the next few days,
>> and hopefully error rates will reduce.
>> 
>> There is no reason to believe that your script is misusing the service
>> on the basis of this outcome, but thank you for your concern. It's always
>> a good idea to wrap calls in some kind of backoff-then-retry loop but I
>> understand how frustrating it can be if things seem to constantly stall.
>> 
>> I will keep you posted.
>> 
>> Dan.
>> 
>> On Mon, Oct 05, 2020 at 03:03:50PM +0200, Johann Lieberwirth wrote:
>>> Dear Ensembl Developers,
>>>  
>>> I’m using VEP REST services for annotations with the python package requests and am receiving a lot of ERROR 503 for about one week now. They occur only for GRCh37 as far as I noticed. If I refresh the request for a couple of times without changing any parameters, at some point I get the expected results. This is a little unreliable. Is this a misuse of the service from my side or is there some problem on yours?
>>>  
>>> Best,
>>> Johann
>>> _______________________________________________
>>> Dev mailing list    Dev at ensembl.org <mailto:Dev at ensembl.org>
>>> Posting guidelines and subscribe/unsubscribe info: https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org <https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org>
>>> Ensembl Blog: http://www.ensembl.info/ <http://www.ensembl.info/>
>> _______________________________________________
>> Dev mailing list    Dev at ensembl.org <mailto:Dev at ensembl.org>
>> Posting guidelines and subscribe/unsubscribe info: https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org <https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org>
>> Ensembl Blog: http://www.ensembl.info/ <http://www.ensembl.info/>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20201006/f2f3eb84/attachment.html>