Re: [VOTE] Release Apache Mesos 1.3.1 (rc1)

2017-08-01 Thread Vinod Kone 
+1 (binding)

Tested on ASF CI. The 2 red builds are known flaky tests (health checks)
and a perf core dump issue that's fixed on HEAD.

*Revision*: 1beaede8c13f0832d4921121da34f924deec8950

   - refs/tags/1.3.1-rc1

Configuration Matrix gcc clang
centos:7 --verbose --enable-libevent --enable-ssl autotools
[image: Failed]

[image: Not run]
cmake
[image: Success]

[image: Not run]
--verbose autotools
[image: Success]

[image: Not run]
cmake
[image: Success]

[image: Not run]
ubuntu:14.04 --verbose --enable-libevent --enable-ssl autotools
[image: Success]

[image: Success]

cmake
[image: Success]

[image: Success]

--verbose autotools
[image: Success]

[image: Failed]

cmake
[image: Success]

[image: Success]


On Fri, Jul 28, 2017 at 5:45 PM, Michael Park  wrote:

> Hi all,
>
> Please vote on releasing the following candidate as Apache Mesos 1.3.1.
>
> The CHANGELOG for the release is available at:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_
> plain;f=CHANGELOG;hb=1.3.1-rc1
> 
> 
>
> The candidate for Mesos 1.3.1 release is available at:
> https://dist.apache.org/repos/dist/dev/mesos/1.3.1-rc1/mesos-1.3.1.tar.gz
>
> The tag to be voted on is 1.3.1-rc1:
> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.3.1-rc1
>
> The MD5 checksum of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.3.1-rc1/
> mesos-1.3.1.tar.gz.md5
>
> The signature of the tarball can be found at:
> https://dist.apache.org/repos/dist/dev/mesos/1.3.1-rc1/
> mesos-1.3.1.tar.gz.asc
>
> The PGP key used to sign the release is here:
> https://dist.apache.org/repos/dist/release/mesos/KEYS
>
> The JAR is up in Maven in a staging repository here:
> https://repository.apache.org/content/repositories/orgapachemesos-1200
>
> Please vote on releasing this package as

Re: Latest Mesos (1.4.0) Fails to Build on Ubuntu 14.04.5

2017-08-01 Thread Benjamin Mahler 
That file path looks valid from what I can tell:

/opt/mesos/build/src/../../src/python/cli/src/mesos/__init__.py

Is the file not there? Is the directory not there?

On Fri, Jul 28, 2017 at 9:45 AM, Traiano Welcome  wrote:

> Hi All
>
> The latest version of mesos fails to build on Ubuntu 14.04.5. make fails
> with the following error:
>
> -
> .
> .
> .
> cp: cannot stat '../../src/python/cli/src/mesos/__init__.py': No such
> file or directory
> make[2]: *** [python/cli/src/mesos/__init__.py] Error 1
> make[2]: Leaving directory `/opt/mesos/build/src'
> make[1]: *** [all] Error 2
> make[1]: Leaving directory `/opt/mesos/build/src'
> make: *** [all-recursive] Error 1
> -
>
> Installation steps leading up to the make failure:
>
>
> sudo apt-get update
> sudo apt-get install -y tar wget git
>
> git clone https://git-wip-us.apache.org/repos/asf/mesos.git
>
> sudo apt-get install -y openjdk-7-jdk
> sudo apt-get install -y autoconf libtool
> sudo apt-get -y install build-essential python-dev python-six 
> python-virtualenv libcurl4-nss-dev libsasl2-dev libsasl2-modules maven 
> libapr1-dev libsvn-dev
> cd mesos
>
> mkdir build
> ../configure
> make
>
>
>
> Does anyone know how to fix this?
>
> Thanks,
> Traiano
>

Re: Hadoop on Mesos: FATAL mapred.MesosScheduler: Failed to initialize the TaskScheduler

2017-08-01 Thread tommy xiao 
Traiano,

i am not also use it anymore, so i just share with you.

2017-07-31 2:27 GMT+08:00 Traiano Welcome :

> Hi Tommy
>
> On Sun, Jul 30, 2017 at 9:37 PM, tommy xiao  wrote:
>
>> why not use Myriad?
>>
>> https://cwiki.apache.org/confluence/display/MYRIAD/Myriad+Home
>>
>
>
> I'm in doubt about the future of this project. I'm told it's likely to be
> discontinued soon due to the lack of contributors.
> In any case - have you perhaps seen a successful deployment of this ?
>
>
>
>
>
>>
>>
>>
>> 2017-07-23 17:27 GMT+08:00 Traiano Welcome :
>>
>>>
>>> Hi List!
>>>
>>> I'm working on configuring hadoop to use the mesos scheduler, using the
>>> procedure outlined in "Apache Mesos Essentials" here:
>>>
>>> https://pastebin.com/y1ERJZqq
>>>
>>> Currently I've a 3 node mesos cluster, with an HDFS namenode
>>> communicating successfully with two HDFS data nodes. However, when I try to
>>> start up the jobtracker it fails with the following error:
>>>
>>> 17/07/22 18:44:38 FATAL mapred.MesosScheduler: Failed to initialize the
>>> TaskScheduler
>>> java.lang.ClassNotFoundException:  org.apache.hadoop.mapred.JobQu
>>> eueTaskScheduler
>>>
>>> Some more context around the error:
>>>
>>>  17/07/22 18:44:38 INFO mapred.CompletedJobStatusStore: Completed job
>>> store is inactive
>>>  17/07/22 18:44:38 FATAL mapred.MesosScheduler: Failed to initialize the
>>> TaskScheduler
>>>  java.lang.ClassNotFoundException:  org.apache.hadoop.mapred.JobQu
>>> eueTaskScheduler
>>>
>>> at java.net.URLClassLoader$1.run(URLClassLoader.java:359)
>>> at java.net.URLClassLoader$1.run(URLClassLoader.java:348)
>>> at java.security.AccessController.doPrivileged(Native Method)
>>> at java.net.URLClassLoader.findClass(URLClassLoader.java:347)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
>>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:312)
>>> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
>>> at java.lang.Class.forName0(Native Method)
>>> at java.lang.Class.forName(Class.java:195)
>>> at   org.apache.hadoop.mapred.MesosScheduler.start(MesosScheduler
>>> .java:160)
>>> atorg.apache.hadoop.mapred.JobTracker.offerService(JobTracker.
>>> java:2186)
>>> at org.apache.hadoop.mapred.JobTracker.main(JobTracker.java:4548)
>>> 17/07/22 18:44:38 INFO mapred.JobTracker: SHUTDOWN_MSG:
>>>
>>> Is there some way I could debug this further to trace the root cause of
>>> this error?
>>>
>>> Here is a full paste of the debug output when starting up the jobtracker:
>>>
>>>  https://pastebin.com/a61wN4vQ
>>>
>>>
>>>
>>
>>
>> --
>> Deshi Xiao
>> Twitter: xds2000
>> E-mail: xiaods(AT)gmail.com
>>
>
>


-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com