CopyPastor

Detecting plagiarism made easy.

Score: 0.8516855746109314; Reported for: String similarity Open both answers

Possible Plagiarism

Plagiarized on 2022-02-01
by RithwikBojja-MT

Original Post

Original - Posted on 2021-09-08
by SaiKarri-MT



            
Present in both answers; Present only in the new answer; Present only in the old answer;





FunctionApp exits with error code as 137 which is caused by out-of-memory issues in your Python function app.
Have a look on the [service limits in Microsoft Documentation](https://docs.microsoft.com/en-us/azure/azure-functions/functions-scale#service-limits) based on the plans which you’ve chosen in your function app, I assume you’ve used Consumption plan.
Now to check whether it is timeout issue as it mentions 137 error code, keep an eye on Application Insights logs when your function app is executed.
In the errors if you find anything like “Timeout value of 00:05:00 exceeded by function”, then try to investigate about below points:
1. Check why the code execution is taking more time, if you found any such scenarios then we can fix it from code itself. 2. Increase the default timeout.
Below is how we can modify default timeout. By default, it will be as 5 minutes, we can increase it accordingly to check.
```python { "functionTimeout": "00:05:00" }
```
Check the [documentation](https://docs.microsoft.com/en-us/azure/azure-functions/functions-host-json#functiontimeout) for function timeout settings
functionTimeout indicated the timeout duration for all the functions and not for the single function.
You can update the default timeout value, save it, and test your function again.
Also refer to the documentation about [Memory profiling on Python function apps](https://docs.microsoft.com/en-us/azure/azure-functions/python-memory-profiler-reference#memory-profiling-process) to understand more about managing the memory in our functions.
FunctionApp exits with error code as 137 which is caused by out-of-memory issues in your Python function app.
Have a look on the [service limits in Microsoft Documentation][1] based on the plans which you’ve chosen in your function app, I assume you’ve used Consumption plan.
Now to check whether it is timeout issue as it mentions 137 error code, keep an eye on Application Insights logs when your function app is executed.
In the errors if you find anything like “Timeout value of 00:05:00 exceeded by function”, then try to investigate about below points:
1. Check why the code execution is taking more time, if you found any such scenarios then we can fix it from code itself.
2. Increase the default timeout.
Below is how we can modify default timeout. By default, it will be as 5 minutes, we can increase it accordingly to check.
{ "functionTimeout": "00:05:00" }
Check the [documentation][2] for function timeout settings
functionTimeout indicated the timeout duration for all the functions and not for the single function.
You can update the default timeout value, save it, and test your function again.
Also refer to the documentation about [Memory profiling on Python function apps][3] to understand more about managing the memory in our functions.

[1]: https://docs.microsoft.com/en-us/azure/azure-functions/functions-scale#service-limits [2]: https://docs.microsoft.com/en-us/azure/azure-functions/functions-host-json#functiontimeout [3]: https://docs.microsoft.com/en-us/azure/azure-functions/python-memory-profiler-reference#memory-profiling-process

        
Present in both answers; Present only in the new answer; Present only in the old answer;