1358035421 commented on PR #7158: URL: https://github.com/apache/kyuubi/pull/7158#issuecomment-3125194227
> From the perspective of kyuubi admin, I don't want to allow users to set the session idle timeout, because they might set a too large timeout and affect the stability of the service. Hi,turboFei 1.In spark, The kyuubi.session.idle.timeout in sessionManager's conf is actually set by the first user who creates the Spark driver pod via the first connection, so it is already user-defined and not strictly controlled by the admin only. (This is to address your concern that users shouldn't be able to set it — in reality, they already can.) 2.If the first connecting user sets a very large timeout, currently there is no restriction on this value. This means a user can already set an excessive value, which can potentially affect system stability. 3.I agree with your concern about stability, but I don't think this should be enforced by limiting the kyuubi.session.idle.timeout config itself. If more control is needed to avoid excessively large values, we can add additional logic to validate or restrict the timeout value when it is set, instead of changing the current config's behavior. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
