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

HandleAutoAnalyze panic if the table is dropped #42007

Closed
xiongjiwei opened this issue Mar 8, 2023 · 0 comments · Fixed by #42462
Closed

HandleAutoAnalyze panic if the table is dropped #42007

xiongjiwei opened this issue Mar 8, 2023 · 0 comments · Fixed by #42462
Assignees
Labels
affects-6.4 affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-6.6 affects-7.0 component/statistics severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@xiongjiwei
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

[2023/03/08 03:18:44.023 +00:00] [ERROR] [update.go:1090] ["HandleAutoAnalyze panicked"] [error="runtime error: invalid memory address or nil pointer dereference"] [stack="github.com/pingcap/tidb/statistics/handle.(*Handle).HandleAutoAnalyze.func1\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/statistics/handle/update.go:1090\nruntime.gopanic\n\t/usr/local/go/src/runtime/panic.go:884\ngit.luolix.top/pingcap/tidb/executor.(*ExecStmt).Exec.func1\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/executor/adapter.go:458\nruntime.gopanic\n\t/usr/local/go/src/runtime/panic.go:884\nruntime.panicmem\n\t/usr/local/go/src/runtime/panic.go:260\nruntime.sigpanic\n\t/usr/local/go/src/runtime/signal_unix.go:837\ngit.luolix.top/pingcap/tidb/executor.(*AnalyzeExec).newAnalyzeHandleGlobalStatsJob\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/executor/analyze_global_stats.go:125\ngit.luolix.top/pingcap/tidb/executor.(*AnalyzeExec).handleGlobalStats\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/executor/analyze_global_stats.go:65\ngit.luolix.top/pingcap/tidb/executor.(*AnalyzeExec).Next\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/executor/analyze.go:200\ngit.luolix.top/pingcap/tidb/executor.Next\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/executor/executor.go:324\ngit.luolix.top/pingcap/tidb/executor.(*ExecStmt).next\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/executor/adapter.go:1211\ngit.luolix.top/pingcap/tidb/executor.(*ExecStmt).handleNoDelayExecutor\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/executor/adapter.go:956\ngit.luolix.top/pingcap/tidb/executor.(*ExecStmt).handleNoDelay\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/executor/adapter.go:781\ngit.luolix.top/pingcap/tidb/executor.(*ExecStmt).Exec\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/executor/adapter.go:576\ngit.luolix.top/pingcap/tidb/session.runStmt\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:2338\ngit.luolix.top/pingcap/tidb/session.(*session).ExecuteStmt\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:2195\ngit.luolix.top/pingcap/tidb/session.(*session).ExecuteInternalStmt\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:2088\ngit.luolix.top/pingcap/tidb/session.(*session).ExecRestrictedSQL.func1\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:2052\ngit.luolix.top/pingcap/tidb/session.(*session).withRestrictedSQLExecutor\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:2038\ngit.luolix.top/pingcap/tidb/session.(*session).ExecRestrictedSQL\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/session/session.go:2042\ngit.luolix.top/pingcap/tidb/statistics/handle.(*Handle).execRestrictedSQLWithStatsVer.func1\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/statistics/handle/handle.go:427\ngit.luolix.top/pingcap/tidb/statistics/handle.(*Handle).withRestrictedSQLExecutor\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/statistics/handle/handle.go:407\ngit.luolix.top/pingcap/tidb/statistics/handle.(*Handle).execRestrictedSQLWithStatsVer\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/statistics/handle/handle.go:419\ngit.luolix.top/pingcap/tidb/statistics/handle.(*Handle).execAutoAnalyze\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/statistics/handle/update.go:1299\ngit.luolix.top/pingcap/tidb/statistics/handle.(*Handle).autoAnalyzePartitionTableInDynamicMode\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/statistics/handle/update.go:1282\ngit.luolix.top/pingcap/tidb/statistics/handle.(*Handle).HandleAutoAnalyze\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/statistics/handle/update.go:1153\ngit.luolix.top/pingcap/tidb/domain.(*Domain).autoAnalyzeWorker\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/domain/domain.go:2226\ngit.luolix.top/pingcap/tidb/domain.(*Domain).UpdateTableStatsLoop.func3\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/domain/domain.go:2010\ngit.luolix.top/pingcap/tidb/util.(*WaitGroupEnhancedWrapper).Run.func1\n\t/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/util/wait_group_wrapper.go:96"]

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

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

@xiongjiwei xiongjiwei added the type/bug The issue is confirmed as a bug. label Mar 8, 2023
@ti-chi-bot ti-chi-bot added may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 labels Mar 9, 2023
@xuyifangreeneyes xuyifangreeneyes removed may-affects-4.0 This bug maybe affects 4.0.x versions. may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-5.0 This bug maybe affects 5.0.x versions. may-affects-6.1 may-affects-6.5 affects-7.0 labels Mar 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.4 affects-6.5 This bug affects the 6.5.x(LTS) versions. affects-6.6 affects-7.0 component/statistics severity/major sig/planner SIG: Planner type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants