-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Scylla on AWS throws a SIGSEGV #326
Comments
which ami? On 9/9/15, slivne notifications@github.com wrote:
Asias |
On Wed, Sep 9, 2015 at 4:20 PM, slivne notifications@github.com wrote:
Could it be out of memory or very low memory condition?
|
ami-6fb9d70a started with --clustername sl I'll write a wiki page on how to start a cluster via the ami and update the its on scylla boot the machine is a m4.xlarge 16GB, 4 CPUS - I doubt we ran On Wed, Sep 9, 2015 at 4:34 PM, Dor Laor notifications@github.com wrote:
|
Could be related to the problem I am seeing (and investigating): 2015-09-09 15:38 GMT+02:00 slivne notifications@github.com:
|
2015-09-09 15:47 GMT+02:00 Tomasz Grabiec tgrabiec@gmail.com:
I've just posted a patch which fixed the problem for me:
|
Comments on your ami-6fb9d70a on N. virginia
cat /usr/lib/systemd/system/scylla-server.service [Service] [Install] |
Regarding cluster, With https://github.com/cloudius-systems/urchin/wiki/Using-AWS-AMI, I started 3 nodes cluster. One of the node fails to join the cluster, the second node.
|
I can confirm with
The abort goes away. After update the patched scylla binary on the failed node. I can rejoin the node into the cluster (this also suggests we are good in terms of rejoining a node). See blow:
|
Good progress Asias. Can you please provide details about what was tested, how (A wiki for new On Thu, Sep 10, 2015 at 3:58 AM, Asias He notifications@github.com wrote:
|
I updated it here: https://github.com/cloudius-systems/urchin/wiki/Using-AWS-AMI I'm still have trouble running cassandra-stress against a cluster. |
When starting a cluster on AWS via the AMI scylla sometimes crashes
it happens even when running via the command line
rm -Rf /data/data/; rm -Rf /data/commitlog/ ; env HOME=/var/lib/scylla /usr/bin/scylla --log-to-syslog 1 --default-log-level info --options-file /var/lib/scylla/conf/scylla.yaml --network-stack posix
not sure there is enough data here to work with we are updating the ami to install debug info
The text was updated successfully, but these errors were encountered: