GitHub user kunwp1 added a comment to the discussion: What should Texera do when a computing unit dies?
I think we need to limit our scope and focus on showing user-friendly message that your CU has an issue with a reason so that user can avoid the same issue. There can be many reasons why CU dies and from my experience of managing the dknet deployment, two of the main reasons: 1. The user running workflow causes CU to be OOM-killed. 2. The user stores a huge amount of data to CU's local file system and causes out-of-storage issue. So I suggest to focus on these two use cases. To answer your questions, 1. I prefer mirroring Kubernetes because it's simple. 2. Show actionable error message to increase the memory size or reduce storing data to the local file system. And limit the scope to the owner of the CU. 3. No need to automatically recover the CU but instead give users a chance to create with a different configuration. GitHub link: https://github.com/apache/texera/discussions/7670#discussioncomment-18022865 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
