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

Allowing all replicas to be lost is something that SQL can execute[Feature] #36304

Open
3 tasks done
fdf1779 opened this issue Jun 14, 2024 · 0 comments
Open
3 tasks done
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@fdf1779
Copy link

fdf1779 commented Jun 14, 2024

Search before asking

  • I had searched in the issues and found no similar issues.

Description

When all tables are lost in certain application scenarios, Doris's queries and load imports will report errors
Alive replica num 0<quorum replica num 1, alive backups: []
It is necessary to use recover_with_empty_tablet to wait for the missing tablet to be empty before execution, as this will affect the current query and import,
Is there a plan in the future to allow users to configure that tablet loss will not affect the current business and will issue a warning, and that the remaining tablets can be queried.

Use case

No response

Related issues

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@fdf1779 fdf1779 added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant