You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the user set server-side timeouts, or service level timeouts, this impacts schema fetches. The timeout can be too low to allow a schema fetch when the schema is very large.
Instead, qualify schema (and other metadata) fetches with USING TIMEOUT (with a high and configurable default) so schema fetches work regardless of timeout tuning.
USING TIMEOUT is not supported by cassandra and support by all major scylla versions, so it is safe to assume it is supported by seeing scylla-specific metadata.
Minimal supported scale is ms, so statement suffix should look like this: USING TIMEOUT {timeout_in_ms} ms
Requirements
Timeout should be configurable and default should be 2s
0 signals that feature is disabled
The text was updated successfully, but these errors were encountered:
wprzytula
changed the title
Rust implementation of "Decouple schema fetch queries from server-side timeouts"
Decouple schema fetch queries from server-side timeouts
Aug 6, 2024
Details
If the user set server-side timeouts, or service level timeouts, this impacts schema fetches. The timeout can be too low to allow a schema fetch when the schema is very large.
Instead, qualify schema (and other metadata) fetches with USING TIMEOUT (with a high and configurable default) so schema fetches work regardless of timeout tuning.
Core issue: scylladb/scylladb#18471
Limitations
USING TIMEOUT
is not supported bycassandra
and support by all majorscylla
versions, so it is safe to assume it is supported by seeing scylla-specific metadata.ms
, so statement suffix should look like this:USING TIMEOUT {timeout_in_ms} ms
Requirements
2s
0
signals that feature is disabledThe text was updated successfully, but these errors were encountered: