Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decouple schema fetch queries from server-side timeouts #1052

Open
dkropachev opened this issue Aug 4, 2024 · 0 comments
Open

Decouple schema fetch queries from server-side timeouts #1052

dkropachev opened this issue Aug 4, 2024 · 0 comments
Assignees
Milestone

Comments

@dkropachev
Copy link
Collaborator

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

  1. 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.
  2. Minimal supported scale is ms, so statement suffix should look like this: USING TIMEOUT {timeout_in_ms} ms

Requirements

  1. Timeout should be configurable and default should be 2s
  2. 0 signals that feature is disabled
@wprzytula 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
@wprzytula wprzytula added this to the 0.16.0 milestone Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants