Closed natanlao closed 6 years ago
Upon inspection, it turns out the instance is still up - my new guess is that since the test instance is a t2.micro, we may just need to set a longer timeout...
Further testing implies that this conclusion is correct. It makes sense, because:
A good solution would be to increase the timeout, but only for the provisioning scripts - the default value is ten seconds, which should be long enough for any lambda query (but maybe not for uploading the test data on a t2.micro).
Requests to the ElasticSearch instance we use for testing are timing out - it appears that the instance is down.
┆Issue is synchronized with this JIRA Story ┆Project Name: dos-azul-lambda ┆Issue Number: DAL-74