Re: New 1.5 Marathon deb package - no documentation

. > > Marathon binary seems to completely ignore my /etc/marathon/* config files > used by previous version and when looking at the systemd file, I do not > understand how to pass startup command line switches in this version. > > > Is there any documentation I missed ? > > > Thanks. > > -- Best Regards, Haosdent Huang

Re: Data locality in Mesos

o update the `datasets` > attribute dynamically, but without affecting the jobs that are running on > node A. Is such a thing possible? > > Is there an approach other than attributes to describe the data that > resides on a node in order to achieve data locality? > > Thanks > Tobias > > -- Best Regards, Haosdent Huang

Re: Test framework stalled

pearing on the dashboard. I have enough > resources available. > > Any idea what is happening? > > Thanks > -- Best Regards, Haosdent Huang

Re: [WebUI] Sandboxes proxy

in any way? >> >> *Context: *Our network topology doesn’t allow users to access the agents >> subnet so when they try to reach the Mesos agent port (eg: >> `172.x.x.x:5051`), it doesn’t (obviously) work. >> >> *Web UI error:* >> >> ​ >> Thanks! >> >> -- >> >> Jean-Baptiste FAREZ >> > -- Best Regards, Haosdent Huang

Re: Failed to create the cgroup at ...

s occured very frequently on my server. > How can I resolve this problem ? > > Best Regards, > Weijia.Liu > > -- Best Regards, Haosdent Huang

Re: mesos container cluster came across health check coredump log

.@gmail.com> wrote: > >> Alex，Yes, let me have a try. >> >> 2017-03-31 3:16 GMT+08:00 Alex Rukletsov <a...@mesosphere.com>: >> >>> This is https://issues.apache.org/jira/browse/MESOS-7210. Deshi, do you >>> want to send the patch? I or Haosdent

Re: How to write acls for mesos

"values": ["tjop_marathon"] }, > "users": { "values": ["user_00","root"] } > } > ] > } > credentials: > { > "credentials": [ > { > "principal": "tjop_marathon", > "secret": "tjop_marathon" > }, > { > "principal": "tjop_mesos_slave", > "secret": "tjop_mesos_slave" > } > ] > } > the marathon is active framework in mesos,but whlile I create app in > marahon ,the app keep in waiting status > > please help me,thanks > -- Best Regards, Haosdent Huang

Re: compile mesos failed

amin Mahler";<bmah...@apache.org>; > *发送时间:* 2017年1月23日(星期一) 上午6:16 > *收件人:* "user"<user@mesos.apache.org>; > *抄送:* "dev"<d...@mesos.apache.org>; > *主题:* Re: Welcome Neil Conway as Mesos Committer and PMC member! > > -- Best Regards, Haosdent Huang

Re: Welcome Neil Conway as Mesos Committer and PMC member!

> https://docs.google.com/document/d/137MYwxEw9QCZRH09CXfn1544p1LuM >> uoj9LxS-sk2_F4/edit >> <https://docs.google.com/document/d/137MYwxEw9QCZRH09CXfn1544p1LuMuoj9LxS-sk2_F4/edit> >> >> Thanks, >> Vinod >> > -- Best Regards, Haosdent Huang

Re: Default executor grace period

n it's container is destroyed. > > Is this desired behavior? How to use grace period with default executor? > > Thanks > Tomek > -- Best Regards, Haosdent Huang

Re: Question on dynamic reservations

h offers which should have been reserved > for a task and a new offer. > This leaves us in the situation that if one stateful task fails and there > are new stateful tasks, the new tasks can be scheduled on failed task's > Mesos agent, filling it up and taking it's port, cpu and memory. > > > -- > Regards > Povilas Versockas > -- Best Regards, Haosdent Huang

Re: Sigkill while running mesos agent (1.0.1) in docker

ontainer to "agent" and > added MESOS_DOCKER_KILL_ORPHANS=false. > > > > On 13 Jan 2017, 02:14 +0100, haosdent <haosd...@gmail.com>, wrote: > > Is it caused by your container riemann-elasticsearch could not start > successfully? > > On Fri, Jan 13, 20

Re: Sigkill while running mesos agent (1.0.1) in docker

2d919d27babb71, >> name=host, type=host) >> 2017-01-13T01:18:21.705874041+01:00 container stop >> 1fddd8e8f956f4545c8b36b088eeca74d157eb1923867d28bf2d919d27babb71 >> (build-date=20161214, image=alisw/mesos-slave:1.0.1, license=GPLv2, >> name=mesos-slave, vendor=CentOS) >> `

Re: Sigkill while running mesos agent (1.0.1) in docker

1+01:00 container stop 1fddd8e8f956f4545c8b36b088eeca74d157eb1923867d28bf2d919d27babb71 (build-date=20161214, image=alisw/mesos-slave:1.0.1, license=GPLv2, name=mesos-slave, vendor=CentOS) ``` Ciao, Giulio On 13 Jan 2017, 01:06 +0100, haosdent <haosd...@gmail.com>, wrote: Hi, @Giuliio According to your log, it looks normal. Do you have

Re: Sigkill while running mesos agent (1.0.1) in docker

; session establishment complete on server [XX.YY.ZZ.WW:2181 > ], sessionId=0x35828ae70fb2065, negotiated timeout=1 > > Any idea of what might be going on? Looks like an OOM, but I do not see it > in /var/log/messages and it also happens with --oom-kill-disable. > > -- > Ciao, > Giulio > -- Best Regards, Haosdent Huang

Re: Error running Application in Marathon

bin/mesos-agent.sh --master=192.168.1.69:5050 > --work_dir=/var/lib/mesos –log_dir=/opt/mesos/logs –log_level=INFO –quiet > > > > Marathon I launch it via: > > #export MESOS_NATIVE_JAVA_LIBRARY=/usr/loca/lib/libmesos-1.1.0.so > > #export MESOS_WORK_DIR=/tmp/mesos/

Re: Error running Application in Marathon

e. If you are not > the intended recipient, please do not copy or disclose its content but > contact the sender immediately upon receipt. > -- Best Regards, Haosdent Huang

Re: cron-like scheduling in mesos framework?

> -V > -- Best Regards, Haosdent Huang

Re: compile failed on mesos upstream master branch

tests/.deps/mesos_tests-cluster.Tpo tests/.deps/mesos_tests- > cluster.Po > > mv -f tests/.deps/mesos_tests-authorization_tests.Tpo > tests/.deps/mesos_tests-authorization_tests.Po > > mv -f tests/.deps/mesos_tests-anonymous_tests.Tpo tests/.deps/mesos_tests- > anonymous_tests

Re: compile failed on mesos upstream master branch

-I/usr/include/apr-1 -I/usr/include/apr-1.0 -g1 > -O0 -Wno-unused-local-typedefs -MT libry_http_parser_la-http_parser.lo > -MD -MP -MF .deps/libry_http_parser_la-http_parser.Tpo -c > /mesos/3rdparty/http-parser-2.6.2/http_parser.c -fPIC -DPIC -o > .libs/libry_http_parser_la-http_parser.o > > gcc: error: /mesos/3rdparty/http-parser-2.6.2/http_parser.c: No such file > or directory > > gcc: fatal error: no input files > > compilation terminated. > > ``` > > > > -- > Deshi Xiao > Twitter: xds2000 > E-mail: xiaods(AT)gmail.com > -- Best Regards, Haosdent Huang

Re: Too many files

is also 4000. > > > On Dec 29, 2016, at 19:48, haosdent <haosd...@gmail.com> wrote: > > Hi, @Kiril It sounds like your executor reaches max open file limit. May > you show the result of > > $ cat /proc/${your_executor_pid}/limits > > > > On Fri, Dec 30,

Re: Too many files

t;,"PATH":"\/usr\/local\/sbin:\/usr\/local\/bin:\/usr\/sbin > :\/usr\/bin:\/sbin:\/bin"} --help=false --pipe_read=12 --pipe_write=13 -- > pre_exec_commands=[] --runtime_directory=/var/run/mesos > /containers/ee8857e2-ac19-4f07-810d-c2e71fbf522e --unshare_namespace_mnt=false > --user=ec2-user --working_directory=/var/lib/mesos/slaves/7e30a916-1296- > 4f47-813a-0972030b6907-S14/frameworks/7e30a916-1296-4f47- > 813a-0972030b6907-0020/executors/client_b12.tar-0f9e8f80-a217-4b28-bb5e- > 4dd7cc587381/runs/ee8857e2-ac19-4f07-810d-c2e71fbf522e > > Thanks, > -Kiril​ > -- Best Regards, Haosdent Huang

Re: Let MesosContainerizer support ramdisk.

uted and Parallel Software Lab > > Huawei Technologies Co., Ltd. > > Email:pangbingqi...@huawei.com <sut...@huawei.com> > > > > > -- Best Regards, Haosdent Huang

Re: how to debug when a task is killed

gt; > Thanks very much！ > > -- > Thanks & Best Regards > 卢文泉 | Adolph Lu > TEL：+86 15651006559 <+86%20156%205100%206559> > Linker Networks(http://www.linkernetworks.com/) > -- Best Regards, Haosdent Huang

Re: Mesos 1.1 web ui issues

Hi, @haripriya Ping me in Mesos Slack (https://mesos.slack.com/) when you are available, I think it would speed up the progress to solve your problem. My id is @haosdent. If you have not join Mesos Slack before, you could join it via https://mesos-slackin.herokuapp.com . On Tue, Dec 20, 2016 at 2

Re: Libraries to access Mesos HTTP endpoints

oints/ > [2] https://dcos.io/docs/1.8/usage/cli/command-reference/ > [3] https://pypi.python.org/pypi/mesos.interface/ > > Kota UENISHI > -- Best Regards, Haosdent Huang

Re: [MESOS-6240] Allow executor/agent communication over non-TCP/IP stream socket.

uted and Parallel Software Lab >> >> Huawei Technologies Co., Ltd. >> >> Email:pangbingqi...@huawei.com <sut...@huawei.com> >> >> >> >> >> > > > > -- > Deshi Xiao > Twitter: xds2000 > E-mail: xiaods(AT)gmail.com > -- Best Regards, Haosdent Huang

Re: Mesos 1.1 web ui issues

not be resolved. On Fri, Dec 16, 2016 at 6:51 AM, Haripriya Ayyalasomayajula < aharipriy...@gmail.com> wrote: > Hello @Haosdent, > > After I tried to use hostname, I still see the error. This is the output I > see in developer tools for chrome: > > Failed to load resource: the server

Re: Can I consider other framework tasks as a resource? Does it make sense?

t; concepts? > > > > Or I just should keep distinction between resources and > requirements/policies or whatever but anyway does this kind of logic still > belongs to scheduler or it should be somewhere else? I’m trying to > understand which logic should be in scheduler and what should go somewhere > else. > > > > Many thanks, > > Petr > > > -- Best Regards, Haosdent Huang

Re: Mesos 1.1 web ui issues

ps aux |grep mesos-master` on every master and paste their outputs here? On Wed, Dec 7, 2016 at 4:39 AM, Haripriya Ayyalasomayajula < aharipriy...@gmail.com> wrote: > Hello, @Haosdent, > > Thanks for suggesting these. > I'm attaching a snapshot of the error I've seen in Chrome

Re: Mesos 1.1 web ui issues

"cluster1", but that doesn't work either. > > /usr/sbin/mesos-master --zk=zk://mesos1:2181,mesos2:2181,mesos3:2181/mesos > --port=5050 --log_dir=/var/log/mesos --acls=/etc/mesos_acls.json > --authenticate_frameworks=true --cluster=cluster1 > --credentials=/etc/auth/credential

Re: Failure reason documentation

ath...@groupon.com> wrote: > I think he's looking for documentation about what precisely each reason > *means*. A la how there are comments beside the TaskState list in > mesos.proto. > > - Erik > > On Sun, Dec 4, 2016 at 10:07 AM haosdent <haosd...@gmail.com> wrote: > >

Re: Failure reason documentation

e various reasons mesos >> includes when a job fails. Is there a place that describes what the reasons >> mean? >> >> Thanks, >> Wil >> >> -- Best Regards, Haosdent Huang

Re: MESOS-6233 Allow agents to re-register post a host reboot

onor the restart policy. Without this, you have to lock > > the framework to a Mesos version. > > > > An empty RestartPolicy is also problematic since it precludes using > > RestartPolicy in pods. If you later want to restart a task inside a pod > but > > not across agent restarts you would have no way to express that. > > > > J > > > > > -- > Deshi Xiao > Twitter: xds2000 > E-mail: xiaods(AT)gmail.com > -- Best Regards, Haosdent Huang

Re: mesos leader switch may lead orphan tasks

29, 2016 at 09:31:08PM +0800, haosdent wrote: > > Do your jobs scheduled by marathon or your framework? > > We started 3 frameworks(marathon, storm, chronos) before upgrading. > > Here is the relative logs from the leading master > > -8<--

Re: mesos leader switch may lead orphan tasks

... > Adding task ... > Adding task ... > ... > SUBSRIBE framework > SUBSRIBE framework > ... > ``` > > So the problem is when it adding existed tasks, it can not found > corresponding > framework, so the task becomes **Orphan**. > > Is this a known preempt issue or am I missing anything? > > -- > Thanks, > Chengwei > -- Best Regards, Haosdent Huang

Re: Force offer from all of the slaves

I can make sure am presented with offers from all the > slaves all the time ? > > Thanks > > > > -- Best Regards, Haosdent Huang

Re: Question on Mesos 1.1.0 LaunchGroup

st, > and then try mesos to be a scheduler. > > It's true, I could control more on mesos framwork. But it's much more > costly than k8s. > > Switch to another containerizer technology may be simple and easy to me, > but seems impassible to my company in a period of time. > ---

Re: Question on Mesos 1.1.0 LaunchGroup

why leave docker. Would we could have launch_group for > docker in the future? > Or we can only write an executor for that. > > Thanks. > > -- > *From:* haosdent <haosd...@gmail.com> > *Sent:* Monday, November 21, 2016 8:18:13 AM > > *To:*

Re: Question on Mesos 1.1.0 LaunchGroup

Yep, only mesos container is supported. On Mon, Nov 21, 2016 at 4:14 PM, Qi Feng <athlum5...@outlook.com> wrote: > Thanks haosdent. > > > I tried to use docker containerInfo to launch group task, but got "Docker > ContainerInfo > is not supported on the task"

Re: Running mesos-slave in the docker that leave many zombie process

Pass the `--pid=host` flag when starting the docker container may resolve this. >start the mesos_slave container with "--pid=host" so that it uses the process namespace of the host. On Mon, Nov 21, 2016 at 2:30 PM, haosdent <haosd...@gmail.com> wrote: > No sure if it relat

Re: Question on Mesos 1.1.0 LaunchGroup

task_group =3D 2; > } > > What's more, an executor id is required in executorInfo. How would I build > = > the executorInfo if I use the default executor of mesos? > https://github.com/apache/mesos/blob/1.1.x/include/mesos/mesos.proto#L566 > > Thanks for any reply. > -- Best Regards, Haosdent Huang

Re: Mesos containerizer & isolation

ot seem to be supported (yet?) by the >> Docker image provider. Is there any method (except `sudo`/`setuser`) to >> achieve running as a user present in the image's /etc/fstab? >> - I may have to run untrusted code, so can I make sure that users cannot >> break out of the chroot? What about UID namespacing, so that root in the >> chroot does not become root on the host system when breaking out? >> >> Thanks for your help >> Tobias >> > > -- Best Regards, Haosdent Huang

Re: On Mesos versioning and deprecation policy

een versions X and Y. > > --> We should decouple internal protos used by Mesos from the unversioned > protos used by driver based frameworks. > > I will spend some time in the next few weeks to create/update the > documentation reflecting these points. > > Anything else I m

Re: Performance regression in v1 api vs v0

API also uses HTTP (well, more or less). I would be thankful for any > comments and experience reports of other users. > > Thanks, > Dario > > -- Best Regards, Haosdent Huang

Re: On Mesos versioning and deprecation policy

clusters. >>>> >>> >>> According to the versioning doc upgradability depends on whether you >>> depend on deprecated/removed features. >>> >>> That paragraph should be explained more precisely: >>> - "deprecated" means yo

Re: How to shutdown mesos-agent gracefully?

laus > -- > > Regards, > > Da (Klaus), Ma (马达), PMP® | Software Architect > IBM Platform Development & Support, STG, IBM GCG > +86-10-8245 4084 | mad...@cn.ibm.com | http://k82.me > -- Best Regards, Haosdent Huang

Re: Resource Isolation in Mesos

tes":0,"mem\_swap\_bytes":0,"mem\_ > total\_bytes":0,"mem\_unevictable\_bytes":0," > timestamp":1475668277.62915},"status":{"executor\_pid":14454}}] > > Output for Agent running on Rhel 6 > > [{"container\_

Re: Troubleshooting tasks that are stuck in the 'Staging' state

<fr...@frankscholten.nl> wrote: > Ok. How do you typically monitor the messages between Master and > Agents? Do you have some tools for this on the cluster? > > On Tue, Oct 4, 2016 at 6:21 PM, haosdent <haosd...@gmail.com> wrote: > > Hi, @Frank Thanks for your in

Re: Resource Isolation in Mesos

; task memory usage as 2.2G/1.0G where 2.2 is used and 1.0G is allocated but > since we don't have cgroups their so task are not getting killed. > > On rhel7 UI is showing 0B/1.0G for task memory details. > > Any idea is this rhel7 fault or do I need to adjust some configurations

Re: Resource Isolation in Mesos

UI shows the total memory allocated to framework but it is not showing > memory used by task.It always shows 0B/33MB. > > Not sure if this is rhel7 issue or mesos 1.0.1. > > Any suggestions ? > On 26 Sep 2016 21:55, "haosdent" <haosd...@gmail.com> wrote: > >> Hi, @Srika

Re: Troubleshooting tasks that are stuck in the 'Staging' state

hat are > stuck in the 'staging' state. Typically they have no logs in the > sandbox. > > Are there are any endpoints or things to look for in logs to identify > a root cause? > > Is there a troubleshooting guide for Mesos to solve problems like this? > > Cheers, > > Frank > -- Best Regards, Haosdent Huang

Re: Target version vs Fixed Version

----- > Target Version/s: 1.0.2 >Fix Version/s: (was: 1.0.2) > -- Best Regards, Haosdent Huang

Re: Web UI no longer shows Tasks information

ick, do you see any errors in your browser's > console? > > On Tue, Sep 27, 2016 at 4:29 AM, Rodrick Brown <rodr...@orchard-app.com> > wrote: > >> >> On Sep 27, 2016, at 3:43 AM, haosdent <haosd...@gmail.com> wrote: >> >> Hi, @Rodrick >> &

Re: cgroup blkio controller for persistent volume ?

for managing persistent volume > isolation ? > If true, did you already notice a drop in I/O performance compared to host > volume like with Docker (cf https://github.com/docker/docker/issues/21485 > ) ? > -- Best Regards, Haosdent Huang

Re: multi-tenancy in mesos

mesos > cluster? > could you please share some hints? thanks a lot. > > -- > Deshi Xiao > Twitter: xds2000 > E-mail: xiaods(AT)gmail.com > -- Best Regards, Haosdent Huang

Re: Unified cgroups isolator

Yu <yujie@gmail.com> wrote: > Hi, > > We just merged the unified cgroups isolator. Huge shout out to @haosdent > and @qianzhang to make this happen! > https://issues.apache.org/jira/browse/MESOS-4697 > > Just to give you some context. Previously, it's a huge pain to ad

Re: forcing framework to re-schedule?

/mesos/blob/1.0.x/include/mesos/v1/mesos.proto#L358 ). On Tue, Sep 13, 2016 at 2:53 AM, Victor L <vlyamt...@gmail.com> wrote: > How can i explicitly kill the task from my class? > > On Mon, Sep 12, 2016 at 2:10 PM, haosdent <haosd...@gmail.com> wrote: > >> If the t

Re: forcing framework to re-schedule?

at 2:03 AM, Victor L <vlyamt...@gmail.com> wrote: > It checks if process is functional. I don't think standard healthchecks > wouldn't be sufficient for my purpose and my question still stands: how to > use result... > > On Mon, Sep 12, 2016 at 1:48 PM, haosdent <haosd...@g

Re: forcing framework to re-schedule?

odically checking if main process ( started by > framework) is running... > What would be the mechanism to "communicate" failure to the framework to > cause specific outcome? For example: how can i use failure to cause > framework to reschedule deployment on different node? > Thanks, > -- Best Regards, Haosdent Huang

Re: Question about the deprecated policy after 1.0

lleague of mine was testing our internal scheduler against HEAD of > mesos, and discovered that any task they submitted was being rejected as > TASK_ERROR, since we were setting health checks, but not sending type. I > filed MESOS-6110, on the 30th of August, and haosdent huang has

Re: Support HTTP(s)/TCP Health Check in Mesos

Just test with curl 7.50.1, HTTP 2 is supported. On Sat, Sep 3, 2016 at 12:32 AM, haosdent <haosd...@gmail.com> wrote: > The current implementation of HTTP(s) health check is based on curl. > According to the document of curl > > >Since 7.47.0, the curl tool enables HTTP/2

Re: Support HTTP(s)/TCP Health Check in Mesos

ing HTTP/2 for any communication that > happens in Mesos would provide a nice improvement in heavy load situations. > > On Fri, Sep 2, 2016 at 10:59 AM, haosdent <haosd...@gmail.com> wrote: > > > Hi, dear friends. @alexr and I are working on supporting HTTP(s)/TCP > He

Support HTTP(s)/TCP Health Check in Mesos

tion cycle of this? Any concerns and questions are appreciated, thanks a lot! -- Best Regards, Haosdent Huang

Re: Best Practices for Scheduler in Scala

the "Hello World" > approach, the Nokia library or write a client for the HTTP API myself. Any > suggestions? > > Thank you, > Tobias > > -- Best Regards, Haosdent Huang

Re: Setup Multi Node Mesos Cluster

ailed to call scheduler's statusUpdate > > Any idea or pointer where I am doing wrong. > -- > Regards, > Mahendra > -- Best Regards, Haosdent Huang

Re: how to enable force_pull_image on docker containerizer

out how to enable force_pull_image for > mesos-slave. There are hints here > <https://issues.apache.org/jira/browse/MESOS-1886> but still not clear to > me. > > Any additional hints appreciated. > > > -- Best Regards, Haosdent Huang

Re: 答复: mesos-go example scheduler doesn't work

Hi, could you show the associate logs in Mesos Agent? On Aug 19, 2016 5:49 PM, "志昌 余" wrote: > I ran a scheduler with a cluster (3 nodes) of mesos masters. The > "127.0,.0.1" in mesos log looks strange. (I guess mesos-go reported a wrong > IP to mesos?) > > So I

Re: Mesos python bindings

professional advisors, including those specializing in > legal, tax and accounting matters. Orchard does not provide legal, tax or > accounting advice. > -- Best Regards, Haosdent Huang

Do all the topics in MesosCon Asia share in English

Hi, MesosCon Aisa is accepting submissions now which close on September 9th. Do all the topics are supposed to be shared in English? Or accept sharing in Chinese as well? -- Best Regards, Haosdent Huang

Re: Using mesos' cfs limits on a docker container?

Personally, I suggest to use the approach @Joseph and @Avinash mentioned. Because zhitao and my patches require Docker >= 1.7.0 . On Mon, Aug 15, 2016 at 1:27 AM, haosdent <haosd...@gmail.com> wrote: > Not sure if this related to https://issues.apache.org/ > jira/browse/MESOS-2

Re: Using mesos' cfs limits on a docker container?

>>> Mark >>> -- >>> >>> Mark Hammons - +33 06 03 69 56 56 >>> >>> Research Engineer @ BioEmergences >>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__bioemergences.iscpif.fr=DQMFaQ=LNdz7nrxyGFUIUTz2qIULQ=cPg4mUupZEtURFK34GyDCtRjHoUmKrI7oHRZqAh3hZY=p3yjpxMelmcew1dQtqJniCFVDpbSbJQBXaW-mA1QVHU=hlyM8jpFaEkcQ5X8UJs0BTG53J2X6F-zEs0JIKxCFEQ=> >>> >>> Lab Phone: 01 69 82 34 19 >>> >> >> -- Best Regards, Haosdent Huang

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

rg/repos/dist/dev/mesos/1.0.1-rc1/mesos >> >> -1.0.1.tar.gz.md5 >> >> >> >> >> >> The signature of the tarball can be found at: >> >> >> >> https://dist.apache.org/repos/dist/dev/mesos/1.0.1-rc1/mesos >> >> -1.0.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-1155 >> >> >> >> >> >> Please vote on releasing this package as Apache Mesos 1.0.1! >> >> >> >> >> >> The vote is open until Mon Aug 15 17:29:33 PDT 2016 and passes if a >> >> majority of at least 3 +1 PMC votes are cast. >> >> >> >> >> >> [ ] +1 Release this package as Apache Mesos 1.0.1 >> >> >> >> [ ] -1 Do not release this package because ... >> >> >> >> >> >> Thanks, >> >> >> > >> > >> > > -- Best Regards, Haosdent Huang

Re: Master pailer failure 0.28.2

0)(anonymous function) @ >> angular-1.2.3.min.js:84(anonymous function) @ angular-1.2.3.min.js:62s @ >> angular-1.2.3.min.js:74$digest @ angular-1.2.3.min.js:99$apply @ >> angular-1.2.3.min.js:101f @ angular-1.2.3.min.js:67Q @ >> angular-1.2.3.min.js:71y.onreadystatechange @ angular-1.2.3.min.js:72 >> >> >> Has anyone seen this before? >> > -- Best Regards, Haosdent Huang

Re: Mesos logging

s using the Google Logging > > Library. > > Looking in the logs I only seem to be able to find output from VLOG > > statements. What do I need to do to get the output from the LOG > > statements? Where would I typically find the output? I'm using CentOS > > 7.2 and found the output so far in the files below /var/log/mesos. > > > > thanks, > > Hendrik > > > > -- Best Regards, Haosdent Huang

Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

Oh, it is because Homebrew still using Mesos 0.28.1. Open a pull request to update it to Mesos 1.0.0 just now. https://github.com/Homebrew/homebrew-core/pull/3704 Sorry for noise. On Mon, Aug 8, 2016 at 6:15 PM, haosdent <haosd...@gmail.com> wrote: > Hi, I noted that we have not yet upd

Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

orage" >>> header in the release post please? >>> >>> Great work otherwise everyone! >>> >>> >>> On Wednesday, July 27, 2016, Vinod Kone <vinodk...@apache.org> wrote: >>> >>>> Hi all, >>>> >>>>

Re: Parameters for the Docker Executor

ocumentation does > not show them with a = but if that works it would be good. What about > --oom-kill-disable and --read-only? > > On 06/08/16 10:52, haosdent wrote: > > Hi, @Hendrik All these parameters follow this form `--key=value`. For > > example, you could use > > &

Re: Parameters for the Docker Executor

ngs > --expose value > --ip string > --link value > --oom-kill-disable > --read-only > --security-opt value > > On 06/08/16 08:58, haosdent wrote: > > Hi, @Hendrik > > > > >which seems to be quite a restriction when looking at a

Re: Parameters for the Docker Executor

che/mesos/blob/master/include/mesos/mesos.proto > [2] https://github.com/apache/mesos/blob/master/src/docker/docker.cpp > -- Best Regards, Haosdent Huang

Re: Running a mesos executor within a container....

container > it was too small to contain the binaries I downloaded. > > Mark Edgar Hammons II - Research Engineer at BioEmergences > 0603695656 > > On 01 Aug 2016, at 03:57, haosdent <haosd...@gmail.com> wrote: > > >First, the binaries I get mesos to download into my sand

Re: Log the print out instead of print screen

f-0466 > I0801 10:53:56.31438820 sched.cpp:1911] Asked to stop the driver > I0801 10:53:56.31469024 sched.cpp:1143] Stopping framework > 'a8180ad8-5fb6-4696-bacf-462552ffe4ef-0466' > I0801 10:53:56.31511057 sched.cpp:1911] Asked to stop the driver > > > Thank you, > Bryan > -- Best Regards, Haosdent Huang

Re: never finish unresponsive tasks

Is there anyway that by default allocate unlimited memory to > tasks? Or its not even the root problem? > > Thank you, > Bryan > > -- Best Regards, Haosdent Huang

Re: Cadvisor and Mesos: cgroup monitoring

ces. > > > I will try snap with the plugin from Roger. > > > Thanks. > -- > *De :* haosdent <haosd...@gmail.com> > *Envoyé :* vendredi 29 juillet 2016 17:30:20 > > *À :* user > *Objet :* Re: Cadvisor and Mesos: cgroup monitorin

Re: Running a mesos executor within a container....

s - +33 06 03 69 56 56 > > Research Engineer @ BioEmergences <http://bioemergences.iscpif.fr> > > Lab Phone: 01 69 82 34 19 > -- Best Regards, Haosdent Huang

Re: [Mesos 2.0] Let's talk about the future

esos, basically you only >> ask an IP for your container, all port rules are managed directly via the >> tool), and current Docker bridge/user mode with Mesos is far more easy to >> setup/use. >> >> Olivier >> >> >> >> I would appreciate it if you could either share your ideas or vote on >> these items, and we will discuss it in next community sync. >> >> We may not have an unshakeable conclusion as container technology is >> evolving at an ever faster pace, but the whole community, especially >> newbies like myself, would profoundly benefit from a clear plan and >> priority for next 3-6 months. >> >> Cheers, >> /Jay >> >> >> > > > -- > Cheers, > > Zhitao Li > -- Best Regards, Haosdent Huang

Re: Cadvisor and Mesos: cgroup monitoring

to root `/`. > > Thanks for the answer. > -- > *De :* haosdent <haosd...@gmail.com> > *Envoyé :* vendredi 29 juillet 2016 16:21:07 > *À :* user > *Objet :* Re: Cadvisor and Mesos: cgroup monitoring > > >- is there a way to "lin

Re: Cadvisor and Mesos: cgroup monitoring

e a way to "link" the cgroup id to the mesos task id? > > > Thanks for any clue. > > > And a good sysadmin appreciation day! > > > Aurélien. > > -- Best Regards, Haosdent Huang

Re: [Mesos 2.0] Let's talk about the future

t; > We may not have an unshakeable conclusion as container technology is > evolving at an ever faster pace, but the whole community, especially > newbies like myself, would profoundly benefit from a clear plan and > priority for next 3-6 months. > > Cheers, > /Jay > > -- Best Regards, Haosdent Huang

Re: docker 'expose' integration

Docker integration support the EXPOSE directive in Dockerfiles? > > > What must be done in order to network docker containers properly? (Esp. > with the Aurora framework) > > > > Thank you! > > > -- Best Regards, Haosdent Huang

Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

support includes running > > containers > > > > with and without filesystem isolation (i.e. running both imageless > > > > > > containers as well as containers using a docker image). Frameworks > > must > > > > opt-in to receiving GPU resources via the GPU_RESOURCES framework > > > > > > capability (see the scarce resource problem in MESOS-5377). We > > support > > > > 'nvidia-docker'-style docker containers by injecting a volume that > > > > > > contains the Nvidia libraries / binaries when the docker image has > > > > > > the 'com.nvidia.volumes.needed' label. Support for the docker > > > > > > containerizer will come in a future release. > > > > > > > > * [MESOS-5724] - SSL certificate validation allows for additional IP > > address > > > > subject alternative name extension verification. > > > > 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.0.0-rc4 > > > > > > > > > > > > > The candidate for Mesos 1.0.0 release is available at: > > > > > https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc4/mesos-1.0.0.tar.gz > > > > > > The tag to be voted on is 1.0.0-rc4: > > > > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.0.0-rc4 > > > > > > The MD5 checksum of the tarball can be found at: > > > > > > > https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc4/mesos-1.0.0.tar.gz.md5 > > > > > > The signature of the tarball can be found at: > > > > > > > https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc4/mesos-1.0.0.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-1153 > > > > > > Please vote on releasing this package as Apache Mesos 1.0.0! > > > > > > [ ] +1 Release this package as Apache Mesos 1.0.0 > > > > [ ] -1 Do not release this package because ... > > > > > > Thanks, > > > -- Best Regards, Haosdent Huang

Re: Releasing a Scala API for Mesos

t regards, > > Attila Szarvas > Research Engineer > Nokia Bell Labs, Budapest -- Best Regards, Haosdent Huang

Re: mesos crash

nt server > > > -- 原始邮件 ------ > *发件人:* "haosdent";<haosd...@gmail.com>; > *发送时间:* 2016年7月19日(星期二) 下午5:05 > *收件人:* "user"<user@mesos.apache.org>; > *主题:* Re: mesos crash > > Hi, > >I start two master node : &g

Re: Marathon endpoint link and host networking

? > > Is anyone else experiencing the same issue? > > I'm running the following mesos/marathon version on centos 7u2: > > [root@cluster1-headnode1 ~]# rpm -qa |grep -Ew 'mesos|marathon' > marathon-1.1.1-1.0.472.el7.x86_64 > mesos-0.28.1-2.0.20.centos701406.x86_64 > > Thanks in advance. > > Cheers, > Matteo > > -- Best Regards, Haosdent Huang

Re: mesos crash

eferEEUlS1_E_E9_M_invokeERKSt9_Any_dataS1_ > @ 0x4a4833 std::function<>::operator()() > @ 0x49f0eb > > _ZN7process8internal3runISt8functionIFvRKSsEEJS4_EEEvRKSt6vectorIT_SaIS8_EEDpOT0_ > @ 0x7fe6f9176ecc process::Future<>::fail() > @ 0x7fe6f916feac process::Promise<>::fail() > > > > error logs is > Log file created at: 2016/07/19 11:50:25 > Running on machine: oss-mesos-master-bjc-001 > Log line format: [IWEF]mmdd hh:mm:ss.uu threadid file:line] msg > F0719 11:50:25.262277 5381 master.cpp:1662] Recovery failed: Failed to > recover registrar: Failed to perform fetch within 2mins > can you help me.thanks > -- Best Regards, Haosdent Huang

Re: [VOTE] Release Apache Mesos 1.0.0 (rc2)

+1 Tested on CentOS 7. - sudo make check - upgrade from 0.28.2 to 1.0.0-rc2 On Fri, Jul 15, 2016 at 7:47 PM, Alex Rukletsov <a...@mesosphere.com> wrote: > Haosdent investigated the issue, and it seems that health checks do work > for docker executor. Hence I retract my n

Re: scp with mesos fetcher

> Bryan > -- Best Regards, Haosdent Huang

Re: Return a vector value from custom executor

hat is the best practice to have a custom executor to return large size > (~200mb) value (e.g. matrix array, or numpy array) ? > > B.R > Bryan > -- Best Regards, Haosdent Huang

Re: Escaped characters in the 'env' argument passed to mesos-execute

. > > > Thanks, > June Taylor > System Administrator, Minnesota Population Center > University of Minnesota > > On Thu, Jun 30, 2016 at 12:28 PM, Chris Baker <ch...@galacticfog.com> > wrote: > >> +1 >> >> On Thu, Jun 30, 2016 at 1:15 PM haosden

Re: Escaped characters in the 'env' argument passed to mesos-execute

be 1 string >>> value for the --command parameter? >>> >>> --command=/home/john/anaconda3/bin/python /home/john/mesos/error_msg.py >>> read >>> >>> Similarly how is the shell to know that you *don't* want to end this >>> command and start a new

  1   2   3   4   5   >