问题
One of our API servers processes short Cell Phone Videos and the Background process can take up to a min.
I am aware of best practices regarding moving this to a WebJob and or using Hangfire.
For the hypothetical solution of performing this task on our API Server(It just waits for Azure Media Services by polling unfortunately, so not CPU bound).
What are the pitfalls of using a very long Shutdown Timeout as described in:
- Implement background tasks in microservices with IHostedService and the BackgroundService class
- Host configuration values - Shutdown Timeout
Looking for more than just opinion based answers such as "Its bad practice to do that in ASP.Net". This configuration exists for a reason and I would like to understand the actual drawbacks.
~Thx
来源：https://stackoverflow.com/questions/50371737/asp-net-core-2-0-shutdown-timeout-what-issues-can-i-expect-using-a-very-long-ti