Hi,
it is a known issue with Marathon:
https://jira.d2iq.com/browse/MARATHON-8180
AFAIK it hasn't been fixed yet. You can tune GC or increase memory limits,
but the memory usage will grow indefinitely with a higher number of tasks.
Regards,
Tomas
On Wed, 26 Aug 2020 at 11:11, Marc Roos
Hi Alex,
looks like you've restarted Marathon during election. Try to backup
ZooKeeper data and then go to exhibitor / ZooKeeper CLI and remove flag
from Marathon namespace:
/state/migration-in-progress
According to https://github.com/mesosphere/marathon/pull/5662 the flag
should be removed
Hi,
try Chronos framework https://mesos.github.io/chronos/
Tomas
On 6 January 2017 at 17:40, l vic wrote:
> Hi,
> Is there a way to schedule mesos framework task for execution at certain
> day/time?
> Thank youm
> -V
>
Hi,
we're using `mesos tail -f`, `mesos cat`, `mesos ps` quite a lot. It would
be nice if you keep those. Is there a document describing changes that
you're planning?
just few ideas, it would be nice to have a command for:
- listing all instances of a given task
- join stderr and stdout (for
It's interesting idea, but if you use ZooKeeper for Marathon or Mesos
discovery you might easily end up in chicken-egg problem. You would like to
start Marathon, but there's no ZooKeeper available until you start Marathon.
If 3 ZooKeepers aren't enough for you, you might consider deploying
Hi,
libmesos.so will be dependent on the libcurl-dev library that is present on
the machine where you've built the package.
So, in case of Debian, libmesos will be dependent on one of these packages:
libcurl4-nss-dev,libcurl4-gnutls-dev, libcurl4-openssl-dev
It's not a new dependency, same
[unnecessary] system mutations__.
Is this asking too much of mesos/mesosphere in their present forms?
On Tue, Aug 4, 2015 at 4:42 PM, Tomas Barton barton.to...@gmail.com
wrote:
Hi Jay,
as long as the libcurl-dev dependency is concerned you can use any of
libcurl4-openssl-dev, libcurl4
Hi Jay,
as long as the libcurl-dev dependency is concerned you can use any of
libcurl4-openssl-dev, libcurl4-gnutls-dev or libcurl4-nss-dev. Just make
sure one of these libraries is installed on all of your worker (slave)
nodes. If you don't need any modification of the mesos packaging, you can
+1
tested on Ubuntu 14.04 LTS and Debian 7 Wheezy with gcc 4.8.4
On 1 May 2015 at 03:51, Elizabeth Lingg elizab...@mesosphere.io wrote:
It seemed to be different symptoms with the same cause.
Thanks,
Elizabeth
On Thu, Apr 30, 2015 at 6:09 PM, Benjamin Mahler
benjamin.mah...@gmail.com
Hi,
sorry for late reply. I found the message accidentally in spam.
It seems like Storm is binding to localhost 127.0.1.1:52310
http://scheduler-37d9a510-1136-4adb-be09-c9c2e388611f@127.0.1.1:52310/
instead
of using public interface.
Regards,
Tomas
On 19 January 2015 at 14:04, Ondrej Smola
apt-get install libapr1-dev libsvn-dev
should fix that. (for this error just libsvn-dev is enough)
Tomas
On 29 January 2015 at 22:35, Dan Dong dongda...@gmail.com wrote:
Hi,
When I tried to build mesos-0.21.0 on Ubuntu-14.04, I get this error:
Have a look at mesos.cli:
https://pypi.python.org/pypi/mesos.cli/0.1.3
you can easily do
mesos tail {task id}
and access log file on any slave machine or connect to machine where is
given task running.
On 13 January 2015 at 22:48, David Greenberg dsg123456...@gmail.com wrote:
I was trying
?
On Thu, Jan 8, 2015 at 5:00 PM, Tomas Barton barton.to...@gmail.com
wrote:
Hi Itamar,
there's definitely certain limit of machines which can Mesos master
handle. This limit is between 10 000 - 20 000 (that's number
reported by Twitter). This bottleneck is caused by event loop which
handles
Hi Dan,
this depends on your distribution. Mesosphere package comes with wrapper
script which uses configuration
placed in /etc/default/mesos and /etc/mesos-master, /etc/mesos-slave
https://github.com/mesosphere/mesos-deb-packaging/blob/master/mesos-init-wrapper
which distribution do you use?
for mesos 0.21.0?
ls ~/mesos-0.21.0/build/
3rdparty bin config.log config.lt config.status ec2 include lib
libexec libtool Makefile mesos.pc mpi sbin share src
Cheers,
Dan
2015-01-07 9:47 GMT-06:00 Tomas Barton barton.to...@gmail.com:
Hi Dan,
this depends on your
Hi,
Mesos = 0.21 requires GCC = 4.8 for building
https://issues.apache.org/jira/browse/MESOS-1044
Tomas
On 18 December 2014 at 07:38, Ritwik ritwik.ya...@gmail.com wrote:
Thanks Michael for your reply.
*I was able to resolve the issue by upgrading from GCC 4.6 to GCC 4.8*
It seems to
://downloads.mesosphere.io/storm/storm-mesos-0.9.tgz
It would be great if you could let me know how to deploy Storm topology
over Marathon. Thanks a lot,
Obaid
PS
*From:* Tomas Barton [mailto:barton.to...@gmail.com]
*Sent:* Tuesday, December 09, 2014 2:15 AM
*To:* user
*Subject
Storm-Mesos framework however now I
want to use Marathon to launch nimbus and my tasks .
Thanks
Obaid
*From:* Tomas Barton [mailto:barton.to...@gmail.com]
*Sent:* Tuesday, December 09, 2014 11:17 AM
*To:* Salikeen, Obaid
*Cc:* user@mesos.apache.org
*Subject:* Re: How to launch
Just to make sure, all slaves are running with:
--isolation='cgroups/cpu,cgroups/mem'
Is there something suspicious in mesos slave logs?
On 26 September 2014 13:20, Stephan Erb stephan@blue-yonder.com wrote:
Hi everyone,
I am having issues with the cgroups isolation of Mesos. It seems
Hi James,
Spark has support for HDFS, however you don't have to use it and there's no
need to install whole Hadoop stack. I've tested Mesos and Spark with FhGFS
distributed filesystem and it works just fine.
Tomas
On 8 September 2014 06:39, Vinod Kone vinodk...@gmail.com wrote:
Hi James,
There is some overhead for the JVM itself, which should be added to the
total usage of memory for the task. So you can't have the same amount of
memory for the task as you pass to java, -Xmx parameter.
On 2 September 2014 20:43, Benjamin Mahler benjamin.mah...@gmail.com
wrote:
Looks like
The later is definitely a better choice. Yet another fork of storm-mesos is
here:
https://github.com/deric/storm-mesos
On 19 August 2014 20:22, Yaron Rosenbaum yaron.rosenb...@gmail.com wrote:
I'm not getting it from git, but rather downloading it from:
Hi,
that's quite strange. Try to run
ldconfig
and then again make.
You can find binary packages for Debian here:
http://mesosphere.io/downloads/
Tomas
On 23 July 2014 10:09, Itamar Ostricher ita...@yowza3d.com wrote:
Hi,
I'm trying to do a clean build of mesos for the 0.19.0 tarball.
I
, so that the assumption need not be made.
On Tue, Jul 22, 2014 at 2:40 AM, Tomas Barton barton.to...@gmail.com
wrote:
Hi,
what is the best way to upgrade Mesos cluster from 0.18 to 0.19? I've
tried to read all documentation before doing actual upgrade, but I still
don't understand a few
Hi,
what is the best way to upgrade Mesos cluster from 0.18 to 0.19? I've tried
to read all documentation before doing actual upgrade, but I still don't
understand a few things.
What should be the quorum size?
The --help says that It is imperative to set this value to be a majority
of masters
Hi,
have you tried setting '--ip 10.69.69.45' ?
So, mesos-master is binded to a wrong interface? Or you have problem with
mesos-slaves?
Tomas
On 1 July 2014 12:16, Damien Hardy dha...@viadeoteam.com wrote:
Hello,
We would like to use spark on mesos but mesos cluster is accessible via
Hi,
I have a problem with Mesos executor initialization. A slave receives a
task and is launching an executor, stderr:
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0601 14:54:36.055747 15807 exec.cpp:131] Version: 0.18.2
stdout:
3399 [main] INFO
will go with stdout/stderr pipeline instead (using logrotate
copytruncate to handle open file descriptors)
Thank you
Le 15/05/2014 22:02, Tomas Barton a écrit :
Hi Damien,
do you use the `--log_dir` switch? If so, mesos is creating quite many
files in a strange format:
mesos-slave
Hi,
I have similar issue, Mesos is trying to keep alive a framework that is
crashing:
I0528 16:42:52.487659 6009 master.cpp:929] Framework
20140528-054038-316558480-5050-17117-0003 failed over
I0528 16:42:52.487927 6009 hierarchical_allocator_process.hpp:378]
Activated framework
, May 23, 2014 at 8:51 AM, Tomas Barton barton.to...@gmail.comwrote:
I've set up the --hostname mesos-m1.example.com but it crashes the master
I0523 17:46:22.166190 18203 contender.cpp:127] Joining the ZK group
I0523 17:46:30.253983 18197 http.cpp:391] HTTP request for
'/master/state.json
Hi Damien,
do you use the `--log_dir` switch? If so, mesos is creating quite many
files in a strange format:
mesos-slave.{hostname}.invalid-user.log.INFO.20140409-155625.7545
when you forward stdout of the service to a single file and afterwards
apply simple logroate
rules, you might get nicer
Hi Chengwei,
| 1. Is it necessary to deploy storm nimbus on the mesos master node?
Yes, basically Nimbus runs as Mesos framework (inside Mesos master), if
Mesos master dies, it should start automatically on a different node.
It's not a standard Nimbus, it's MesosNimbus (Mesos framework):
code
32 matches
Mail list logo