gyfora commented on PR #357:
URL:
https://github.com/apache/flink-kubernetes-operator/pull/357#issuecomment-1232646931
@Grypse this seems like a fairly large architecture decision that we
underestimated at first. We would like to kindly ask you to prepare your
proposal in a FLIP format and post it on the DEV mailing list.
Please describe the following points in the FLIP:
- What is the benefit of using StatefulSet for TaskManagers?
- Does this only affect local recovery? What is the performance gain
compared to Deployments?
- What benefit do we have compared to the PVC available in the
podTemplate? Seems like ReadWriteMany PVCs already provide the same benefits
for Deployments
- What is the implication of TaskManager startup time? Deployments start
pods faster as they dont need to wait for termination
- Should we make Deployment / StatefulSet configurable?
- What is the benefit of using StatefulSet for JobManagers?
- What data would the jobmanager store in PVC? What is the performance
gain?
- Does this only affect state handles? That is very small data.
- Why can't we do this already with the podTemplate?
--
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.
To unsubscribe, e-mail: issues-unsubscr...@flink.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
