-
Notifications
You must be signed in to change notification settings - Fork 6k
Closed
Labels
affects-7.6severity/majorsig/diagnosisSIG: DiagnosisSIG: Diagnosissig/sql-infraSIG: SQL InfraSIG: SQL Infratype/bugThe issue is confirmed as a bug.The issue is confirmed as a bug.
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
- deploy v6.5.0 cluster with config:
server_configs:
tidb:
enable-telemetry: true
new_collations_enabled_on_first_bootstrap: false
performance.gogc: 200
- upgrade to nightly
2. What did you expect to see? (Required)
upgrade successfully
3. What did you see instead (Required)
panic: runtime error: index out of range [0] with length 0
goroutine 7710 [running]:
github.com/pingcap/tidb/pkg/util/chunk.(*Column).GetString(...)
/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/util/chunk/column.go:588
github.com/pingcap/tidb/pkg/util/chunk.Row.GetString({0xc004237130?, 0xf?}, 0x0?)
/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/util/chunk/row.go:76 +0xcd
github.com/pingcap/tidb/pkg/telemetry.getClusterInfo({0x6416a28, 0xc003ea1a10}, {0x648dd40?, 0xc004e6cf00})
/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/telemetry/data_cluster_info.go:65 +0x285
github.com/pingcap/tidb/pkg/telemetry.generateTelemetryData({0x648dd40, 0xc004e6cf00}, {0xc003401d10, 0x24})
/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/telemetry/data.go:45 +0x186
github.com/pingcap/tidb/pkg/telemetry.reportUsageData({0x648dd40, 0xc004e6cf00}, 0xc004faafc0)
/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/telemetry/telemetry.go:116 +0xd6
github.com/pingcap/tidb/pkg/telemetry.ReportUsageData({0x648dd40, 0xc004e6cf00}, 0xc004faafc0)
/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/telemetry/telemetry.go:159 +0x8c
github.com/pingcap/tidb/pkg/telemetry.InitialRun({0x648dd40, 0xc004e6cf00}, 0xc002afef70?)
/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/telemetry/telemetry.go:177 +0x2e8
github.com/pingcap/tidb/pkg/domain.(*Domain).TelemetryReportLoop(0xc0027d2600, {0x648dd40?, 0xc004e6cf00?})
/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/domain/domain.go:1919 +0x70
github.com/pingcap/tidb/pkg/session.bootstrapSessionImpl.func1()
/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/session/session.go:3384 +0x3a
created by github.com/pingcap/tidb/pkg/session.bootstrapSessionImpl in goroutine 1
/home/jenkins/agent/workspace/build-common/go/src/github.com/pingcap/tidb/pkg/session/session.go:3383 +0xa27
panic: runtime error: index out of range [0] with length 0
4. What is your TiDB version? (Required)
master
Metadata
Metadata
Assignees
Labels
affects-7.6severity/majorsig/diagnosisSIG: DiagnosisSIG: Diagnosissig/sql-infraSIG: SQL InfraSIG: SQL Infratype/bugThe issue is confirmed as a bug.The issue is confirmed as a bug.