I am compiling my code like this:
javac Executor.java Framework.java -cp protobuf-2.4.1.jar:mesos-0.15.0.jar
jar cf mexample.jar *.class
and content of my framework and executor files are:
framework:
#!/bin/sh
# This script uses MESOS_SOURCE_DIR and MESOS_BUILD_DIR which come
# from configuration substitutions.
MESOS_SOURCE_DIR=/home/mrez/workspace/mesos/build/..
MESOS_BUILD_DIR=/home/mrez/workspace/mesos/build
# Locate Java from environment or use configure discovered location.
JAVA_HOME=${JAVA_HOME-/usr/lib/jvm/java-7-oracle}
JAVA=${JAVA-${JAVA_HOME}/bin/java}
# Use colors for errors.
. ${MESOS_SOURCE_DIR}/support/colors.sh
PROTOBUF_JAR=${MESOS_BUILD_DIR}/protobuf-2.4.1.jar
test ! -e ${PROTOBUF_JAR} && \
echo "${RED}Failed to find ${PROTOBUF_JAR}${NORMAL}" && \
exit 1
MESOS_JAR=${MESOS_BUILD_DIR}/src/mesos-0.15.0.jar
test ! -e ${MESOS_JAR} && \
echo "${RED}Failed to find ${MESOS_JAR}${NORMAL}" && \
exit 1
#EXAMPLES_JAR=${MESOS_BUILD_DIR}/src/examples.jar
EXAMPLES_JAR=/home/mrez/workspace/mesone/target/mexample.jar
test ! -e ${EXAMPLES_JAR} && \
echo "${RED}Failed to find ${EXAMPLES_JAR}${NORMAL}" && \
exit 1
# Need to run in the directory containing this script so that the
# framework is able to find the executor.
cd `dirname ${0}`
exec ${JAVA} -cp ${PROTOBUF_JAR}:${MESOS_JAR}:${EXAMPLES_JAR} \
-Djava.library.path=${MESOS_BUILD_DIR}/src/.libs \
Framework "${@}"
executor:
#!/bin/sh
# This script uses MESOS_SOURCE_DIR and MESOS_BUILD_DIR which come
# from configuration substitutions.
MESOS_SOURCE_DIR=/home/mrez/workspace/mymesos/build/..
MESOS_BUILD_DIR=/home/mrez/workspace/mymesos/build
# Locate Java from environment or use configure discovered location.
JAVA_HOME=${JAVA_HOME-/usr/lib/jvm/java-7-oracle}
JAVA=${JAVA-${JAVA_HOME}/bin/java}
# Use colors for errors.
. ${MESOS_SOURCE_DIR}/support/colors.sh
PROTOBUF_JAR=${MESOS_BUILD_DIR}/protobuf-2.4.1.jar
test ! -e ${PROTOBUF_JAR} && \
echo "${RED}Failed to find ${PROTOBUF_JAR}${NORMAL}" && \
exit 1
MESOS_JAR=${MESOS_BUILD_DIR}/src/mesos-0.15.0.jar
test ! -e ${MESOS_JAR} && \
echo "${RED}Failed to find ${MESOS_JAR}${NORMAL}" && \
exit 1
#EXAMPLES_JAR=${MESOS_BUILD_DIR}/src/examples.jar
EXAMPLES_JAR=/home/mrez/workspace/mesone/target/mexample.jar
test ! -e ${EXAMPLES_JAR} && \
echo "${RED}Failed to find ${EXAMPLES_JAR}${NORMAL}" && \
exit 1
exec ${JAVA} -cp ${PROTOBUF_JAR}:${MESOS_JAR}:${EXAMPLES_JAR} \
-Djava.library.path=${MESOS_BUILD_DIR}/src/.libs \
Executor "${@}"
Best Regards
Mohamad Rezaei
-------------------
Researcher at PDC
KTH Royal Institute of Technology
On Thu, Oct 31, 2013 at 1:53 PM, Mohamad Rezaei <[email protected]> wrote:
> The error that I am getting is simple. On slave in short (for each
> executor):
> ===============================================
> 336-I1031 13:40:04.390418 5933 slave.cpp:2066] Monitoring executor
> default of framework 201310311338-16842879-5050-5922-0001 forked at pid 6263
> 337-I1031 13:40:05.020405 5933 process_isolator.cpp:479] Telling slave of
> terminated executor 'default' of framework
> 201310311338-16842879-5050-5922-0001
> 338-I1031 13:40:05.024759 5931 slave.cpp:2122] Executor 'default' of
> framework 201310311338-16842879-5050-5922-0001 has exited with status 127
> 339:I1031 13:40:05.025979 5931 slave.cpp:1737] Handling status update
> TASK_LOST (UUID: 85bc8a24-9f9c-46ce-b644-e7e0f6844d52) for task 7 of
> framework 201310311338-16842879-5050-5922-0001 from @0.0.0.0:0
> 340:I1031 13:40:05.026260 5931 status_update_manager.cpp:305] Received
> status update TASK_LOST (UUID: 85bc8a24-9f9c-46ce-b644-e7e0f6844d52) for
> task 7 of framework 201310311338-16842879-5050-5922-0001
> 341:I1031 13:40:05.026358 5931 status_update_manager.cpp:356] Forwarding
> status update TASK_LOST (UUID: 85bc8a24-9f9c-46ce-b644-e7e0f6844d52) for
> task 7 of framework 201310311338-16842879-5050-5922-0001 to
> [email protected]:5050
> 342-I1031 13:40:05.027835 5932 status_update_manager.cpp:380] Received
> status update acknowledgement (UUID: 85bc8a24-9f9c-46ce-b644-e7e0f6844d52)
> for task 7 of framework 201310311338-16842879-5050-5922-0001
> 343-I1031 13:40:05.028039 5931 slave.cpp:2257] Cleaning up executor
> 'default' of framework 201310311338-16842879-5050-5922-0001
> 344-I1031 13:40:05.028210 5932 gc.cpp:56] Scheduling
> '/tmp/mesos/slaves/201310311323-16842879-5050-5037-0/frameworks/201310311338-16842879-5050-5922-0001/executors/default/runs/0c0cb61f-b119-4450-afaf-f547ac6d04bc'
> for gc 6.99999967427259days in the future
> ========================================================
> on mesos master for each executor:
> ========================================================
> 246-I1031 13:40:05.387863 5925 master.cpp:2118] Launching task 8 of
> framework 201310311338-16842879-5050-5922-0001 with resources cpus(*):1;
> mem(*):128 on slave 201310311323-16842879-5050-5037-0 (iStrader)
> 247-I1031 13:40:05.388151 5924 hierarchical_allocator_process.hpp:590]
> Framework 201310311338-16842879-5050-5922-0001 filtered slave
> 201310311323-16842879-5050-5037-0 for 1secs
> 248-I1031 13:40:06.026221 5925 master.cpp:1476] Executor default of
> framework 201310311338-16842879-5050-5922-0001 on slave
> 201310311323-16842879-5050-5037-0 (iStrader) exited with status 32512
> 249:I1031 13:40:06.026422 5926 master.cpp:1425] Status update TASK_LOST
> (UUID: 35aed42c-810c-4465-9968-13a2eb66cb35) for task 8 of framework
> 201310311338-16842879-5050-5922-0001 from slave(1)@127.0.1.1:5051
> 250-I1031 13:40:06.026495 5926 master.hpp:403] Removing task 8 with
> resources cpus(*):1; mem(*):128 on slave 201310311323-16842879-5050-5037-0
> (iStrader)
> 251-I1031 13:40:06.026657 5926 hierarchical_allocator_process.hpp:637]
> Recovered cpus(*):1; mem(*):128 (total allocatable: cpus(*):4; mem(*):2906;
> disk(*):80784; ports(*):[31000-32000]) on slave
> 201310311323-16842879-5050-5037-0 from framework
> 201310311338-16842879-5050-5922-0001
> 252-2013-10-31
> 13:40:06,126:5922(0x7f84732fd700):ZOO_DEBUG@zookeeper_process@1983: Got
> ping response in 0 ms
>
> =============================================================================
>
> I don't get it why it is 127.0.1.1 and not 127.0.0.1. Weird isn't it? I am
> looking inside master.cpp but I cannot find the reason.
>
>
> ALSO, I am starting my master and slave in a single machine like this:
> mesos-slave --master=zk://localhost:2181/mesos 2> ~/mesos-slave
> mesos-master --zk=zk://localhost:2181/mesos 2> ~/mesos-master
>
> see, I am just using localhost not the 127.0.0.1.
>
>
> Best Regards
> Mohamad Rezaei
> -------------------
> Researcher at PDC
> KTH Royal Institute of Technology
>
>
> On Wed, Oct 30, 2013 at 7:05 PM, Mohamad Rezaei <[email protected]> wrote:
>
>> OK,
>>
>> I can see them myself, but I will send the log tomorrow. I just came back
>> from university, and they started elictricity/fire tests! So no electricity
>> until tomorrow. ;-)
>>
>>
>> Best Regards
>> Mohamad Rezaei
>> -------------------
>> Researcher at PDC
>> KTH Royal Institute of Technology
>>
>>
>> On Wed, Oct 30, 2013 at 6:13 PM, Vinod Kone <[email protected]> wrote:
>>
>>> I don't see the attachments. Did you forget to attach them? Or maybe the
>>> Apache mail servers strip attachments?
>>>
>>> Can you explain a bit more on what your setup is and what are the exact
>>> steps (commands) you used to repro the problem? Log outputs of
>>> slave/master/framework would also make it easier to diagnose.
>>>
>>>
>>> On Wed, Oct 30, 2013 at 9:11 AM, Mohamad Rezaei <[email protected]> wrote:
>>>
>>> > Hi all,
>>> >
>>> > I have moved the example java files to another location, and changed
>>> the
>>> > name of all the classes but with the same internal code as the default
>>> > examples. Also I have changed the two "test-executor" and
>>> "test-framework"
>>> > files accordingly so the can run the classes that I am mentioning. But
>>> I
>>> > get task lost on slaves since I think slaves cannot find the
>>> corresponding
>>> > executors. I am not sure actually if this is the problem or not. I have
>>> > attached the files in here.
>>> >
>>> > Did I have to do something else?
>>> >
>>> > Best Regards
>>> > Mohamad Rezaei
>>> > -------------------
>>> > Researcher at PDC
>>> > KTH Royal Institute of Technology
>>> >
>>>
>>
>>
>
