-
Notifications
You must be signed in to change notification settings - Fork 832
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
coordinator crashed frequency #7093
Comments
Hm, |
no, memory is normal, keep on 50%
latest restart log(we tried 3.3.19/3.3.11, all encouter restart problem):
|
Can you try to increase the logging on the coordinator?
and run it interactive? |
i and zqhxuyuan are the same team.we had changed the log's config,before crash.the log is:
|
and after the last log line it will abort again with the same place as posted above? |
yes. the same log,and the same place crash,the bt info is : |
Did you already install the debug package? https://download.arangodb.com/arangodb33/CentOS_6/x86_64/arangodb3-debuginfo-3.3.17-1.x86_64.rpm |
Since you run on a relative old centos, which exact cpu architecture do you run on? Can you post one line each from |
the 3.1.17and 3.1.19 both has the same crash, I has installed the debug package, the info is : |
the cpu info is: cpu family : 6 |
maybe the arangodb3-debuginfo-3.3.19-1.x86_64.rpm miss the other ebugging symbols below,or i should install from other rpm package ? Reading symbols from /usr/lib64/libssl.so.10...(no debugging symbols found)...done. |
hm, sorry my bad regarding the trace log, it should have been You need to install the debug symbol package matching your installed program package. Another thing worth trying would be to fix the number of spawned V8 contexts to i.e. 8: |
I add the V8 contexts :--javascript.v8-contexts 8, the same crash happeped, |
The release in question here is long EOLed. |
Environment:
we use supervisor mode to start coordinator. and notice cooordinator node crash frequency.
we have tried coordinator version 3.3.17 and 3.3.19. our agency/dbserver version is 3.3.17.
when coordinator restart by supervisor mode, the coordinator.log file have little useful information:
and arangod.log.supervisor log file:
the process was killed by send signal 11.
so we tried start by normal mode(un-supervisor),when coordinator crashed, we analyze the core dump:
Thanks!
The text was updated successfully, but these errors were encountered: