You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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)
The text was updated successfully, but these errors were encountered: