[
https://issues.apache.org/jira/browse/FLINK-24332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17426497#comment-17426497
]
Yang Wang commented on FLINK-24332:
-----------------------------------
Yes, each {{TaskManager}} pod should get a new PVC.
It is not a problem that new launched TaskManager will receive the same PVC as
the previous one in StatefulSet. The problem is using naked pod has more
advantages than StatefulSet for TaskManager.
* Flink could delete specific naked TaskManager pod easily. And it is more
difficult to do this in StatefulSet.
* I am not sure whether Flink could work normally when we allow the
TaskManager pod could be restarted. For example, same hostname with different
IP, or TM register more than once to RM/JM.
* For fine-grained resource management, we might have various TaskManager pods
with different spec(2G, 4G, etc.).
> Support to mount a dynamically-created persistent volume claim per TaskManager
> ------------------------------------------------------------------------------
>
> Key: FLINK-24332
> URL: https://issues.apache.org/jira/browse/FLINK-24332
> Project: Flink
> Issue Type: New Feature
> Components: Deployment / Kubernetes
> Reporter: Yang Wang
> Priority: Major
>
> Pod template could be used to mount a same PVC for all the TaskManagers.
> However, in many cases, users need to mount dynamically-created persistent
> volume claim for each TaskManager.
>
> Refer to
> [https://lists.apache.org/thread.html/r08ed40ee541c69a74c6d48cc315671198a1910dbd34fd731fe77da37%40%3Cuser.flink.apache.org%3E]
> for more information.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
