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

[YCQL] Improve error code sent from the server to the driver #23355

Open
1 task done
dr0pdb opened this issue Aug 1, 2024 · 0 comments
Open
1 task done

[YCQL] Improve error code sent from the server to the driver #23355

dr0pdb opened this issue Aug 1, 2024 · 0 comments
Assignees
Labels
area/ycql Yugabyte CQL (YCQL) kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue

Comments

@dr0pdb
Copy link
Contributor

dr0pdb commented Aug 1, 2024

Jira Link: DB-12280

Description

Came up in a customer incident. Right now, the CQL server doesn't send the appropriate error codes to the driver in some scenarios.

For example, it never sends the READ_TIMEOUT and WRITE_TIMEOUT errors even in case of timeouts.

The list of errors that we send from the server:

  1. SERVER_ERROR: example, authentication failure
  2. PROTOCOL_ERROR: example, unsupported compression method
  3. BAD_CREDENTIALS: example, password mismatch or ldap failure
  4. OVERLOADED
    When we run out of cql processors
    Soft memory limit hit
    Shutdown
  5. SYNTAX_ERROR: wrong syntax (parser)
  6. UNAUTHORIZED
  7. INVALID: example, stale metadata cache
  8. UNPREPARED: couldn’t understand when we send it.

We never send the following error codes:

  1. UNAVAILABLE
  2. IS_BOOTSTRAPPING
  3. TRUNCATE_ERROR
  4. WRITE_TIMEOUT
  5. READ_TIMEOUT
  6. READ_FAILURE
  7. FUNCTION_FAILURE
  8. WRITE_FAILURE
  9. CONFIG_ERROR
  10. ALREADY_EXISTS

Investigate and see if there are scenarios where a different error code can be sent. It'll help the driver better guage the issue and retry if needed.

Issue Type

kind/enhancement

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.
@dr0pdb dr0pdb added area/ycql Yugabyte CQL (YCQL) status/awaiting-triage Issue awaiting triage labels Aug 1, 2024
@yugabyte-ci yugabyte-ci added kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue labels Aug 1, 2024
@yugabyte-ci yugabyte-ci removed the status/awaiting-triage Issue awaiting triage label Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ycql Yugabyte CQL (YCQL) kind/enhancement This is an enhancement of an existing feature priority/medium Medium priority issue
Projects
None yet
Development

No branches or pull requests

3 participants