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

dump historical stats failed because of too large entry. #47649

Closed
hawkingrei opened this issue Oct 16, 2023 · 0 comments · Fixed by #47653
Closed

dump historical stats failed because of too large entry. #47649

hawkingrei opened this issue Oct 16, 2023 · 0 comments · Fixed by #47653
Labels
severity/moderate sig/planner SIG: Planner type/bug The issue is confirmed as a bug.

Comments

@hawkingrei
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

if you have a large cluster tidb with a huge number of partition table.

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

save historical stats successfully

3. What did you see instead (Required)

{"log":"[domain.go:2144] [\"dump historical stats failed\"] [error=\"record table db0ios.table28ios's historical stats failed, err:[kv:8025]entry too large, the max entry size is 6291456, the size of data is 6291516\"] [tableID=254127]","container":"tidb","pod":"tc-tidb-2","namespace":"partition-analyze-test-tps-2730857-1-178","level":"WARN"}


2023-10-15 16:02:36	
{"log":"[session.go:2283] [\"run statement failed\"] [schemaVersion=309] [error=\"[kv:8025]entry too large, the max entry size is 6291456, the size of data is 6291516\"] [session=\"{\\n  \\\"currDBName\\\": \\\"\\\",\\n  \\\"id\\\": 0,\\n  \\\"status\\\": 3,\\n  \\\"strictMode\\\": true,\\n  \\\"txn\\\": \\\"444951941130485765\\\",\\n  \\\"user\\\": null\\n}\"]","container":"tidb","pod":"tc-tidb-2","namespace":"partition-analyze-test-tps-2730857-1-178","level":"WARN"}

4. What is your TiDB version? (Required)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/moderate 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.

1 participant