[ensembl-dev] VEP API returning 400 for memory error

[Anja Thormann]

Dear Asier,

thank you for your feedback. Could you please let me know which VEP endpoint and settings you use? If you are using a POST endpoint, how many variant ids or regions are you sending? I assume that the problem happens at a point during the VEP calculation where it is difficult to differentiate the cause of the problem. But we will investigate further and hopefully be able to provide a more accurate error report.

Best wishes,
Anja

> On 21 Aug 2019, at 12:47, Asier Gonzalez <gonzaleza at ebi.ac.uk> wrote:
> 
> Hi,
> 
> I have an script that calls the VEP API for a few thousand variants and does some processing. The script captures HTTP errors and messages and I have found a few cases where the 400 error is accompanied by a  "ERROR: Cannot allocate memory" message. If I query the API again with the ids that produced that error I get a results so I understand that this is a temporary issue. I could handle the 400 errors further to control these cases but I wonder if it is an expected case or if it an issue as it sounds as this should be an 5XX error instead of a 400.
> 
> Kind regards,
> Asier
> 
> 
> _______________________________________________
> Dev mailing list    Dev at ensembl.org
> Posting guidelines and subscribe/unsubscribe info: https://lists.ensembl.org/mailman/listinfo/dev_ensembl.org
> Ensembl Blog: http://www.ensembl.info/