Skip to content
This repository has been archived by the owner on Feb 6, 2024. It is now read-only.

Cluster not found when CeresMeta runs online for a long time. #216

Open
ZuLiangWang opened this issue Jul 13, 2023 · 0 comments
Open

Cluster not found when CeresMeta runs online for a long time. #216

ZuLiangWang opened this issue Jul 13, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@ZuLiangWang
Copy link
Contributor

Describe this problem
When the CeresMeta cluster runs online for a long time, the DefaultCluster cannot be loaded normally, resulting in a ClusterNotFound error.

Steps to reproduce
Not sure, maybe a restart of the CeresMeta node.

Expected behavior

2023-07-13 14:07:02.662 ERRO [common_util/src/panic.rs:42] thread 'main' panicked 'Fail to create default schema: CreateSchemaWithCause { catalog: "[cere](https://github.com/CeresDB/ceresmeta/issues/new?assignees=&labels=bug&projects=&template=bug_report.md#)[sdb](https://github.com/CeresDB/ceresmeta/issues/new?assignees=&labels=bug&projects=&template=bug_report.md#)", schema: "public", source: BadResponse { code: 404, msg: "grpc alloc schema idget cluster: (#404)cluster not found, cause:cluster name:defaultCluster

Additional Information

@ZuLiangWang ZuLiangWang added the bug Something isn't working label Jul 13, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant