You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2021/06/01 03:35:55 UTC

[GitHub] [flink] xintongsong commented on a change in pull request #16016: [FLINK-22796] Update mem_setup_tm documentation

xintongsong commented on a change in pull request #16016:
URL: https://github.com/apache/flink/pull/16016#discussion_r642757794



##########
File path: docs/content/docs/deployment/memory/mem_setup_tm.md
##########
@@ -98,13 +98,14 @@ See also [how to configure memory for state backends]({{< ref "docs/deployment/m
 If your job contains multiple types of managed memory consumers, you can also control how managed memory should be shared across these types.
 The configuration option [`taskmanager.memory.managed.consumer-weights`]({{< ref "docs/deployment/config" >}}#taskmanager-memory-managed-consumer-weights) allows you to set a weight for each type, to which Flink will reserve managed memory proportionally.
 Valid consumer types are:
-* `DATAPROC`: for RocksDB state backend in streaming and built-in algorithms in batch.
+* `OPERATOR`: for built-in algorithms in streaming or batch.

Review comment:
       Similar to `PYTHON`, we can omit "in streaming or batch"
   ```suggestion
   * `OPERATOR`: for built-in algorithms.
   ```

##########
File path: docs/content/docs/deployment/memory/mem_setup_tm.md
##########
@@ -98,13 +98,14 @@ See also [how to configure memory for state backends]({{< ref "docs/deployment/m
 If your job contains multiple types of managed memory consumers, you can also control how managed memory should be shared across these types.
 The configuration option [`taskmanager.memory.managed.consumer-weights`]({{< ref "docs/deployment/config" >}}#taskmanager-memory-managed-consumer-weights) allows you to set a weight for each type, to which Flink will reserve managed memory proportionally.
 Valid consumer types are:
-* `DATAPROC`: for RocksDB state backend in streaming and built-in algorithms in batch.
+* `OPERATOR`: for built-in algorithms in streaming or batch.

Review comment:
       > Batch jobs can use it for sorting, hash tables, caching of intermediate results.
   
   I think we should also update for this sentence, since now it applies to both streaming and batch.
   
   (Github does not allow me to comment on lines that are not changed by this PR. :( )




-- 
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:
users@infra.apache.org