GitHub user yrenat edited a comment on the discussion: Proposal: Automatically terminate idle Kubernetes Computing Units
Hi all, after investigating current solutions and several discussions with @chenlica, we concluded that our current CU implementation with Kubernetes is a reasonable/common approach. Kubernetes itself also does not seem to provide a convenient built-in way to handle the garbage collection we need. @chenlica agrees with my current garbage-collection implementation, but pointed out one issue: users cannot decide how long a CU can stay idle before being removed. Right now, this timeout is fixed by developers and is the same for all CUs/users. We agreed that users should be able to set this value themselves. However, this may require passing the user input from the frontend to the backend and using it dynamically for each CU, which I assume is not very straightforward. I would like to hear from anyone who has worked on similar frontend-to-backend parameter passing in this module, or knows something that I can refer to. Thanks GitHub link: https://github.com/apache/texera/discussions/6264#discussioncomment-17988660 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
