[jira] [Commented] (CASSANDRA-15351) Allow configuring timeouts on the per-request basis
[ https://issues.apache.org/jira/browse/CASSANDRA-15351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16973136#comment-16973136 ] Alex Petrov commented on CASSANDRA-15351: - I would say that the propagation mechanism is the same, and only capping mechanism is different. In case proposed in this ticket, we allow potentially longer requests to run and respect client timeout no matter what, and in 2848 we respect server-side timeout if it's lower than the one requested by client. I agree here that it's better to leave some control to Cassandra, let it time-out requests, and use its configuration as a worst-case scenario / cap. There's a stronger point by about not exposing this until we properly fix timeouts for SRP, digests, etc, but this seems to be fixed in [CASSANDRA-12256]. Probably too specific to the code produced for 2848, but there are some good points in the review of the patch as well, which should probably be taken into consideration. That said, I suggest we close this ticket as a dupe and continue discussion on the original ticket. > Allow configuring timeouts on the per-request basis > --- > > Key: CASSANDRA-15351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15351 > Project: Cassandra > Issue Type: New Feature > Components: Messaging/Client >Reporter: Alex Petrov >Assignee: Yifan Cai >Priority: Normal > > Some queries need to be ran with a higher timeout value, which should be > possible without allowing _all_ requests to be above this value. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15351) Allow configuring timeouts on the per-request basis
[ https://issues.apache.org/jira/browse/CASSANDRA-15351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16972866#comment-16972866 ] Yifan Cai commented on CASSANDRA-15351: --- A requirement difference between this ticket and CASSANDRA-2848 One of the conclusion from the discussion in CASSANDRA-2848 is that the client specified timeout values have the upper bound set in DatabaseDescriptor. This ticket wants to increase the timeout for some queries to be higher than the one set in DatabaseDescriptor. > Allow configuring timeouts on the per-request basis > --- > > Key: CASSANDRA-15351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15351 > Project: Cassandra > Issue Type: New Feature > Components: Messaging/Client >Reporter: Alex Petrov >Assignee: Yifan Cai >Priority: Normal > > Some queries need to be ran with a higher timeout value, which should be > possible without allowing _all_ requests to be above this value. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Commented] (CASSANDRA-15351) Allow configuring timeouts on the per-request basis
[ https://issues.apache.org/jira/browse/CASSANDRA-15351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16948838#comment-16948838 ] Sankalp Kohli commented on CASSANDRA-15351: --- Dupe of https://issues.apache.org/jira/browse/CASSANDRA-2848 ?? > Allow configuring timeouts on the per-request basis > --- > > Key: CASSANDRA-15351 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15351 > Project: Cassandra > Issue Type: New Feature > Components: Messaging/Client >Reporter: Alex Petrov >Priority: Normal > > Some queries need to be ran with a higher timeout value, which should be > possible without allowing _all_ requests to be above this value. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
