[ https://issues.apache.org/jira/browse/MESOS-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dominic Hamon closed MESOS-932. ------------------------------- Resolution: Fixed > building spark0.8.1 with mesos 0.15.0 error becauseof protobuf is not > compatible > -------------------------------------------------------------------------------- > > Key: MESOS-932 > URL: https://issues.apache.org/jira/browse/MESOS-932 > Project: Mesos > Issue Type: Bug > Components: libprocess > Affects Versions: 0.15.0 > Environment: hadoop2.2.0+spark0.8.0+mesos0.15.0 > Reporter: liuhanbing > Labels: test > Original Estimate: 96h > Remaining Estimate: 96h > > I've tried building spark0.8.1 with mesos 0.15.0 and I have the exact error: > Stack: [0x00007f4cd1734000,0x00007f4cd1835000], sp=0x00007f4cd1833490, free > space=1021k > Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native > code) > V [libjvm.so+0x514706] unsigned+0xb6 > j org.apache.mesos.MesosSchedulerDriver.initialize()V+0 > j > org.apache.mesos.MesosSchedulerDriver.<init>(Lorg/apache/mesos/Scheduler;Lorg/apache/mesos/Protos$FrameworkInfo;Ljava/lang/String;)V+62 > j > org.apache.spark.scheduler.cluster.mesos.MesosSchedulerBackend$$anon$1.run()V+44 > v ~StubRoutines::call_stub > Java Threads: ( => current thread ) > =>0x00007f4cd4186800 JavaThread "MesosSchedulerBackend driver" daemon > [_thread_in_vm, id=19685, stack(0x00007f4cd1734000,0x00007f4cd1835000)] > 0x00007f4cd4170800 JavaThread "Timer-0" daemon [_thread_blocked, id=19684, > stack(0x00007f4cd1835000,0x00007f4cd1936000)] > 0x00007f4cd4077000 JavaThread "qtp1645300503-49" daemon [_thread_blocked, > id=19683, stack(0x00007f4cd33f4000,0x00007f4cd34f5000)] > 0x00007f4cd4075000 JavaThread "qtp1645300503-48" daemon [_thread_blocked, > id=19682, stack(0x00007f4cd34f5000,0x00007f4cd35f6000)] > It looks like the protobuf is not compatible. spark0.8.1 has protobuf2.5.0 > but mesos0.15.0 still has protobuf2.4.1. > I've rebuild mesos 0.15.0 using protobuf 2.5.0.The error I am having still > seems to be related to protobuf seriously do not know how > to try to debug that. > any idears? -- This message was sent by Atlassian JIRA (v6.3.4#6332)