Aerospike crash after re-joining a disabled node ( aerospike-server-community-3.7.2-el6) Operations


#1

Jan 29 2016 15:28:28 GMT: WARNING (as): (signal.c::161) SIGSEGV received, aborting Aerospike Community Edition build 3.7.2 os el6 Jan 29 2016 15:28:28 GMT: WARNING (as): (signal.c::163) stacktrace: found 7 frames Jan 29 2016 15:28:28 GMT: WARNING (as): (signal.c::163) stacktrace: frame 0: /usr/bin/asd(as_sig_handle_segv+0x62) [0x48c693] Jan 29 2016 15:28:28 GMT: WARNING (as): (signal.c::163) stacktrace: frame 1: /lib64/libc.so.6() [0x3b396326a0] Jan 29 2016 15:28:28 GMT: WARNING (as): (signal.c::163) stacktrace: frame 2: /usr/bin/asd(cf_queue_push+0xc) [0x545661] Jan 29 2016 15:28:28 GMT: WARNING (as): (signal.c::163) stacktrace: frame 3: /usr/bin/asd(ssd_post_write+0x3e9) [0x513890] Jan 29 2016 15:28:28 GMT: WARNING (as): (signal.c::163) stacktrace: frame 4: /usr/bin/asd(ssd_write_worker+0x12a) [0x513b62] Jan 29 2016 15:28:28 GMT: WARNING (as): (signal.c::163) stacktrace: frame 5: /lib64/libpthread.so.0() [0x3b39a07a51] Jan 29 2016 15:28:28 GMT: WARNING (as): (signal.c::163) stacktrace: frame 6: /lib64/libc.so.6(clone+0x6d) [0x3b396e893d]


#2

Could you share the configuration you used?

Also, can you send us the warnings that occurred prior to the stack trace.

What operations were going on towards the cluster when this occurred - Scans, batch operations, secondary index queries?