[no subject]
Hello to all users, contributors and Committers! The Travel Assistance Committee (TAC) are pleased to announce that travel assistance applications for Community over Code EU 2024 are now open! We will be supporting Community over Code EU, Bratislava, Slovakia, June 3th - 5th, 2024. TAC exists to help those that would like to attend Community over Code events, but are unable to do so for financial reasons. For more info on this years applications and qualifying criteria, please visit the TAC website at < https://tac.apache.org/ >. Applications are already open on https://tac-apply.apache.org/, so don't delay! The Apache Travel Assistance Committee will only be accepting applications from those people that are able to attend the full event. Important: Applications close on Friday, March 1st, 2024. Applicants have until the the closing date above to submit their applications (which should contain as much supporting material as required to efficiently and accurately process their request), this will enable TAC to announce successful applications shortly afterwards. As usual, TAC expects to deal with a range of applications from a diverse range of backgrounds; therefore, we encourage (as always) anyone thinking about sending in an application to do so ASAP. For those that will need a Visa to enter the Country - we advise you apply now so that you have enough time in case of interview delays. So do not wait until you know if you have been accepted or not. We look forward to greeting many of you in Bratislava, Slovakia in June, 2024! Kind Regards, Gavin (On behalf of the Travel Assistance Committee)
[no subject]
Anyone maybe knows if it is possible to add 'host route' with the default cni plugins, something like this: ip route add 192.168.10.153/32 dev eth0
[no subject]
Hi all, I'm considering creating an "Operations Working Group". It could focus on making Mesos clusters easier to manage, deploy, and operate. Some possible topics that could be discussed in the working group: - Best practices for operating a Mesos cluster - Packaging - Tools to deploy, upgrade, and operate Mesos clusters (Puppet, Saltstack, Terraform, Mesos CLI, etc.) - Observability through metrics, logging, and debug/information endpoints Please let me know if you think that such a working group would be useful for the community and if you would be interesting in joining its meetings. Thanks! -Gastón
[no subject]
Resolved on my own!
[no subject]
Hello!, I'm using the follow marathon script [1] to launch cassandra non-seeds nodes, it is working properly. [1] - http://hastebin.com/visujikela.lua As you can see in the script, I'm limiting CPU and Memory. But some nodes of my cluster is not that big, even because the cluster isn't big yet. As we know, cassandra generally uses a lot of memory as cache etc.. 1) I would like to know if Mesos will kill (and keep killing) Cassandra process if it reach the memory limit? if Yes, how can I block Mesos from kill it? 2) If I have one server with 4gb memory where I deployed Mesos Slave, and I create a container (by using marathon) with mem=1024 (for example) the processing within that container, when they ask about the memory available, they will receive 4gb or 1gb? Thank you! -- Rafael Capucho Bachelor of Computer Science Federal University of São Paulo Institute of Science and Technology - ICT PGP-Public Key: 2048R/7389A96F pgp.mit.edu FP: EDB5 CDEE 8442 99CC C92D 9173 6B32 A5C9 7389 A96F
[no subject]
Hi Aaron, You can set memory in /etc/mesos-slave/resources example: cpus(*):4;mem(*):16067;ports(*):[80-80,31000-32000] with this configuration mesos offers 15.7GB RAM on one of our nodes. 2015-05-21 12:51 GMT+02:00 Aaron Carey : > I've managed to increase the disksize by playing with some docker > options, > > Anyone have any idea about the memory? > > Thanks, > Aaron > > -- > *From:* Aaron Carey [aca...@ilm.com] > *Sent:* 21 May 2015 11:19 > *To:* user@mesos.apache.org > *Subject:* How slaves calculate resources > > Hi, > > I was just trying to figure out how Mesos slaves report the amount of > resources available to them on the host? > > We have some slaves running on AWS t2.medium machines (2cpu, 4Gb RAM) with > 32GB disks. > > The slaves are running inside docker containers. > > They report 2 cpus (correct), 2.5GB RAM and 4.9GB disk. > > Any ideas why this is different from what I can see on the machine? (both > on the host and within the slave docker container)? > > Thanks, > Aaron >
[no subject]
J. Sai Sagar Associate Engineer, Innovation Labs Impetus - Bangalore