[mgbl] support for http timeout?

[ARolek]

We're dealing with a situation where a tile provider is taking very long to respond (10s of minutes) and not closing the connection, so atlante is hanging and never really failing. The queue is then killing the job after 30 minutes and no fail is reported from the worker. A couple ideas:

1. Can a http timeout be configured for tile requests?
2. If an atlante worker is killed can it fire a fail event to the coordinator before it shuts down so the error is reported?

[gdey]

Do you know what type of kill is happening? Is it a hard kill (I assume it is) or a soft one? If it's a soft kill I can catch it and try sending the message. But if it's a hard kill then no. It, also, be it does both in which case sometimes we would be. I think it makes send to do this regardless.

[ARolek]

@gdey looks like it does both: https://docs.aws.amazon.com/batch/latest/userguide/job_timeouts.html

You specify an attemptDurationSeconds parameter, which must be at least 60 seconds, either in your job definition, or when you submit the job. When this number of seconds has passed following the job attempt's startedAt timestamp, AWS Batch terminates the job. On the compute resource, your job's container receives a SIGTERM signal to give your application a chance to shut down gracefully. If the container is still running after 30 seconds, a SIGKILL signal is sent to forcefully shut down the container.