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

infoschema_v2: panic loadSchemaInLoop #52683

Closed
GMHDBJD opened this issue Apr 17, 2024 · 0 comments · Fixed by #52983
Closed

infoschema_v2: panic loadSchemaInLoop #52683

GMHDBJD opened this issue Apr 17, 2024 · 0 comments · Fixed by #52983
Assignees
Labels
component/ddl This issue is related to DDL of TiDB. feature/developing the related feature is in development severity/minor type/bug This issue is a bug.

Comments

@GMHDBJD
Copy link
Contributor

GMHDBJD commented Apr 17, 2024

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

start tidb with tidb_schema_cache_size=1024

2. What did you expect to see? (Required)

no panic

3. What did you see instead (Required)

<html>
<body>
<!--StartFragment-->
{"stream":"stdout","namespace":"testbed-tps-7567852-1-827","log":"[2024/04/17 12:17:32.377 +00:00] [ERROR] [misc.go:114] [\"panic in the recoverable goroutine\"] [label=domain] [funcInfo=loadSchemaInLoop] [r=\"[tikv:9006]GC life time is shorter than transaction duration, transaction starts at 2024-04-17 12:04:17.553 +0000 UTC, GC safe point is 2024-04-17 12:04:17.703 +0000 UTC\"] [stack=\"github.com/pingcap/tidb/pkg/util.Recover\\n\\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/util/misc.go:118\\nruntime.gopanic\\n\\t/usr/local/go/src/runtime/panic.go:914\\ngithub.com/pingcap/tidb/pkg/infoschema.(*infoschemaV2).SchemaTables\\n\\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/infoschema/infoschema_v2.go:540\\ngithub.com/pingcap/tidb/pkg/infoschema.(*bundleInfoBuilder).updateInfoSchemaBundlesV2\\n\\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/infoschema/infoschema_v2.go:839\\ngithub.com/pingcap/tidb/pkg/infoschema.updateInfoSchemaBundles\\n\\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/infoschema/infoschema_v2.go:682\\ngithub.com/pingcap/tidb/pkg/infoschema.(*Builder).Build\\n\\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/infoschema/builder.go:769\\ngithub.com/pingcap/tidb/pkg/domain.(*Domain).loadInfoSchema\\n\\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/domain/domain.go:320\\ngithub.com/pingcap/tidb/pkg/domain.(*Domain).Reload\\n\\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/domain/domain.go:606\\ngithub.com/pingcap/tidb/pkg/domain.(*Domain).loadSchemaInLoop\\n\\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/domain/domain.go:913\\ngithub.com/pingcap/tidb/pkg/domain.(*Domain).Init.func3\\n\\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/domain/domain.go:1286\\ngithub.com/pingcap/tidb/pkg/util.(*WaitGroupEnhancedWrapper).Run.func1\\n\\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/util/wait_group_wrapper.go:99\"]","pod":"infoschema-tidb-2","container":"fluentbit","date":1713356252.377057}
--


<!--EndFragment-->
</body>
</html>

4. What is your TiDB version? (Required)

nightly

@GMHDBJD GMHDBJD added type/bug This issue is a bug. severity/minor labels Apr 17, 2024
@seiya-annie seiya-annie added feature/developing the related feature is in development component/ddl This issue is related to DDL of TiDB. labels Apr 18, 2024
@tiancaiamao tiancaiamao self-assigned this Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/ddl This issue is related to DDL of TiDB. feature/developing the related feature is in development severity/minor type/bug This issue is a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants