Okay, I guess MapRFS is protocol compatible with HDFS, but not
uri-compatible. I know the MapR guys have gotten MapR on Mesos working.
They may have more answers for you on how they accomplished this.
why hard code the file prefixes?
We allow any uri, so we need to have handlers coded for each
Hello friends,
I'm Adam from Mesosphere (adam-mesos), also an Apache Mesos committer, and
lately I've been working on a Kubernetes-Mesos framework with Niklas and
Connor. I'm excited to meet the rest of the community and discuss how we
can make the Mesos ecosystem even more awesome and get the
Hi
I have created a Docker based Mesos setup, including chronos, marathon, and
storm.
Following advice I saw previously on this mailing list, I have run all
frameworks directly on the Mesos master (is this correct? is it guaranteed to
have only one master at any given time?)
Chronos and
Adam - I am new to using Jira properly. (I couldn't find the JIRA for the
Tachyon change as an example, so I linked to the code... is that ok?)
I created
https://issues.apache.org/jira/browse/MESOS-1711
If you wouldn't mind taking a quick look to make sure I filled things out
correctly to get
Can you paste the slave/executor log related to the executor failure?
@vinodkone
On Aug 18, 2014, at 5:05 AM, Yaron Rosenbaum ya...@whatson-social.com wrote:
Hi
I have created a Docker based Mesos setup, including chronos, marathon, and
storm.
Following advice I saw previously on this
Hi All,
My name is Nic Grayson (@nicgrayson). I'm an infrastructure engineer at
Banno (banno.com). Zach Cox from Banno will also be also be attending.
We are in the process migrating hosting of our web applications and api to
docker on mesos with marathon. We are really looking forward to seeing
Hi @vinodkone
nimbus log:
2014-08-18 15:49:53 b.s.d.nimbus [INFO] Executor wordcount-1-1408376868:[2 2]
not alive
2014-08-18 15:49:53 b.s.d.nimbus [INFO] Executor wordcount-1-1408376868:[2 2]
not alive
2014-08-18 15:49:53 b.s.d.nimbus [INFO] Executor wordcount-1-1408376868:[3 3]
not alive
@vinodkone
Finally found some relevant logs..
Let's start with the slave:
slave_1 | I0818 16:18:51.700827 9 slave.cpp:1043] Launching task
82071a7b5f41-31000 for framework 20140818-161802-2214597036-5050-10-0002
slave_1 | I0818 16:18:51.703234 9 slave.cpp:1153] Queuing task
:51.700827 9 slave.cpp:1043] Launching task
82071a7b5f41-31000 for framework 20140818-161802-2214597036-5050-10-0002
slave_1 | I0818 16:18:51.703234 9 slave.cpp:1153] Queuing task
'82071a7b5f41-31000' for executor wordcount-1-1408378726 of framework
'20140818-161802-2214597036-5050-10-0002
for framework 20140818-161802-2214597036-5050-10-0002
slave_1 | I0818 16:18:51.703234 9 slave.cpp:1153] Queuing task
'82071a7b5f41-31000' for executor wordcount-1-1408378726 of framework
'20140818-161802-2214597036-5050-10-0002
slave_1 | I0818 16:18:51.703335 8 mesos_containerizer.cpp
Mesos also provides the ability to reserve resources, if you need
guarantees about the resources available to a particular framework.
For now, resources can be reserved at the per-slave level and they will
*only* be offered to the role that has them reserved.
On Mon, Aug 18, 2014 at 2:13 AM,
OK, I can confirm it is a bug due to the new docker stuff. Partially my bad
not test it on mac.
I need to have rc2 with the bug fix. I'll submit a bug fix shortly.
- Jie
On Mon, Aug 18, 2014 at 1:53 PM, Vinod Kone vinodk...@gmail.com wrote:
make check succeed on Centos 5.5 but failed on
On Sat, Aug 16, 2014 at 4:26 AM, John Omernik j...@omernik.com wrote:
I've confirmed on the package I am using that when I untar it using tar
zxf as root, that the task-controller does NOT lose the setuid bit. But on
the lost tasks in Mesos I get the error below. What's interesting is that
13 matches
Mail list logo
