carp84 commented on a change in pull request #14248:
URL: https://github.com/apache/flink/pull/14248#discussion_r532335274



##########
File path: docs/deployment/resource-providers/standalone/docker.zh.md
##########
@@ -268,6 +268,18 @@ The `ENABLE_BUILT_IN_PLUGINS` should contain a list of 
plugin jar file names sep
 
 There are also more [advanced ways](#advanced-customization) for customizing 
the Flink image.
 
+### Switch memory allocator
+
+Flink introduced `jemalloc` as default memory allocator to resolve memory 
fragmentation problem (please refer to 
[FLINK-19125](https://issues.apache.org/jira/browse/FLINK-19125)).
+User could still switch back to previous `glibc` as memory allocator if 
wanting to keep behavior as before or meeting some unexpected memory related 
problem.
+Please contact Flink community via user mail list if you found any regression 
under current `jemalloc` memory allocator.
+
+You could switch back to `glibc` as memory allocator by passing 
`disable-jemalloc` parameter:

Review comment:
       ```suggestion
   You could switch back to use `glibc` as memory allocator to restore the old 
behavior or if any unexpected memory consumption or problem observed (and 
please report the issue via JIRA or mailing list if you found any), by passing 
`disable-jemalloc` parameter:
   ```

##########
File path: docs/deployment/resource-providers/standalone/docker.md
##########
@@ -268,6 +268,18 @@ The `ENABLE_BUILT_IN_PLUGINS` should contain a list of 
plugin jar file names sep
 
 There are also more [advanced ways](#advanced-customization) for customizing 
the Flink image.
 
+### Switch memory allocator
+
+Flink introduced `jemalloc` as default memory allocator to resolve memory 
fragmentation problem (please refer to 
[FLINK-19125](https://issues.apache.org/jira/browse/FLINK-19125)).
+User could still switch back to previous `glibc` as memory allocator if 
wanting to keep behavior as before or meeting some unexpected memory related 
problem.
+Please contact Flink community via user mail list if you found any regression 
under current `jemalloc` memory allocator.
+
+You could switch back to `glibc` as memory allocator by passing 
`disable-jemalloc` parameter:

Review comment:
       ```suggestion
   You could switch back to use `glibc` as memory allocator to restore the old 
behavior or if any unexpected memory consumption or problem observed (and 
please report the issue via JIRA or mailing list if you found any), by passing 
`disable-jemalloc` parameter:
   ```




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to