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

[Bug]: mo was hung on eks with 3*cns during loading ssb data #9935

Closed
1 task done
aressu1985 opened this issue Jun 8, 2023 · 15 comments
Closed
1 task done

[Bug]: mo was hung on eks with 3*cns during loading ssb data #9935

aressu1985 opened this issue Jun 8, 2023 · 15 comments
Assignees
Labels
kind/bug Something isn't working needs-triage severity/s1 High impact: Logical errors or data errors that must occur
Milestone

Comments

@aressu1985
Copy link
Contributor

Is there an existing issue for the same bug?

  • I have checked the existing issues.

Environment

- Version or commit-id (e.g. v0.1.0 or 8b23a93): 3cdceab
- Hardware parameters:
  3*CN: 16C 64G
  1*DN: 16C 64G
  3*LOG: 4C 8G
- OS type:
- Others:
  CN DISK CACHE: 100G
  CN MEM  CACHE: 16G

Actual Behavior

image

log:
hung-cn0.log
hung-cn1.log
hung-cn2.log
hung-dn0.log

Expected Behavior

No response

Steps to Reproduce

1、run a mo cluster on eks with 3*cn
2、load ssb data

Additional information

No response

@aressu1985 aressu1985 added this to the V0.8.0 milestone Jun 8, 2023
@matrixorigin matrixorigin deleted a comment from guguducken Jun 9, 2023
@sukki37
Copy link
Contributor

sukki37 commented Jun 9, 2023

part of this issue is related to #9914

@matrixorigin matrixorigin deleted a comment from guguducken Jun 13, 2023
@jianwan0214
Copy link
Contributor

should fix with #10001, I' ll check it.

@jianwan0214
Copy link
Contributor

可以进行验证了 @aressu1985

@aressu1985
Copy link
Contributor Author

fixed:nightly-d4d74e7

@aressu1985
Copy link
Contributor Author

@jianwan0214
Copy link
Contributor

还没看

@fengttt fengttt assigned ouyuanning and unassigned jianwan0214 Jul 23, 2023
@ouyuanning
Copy link
Contributor

not working on this today

@ouyuanning
Copy link
Contributor

not working on it

4 similar comments
@ouyuanning
Copy link
Contributor

not working on it

@ouyuanning
Copy link
Contributor

not working on it

@ouyuanning
Copy link
Contributor

not working on it

@ouyuanning
Copy link
Contributor

not working on it

@ouyuanning
Copy link
Contributor

waiting for repro in daily run.

@aressu1985 aressu1985 added severity/s1 High impact: Logical errors or data errors that must occur and removed severity/s-1 labels Jul 31, 2023
@aressu1985
Copy link
Contributor Author

downgrade to s-1

@sukki37
Copy link
Contributor

sukki37 commented Aug 29, 2023

This issue has been inactive for a while. To help keep our backlog clear, I'm going to close this. If you feel this is still relevant, please comment or reopen.

@sukki37 sukki37 closed this as completed Aug 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working needs-triage severity/s1 High impact: Logical errors or data errors that must occur
Projects
None yet
Development

No branches or pull requests

5 participants