Re: [PR] Bound async file-cleanup deletions with a configurable timeout [polaris]

["ayushtkn (via GitHub)" <gi...@apache.org>]

ayushtkn commented on PR #5398:
URL: https://github.com/apache/polaris/pull/5398#issuecomment-5489909917

   > If that makes sense, I'll wire it up; it touches the retry path in TaskExecutorImpl, so I didn't change it yet.
   
   That makes sense to me. If a task has already hit the default 1h timeout, retrying immediately in-process seems unlikely to succeed — we'd mostly be tying up more executor threads and multiplying in-flight deletes against the same stalled endpoint. I'd lean toward making timeout terminal for the current cycle and leaving the task entity in place (same end state as today after retries exhaust, just without the pile-up).
   
   That is my take on this, maybe we should wait for further feedback from other folks before to see if others think differently.


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

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