[
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 stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: auto-deprioritized-major, stale-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)
