[SOLVED] Java Azure Function App Blob Trigger – Memory Not Released After Invocation

Java Azure Function App Blob Trigger – Memory Not Released After Invocation

I am running a Java Azure Function App with a Blob Trigger on an App Service Plan. However, I have noticed that after each function invocation and successful completion, the memory usage remains high and does not decrease. This behavior persists even when the function becomes idle.

Are there specific JVM configurations or Azure Function settings to enforce better memory cleanup?

Solution

Turn off Always on under FunctionApp=>Settings=>Configuration=>General Settings and check if the memory usage is still high:

enter image description here

Check the memory usage of the function under Function App=>Diagnose and solve problems=>Memory Analysis:

enter image description here

Try setting -io.netty.noPreferDirect: false and io.netty.maxDirectMemory: -1, refer GitHub issue.

I have created a Java Blob Triggered Azure function App with App Service Plan and observed the memory usage.

Uploaded two files to the Storage Container and the metrics of function App is below: Metrics:

enter image description here And the function App started to utilize the memory after restarting it.

enter image description here