Alberto created MESOS-2820:
------------------------------

             Summary: SIGSEGV received on start mesos scheduler driver
                 Key: MESOS-2820
                 URL: https://issues.apache.org/jira/browse/MESOS-2820
             Project: Mesos
          Issue Type: Bug
    Affects Versions: 0.22.1
         Environment: Linux Fedora
            Reporter: Alberto


I'm trying to create a CassandraSQLContext using the datastax 
spark-cassandra-connector. My SparkContext is configured to use a locally 
running mesos cluster. 

When I create the CassandraSQLContext using proper parameters everything works 
fine but when I pass a non existing or wrong mesos cluster ip. I'm getting a 
SIGSEGV signal and my VM is being shutdown. See following the trace of the 
error:

ABOUT TO CREATE THE CASSANDRA SQL CONTEXT...........................
[Dynamic-linking native method java.lang.Class.getCheckMemberAccessMethod ... 
JNI]
[Dynamic-linking native method java.net.NetworkInterface.init ... JNI]
[Dynamic-linking native method java.net.NetworkInterface.getAll ... JNI]
[Dynamic-linking native method java.net.Inet6AddressImpl.getHostByAddr ... JNI]
[Dynamic-linking native method java.lang.UNIXProcess.init ... JNI]
[Dynamic-linking native method java.lang.UNIXProcess.forkAndExec ... JNI]
[Dynamic-linking native method java.lang.UNIXProcess.waitForProcessExit ... JNI]
[Dynamic-linking native method java.net.PlainSocketImpl.socketCreate ... JNI]
[Dynamic-linking native method java.net.PlainSocketImpl.socketBind ... JNI]
[Dynamic-linking native method java.net.PlainSocketImpl.socketListen ... JNI]
[Dynamic-linking native method java.net.PlainSocketImpl.socketSetOption ... JNI]
[Dynamic-linking native method java.net.PlainSocketImpl.socketAccept ... JNI]
[Dynamic-linking native method sun.nio.ch.ServerSocketChannelImpl.accept0 ... 
JNI]
[Dynamic-linking native method org.apache.mesos.MesosSchedulerDriver.initialize 
... JNI]
WARNING: Logging before InitGoogleLogging() is written to STDERR
W0605 13:43:12.363229 25629 sched.cpp:1323] 
**************************************************
Scheduler driver bound to loopback interface! Cannot communicate with remote 
master(s). You might want to set 'LIBPROCESS_IP' environment variable to use a 
routable IP address.
**************************************************
[Dynamic-linking native method org.apache.mesos.MesosSchedulerDriver.start ... 
JNI]
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f537a894495, pid=25488, tid=139995558737664
#
# JRE version: Java(TM) SE Runtime Environment (7.0_75-b13) (build 1.7.0_75-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.75-b04 mixed mode linux-amd64 
compressed oops)
# Problematic frame:
# C  [libc.so.6+0x83495]  cfree+0x55
#
# Core dump written. Default location: 
/home/arodriguez/dev/datavis-master/back/core or core.25488 (max size 50000 
kB). To ensure a full core dump, try "ulimit -c unlimited" before starting Java 
again
#
# An error report file with more information is saved as:
# /home/arodriguez/dev/datavis-master/back/hs_err_pid25488.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to