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

No enough data in blob file #5076

Closed
flowbehappy opened this issue Jun 6, 2022 · 0 comments · Fixed by #5127
Closed

No enough data in blob file #5076

flowbehappy opened this issue Jun 6, 2022 · 0 comments · Fixed by #5127
Assignees
Labels
affects-6.1 This bug affects the 6.1.x(LTS) versions. component/storage severity/critical type/bug The issue is confirmed as a bug.

Comments

@flowbehappy
Copy link
Contributor

flowbehappy commented Jun 6, 2022

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

ch-benchmark workload.

  1. Restore data with BR.
  2. Run some TP updates
  3. Do AP queries.

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

Queries run smoothly without errors.

3. What did you see instead (Required)

[2022-06-06 12:17:27] execute run failed, err execute query q1 failed Error 1105: other error for mpp stream: DB::Exception: Exchange receiver meet error : DB::Exception: No enough data in file /data0/db/page/log/blobfile_6, read bytes: 0 , expected bytes: 43
[Current] Q1_ERR - Count: 1, Sum(ms): 8853.7, Avg(ms): 8854.2

4. What is your TiFlash version? (Required)

6.1 nightly.

@flowbehappy flowbehappy added type/bug The issue is confirmed as a bug. severity/critical component/storage affects-6.1 This bug affects the 6.1.x(LTS) versions. labels Jun 6, 2022
ti-chi-bot pushed a commit that referenced this issue Jun 7, 2022
ti-chi-bot pushed a commit that referenced this issue Jun 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.1 This bug affects the 6.1.x(LTS) versions. component/storage severity/critical type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants