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 2022/08/31 07:36:59 UTC

[GitHub] [flink-kubernetes-operator] morhidi commented on pull request #357: [FLINK-29110] Use StatefulSet instead of Deployment to deploy JM and …

morhidi commented on PR #357:
URL: https://github.com/apache/flink-kubernetes-operator/pull/357#issuecomment-1232574252

   Hi Folks,
   
   It would be really great to see what `faster` recovery means here, through an example. In general this sounds a fair benefit but before choosing a more complicated path here it would be great to see some obvious gains.
   
   Would this solution benefit reactive scaling for example? Would this mean that in case of a TM failure it could recover before the job is being restarted with a lower parallelism? 
   
   @Grypse do you have any comparison that would help us decide to embrace this feature?
   
   Thanks,
   Matyas


-- 
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-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org