[
https://issues.apache.org/jira/browse/CASSANDRA-15351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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: [email protected]
For additional commands, e-mail: [email protected]
