Skip to content
This repository was archived by the owner on Feb 6, 2024. It is now read-only.
This repository was 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

@ZuLiangWang

Description

@ZuLiangWang

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions