Re: mesos git commit: Added documentation for access_sandboxes and access_mesos_logs acls.

Sorry guys, that was an oversight. I added reviews: https://reviews.apache.org/r/48310/ - Fixes some endpoint spaces in docs. https://reviews.apache.org/r/48311/ - Result of running the script. > On 06 Jun 2016, at

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

Hi Vinod, In convert.cpp we compare the major versions of the native library and the jar. This makes upgrading frameworks unnecessarily hard because you would have to deploy Mesos and frameworks in lockstep.

Re: mesos/kafka issues (reviving old thread)

Vinod, In my case, have two vagrant VMs, one where mesos-master runs and frameworks on another. This is my dev/debug setup where both marathon and kafka frameworks are failing not just kafka. But we do have a real (bare metal machines cluster) running marathon successfully but kafka framework

Re: mesos/kafka issues (reviving old thread)

Right, mentioning ZK may have been a distraction. My point was that the inactive mesos-master on the host running kafka-mesos scheduler is communicating with the active mesos-master. To elaborate, this problem currently arises when a mesos-master failover occurs. If I shut off the active

Re: Mesos HA does not work (Failed to recover registrar)

@Qian, I think you're running issues with firewall, did you make sure your master can reach from each other? FROM master A $ telnet B 5050 I think it fail to connect. Please ensure shutdown any firewall. -- Thanks, Chengwei On Mon, Jun 06, 2016 at 09:06:43PM +0800, Qian Zhang wrote: > I

Re: Mesos 0.24.1 on Raspberry Pi 3

Cool stuff Andrew, thanks for sharing! On Thu, Jun 2, 2016 at 11:50 AM, Andrew Spyker wrote: > FYI, based on the work others have done in the past, Netflix was able to > get Mesos agent building and running on Raspberry Pi natively and under > Docker containers.

Re: Status acknowledgements in MesosExecutor

Hi Evers, Thanks for taking this on. Vinod has agreed to shepherd this and I would be happy to be the initial reviewer for the patches. -anand > On Jun 1, 2016, at 10:27 AM, Evers Benno wrote: > > Some more context about this bug: > > We did some tests with a

Re: [C++11] Please use `nullptr`!

Thanks Tomasz! Does the style checker now catch NULL introductions? On Mon, Jun 6, 2016 at 2:12 PM, Michael Park wrote: > Hello, > > Tomasz Janiszewski kindly started the initiative on the migration to > `nullptr`, and we have closed MESOS-3243 >

Re: mesos git commit: Added documentation for access_sandboxes and access_mesos_logs acls.

Good point. Vinod was working on the endpoints script right next to me, but I guess he did his pre-release run before I committed Alexander's change. We'll have to do another run before rc2. On Mon, Jun 6, 2016 at 5:36 AM, Neil Conway wrote: > FYI, this commit should have

Re: 0.28.2 has been released

Hi Craig, I should be sending out a link to the RPM packages in a couple of days. (Our packaging scripts had some issues and I am working on fixing them). Kapil On Mon, Jun 6, 2016 at 6:15 AM, craig w wrote: > Jie, > > Thanks for the updates. When will the packages be

[C++11] Please use `nullptr`!

Hello, Tomasz Janiszewski kindly started the initiative on the migration to `nullptr`, and we have closed MESOS-3243 . The existing instances of `NULL` have been replaced with `nullptr`, and any new or remaining instances of `NULL` are bugs.

Re: mesos/kafka issues (reviving old thread)

ZK communication is little different from framework communication. In the former case, the ZK client library inside master opens up a connection to the ZK server ensemble. In the latter case, the scheduler driver inside the framework scheduler opens up a connection to the mesos master. But it is

Re: mesos/kafka issues (reviving old thread)

inline On 6/6/16, 8:40 AM, "Vinod Kone" wrote: >Have you tried running a different framework than the kafka one (maybe >marathon? or chronos?) to rule out framework related issues? I'm surprised >that it works when the scheduler and master are on the same host but not

Re: mesos/kafka issues (reviving old thread)

Hiya Vinit, I’ve made some progress, I have a conditionally working setup, and another setup which was working now failing in new ways. It does sound like your captures are similar to mine, what I found is that if I run the scheduler on, say, zk01 (which is also a mesos-master), while it is

Re: 0.28.2 has been released

Jie, Thanks for the updates. When will the packages be available (in particular RPM)? -craig On Sun, Jun 5, 2016 at 2:31 PM, Jie Yu wrote: > Hi folks, > > I just released Mesos 0.28.2 and updated the website. > > It includes some important bug fixes. The change log can be

Re: mesos/kafka issues (reviving old thread)

inline On 6/3/16, 2:19 PM, "Vinit Mahedia" wrote: >Justin, >Yeah - as long as everything is on a single box (mesos-kafka scheduler, >mesos-master, zk etc.) >things work just fine, which is what I meant by local setup. > > >I did a local cluster setup as well, 3 vagrant

Re: Proposal: move content in Wiki to docs in code repo

Works for me. Some things we might miss from wiki would be comments and ability to watch for updates; but I don't think many people use them. On Mon, Jun 6, 2016 at 3:15 PM, Gilbert Song wrote: > +1. > > At least I personally rarely touch the wiki. > > Gilbert > > On Mon,

Re: Proposal: move content in Wiki to docs in code repo

+1. At least I personally rarely touch the wiki. Gilbert On Mon, Jun 6, 2016 at 11:51 AM, Zhou Z Xing wrote: > +1 > > It's good idea to collect and gather every thing in one single repo, would > be easier for users to find out. > > Thanks & Best Wishes, > > Tom Xing(邢舟) >

Re: Proposal: move content in Wiki to docs in code repo

+1 It's good idea to collect and gather every thing in one single repo, would be easier for users to find out. Thanks & Best Wishes, Tom Xing(邢舟) Emerging Technology Institute, IBM China Software Development Lab -- IBM China Software Development Laboratory (CSDL) Notes

Re: Proposal: move content in Wiki to docs in code repo

+1 For a long time I didn't knew that wiki exists. It's hidden from a new users and search engines - I remember only one place where it's linked in docs. I can help with move. pon., 6.06.2016, 20:29 użytkownik Jie Yu napisał: > Hi folks, > > I am proposing moving our

Re: Proposal: move content in Wiki to docs in code repo

+1 I think moving the wiki into docs would make information about working groups, release tracking first class citizens and help disseminate information better. On Mon, Jun 6, 2016 at 11:29 AM, Jie Yu wrote: > Hi folks, > > I am proposing moving our content in Wiki (e.g.,

Proposal: move content in Wiki to docs in code repo

Hi folks, I am proposing moving our content in Wiki (e.g., working groups, release tracking, etc.) to our docs in the code repo. I personally found that wiki is hard to use and there's no reviewing process for changes in the Wiki. The content in Wiki historically received less attention than that

Re: Mesos installation in cloud network fails when zookeeper elects a master with internal ip

>Here I am facing another issue in mesos master installation. I am passing > internal ip address to /etc/mesos-master/hostname and ip files in each > master node. > > my hostname and ip file looks like: > 10.40.0.128 Hi, @Pankaj You could not use same hostname and ip in each master node. Instead,

Re: Mesos HA does not work (Failed to recover registrar)

Hi, @Qian Zhang Your issue reminds me of this http://search-hadoop.com/m/0Vlr69BZgz1NlAPP1=Re+Mesos+Masters+Leader+Keeps+Fluctuating which I could not reproduce in my env. I am not sure whether your case are same with Stefano or not. On Mon, Jun 6, 2016 at 9:06 PM, Qian Zhang

Re: [MesosCon][Slides] Any slides sharing plan for MesosCon

Great! Thanks Artem :D On Monday, June 6, 2016, Artem Harutyunyan wrote: > Hi Guangya, > > You should see the slides if you go to individual talk pages, like this one > [0] > < >

Re: mesos/kafka issues (reviving old thread)

Have you tried running a different framework than the kafka one (maybe marathon? or chronos?) to rule out framework related issues? I'm surprised that it works when the scheduler and master are on the same host but not when they are different. Looks like the request packets are getting dropped

Re: [MesosCon][Slides] Any slides sharing plan for MesosCon

Hi Guangya, You should see the slides if you go to individual talk pages, like this one [0] . Some of the speakers have uploaded their slides to Sched.

Re: Mesos HA does not work (Failed to recover registrar)

I deleted everything in the work dir (/var/lib/mesos/master), and tried again, the same error still happened :-( Thanks, Qian Zhang On Mon, Jun 6, 2016 at 3:03 AM, Jean Christophe “JC” Martin < jch.mar...@gmail.com> wrote: > Qian, > > Zookeeper should be able to reach a quorum with 2, no need

Re: mesos git commit: Added documentation for access_sandboxes and access_mesos_logs acls.

FYI, this commit should have included the changes produced by re-running the `generate-endpoint.py` script. Neil On Wed, Jun 1, 2016 at 8:26 AM, wrote: > Repository: mesos > Updated Branches: > refs/heads/master 5263a6211 -> 53b5164bb > > > Added documentation for

Re: Mesos Coverity Scan

There is an issue from the coverity scan preventing us to build/check Mesos correctly (see answer from coverity team below). I will keep you posted on the progress here. "This is a known issue which required a fix by devs in the upcoming 8.1 release. This should be integrated into SCAN over the

Re: WebUI authentication in 1.0.0-rc1

Hi, thanks for the pointer. For people having the same problem, it seems that you have to actually provide six new ACL rules to restore the previous behaviour: get_endpoints, view_frameworks, view_tasks, view_executors, access_sandboxes, and access_mesos_logs. On 03.06.2016 21:59, Michael Park

Rack awareness support for Mesos

Hi, Mesos folks I've been thinking about Mesos rack awareness support for a while, it's a common interest for lots of data center applications to provide data locality, fault tolerance and better task placement. Create MESOS-5545 to track the story, and here is the initial design doc [1] to