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

doris be restarted #48509

Open
772566741qqcom opened this issue Mar 1, 2025 · 0 comments
Open

doris be restarted #48509

772566741qqcom opened this issue Mar 1, 2025 · 0 comments

Comments

@772566741qqcom
Copy link

Our Doris is managed by a supervisor, but we cannot see any related logs information about stop in be.INFO.Log file. We only see some information about startup logs.
And the server host is relatively large (96 cores, 256GB), and the concurrency and data volume are not too large, so it cannot meet the conditions for memory overflow.
I don't know why the BE instance is rebooted (suspected to be caused by a supervisor reboot). while reviewing the supervisor.log, the following information was found:
exit : dorie_be (Exit status 139; not expected)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant