You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2022/01/07 22:39:00 UTC

[jira] [Updated] (FLINK-5263) Add docs about JVM sharing between tasks

     [ https://issues.apache.org/jira/browse/FLINK-5263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-5263:
----------------------------------
      Labels: auto-deprioritized-major auto-deprioritized-minor  (was: auto-deprioritized-major stale-minor)
    Priority: Not a Priority  (was: Minor)

This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion.


> Add docs about JVM sharing between tasks
> ----------------------------------------
>
>                 Key: FLINK-5263
>                 URL: https://issues.apache.org/jira/browse/FLINK-5263
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation
>            Reporter: Ufuk Celebi
>            Priority: Not a Priority
>              Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> I've seen the question about why/how JVMs are shared between tasks and jobs pop up on the mailing lists multiple times now. It makes sense to write down which config options affect this, how to effectively configure one JVM per task and job, and other related issues like PROs and CONs of Flink's approach to things.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)