date:20160319

What are the invalid-user.log files?

2016-03-19 Thread Peter Steele

I'm testing out mesos for the first time and after installing the 
software I'm seeing numerous log files of the form


mesos-slave..invalid-user.log.INFO.20160317-062640.918

I don't see any errors in the logs themselves, but the fact that 
"invalid-user" is part of the name makes me think I'm missing something 
in my config. The mesos-master.WARNING log has the message


W0317 06:26:41.178268   915 authenticator.cpp:511] No credentials 
provided, authentication requests will be refused


which I'm thinking might be related. What am I missing?

Peter

Re: Unstability on Mesos 0.27

2016-03-19 Thread Guillermo Rodriguez

Hi,

 I have reported all my problems already. That's why I installed 0.27.2 and I'm 
waiting for 0.28 because I see many solutions there.

 The lastest crash I was unable to identify. There were no logs at all of any 
error. I just know marathon and mesos decided to shutdown at the same time. I 
guess marathon won't crash mesos but crashing mesos will crash marathon.

 Will report if I see this again.

 Luck!




 From: "Jie Yu" 
Sent: Friday, March 18, 2016 2:48 AM
To: "user" , gu...@spritekin.com
Cc: "Gabriel Menegatti" 
Subject: Re: Unstability on Mesos 0.27
 Thanks for reporting! Can you be more specific about which component crashes a 
lot? Is it the framework, the master, the agent, or the executor. As Artem and 
Vinod mentioned, it'll be really helpful if you can provide the relevant log 
(master/agent/executor's log) so that we can pinpoint the issue.
 - Jie   On Thu, Mar 17, 2016 at 1:45 AM, Guillermo Rodriguez 
 wrote:   Update to 0.27.2 or wait for 0.28.0.

 I experienced many crashes as well with 0.27.1 due to crashes in the 
frameworks bringing down the whole cluster (swarm specially). Also problems in 
the resource precision that also crashed the servers and crashes when nodes 
disconnected.

 I really found 0.27 very unstable.

 Many of this problems were solved for 0.27.2 and my latest environment has 
proven way more stable. It is still not fully stable as the cluster crashed 
yesterday due to a crash in marathon, but way better overall and quick to 
recover.

 Luck!
 Guimo




 From: "Klaus Ma" 
Sent: Thursday, March 17, 2016 1:36 PM
To: user@mesos.apache.org
Cc: "Gabriel Menegatti" 
Subject: Re: Unstability on Mesos 0.27
If Mesos daemon crashed, I'd suggest to log a JIRA and append more detail, 
e.g. steps, master/agent log.

   
 Da (Klaus), Ma (??) | PMP® | Advisory Software Engineer  Platform OpenSource 
Technology, STG, IBM GCG  +86-10-8245 4084 | klaus1982...@gmail.com | 
http://k82.me

 On Thu, Mar 17, 2016 at 8:26 AM, Vinod Kone  wrote:  
  Hey Gabriel,
   Could you share more details on what the crashes are and what your setup is 
(docker containerizer?). Any logs (master, agent, application) that can shed 
light would be useful to diagnose.
 On Wed, Mar 16, 2016 at 5:12 PM, Alfredo Carneiro 
 wrote: Hello guys,

 I am using Mesos 0.27 with different kinds of applications, such as, crawlers, 
databases and websites. However, I have faced many crashes and I couldn't find 
what it is the matter.

 We have 14 machines with 8Gb of ram and 4 cpu each. Usually, we run about 40 
instance of our crawler, which they start stopping of nowhere (but the 
containers keep running). The day before yesterday we decided try to test our 
entire infrastrcuture and we scaled our crawler up to 110 instances. 
Unfortunately, today we've faced a big crash that affected mainly our crawler 
and our databases.

 So, I am wondering if anyone else have the same problem, such as apps which 
crashes of nowhere or something else which could be related to some unstability 
on Mesos.

 --
 Alfredo Miranda

Re: verbose logging with the docker executor

2016-03-19 Thread James Peach

> On Mar 17, 2016, at 10:09 AM, Clarke, Trevor  wrote:
> 
> Looking in the docker executor, the docker command line is logged with 
> VLOG(1) but I'm not sure how to generate that level of log output. Some 
> googling suggests it's used in the google logging library and verbose logging 
> would be enabled with something like --v=1 but that's not a valid mesos-slave 
> option. Can someone point me in the right direction? (currently using 0.24.1)

You can set the GLOG_v environment variable (see 
https://google-glog.googlecode.com/svn/trunk/doc/glog.html#verbose) to the 
desired verbosity level and then restart mesos-slave. If you just want to 
increase the log level without a restart, you can hit the /logging/toggle 
endpoint on the mesos-slave (do curl http://127.0.0.1:5051/help/logging/toggle 
for the online help).

J

Re: What are the invalid-user.log files?

2016-03-19 Thread haosdent

Not sure why glog could not get USER environment variable correctly after
looking its code. But should not affect you running mesos.

On Fri, Mar 18, 2016 at 1:11 AM, haosdent  wrote:

> root should be fine.
>
> On Fri, Mar 18, 2016 at 12:53 AM, Peter Steele  wrote:
>
>> My USER var is root. Do I need to create a non-root user for mesos to run
>> under?
>>
>>
>> On 03/17/2016 09:22 AM, haosdent wrote:
>>
>> glog get the user name by environment variable "USER" in Linux.
>> https://github.com/google/glog/blob/master/src/utilities.cc#L290-L302 I
>> think you could check the environment variable "USER" before you start
>> Mesos slave.
>>
>> On Fri, Mar 18, 2016 at 12:19 AM, haosdent  wrote:
>>
>>> invalid-user is from glog
>>> 
>>> https://github.com/google/glog/blob/master/src/logging.cc#L1036
>>>
>>> >W0317 06:26:41.178268   915 authenticator.cpp:511] No credentials
>>> provided, authentication requests will be refused
>>> >which I'm thinking might be related. What am I missing?
>>>
>>> I think should not related. This is a warning message if you don't pass
>>> `credentials` flag when start mesos master.
>>>
>>> On Thu, Mar 17, 2016 at 10:07 PM, Peter Steele < 
>>> pste...@peaxy.net> wrote:
>>>
 I'm testing out mesos for the first time and after installing the
 software I'm seeing numerous log files of the form

 mesos-slave..invalid-user.log.INFO.20160317-062640.918

 I don't see any errors in the logs themselves, but the fact that
 "invalid-user" is part of the name makes me think I'm missing something in
 my config. The mesos-master.WARNING log has the message

 W0317 06:26:41.178268   915 authenticator.cpp:511] No credentials
 provided, authentication requests will be refused

 which I'm thinking might be related. What am I missing?

 Peter


>>>
>>>
>>> --
>>> Best Regards,
>>> Haosdent Huang
>>>
>>
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>
>>
>>
>
>
> --
> Best Regards,
> Haosdent Huang
>



-- 
Best Regards,
Haosdent Huang

Re: HTTP API

2016-03-19 Thread Vinod Kone

Thanks for the interest!

We are actively working to make the Framework v1 API stable. We've made
quite a few improvements/fixes to the Scheduler v1 API since 0.24.0. We've
also introduced Executor v1 API in 0.28.0. Both are in *experimental* state.

There are still things left to do to make the Framework v1 API production
ready. Please refer to MESOS-3302
 and MESOS-4855
 for specifics.  Can you
help contributing to any of these?

Other than the issues listed above, we like frameworks to start testing
this API in their staging/testing clusters. This would give us the most
confidence to call it production ready. Can you help?

I'm very optimistically hoping to get this ready by MesosCon Denver, but we
need more help for it to be a realistic deadline. If any one is willing to
help, please reach out to me. I promise to give you my time and shepherd
your contributions.

Thanks,

On Wed, Mar 16, 2016 at 1:38 PM, Zameer Manji  wrote:

> +1
>
> I am also interested in knowing the state of the HTTP API. I have heard
> that it stabilizing the API might be tied with Mesos 1.0 but I don't have a
> source for that. Can a PMC member comment on what the plan is?
>
> On Mon, Mar 14, 2016 at 2:30 PM, Dario Rexin  wrote:
>
>> Hi all,
>>
>> since the introduction of the HTTP API in 0.24 around 7.5 months have
>> passed. What are the plans to make this API stable? There are already
>> features (inverse offers) that are exclusively available through this API,
>> so it would be great to have a timeline, as I think for most people it’s
>> impossible to use experimental features in production.
>>
>> Thanks,
>> Dario
>>
>> --
>> Zameer Manji
>>
>>

Re: Deploying mesos software

2016-03-19 Thread Chris Baker

Peter,

I've had success packaging my own RPMs for Centos 6 and 7 using the
following:
https://github.com/mesosphere/mesos-deb-packaging
In my particular case, I use it to package custom-built versions of mesos.

Chris

On Tue, Mar 15, 2016 at 5:58 PM Peter Steele  wrote:

> Ah, I was apparently looking in the wrong place. This looks more like what
> I need. Thanks very much.
>
>
> Peter
>
>
> On 03/15/2016 02:40 PM, Avinash Sridharan wrote:
>
> There are Mesos packages available for various distributions at the
> Mesosphere download page.
>
> Would this work ?
> https://mesosphere.com/downloads/
>
>
>
> On Tue, Mar 15, 2016 at 2:37 PM, Peter Steele  wrote:
>
>> I've just downloaded and built mesos for the first time. Once we figure
>> things out, we'll want to install the mesos software on hardware different
>> than where it is built. Ordinarily we'd have binary only tarballs for the
>> software we're installing on our servers but there doesn't appear to be a
>> binary only distribution available yet. What's the recommended way to build
>> in one place and install in another?
>>
>> Peter
>>
>>
>
>
> --
> Avinash Sridharan, Mesosphere
> +1 (323) 702 5245
>
>
>

Re: Resource Isolation per Framework

2016-03-19 Thread Pradeep Chhetri

Hello haosdent,

Perfect, then i guess that should solve my issue. I will configure things
and see if it is working as expected or not.

Cheers.

On Fri, Mar 18, 2016 at 3:20 PM, haosdent  wrote:

> Seems common is not necessary in your case. The resources without role
> would share cross all frameworks.
>
> On Fri, Mar 18, 2016 at 9:43 PM, Pradeep Chhetri <
> pradeep.chhetr...@gmail.com> wrote:
>
>> Hello All,
>>
>> I am looking for ways to isolate resources per framework basis. Basically
>> what i want to achieve is segregating machines on which tasks from a
>> framework can run and having a common set of machines which can be shared
>> across all frameworks. So I can think of assigning one role per framework
>> and one role as common for all frameworks. In my case, I will be having
>> roles: marathon, storm, jenkins, spark & common.
>>
>> From Roles & ACLs documentation: I can see that I can assign these roles
>> to mesos agents and define ACLs to allow frameworks to register with mesos
>> master with particular roles.
>>
>> I have few questions:
>>
>> 1. Can I configure a mesos agent to be associated with multiple roles. I
>> can see that there is a parameter --default-role to assign role to a mesos
>> slave but I am not sure whether we can pass multiple roles as value.
>>
>> 2. From ACL documentation, I can provide authorization to a framework so
>> that it can register with multiple roles like this:
>>
>>
>>1.
>>
>> {
>>   "register_frameworks": [
>>{
>>  "principals": {
>>"values": ["marathon"]
>>  },
>>  "roles": {
>>"values": ["marathon", "common"]
>>  }
>>}
>>  ]
>> }
>>
>>
>>
>> But I don't think if we can register a framework to mesos master with
>> multiple roles. I can see this open issue regarding this:
>> https://issues.apache.org/jira/browse/MESOS-1763
>>
>> Can someone provide me some alternative way regarding what i am trying to
>> achieve.
>>
>> --
>> Regards,
>> Pradeep Chhetri
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>



-- 
Regards,
Pradeep Chhetri

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

2016-03-19 Thread Vinod Kone

+1 (binding)

Tested on ASF CI.

On Sun, Mar 13, 2016 at 4:33 PM, Michael Park  wrote:

> +1 (binding)
>
> Internal CI results with the corresponding JIRA tickets for the failed
> tests:
>
> CentOS 6 (non-SSL):
>   - MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward
> (MESOS-3049 )
>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> (MESOS-4039 )
>   - UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 )
>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
> (MESOS-3215 )
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 ,
> MESOS-4053 )
>
> CentOS 6 (SSL):
>   - MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward
> (MESOS-3049 )
>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> (MESOS-4039 )
>   - UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 )
>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
> (MESOS-3215 )
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 ,
> MESOS-4053 )
>
> CentOS 7 (non-SSL):
>   - LimitedCpuIsolatorTest.ROOT_CGROUPS_Pids_and_Tids
> (MESOS-4677 )
>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> (MESOS-4039 )
>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
> (MESOS-3215 )
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 ,
> MESOS-4053 )
>
> CentOS 7 (SSL):
>   - FetcherCacheTest.RemoveLRUCacheEntries
> (MESOS-4156 )
>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> (MESOS-4039 )
>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
> (MESOS-3215 )
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 ,
> MESOS-4053 )
>
> Debian 8 (non-SSL): Success!
> Debian 8 (SSL): Failed with MESOS-2017
> 
>
> Ubuntu 12 (non-SSL):
> Ubuntu 12 (SSL):
> Ubuntu 14 (non-SSL):
> Ubuntu 14 (SSL):
>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 )
>
> Ubuntu 15 (non-SSL): Success!
> Ubuntu 15 (SSL): Success!
>
> On 13 March 2016 at 18:43, Michael Park  wrote:
>
> > While the vote for this release was open until Fri Mar 11 23:59:59 EST
> > 2016,
> > I'm going to give it another 3 days since there has not been any -1
> votes.
> >
> > The vote is extended until Wed Mar 16 23:59:59 EST 2016.
> >
> > On 10 March 2016 at 12:40, Michael Park  wrote:
> >
> >> Thanks Greg!
> >>
> >> On 10 March 2016 at 12:32, Greg Mann  wrote:
> >>
> >>> +1 (non-binding)
> >>>
> >>> Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL
> >>> enabled. All tests pass.
> >>>
> >>> I was also able to successfully test a simple upgrade scenario from
> >>> 0.25.1-rc2 to 0.26.1-rc2 using the script found here:
> >>> https://reviews.apache.org/r/44229/
> >>>
> >>> Cheers,
> >>> Greg
> >>>
> >>>
> >>> On Tue, Mar 8, 2016 at 7:48 PM, Michael Park  wrote:
> >>>
>  Hi all,
> 
>  Please vote on releasing the following candidate as Apache Mesos
> 0.26.1.
> 
> 
>  0.26.1 includes the following:
> 
> 
> 
> 
>  The only diff with RC1 is the following: Fix CGROUPS_ROOT_* tests on
>  systemd platforms.
>  <
> https://github.com/apache/mesos/commit/a896cda4aa8bb9c9bbfba20dda4b68df8dbdf569
> >
>  This patch is necessary in order to make the `systemd` integration
> work
>  correctly.
>  It was part of

Re: Vote on #MesosCon proposals, deadline Friday March 25

2016-03-19 Thread David Greenberg

Hi Jay,

Thanks for your feedback! The reason we're asking for you to rank the
topics is that this will allow us to better understand everyone's relative
preferences--next, we'll use standard voting algorithms to determine the
schedule, to ensure most people get as many talks they want as possible. We
hope you enjoy the program we come up with :)

Thanks,
David

On Sat, Mar 19, 2016 at 12:39 AM Jay JN Guo  wrote:

> Hi,
>
> Thank you for this good work and I'm already looking forward to this
> MesosCon.
>
> Although one minor suggestion here, Accept/Reject on a scale of 10 is a
> bit intimidating. Personally, I only have three feeling toward a topic:
> will go/maybe/not interested, whereas quantifying these feeling into a
> scale of 10 for 154 topics is just too much. Maybe we could simplify the
> form in the future. We could take OpenStack summit voting form as an
> example.
>
> Cheers,
> /J
>
> - Original message -
> From: Kiersten Gaffney 
> To: d...@mesos.apache.org, user@mesos.apache.org
> Cc: David Greenberg , Dave Lester <
> d...@davelester.org>, Kiersten Gaffney 
> Subject: Vote on #MesosCon proposals, deadline Friday March 25
> Date: Sat, Mar 19, 2016 8:11 AM
>
>
> Please take a few minutes the next few days and review what members of the
> community have submitted!
>
> Voting forms close Friday, March 25, 2016, 11:55 PST
>
> A total of 154 proposals were submitted in time for #MesosCon review, up
> significantly from 63 submitted for last year’s conference. Similar to last
> year, the MesosCon program committee is opening these proposals up for
> community review/feedback to better-inform our decisions about what should
> be included in the program.
>
> In order to make it easier to review a subset of the proposals, we’ve
> segmented them based upon two loose themes: Developer and Users.
>
> Developers: http://bit.ly/1RpZPvj
>
> Talks on how frameworks can be used, developed, and integrate with Mesos.
>
> Users: http://bit.ly/1Mspaxp
>
> A combination of talks that are use cases (how company x uses Mesos), and
> operations-focused (how we deploy x, use Docker, etc).
>
> The forms above also include an opportunity to indicate which sessions you
> didn't see proposed but would like to attend.
>
> Thanks in advance for your participation!
>
> Kiersten, Dave, and David (Program Committee)
>
>

Re: Unstability on Mesos 0.27

2016-03-19 Thread Jie Yu

Thanks for reporting! Can you be more specific about which component
crashes a lot? Is it the framework, the master, the agent, or the executor.
As Artem and Vinod mentioned, it'll be really helpful if you can provide
the relevant log (master/agent/executor's log) so that we can pinpoint the
issue.

- Jie

On Thu, Mar 17, 2016 at 1:45 AM, Guillermo Rodriguez 
wrote:

> Update to 0.27.2 or wait for 0.28.0.
>
> I experienced many crashes as well with 0.27.1 due to crashes in the
> frameworks bringing down the whole cluster (swarm specially). Also problems
> in the resource precision that also crashed the servers and crashes when
> nodes disconnected.
>
> I really found 0.27 very unstable.
>
> Many of this problems were solved for 0.27.2 and my latest environment has
> proven way more stable. It is still not fully stable as the cluster crashed
> yesterday due to a crash in marathon, but way better overall and quick to
> recover.
>
> Luck!
> Guimo
>
>
> --
> *From*: "Klaus Ma" 
> *Sent*: Thursday, March 17, 2016 1:36 PM
> *To*: user@mesos.apache.org
> *Cc*: "Gabriel Menegatti" 
> *Subject*: Re: Unstability on Mesos 0.27
>
> If Mesos daemon crashed, I'd suggest to log a JIRA and append more detail,
> e.g. steps, master/agent log.
>
> 
> Da (Klaus), Ma (??) | PMP® | Advisory Software Engineer
> Platform OpenSource Technology, STG, IBM GCG
> +86-10-8245 4084 | klaus1982...@gmail.com | http://k82.me
>
> On Thu, Mar 17, 2016 at 8:26 AM, Vinod Kone  wrote:
>>
>> Hey Gabriel,
>>
>> Could you share more details on what the crashes are and what your setup
>> is (docker containerizer?). Any logs (master, agent, application) that can
>> shed light would be useful to diagnose.
>>
>> On Wed, Mar 16, 2016 at 5:12 PM, Alfredo Carneiro <
>> alfr...@simbioseventures.com> wrote:
>>>
>>> Hello guys,
>>>
>>> I am using Mesos 0.27 with different kinds of applications, such as,
>>> crawlers, databases and websites. However, I have faced many crashes and I
>>> couldn't find what it is the matter.
>>>
>>> We have 14 machines with 8Gb of ram and 4 cpu each. Usually, we run
>>> about 40 instance of our crawler, which they start stopping of nowhere (but
>>> the containers keep running). The day before yesterday we decided try to
>>> test our entire infrastrcuture and we scaled our crawler up to 110
>>> instances. Unfortunately, today we've faced a big crash that affected
>>> mainly our crawler and our databases.
>>>
>>> So, I am wondering if anyone else have the same problem, such as apps
>>> which crashes of nowhere or something else which could be related to some
>>> unstability on Mesos.
>>>
>>> --
>>> Alfredo Miranda
>>>
>>>
>>

Re: How to kill tasks when memory exceeds the cgroup limit?

2016-03-19 Thread Shiyao Ma

Thanks. The limit_swap works.

Re: What are the invalid-user.log files?

2016-03-19 Thread haosdent

I fill this issue in
https://github.com/mesosphere/mesos-deb-packaging/issues/71

On Sat, Mar 19, 2016 at 1:48 AM, haosdent  wrote:

> According I test by systemctl. It didn't export $USER when start service.
>
> ```
> [Unit]
> Description=test
> After=network.target
>
> [Service]
> ExecStart=/bin/env
> ExecStop=/bin/env
>
> [Install]
> WantedBy=multi-user.target
> ```
>
> ```
> $ systemctl status test.service
> Mar 19 01:45:24 localhost env[25754]: LANG=en_SG.UTF-8
> Mar 19 01:45:24 localhost env[25754]:
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
> ```
>
> One possible way is add User and Group in service
> ```
> [Unit]
> Description=test
> After=network.target
>
> [Service]
> ExecStart=/bin/env
> ExecStop=/bin/env
> User=root
> Group=root
>
> [Install]
> WantedBy=multi-user.target
> ```
>
> So that you could see
> ```
> $ systemctl status test.service
> Mar 19 01:44:24 localhost env[25720]: HOME=/root
> Mar 19 01:44:24 localhost env[25720]: LOGNAME=root
> Mar 19 01:44:24 localhost env[25720]: USER=root
> Mar 19 01:44:24 localhost env[25720]: SHELL=/bin/sh
> ```
>
> On Sat, Mar 19, 2016 at 1:26 AM, Steven Schlansker <
> sschlans...@opentable.com> wrote:
>
>> We are seeing the same thing, using Mesosphere .debs on Ubuntu:
>>
>> mesos-master.mesos1-qa-sf.invalid-user.log.WARNING.20160209-221625.12071
>> mesos-master.mesos1-qa-sf.invalid-user.log.WARNING.20160223-211310.1456
>> mesos-master.mesos1-qa-sf.invalid-user.log.WARNING.20160223-211857.5347
>>
>> What if the fallback was to using getpwuid(getuid()) or the like instead
>> of "invalid-user" ?
>>
>>
>> > On Mar 18, 2016, at 9:58 AM, Peter Steele  wrote:
>> >
>> > In my case I am using the CentOS 7 set of rpms  from mesosphere...
>> >
>> > On 03/18/2016 09:14 AM, Pradeep Chhetri wrote:
>> >> I installed mesos using mesosphere debian repository.
>> >>
>> >> On Fri, Mar 18, 2016 at 4:10 PM, haosdent  wrote:
>> >> cool, you install mesos by deb or build it from source directly?
>> >>
>> >> On Mar 19, 2016 12:06 AM, "Pradeep Chhetri" <
>> pradeep.chhetr...@gmail.com> wrote:
>> >> I think it is an upstart issue. I am noticing this issue in Ubuntu
>> 14.04 which uses upstart. This is what i can debug so far:
>> >>
>> >>
>> >> According to this documentation:
>> http://upstart.ubuntu.com/cookbook/#job-environment
>> >>
>> >> When Upstart runs a job, it provides it with a very restrictive
>> environment which contains just two system variables:
>> >>
>> >>  • TERM
>> >>  • PATH
>> >>
>> >> These are the exact two variables i can notice in proc filesystem set
>> as well.
>> >>
>> >> I will post if i find something more.
>> >>
>> >>
>> >> On Fri, Mar 18, 2016 at 2:54 PM, Peter Steele 
>> wrote:
>> >> Yes, I see that as well. Also the case for the mesos master. That
>> explains the invalid-user, but why isn't these processes picking up $USER?
>> >>
>> >>
>> >> On 03/18/2016 07:31 AM, Pradeep Chhetri wrote:
>> >>> I can see that USER environment variable is not set for mesos-slave
>> process from /proc//environ.
>> >>>
>> >>> On Fri, Mar 18, 2016 at 2:19 PM, Pradeep Chhetri <
>> pradeep.chhetr...@gmail.com> wrote:
>> >>> My mesos cluster also produces logs like
>> mesos-slave.ip-172-31-45-33.invalid-user.log.ERROR. I guess log file name
>> shouldnt affect you all because generally you ship these logs in some
>> centralized logging system like logstash/splunk and search there by tags
>> >>>
>> >>> On Fri, Mar 18, 2016 at 1:46 PM, Peter Steele 
>> wrote:
>> >>> What would you suggest to troubleshoot this? Clear something isn't
>> quite right if my log files are called "invalid-user". That said, I have
>> managed to get a containerized application up and running so whatever is
>> wrong isn't fatal. Just ugly...
>> >>>
>> >>>
>> >>> On 03/17/2016 10:42 AM, haosdent wrote:
>>  Not sure why glog could not get USER environment variable correctly
>> after looking its code. But should not affect you running mesos.
>> 
>>  On Fri, Mar 18, 2016 at 1:11 AM, haosdent 
>> wrote:
>>  root should be fine.
>> 
>>  On Fri, Mar 18, 2016 at 12:53 AM, Peter Steele 
>> wrote:
>>  My USER var is root. Do I need to create a non-root user for mesos
>> to run under?
>> 
>> 
>>  On 03/17/2016 09:22 AM, haosdent wrote:
>> > glog get the user name by environment variable "USER" in Linux.
>> https://github.com/google/glog/blob/master/src/utilities.cc#L290-L302 I
>> think you could check the environment variable "USER" before you start
>> Mesos slave.
>> >
>> > On Fri, Mar 18, 2016 at 12:19 AM, haosdent 
>> wrote:
>> > invalid-user is from glog
>> https://github.com/google/glog/blob/master/src/logging.cc#L1036
>> >
>> > >W0317 06:26:41.178268   915 authenticator.cpp:511] No credentials
>> provided, authentication requests will be refused
>> > >which I'm

Re: What are the invalid-user.log files?

2016-03-19 Thread Peter Steele

My USER var is root. Do I need to create a non-root user for mesos to 
run under?

On 03/17/2016 09:22 AM, haosdent wrote:
glog get the user name by environment variable "USER" in Linux. 
https://github.com/google/glog/blob/master/src/utilities.cc#L290-L302 
I think you could check the environment variable "USER" before you 
start Mesos slave.

On Fri, Mar 18, 2016 at 12:19 AM, haosdent > wrote:

invalid-user is from glog
https://github.com/google/glog/blob/master/src/logging.cc#L1036

>W0317 06:26:41.178268   915 authenticator.cpp:511] No credentials
provided, authentication requests will be refused
>which I'm thinking might be related. What am I missing?

I think should not related. This is a warning message if you don't
pass `credentials` flag when start mesos master.

On Thu, Mar 17, 2016 at 10:07 PM, Peter Steele > wrote:

I'm testing out mesos for the first time and after installing
the software I'm seeing numerous log files of the form

mesos-slave..invalid-user.log.INFO.20160317-062640.918

I don't see any errors in the logs themselves, but the fact
that "invalid-user" is part of the name makes me think I'm
missing something in my config. The mesos-master.WARNING log
has the message

W0317 06:26:41.178268   915 authenticator.cpp:511] No
credentials provided, authentication requests will be refused

which I'm thinking might be related. What am I missing?

Peter

-- 
Best Regards,

Haosdent Huang

--
Best Regards,
Haosdent Huang

Compute event at Twitter HQ - 03/31

2016-03-19 Thread Ian Downes

Hello everyone,

I'd like to call attention to an event the Compute group at Twitter is
holding at the end of the month where there will be a few
Aurora/Mesos-related talks:

1. David Robinson, one of our SREs, will talk about how our small team
of SREs manages what is possibly the largest Mesos cluster in
existence.
2. David McLaughlin, Aurora committer/PMC member, will talk about
Workflows, an internal tool we've built to orchestrate deployments
across Aurora clusters.
3. David Hagar, Engineering Manager at TellApart, will talk about
running Aurora/Mesos in AWS.

On top of that there will be lots of other great talks about how we
run the entirety of our compute infrastructure.

The event is on the evening of March 31st at Twitter HQ in San
Francisco. I hope to see many of you there!

https://www.eventbrite.com/e/compute-tickets-22811196904

Thanks,

Ian

Note: This is nearly a straight copy of an email that Joshua sent out
to the Aurora mailing lists.

Unstability on Mesos 0.27

2016-03-19 Thread Alfredo Carneiro

Hello guys,

I am using Mesos 0.27 with different kinds of applications, such as,
crawlers, databases and websites. However, I have faced many crashes and I
couldn't find what it is the matter.

We have 14 machines with 8Gb of ram and 4 cpu each. Usually, we run about
40 instance of our crawler, which they start stopping of nowhere (but the
containers keep running). The day before yesterday we decided try to test
our entire infrastrcuture and we scaled our crawler up to 110 instances.
Unfortunately, today we've faced a big crash that affected mainly our
crawler and our databases.

So, I am wondering if anyone else have the same problem, such as apps which
crashes of nowhere or something else which could be related to some
unstability on Mesos.

-- 
Alfredo Miranda

Re: What are the invalid-user.log files?

2016-03-19 Thread Peter Steele

In my case I am using the CentOS 7 set of rpms  from mesosphere...

On 03/18/2016 09:14 AM, Pradeep Chhetri wrote:

I installed mesos using mesosphere debian repository.

On Fri, Mar 18, 2016 at 4:10 PM, haosdent > wrote:

cool, you install mesos by deb or build it from source directly?

On Mar 19, 2016 12:06 AM, "Pradeep Chhetri"
>
wrote:

I think it is an upstart issue. I am noticing this issue in
Ubuntu 14.04 which uses upstart. This is what i can debug so far:

According to this documentation:
http://upstart.ubuntu.com/cookbook/#job-environment

When Upstart runs a job, it provides it with a very
restrictive environment which contains just two system variables:

  * TERM
  * PATH

These are the exact two variables i can notice in proc
filesystem set as well.

I will post if i find something more.

On Fri, Mar 18, 2016 at 2:54 PM, Peter Steele
> wrote:

Yes, I see that as well. Also the case for the mesos
master. That explains the invalid-user, but why isn't
these processes picking up $USER?

On 03/18/2016 07:31 AM, Pradeep Chhetri wrote:

I can see that USER environment variable is not set for
mesos-slave process from /proc//environ.

On Fri, Mar 18, 2016 at 2:19 PM, Pradeep Chhetri
> wrote:

My mesos cluster also produces logs
like mesos-slave.ip-172-31-45-33.invalid-user.log.ERROR.
I guess log file name shouldnt affect you all because
generally you ship these logs in some centralized
logging system like logstash/splunk and search there
by tags

On Fri, Mar 18, 2016 at 1:46 PM, Peter Steele
> wrote:

What would you suggest to troubleshoot this?
Clear something isn't quite right if my log files
are called "invalid-user". That said, I have
managed to get a containerized application up and
running so whatever is wrong isn't fatal. Just
ugly...

On 03/17/2016 10:42 AM, haosdent wrote:

Not sure why glog could not get USER environment
variable correctly after looking its code. But
should not affect you running mesos.

On Fri, Mar 18, 2016 at 1:11 AM, haosdent
>
wrote:

root should be fine.

On Fri, Mar 18, 2016 at 12:53 AM, Peter
Steele > wrote:

My USER var is root. Do I need to create
a non-root user for mesos to run under?

On 03/17/2016 09:22 AM, haosdent wrote:

glog get the user name by environment
variable "USER" in Linux.

https://github.com/google/glog/blob/master/src/utilities.cc#L290-L302
I think you could check the environment
variable "USER" before you start Mesos
slave.

On Fri, Mar 18, 2016 at 12:19 AM,
haosdent > wrote:

invalid-user is from glog

https://github.com/google/glog/blob/master/src/logging.cc#L1036

>W0317 06:26:41.178268   915
authenticator.cpp:511] No
credentials provided,
authentication requests will be refused
>which I'm thinking might be
related. What am I missing?

I think should not related. This is
a warning message if you don't pass
`credentials` flag when start mesos
master.

On Thu, Mar 17, 2016 at 10:07 PM,
Peter Steele > wrote:

I'm testing out mesos for the

Re: Unstability on Mesos 0.27

2016-03-19 Thread Vinod Kone

Hey Gabriel,

Could you share more details on what the crashes are and what your setup is
(docker containerizer?). Any logs (master, agent, application) that can
shed light would be useful to diagnose.

On Wed, Mar 16, 2016 at 5:12 PM, Alfredo Carneiro <
alfr...@simbioseventures.com> wrote:

> Hello guys,
>
> I am using Mesos 0.27 with different kinds of applications, such as,
> crawlers, databases and websites. However, I have faced many crashes and I
> couldn't find what it is the matter.
>
> We have 14 machines with 8Gb of ram and 4 cpu each. Usually, we run about
> 40 instance of our crawler, which they start stopping of nowhere (but the
> containers keep running). The day before yesterday we decided try to test
> our entire infrastrcuture and we scaled our crawler up to 110 instances.
> Unfortunately, today we've faced a big crash that affected mainly our
> crawler and our databases.
>
> So, I am wondering if anyone else have the same problem, such as apps
> which crashes of nowhere or something else which could be related to some
> unstability on Mesos.
>
> --
> Alfredo Miranda
>

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

2016-03-19 Thread Michael Park

+1 (binding)

Internal CI results with the corresponding JIRA tickets for the failed
tests:

CentOS 6 (non-SSL):
CentOS 6 (SSL):
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 )

CentOS 7 (non-SSL):
  - ProvisionerDockerRegistryPullerTest.ROOT_INTERNET_CURL_ShellCommand
(MESOS-4810)

CentOS 7 (SSL):
  - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers (Fixed in master)
(MESOS-4912 )
  - ProvisionerDockerRegistryPullerTest.ROOT_INTERNET_CURL_ShellCommand
(MESOS-4810 )

Debian 8 (non-SSL):
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 )

Debian 8 (SSL):
  - NsTest.ROOT_setns
(MESOS-3000 )
  - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
(MESOS-4047 )

Ubuntu 12 (non-SSL):
  - HealthCheckTest.ROOT_DOCKER_DockerHealthStatusChange
Failed with MESOS-2017


Ubuntu 12 (SSL): Success!
Ubuntu 14 (non-SSL): Success!
Ubuntu 14 (SSL): Success!
Ubuntu 15 (non-SSL): Success!
Ubuntu 15 (SSL): Success!

On 11 March 2016 at 15:46, Vinod Kone  wrote:

> Hi all,
>
>
> Please vote on releasing the following candidate as Apache Mesos 0.28.0.
>
>
> 0.28.0 includes the following:
>
>
> 
>
> Release Notes - Mesos - Version 0.28.0
>
> 
>
> This release contains the following new features:
>
>   * [MESOS-4343] - A new cgroups isolator for enabling the net_cls
> subsystem in
>
> Linux. The cgroups/net_cls isolator allows operators to provide network
>
> performance isolation and network segmentation for containers within a
> Mesos
>
> cluster. To enable the cgroups/net_cls isolator, append
> `cgroups/net_cls` to
>
> the `--isolation` flag when starting the slave. Please refer to
>
> docs/mesos-containerizer.md for more details.
>
>
>   * [MESOS-4687] - The implementation of scalar resource values (e.g., "2.5
>
> CPUs") has changed. Mesos now reliably supports resources with up to
> three
>
> decimal digits of precision (e.g., "2.501 CPUs"); resources with more
> than
>
> three decimal digits of precision will be rounded. Internally, resource
> math
>
> is now done using a fixed-point format that supports three decimal
> digits of
>
> precision, and then converted to/from floating point for input and
> output,
>
> respectively. Frameworks that do their own resource math and manipulate
>
> fractional resources may observe differences in roundoff error and
> numerical
>
> precision.
>
>
>   * [MESOS-4479] - Reserved resources can now optionally include "labels".
>
> Labels are a set of key-value pairs that can be used to associate
> metadata
>
> with a reserved resource. For example, frameworks can use this feature
> to
>
> distinguish between two reservations for the same role at the same
> agent
>
> that are intended for different purposes.
>
>
>   * [MESOS-2840] - **Experimental** support for container images in Mesos
>
> containerizer (a.k.a. Unified Containerizer). This allows frameworks to
>
> launch Docker/Appc containers using Mesos containerizer without relying
> on
>
> docker daemon (engine) or rkt. The isolation of the containers is done
> using
>
> isolators. Please refer to docs/container-image.md for currently
> supported
>
> features and limitations.
>
>
>   * [MESOS-4793] - **Experimental** support for v1 Executor HTTP API. This
>
> allows executors to send HTTP requests to the /api/v1/executor agent
>
> endpoint without the need for an executor driver. Please refer to
>
> docs/executor-http-api.md for more details.
>
>
>   * [MESOS-4370] Added support for service discovery of Docker containers
> that
>
> use Docker Remote API v1.21.
>
>
> Additional API Changes:
>
>   * [MESOS-4066] - Agent should not return partial state when a request is
> made to /state endpoint during recovery.
>
>   * [MESOS-4547] - Introduce TASK_KILLING state.
>
>   * [MESOS-4712] - Remove 'force' field from the Subscribe Call in v1
> Scheduler API.
>
>   * [MESOS-4591] - Change the object of ReserveResources and CreateVolume
> ACLs to `roles`.
>
>   * [MESOS-3583] - Add stream IDs for HTTP schedulers.
>
>   * [MESOS-4427] - Ensure ip_address in state.json (from NetworkInfo) is
> valid
>
>
> 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=0.28.0-rc2
>
>
> 
>
>
> The candidate for Mesos 0.28.0 release is available at:
>
>

Re: HTTP API

2016-03-19 Thread Joseph Wu

Zameer,

In case you haven't seen this already, there is already a Java-based
scheduler driver for the HTTP API here:
https://github.com/mesosphere/mesos-rxjava


On Thu, Mar 17, 2016 at 5:26 PM, Zameer Manji  wrote:

>
> On Thu, Mar 17, 2016 at 10:03 AM, Vinod Kone  wrote:
>
>> Other than the issues listed above, we like frameworks to start testing
>> this API in their staging/testing clusters. This would give us the most
>> confidence to call it production ready. Can you help?
>>
>
> As a committer of Apache Aurora, I am interested in removing the
> dependency in libmesos and creating a Java Scheduler Driver that
> communicates with the HTTP API. However, it only seems worthwhile to do
> once the API has stabilized. I'll wait for the API to be finalized and then
> assess what work needs to be done for the framework.
>
> --
> Zameer Manji
>
>

Re: How to kill tasks when memory exceeds the cgroup limit?

2016-03-19 Thread Dick Davies

On 18 March 2016 at 20:58, Benjamin Mahler  wrote:
> Interesting, why does it take down the slaves?

This was a good while back, but when swap gets low our slaves kernel
OOM killer tended to mess things up.

> Because a lot of organizations run with swap disabled (e.g. for more
> deterministic performance), we originally did not set the swap limit at all.
> When we introduced the '--cgroups_limit_swap' flag we had to make it default
> to false initially in case any users were depending on the original behavior
> of no swap limit. Now that it's been available for some time, we can
> consider moving the default to true. This is actually reflected in the TODO
> alongside the flag:
>
> https://github.com/apache/mesos/blob/0.28.0/src/slave/flags.cpp#L331-L336
>
> Want to send a patch? We'd need to communicate this change to the default
> behavior in the CHANGELOG and specify how users can keep the original
> behaviour.

I'll see if I can get time - just about to finish a consulting gig and
was going to take a break,
so it might be an option.

Thanks for the explanation, I *knew* there'd be a reason :)


> Also, there's more we would need to do in the long term for use cases that
> desire swapping. The only support today is (1) no memory limits (2) memory
> limit and no swap limit (3) both memory and swap limits. You can imagine
> scenarios where users may want to control how much they're allowed to swap,
> or maybe we want to swap for non-latency sensitive containers. However, it's
> more complicated (the user and operator have to co-operate more, there are
> more ways to run things, etc), and so the general advice is to disable swap
> to keep things simple and deterministic.
>
> On Fri, Mar 18, 2016 at 11:34 AM, Dick Davies 
> wrote:
>>
>> Great!
>>
>> I'm not really sure why mesos even allows RSS limiting without VMEM,
>> it takes down slaves like the Black Death
>> if you accidentally deploy a 'leaker'. I'm sure there's a use case I'm
>> not seeing :)
>>
>> On 18 March 2016 at 16:27, Shiyao Ma  wrote:
>> > Thanks. The limit_swap works.
>
>

Re: [RESULT][VOTE] Release Apache Mesos 0.28.0 (rc2)

2016-03-19 Thread craig w

Great news. Do the rpm's get automatically built and released or will they
come later this week?

On Thu, Mar 17, 2016 at 1:28 PM, Vinod Kone  wrote:

> Hi all,
>
>
> The vote for Mesos 0.28.0 (rc2) has passed with the
>
> following votes.
>
>
> +1 (Binding)
>
> --
>
> Vinod Kone
>
> Michael Park
>
> Kapil Arya
>
>
> +1 (Non-binding)
>
> --
>
> Greg Mann
>
> Daniel Osborne
>
> Jorg Schad
>
> Zhitao Li
>
>
> There were no 0 or -1 votes.
>
>
> Please find the release at:
>
> https://dist.apache.org/repos/dist/release/mesos/0.28.0
>
>
> It is recommended to use a mirror to download the release:
>
> http://www.apache.org/dyn/closer.cgi
>
>
> 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=0.28.0
>
>
> The mesos-0.28.0.jar has been released to:
>
> https://repository.apache.org
>
>
> The website (http://mesos.apache.org) will be updated shortly to reflect
> this release.
>
>
> Thanks,
>



-- 

https://github.com/mindscratch
https://www.google.com/+CraigWickesser
https://twitter.com/mind_scratch
https://twitter.com/craig_links

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

2016-03-19 Thread Benjamin Mahler

These are be captured under:
https://issues.apache.org/jira/browse/MESOS-4979

On Thu, Mar 17, 2016 at 5:04 PM, Benjamin Mahler  wrote:

> Thanks for the hard work! Do we need to backport the rmdir fixes on the
> outstanding release candidates?
>
> commit 5278e5cc50544ed7af28b15a1acd2b2e96a15a47
> Author: Jojy Varghese 
> Date:   Tue Mar 15 17:12:01 2016 -0700
>
> Added support for FTS_SLNONE in rmdir.
>
> Review: https://reviews.apache.org/r/44874/
>
> commit fbe1f37f65fd9f1d4f2c30a3cfd7a50df92ccc2c
> Author: Alex Clemmer 
> Date:   Tue Mar 1 23:29:21 2016 -0800
>
> Stout:[1/2] Fixed error reporting bug in `os::rmdir`.
>
> Review: https://reviews.apache.org/r/43907/
>
> commit f8b7ac28b1a918864a06b3f99f45b0257c7b6f68
> Author: Jojy Varghese 
> Date:   Tue Mar 1 14:32:13 2016 -0800
>
> Added FS_DEFAULT case in rmdir.
>
> We currently dont handle special files like device files in rmdir. This
> change adds FS_DEFAULT as one of the cases where we try to unlink a
> file. Reference: http://man7.org/linux/man-pages/man3/fts.3.html
>
> Review: https://reviews.apache.org/r/44230/
>
> On Wed, Mar 16, 2016 at 8:21 PM, Vinod Kone  wrote:
>
>> +1 (binding)
>>
>> Tested on ASF CI.
>>
>> On Sun, Mar 13, 2016 at 4:33 PM, Michael Park  wrote:
>>
>> > +1 (binding)
>> >
>> > Internal CI results with the corresponding JIRA tickets for the failed
>> > tests:
>> >
>> > CentOS 6 (non-SSL):
>> >   - MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward
>> > (MESOS-3049 )
>> >   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>> > (MESOS-4039 )
>> >   - UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup
>> > (MESOS-4035 )
>> >   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>> > (MESOS-3215 )
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>> > (MESOS-4047 ,
>> > MESOS-4053 )
>> >
>> > CentOS 6 (SSL):
>> >   - MesosContainerizerSlaveRecoveryTest.CGROUPS_ROOT_PerfRollForward
>> > (MESOS-3049 )
>> >   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>> > (MESOS-4039 )
>> >   - UserCgroupIsolatorTest/2.ROOT_CGROUPS_UserCgroup
>> > (MESOS-4035 )
>> >   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>> > (MESOS-3215 )
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>> > (MESOS-4047 ,
>> > MESOS-4053 )
>> >
>> > CentOS 7 (non-SSL):
>> >   - LimitedCpuIsolatorTest.ROOT_CGROUPS_Pids_and_Tids
>> > (MESOS-4677 )
>> >   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>> > (MESOS-4039 )
>> >   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>> > (MESOS-3215 )
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>> > (MESOS-4047 ,
>> > MESOS-4053 )
>> >
>> > CentOS 7 (SSL):
>> >   - FetcherCacheTest.RemoveLRUCacheEntries
>> > (MESOS-4156 )
>> >   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
>> > (MESOS-4039 )
>> >   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
>> > (MESOS-3215 )
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>> >   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
>> > (MESOS-4047 ,
>> > MESOS-4053 )
>> >
>> > Debian 8 (non-SSL): Success!
>> > Debian 8 (SSL): Failed with MESOS-2017
>> > 
>> >
>> > Ubuntu 12 (non-SSL):
>> > Ubuntu 12 (SSL):
>> > Ubuntu 14 (non-SSL):
>> > Ubuntu 14 (SSL):
>> >   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>> >   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
>> > (MESOS-4035 )
>> >
>> > Ubuntu 15 (non-SSL): Success!
>> >

Re: What are the invalid-user.log files?

2016-03-19 Thread Peter Steele

What would you suggest to troubleshoot this? Clear something isn't quite 
right if my log files are called "invalid-user". That said, I have 
managed to get a containerized application up and running so whatever is 
wrong isn't fatal. Just ugly...

On 03/17/2016 10:42 AM, haosdent wrote:
Not sure why glog could not get USER environment variable correctly 
after looking its code. But should not affect you running mesos.

On Fri, Mar 18, 2016 at 1:11 AM, haosdent > wrote:

root should be fine.

On Fri, Mar 18, 2016 at 12:53 AM, Peter Steele > wrote:

My USER var is root. Do I need to create a non-root user for
mesos to run under?

On 03/17/2016 09:22 AM, haosdent wrote:

glog get the user name by environment variable "USER" in
Linux.
https://github.com/google/glog/blob/master/src/utilities.cc#L290-L302
I think you could check the environment variable "USER"
before you start Mesos slave.

On Fri, Mar 18, 2016 at 12:19 AM, haosdent
> wrote:

invalid-user is from glog
https://github.com/google/glog/blob/master/src/logging.cc#L1036

>W0317 06:26:41.178268 915 authenticator.cpp:511] No
credentials provided, authentication requests will be refused
>which I'm thinking might be related. What am I missing?

I think should not related. This is a warning message if
you don't pass `credentials` flag when start mesos master.

On Thu, Mar 17, 2016 at 10:07 PM, Peter Steele
> wrote:

I'm testing out mesos for the first time and after
installing the software I'm seeing numerous log files
of the form

mesos-slave..invalid-user.log.INFO.20160317-062640.918

I don't see any errors in the logs themselves, but
the fact that "invalid-user" is part of the name
makes me think I'm missing something in my config.
The mesos-master.WARNING log has the message

W0317 06:26:41.178268  915 authenticator.cpp:511] No
credentials provided, authentication requests will be
refused

which I'm thinking might be related. What am I missing?

Peter

-- 
Best Regards,

Haosdent Huang

-- 
Best Regards,

Haosdent Huang

-- 
Best Regards,

Haosdent Huang

--
Best Regards,
Haosdent Huang

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

2016-03-19 Thread Michael Park

As there are insufficient votes on this rc along with a request
from Evan Krall to include additional fixes:
https://www.mail-archive.com/user@mesos.apache.org/msg06204.html
,
I'm declaring this rc failed, and will cut be cutting an rc3 early next
week.

Thanks,

MPark

On 13 March 2016 at 19:55, Michael Park  wrote:

> +1 (binding)
>
> Internal CI results with the corresponding JIRA tickets for the failed
> tests:
>
> CentOS 6 (non-SSL):
> CentOS 6 (SSL):
>   - Failed with MESOS-2017
> 
>
> CentOS 7 (non-SSL):
>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> (MESOS-4039 )
>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
> (MESOS-3215 )
>   - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
>   - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
>   - LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable
> (MESOS-3296 )
>   - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
> (MESOS-3410 )
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 ,
> MESOS-4053 )
>
> CentOS 7 (SSL):
>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> (MESOS-4039 )
>   - ContainerizerTest.ROOT_CGROUPS_BalloonFramework
> (MESOS-2672 )
>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
> (MESOS-3215 )
>   - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
>   - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_ImageInVolumeWithRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers
>   - LinuxFilesystemIsolatorTest.ROOT_SandboxEnvironmentVariable
> (MESOS-3296 )
>   - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
> (MESOS-3410 )
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 ,
> MESOS-4053 )
>
> Debian 8 (non-SSL):
> Debian 8 (SSL):
>   - Failed with MESOS-3964
> 
>
> Ubuntu 12 (non-SSL):
>   - DockerContainerizerTest.ROOT_DOCKER_Logs
> (MESOS-4676 )
>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 )
>
> Ubuntu 12 (SSL):
>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 )
>   - ContainerizerTest.ROOT_CGROUPS_BalloonFramework
> (MESOS-2672 )
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 ,
> MESOS-4053 )
>
> Ubuntu 14 (non-SSL):
>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 )
>
> Ubuntu 14 (SSL):
>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 )
>   - ContainerizerTest.ROOT_CGROUPS_BalloonFramework
> (MESOS-2672 )
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 ,
> MESOS-4053 )
>
> Ubuntu

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

2016-03-19 Thread Michael Park

As there are insufficient votes on this rc along with a request
from Evan Krall to include additional fixes:
https://www.mail-archive.com/user@mesos.apache.org/msg06205.html,
I'm declaring this rc failed, and will cut be cutting an rc3 early next
week.

Thanks,

MPark

On 13 March 2016 at 20:57, Michael Park  wrote:

> +1 (binding)
>
> Internal CI results with the corresponding JIRA tickets for the failed
> tests:
>
> CentOS 6 (non-SSL):
> CentOS 6 (SSL):
>   - Failed with MESOS-2017
> 
>
> CentOS 7 (non-SSL):
> CentOS 7 (SSL):
>   - PerfEventIsolatorTest.ROOT_CGROUPS_Sample
> (MESOS-4039 )
>   - CgroupsAnyHierarchyWithPerfEventTest.ROOT_CGROUPS_Perf
> (MESOS-3215 )
>   - LinuxFilesystemIsolatorTest.ROOT_ChangeRootFilesystem
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromSandbox
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHost
>   - LinuxFilesystemIsolatorTest.ROOT_VolumeFromHostSandboxMountPoint
>   - LinuxFilesystemIsolatorTest.ROOT_PersistentVolumeWithRootFilesystem
> (MESOS-3296 )
>   - MesosContainerizerLaunchTest.ROOT_ChangeRootfs
> (MESOS-3410 )
>   - MemoryPressureMesosTest.CGROUPS_ROOT_Statistics
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 ,
> MESOS-4053 )
>   - PerfTest.ROOT_SamplePid
> (MESOS-3079 )
>
> Debian 8 (non-SSL):
> Debian 8 (SSL):
>   - Failed with MESOS-3964
> 
>
> Ubuntu 12 (non-SSL):
> Ubuntu 12 (SSL):
> Ubuntu 14 (non-SSL):
> Ubuntu 14 (SSL):
>   - UserCgroupIsolatorTest/0.ROOT_CGROUPS_UserCgroup
>   - UserCgroupIsolatorTest/1.ROOT_CGROUPS_UserCgroup
> (MESOS-4035 )
>
> Ubuntu 15 (non-SSL):
>   - DockerContainerizerTest.ROOT_DOCKER_Logs
> (MESOS-4676 )
>   - LimitedCpuIsolatorTest.ROOT_CGROUPS_Pids_and_Tids
> (MESOS-4677 )
>
> Ubuntu 15 (SSL): Success!
>
> On 13 March 2016 at 18:42, Michael Park  wrote:
>
>> While the vote for this release was open until Fri Mar 11 23:59:59 EST
>> 2016,
>> I'm going to give it another 3 days since there has not been any -1 votes.
>>
>> The vote is extended until Wed Mar 16 23:59:59 EST 2016.
>>
>> On 10 March 2016 at 12:49, Greg Mann  wrote:
>>
>>> +1 (non-binding)
>>>
>>> Ran `sudo make check` on CentOS 7, using gcc with libevent and SSL
>>> enabled. All tests pass.
>>>
>>> I was also able to successfully test a simple upgrade scenario from
>>> 0.23.1 to 0.24.2-rc2 using the script found here:
>>> https://reviews.apache.org/r/44229/
>>>
>>> Cheers,
>>> Greg
>>>
>>>
>>> On Tue, Mar 8, 2016 at 6:50 PM, Michael Park  wrote:
>>>
 The link to the commit above points to the one on the master branch.
 The following is the one on the `0.24.2-rc2` branch: Fixed compiler
 warning
 in values tests.
 <
 https://github.com/apache/mesos/commit/afb8a0cffaf8bc235ce45087c80bafe87488dcd0
 >

 On 8 March 2016 at 21:21, Michael Park  wrote:

 > Hi all,
 >
 > Please vote on releasing the following candidate as Apache Mesos
 0.24.2.
 >
 >
 > 0.24.2 includes the following:
 >
 >
 
 >
 > The only diff with RC1 is the following: Fixed compiler warning in
 values
 > tests.
 > <
 https://github.com/apache/mesos/commit/bfeb070a2aef52f445eb057076d344fd184eb461
 >

 > As I described in the RC1 [VOTE] thread, even though this is a trivial
 > compile fix,
 > I decided to cut an RC2 in order to avoid breaking those who compile
 Mesos
 > from source.
 >
 > * Improvements
 > - Allocator filter performance
 > - Port Ranges performance
 > - UUID performance
 > - `/state` endpoint performance
 >   - GLOG performance
 >   - Configurable task/framework history
 >   - Offer filter timeout fix for backlogged allocator
 >
 > * Bugs
 >   - SSL
 >   - Libevent
 >   - Fixed point resources math
 >   - HDFS
 >   - Agent upgrade compatibility
 >   - Health checks
 >
 > 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=0.24.2-rc2
 >
 >
 
 >
 > The candidate for Mesos

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

2016-03-19 Thread Michael Park

Hi Evan,

As I mentioned in the 0.25.1 rc2 thread,

I will be cutting an rc3 for 0.24.2 and 0.25.1 to include those patches.

Thanks again!

MPark

On 18 March 2016 at 17:09, Benjamin Mahler  wrote:

> +michael who is managing the release, he'll get back to you shortly,
> apologies for the delay!
>
> On Fri, Mar 11, 2016 at 11:35 AM, Evan Krall  wrote:
>
>> I humbly request that the fixes for these issues are also included in
>> 0.24.2:
>>
>> https://issues.apache.org/jira/browse/MESOS-3738
>> https://issues.apache.org/jira/browse/MESOS-3560
>>
>> Both of these issues caused trouble for us trying to keep up with Mesos
>> upgrades.
>>
>
>

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

2016-03-19 Thread Michael Park

Hi Evan,

Thank you for letting us know of the issues and your explanation!

I will cut an RC3 for 0.24.2 and 0.25.1 to include those patches.

MPark

On 14 March 2016 at 20:25, Evan Krall  wrote:

> On Sun, Mar 13, 2016 at 3:46 PM, Michael Park  wrote:
>
>> Hi Evan,
>>
>> If we wanted to backport those patches as well, we should cut a 0.25.2.
>> I would first like to understand what kind of issues you're running into.
>> Do you mind elaborating a little?
>>
>
>
> For MESOS-3738, we ran into the issue pretty much directly. We run Mesos
> with the Docker executor, and mesos healthchecks stopped reporting
> correctly. Our automation (built on Marathon) waits for healthcheck results
> to be available before considering a task "healthy" and killing old tasks,
> so this bug manifested as deploys getting stuck and never killing old tasks.
>
> There is a patch available in the ticket, and we've built our own copies
> of Mesos, including that patch. However, it took us some time to figure out
> that this was the issue, and we had to set up an internal build pipeline
> for Mesos that includes that patch.
>
>
> For MESOS-3560, we attempted to upgrade a cluster from 0.23.1 to 0.24.1
> and saw that our Mesos slaves were unable to connect to the master due to
> authentication issues. We eventually figured out that we were hitting the
> bug in MESOS-3560, and switched to the older newline-delimited credential
> files.
>
>
> Because the Mesos upgrade process dictates that you should never skip a
> minor version, anybody using Docker, command healthchecks, and
> authentication on <=0.23 will hit both of these bugs and need to patch and
> work around them if they want to upgrade to anything above 0.24.
>
> While we've worked around both of these issues, it's really frustrating
> that these issues have both been fixed for several months, but neither fix
> was released for 0.24 or 0.25. I'm pushing for these patches to be released
> (along with any other unreleased bugfixes that might be scattered around
> JIRA) so that anybody else doing this upgrade doesn't need to feel the same
> pain that we did.
>
>
>> Thanks,
>>
>> MPark
>>
>
>

Re: Unstability on Mesos 0.27

2016-03-19 Thread Artem Harutyunyan

Hi Guillermo,

We would really like to help you, and to understand what the issues are.
Could you please send us all the logs you have so we can inspect them and
figure out what happened?

Artem.

On Thursday, March 17, 2016, Guillermo Rodriguez 
wrote:

> Update to 0.27.2 or wait for 0.28.0.
>
> I experienced many crashes as well with 0.27.1 due to crashes in the
> frameworks bringing down the whole cluster (swarm specially). Also problems
> in the resource precision that also crashed the servers and crashes when
> nodes disconnected.
>
> I really found 0.27 very unstable.
>
> Many of this problems were solved for 0.27.2 and my latest environment has
> proven way more stable. It is still not fully stable as the cluster crashed
> yesterday due to a crash in marathon, but way better overall and quick to
> recover.
>
> Luck!
> Guimo
>
>
> --
> *From*: "Klaus Ma"  >
> *Sent*: Thursday, March 17, 2016 1:36 PM
> *To*: user@mesos.apache.org
> 
> *Cc*: "Gabriel Menegatti"  >
> *Subject*: Re: Unstability on Mesos 0.27
>
> If Mesos daemon crashed, I'd suggest to log a JIRA and append more detail,
> e.g. steps, master/agent log.
>
> 
> Da (Klaus), Ma (??) | PMP® | Advisory Software Engineer
> Platform OpenSource Technology, STG, IBM GCG
> +86-10-8245 4084 | klaus1982...@gmail.com
>  | http://k82.me
>
> On Thu, Mar 17, 2016 at 8:26 AM, Vinod Kone  > wrote:
>>
>> Hey Gabriel,
>>
>> Could you share more details on what the crashes are and what your setup
>> is (docker containerizer?). Any logs (master, agent, application) that can
>> shed light would be useful to diagnose.
>>
>> On Wed, Mar 16, 2016 at 5:12 PM, Alfredo Carneiro <
>> alfr...@simbioseventures.com
>> > wrote:
>>>
>>> Hello guys,
>>>
>>> I am using Mesos 0.27 with different kinds of applications, such as,
>>> crawlers, databases and websites. However, I have faced many crashes and I
>>> couldn't find what it is the matter.
>>>
>>> We have 14 machines with 8Gb of ram and 4 cpu each. Usually, we run
>>> about 40 instance of our crawler, which they start stopping of nowhere (but
>>> the containers keep running). The day before yesterday we decided try to
>>> test our entire infrastrcuture and we scaled our crawler up to 110
>>> instances. Unfortunately, today we've faced a big crash that affected
>>> mainly our crawler and our databases.
>>>
>>> So, I am wondering if anyone else have the same problem, such as apps
>>> which crashes of nowhere or something else which could be related to some
>>> unstability on Mesos.
>>>
>>> --
>>> Alfredo Miranda
>>>
>>>
>>

RE: verbose logging with the docker executor

2016-03-19 Thread Clarke, Trevor

Thanks, worked great

--
Trevor R.H. Clarke
Software Engineer, Ball Aerospace
(937)320-7087


> -Original Message-
> From: James Peach [mailto:jor...@gmail.com]
> Sent: Thursday, March 17, 2016 1:15 PM
> To: user@mesos.apache.org
> Subject: Re: verbose logging with the docker executor
> 
> 
> > On Mar 17, 2016, at 10:09 AM, Clarke, Trevor  wrote:
> >
> > Looking in the docker executor, the docker command line is logged with
> VLOG(1) but I'm not sure how to generate that level of log output. Some
> googling suggests it's used in the google logging library and verbose logging
> would be enabled with something like --v=1 but that's not a valid mesos-
> slave option. Can someone point me in the right direction? (currently using
> 0.24.1)
> 
> You can set the GLOG_v environment variable (see
> https://urldefense.proofpoint.com/v2/url?u=https-3A__google-
> 2Dglog.googlecode.com_svn_trunk_doc_glog.html-
> 23verbose=CwIFAg=jF7FvYH6t0RX1HrEjVCgHQ=BZAdW7eZ7BA-
> TVm8CsncxQ=GbVjJL_4t0MuKdzzh2BCdn8URtcP4hm-
> SshI74wtR6s=Kth4DCGl6bGJ8qGlXTg_hNv4fE0R64-sHJ3neFQIWJs= ) to
> the desired verbosity level and then restart mesos-slave. If you just want to
> increase the log level without a restart, you can hit the /logging/toggle
> endpoint on the mesos-slave (do curl
> https://urldefense.proofpoint.com/v2/url?u=http-3A__127.0.0.1-
> 3A5051_help_logging_toggle=CwIFAg=jF7FvYH6t0RX1HrEjVCgHQ=BZ
> AdW7eZ7BA-TVm8CsncxQ=GbVjJL_4t0MuKdzzh2BCdn8URtcP4hm-
> SshI74wtR6s=X31FOtRYKF_aKYe7Msv_E3qMrBll1G8AE7opQn74oMg=
> for the online help).
> 
> J



This message and any enclosures are intended only for the addressee.  Please 
notify the sender by email if you are not the intended recipient.  If you are 
not the intended recipient, you may not use, copy, disclose, or distribute this 
message or its contents or enclosures to any other person and any such actions 
may be unlawful.  Ball reserves the right to monitor and review all messages 
and enclosures sent to or from this email address.

Can mesos support supports multi-datacenter and multi-region configurations for failure isolation and scalability.

2016-03-19 Thread tommy xiao

recently, i read Nomad blog's article,  , the blog said:
```
Mesos does not support federation or multiple failure isolation regions.
Nomad supports multi-datacenter and multi-region configurations for failure
isolation and scalability.
```

how the  mesos support multi-datacenter and multi-region's  feature?


-- 
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com

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

2016-03-19 Thread Zhitao Li

I don't think it's a blocking issue after some initial investigation.

Changing my vote to +1 (nonbinding)

On Wed, Mar 16, 2016 at 6:07 PM, Vinod Kone  wrote:

>
> On Wed, Mar 16, 2016 at 5:59 PM, Daniel Osborne <
> daniel.osbo...@metaswitch.com> wrote:
>
>> Is this issue a blocker? Are we moving to rc3 or proceeding with 0.28.0?
>>
>
> It was not marked as such, so I'm guessing not. @Jie and @Zhitao, can you
> confirm?
>
> Also, we still need some binding votes for this release to go official.
> @committers: can you please vote?
>



-- 
Cheers,

Zhitao Li

Re: [RESULT][VOTE] Release Apache Mesos 0.28.0 (rc2)

2016-03-19 Thread Bill Farner

Jake - i think that would be wonderful!

On Thu, Mar 17, 2016 at 11:17 AM, Jake Farrell  wrote:

> I've been maintaining a deb/rpm set for Mesos and for Aurora and Thrift we
> have been using the infra supported Bintray to make it available to the
> community via http://www.apache.org/dist/${project}/${os}
>
> If there is interest I'd be happy to put some time into bringing my patches
> into reviews and helping setup jenkins tests, etc.
>
> -Jake
>
>
>
>
>
>
> On Thu, Mar 17, 2016 at 1:41 PM, Vinod Kone  wrote:
>
> > The project itself doesn't officially release rpms/debs, but the
> community
> > members do.  For example, Mesosphere is planning to release rpms/debs
> > shortly.
> >
> > On Thu, Mar 17, 2016 at 10:38 AM, craig w  wrote:
> >
> > > Great news. Do the rpm's get automatically built and released or will
> > they
> > > come later this week?
> > >
> > > On Thu, Mar 17, 2016 at 1:28 PM, Vinod Kone 
> > wrote:
> > >
> > >> Hi all,
> > >>
> > >>
> > >> The vote for Mesos 0.28.0 (rc2) has passed with the
> > >>
> > >> following votes.
> > >>
> > >>
> > >> +1 (Binding)
> > >>
> > >> --
> > >>
> > >> Vinod Kone
> > >>
> > >> Michael Park
> > >>
> > >> Kapil Arya
> > >>
> > >>
> > >> +1 (Non-binding)
> > >>
> > >> --
> > >>
> > >> Greg Mann
> > >>
> > >> Daniel Osborne
> > >>
> > >> Jorg Schad
> > >>
> > >> Zhitao Li
> > >>
> > >>
> > >> There were no 0 or -1 votes.
> > >>
> > >>
> > >> Please find the release at:
> > >>
> > >> https://dist.apache.org/repos/dist/release/mesos/0.28.0
> > >>
> > >>
> > >> It is recommended to use a mirror to download the release:
> > >>
> > >> http://www.apache.org/dyn/closer.cgi
> > >>
> > >>
> > >> 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=0.28.0
> > >>
> > >>
> > >> The mesos-0.28.0.jar has been released to:
> > >>
> > >> https://repository.apache.org
> > >>
> > >>
> > >> The website (http://mesos.apache.org) will be updated shortly to
> > reflect
> > >> this release.
> > >>
> > >>
> > >> Thanks,
> > >>
> > >
> > >
> > >
> > > --
> > >
> > > https://github.com/mindscratch
> > > https://www.google.com/+CraigWickesser
> > > https://twitter.com/mind_scratch
> > > https://twitter.com/craig_links
> > >
> > >
> >
>

Re: What are the invalid-user.log files?

2016-03-19 Thread Peter Steele

Yes, I see that as well. Also the case for the mesos master. That 
explains the invalid-user, but why isn't these processes picking up $USER?

On 03/18/2016 07:31 AM, Pradeep Chhetri wrote:
I can see that USER environment variable is not set for mesos-slave 
process from /proc//environ.

On Fri, Mar 18, 2016 at 2:19 PM, Pradeep Chhetri 
> wrote:

My mesos cluster also produces logs
like mesos-slave.ip-172-31-45-33.invalid-user.log.ERROR. I guess
log file name shouldnt affect you all because generally you ship
these logs in some centralized logging system like logstash/splunk
and search there by tags

On Fri, Mar 18, 2016 at 1:46 PM, Peter Steele > wrote:

What would you suggest to troubleshoot this? Clear something
isn't quite right if my log files are called "invalid-user".
That said, I have managed to get a containerized application
up and running so whatever is wrong isn't fatal. Just ugly...

On 03/17/2016 10:42 AM, haosdent wrote:

Not sure why glog could not get USER environment variable
correctly after looking its code. But should not affect you
running mesos.

On Fri, Mar 18, 2016 at 1:11 AM, haosdent > wrote:

root should be fine.

On Fri, Mar 18, 2016 at 12:53 AM, Peter Steele
> wrote:

My USER var is root. Do I need to create a non-root
user for mesos to run under?

On 03/17/2016 09:22 AM, haosdent wrote:

glog get the user name by environment variable
"USER" in Linux.

https://github.com/google/glog/blob/master/src/utilities.cc#L290-L302
I think you could check the environment variable
"USER" before you start Mesos slave.

On Fri, Mar 18, 2016 at 12:19 AM, haosdent
> wrote:

invalid-user is from glog

https://github.com/google/glog/blob/master/src/logging.cc#L1036

>W0317 06:26:41.178268   915
authenticator.cpp:511] No credentials provided,
authentication requests will be refused
>which I'm thinking might be related. What am I
missing?

I think should not related. This is a warning
message if you don't pass `credentials` flag
when start mesos master.

On Thu, Mar 17, 2016 at 10:07 PM, Peter Steele
>
wrote:

I'm testing out mesos for the first time and
after installing the software I'm seeing
numerous log files of the form

mesos-slave..invalid-user.log.INFO.20160317-062640.918

I don't see any errors in the logs
themselves, but the fact that "invalid-user"
is part of the name makes me think I'm
missing something in my config. The
mesos-master.WARNING log has the message

W0317 06:26:41.178268  915
authenticator.cpp:511] No credentials
provided, authentication requests will be
refused

which I'm thinking might be related. What am
I missing?

Peter

-- 
Best Regards,

Haosdent Huang

-- 
Best Regards,

Haosdent Huang

-- 
Best Regards,

Haosdent Huang

-- 
Best Regards,

Haosdent Huang

-- 
Regards,

Pradeep Chhetri

--
Regards,
Pradeep Chhetri

RE: [VOTE] Release Apache Mesos 0.28.0 (rc2)

2016-03-19 Thread Daniel Osborne

Is this issue a blocker? Are we moving to rc3 or proceeding with 0.28.0?

Sorry if this is a silly question, a bit new to the release / voting process.

Best,
-Dan

From: Zhitao Li [mailto:zhitaoli...@gmail.com]
Sent: Tuesday, March 15, 2016 8:15 AM
To: Jörg Schad 
Cc: user@mesos.apache.org; d...@mesos.apache.org
Subject: Re: [VOTE] Release Apache Mesos 0.28.0 (rc2)

Marked duplicate. Thanks!

On Tue, Mar 15, 2016 at 5:56 AM, Jörg Schad 
> wrote:
I believe the 
ProvisionerDockerRegistryPullerTest.ROOT_INTERNET_CURL_ShellCommand issue is 
already tracked here: https://issues.apache.org/jira/browse/MESOS-4810
@zhitaio could you check whether this describes your issue (if so could you 
close the new issue as duplicate?). Thanks!

On Tue, Mar 15, 2016 at 6:55 AM, Zhitao Li 
> wrote:
Filed https://issues.apache.org/jira/browse/MESOS-4946 to track.

All "OsTest" passes under root on my machine.

On Mon, Mar 14, 2016 at 6:30 PM, haosdent 
> wrote:
Maybe fill a ticket in https://issues.apache.org/jira/browse/MESOS would be 
more convenience for further discussion. By the way, could "OsTest.User" pass 
in your machine? It also call "os::getgid" during test.

On Tue, Mar 15, 2016 at 6:57 AM, Zhitao Li 
> wrote:
When running `sudo make check` on debian 8, I saw the following unaccounted 
test failure:

[ FAILED ] ProvisionerDockerRegistryPullerTest.ROOT_INTERNET_CURL_ShellCommand 
(1129 ms)

It seems to related to an error message with `Failed to change user to 'root': 
Failed to getgid: unknown user`

I've included verbose test log output at 
https://gist.github.com/zhitaoli/95436f4ea2df13c4b137.

On Mon, Mar 14, 2016 at 2:59 PM, Daniel Osborne 
> wrote:
+1 (non-binding)

Ran `sudo make check` on Centos 7. All tests passed.

Also ran some runtime tests with unified containerizer launching docker images 
and regular mesos tasks, as well as some tasks using the docker containerizer. 
All working as expected

Cheers,
-Dan

-Original Message-
From: Vinod Kone [mailto:vinodk...@apache.org]
Sent: Friday, March 11, 2016 12:46 PM
To: dev >; user 
>
Subject: [VOTE] Release Apache Mesos 0.28.0 (rc2)

Hi all,

Please vote on releasing the following candidate as Apache Mesos 0.28.0.

0.28.0 includes the following:

Release Notes - Mesos - Version 0.28.0

This release contains the following new features:

  * [MESOS-4343] - A new cgroups isolator for enabling the net_cls subsystem in

Linux. The cgroups/net_cls isolator allows operators to provide network

performance isolation and network segmentation for containers within a Mesos

cluster. To enable the cgroups/net_cls isolator, append `cgroups/net_cls` to

the `--isolation` flag when starting the slave. Please refer to

docs/mesos-containerizer.md for more details.

  * [MESOS-4687] - The implementation of scalar resource values (e.g., "2.5

CPUs") has changed. Mesos now reliably supports resources with up to three

decimal digits of precision (e.g., "2.501 CPUs"); resources with more than

three decimal digits of precision will be rounded. Internally, resource math

is now done using a fixed-point format that supports three decimal digits of

precision, and then converted to/from floating point for input and output,

respectively. Frameworks that do their own resource math and manipulate

fractional resources may observe differences in roundoff error and numerical

precision.

  * [MESOS-4479] - Reserved resources can now optionally include "labels".

Labels are a set of key-value pairs that can be used to associate metadata

with a reserved resource. For example, frameworks can use this feature to

distinguish between two reservations for the same role at the same agent

that are intended for different purposes.

  * [MESOS-2840] - **Experimental** support for container images in Mesos

containerizer (a.k.a. Unified Containerizer). This allows frameworks to

launch Docker/Appc containers using Mesos containerizer without relying on

docker daemon (engine) or rkt. The isolation of the containers is done using

isolators. Please refer to 
docs/container-image.md for currently supported

features and limitations.

  * [MESOS-4793] - **Experimental** support for v1 Executor HTTP API. This

allows executors to send HTTP requests to the /api/v1/executor agent

endpoint

Re: [RESULT][VOTE] Release Apache Mesos 0.28.0 (rc2)

2016-03-19 Thread Kapil Arya

Here is a link to the rpm/deb packages:

http://open.mesosphere.com/downloads/mesos/#apache-mesos-0.28.0

Best,
Kapil

On Thu, Mar 17, 2016 at 2:33 PM, Vinod Kone  wrote:

> +1
>
> @vinodkone
>
> On Mar 17, 2016, at 11:27 AM, Bill Farner  wrote:
>
> Jake - i think that would be wonderful!
>
> On Thu, Mar 17, 2016 at 11:17 AM, Jake Farrell 
> wrote:
>
>> I've been maintaining a deb/rpm set for Mesos and for Aurora and Thrift we
>> have been using the infra supported Bintray to make it available to the
>> community via http://www.apache.org/dist/${project}/${os}
>>
>> If there is interest I'd be happy to put some time into bringing my
>> patches
>> into reviews and helping setup jenkins tests, etc.
>>
>> -Jake
>>
>>
>>
>>
>>
>>
>> On Thu, Mar 17, 2016 at 1:41 PM, Vinod Kone  wrote:
>>
>> > The project itself doesn't officially release rpms/debs, but the
>> community
>> > members do.  For example, Mesosphere is planning to release rpms/debs
>> > shortly.
>> >
>> > On Thu, Mar 17, 2016 at 10:38 AM, craig w  wrote:
>> >
>> > > Great news. Do the rpm's get automatically built and released or will
>> > they
>> > > come later this week?
>> > >
>> > > On Thu, Mar 17, 2016 at 1:28 PM, Vinod Kone 
>> > wrote:
>> > >
>> > >> Hi all,
>> > >>
>> > >>
>> > >> The vote for Mesos 0.28.0 (rc2) has passed with the
>> > >>
>> > >> following votes.
>> > >>
>> > >>
>> > >> +1 (Binding)
>> > >>
>> > >> --
>> > >>
>> > >> Vinod Kone
>> > >>
>> > >> Michael Park
>> > >>
>> > >> Kapil Arya
>> > >>
>> > >>
>> > >> +1 (Non-binding)
>> > >>
>> > >> --
>> > >>
>> > >> Greg Mann
>> > >>
>> > >> Daniel Osborne
>> > >>
>> > >> Jorg Schad
>> > >>
>> > >> Zhitao Li
>> > >>
>> > >>
>> > >> There were no 0 or -1 votes.
>> > >>
>> > >>
>> > >> Please find the release at:
>> > >>
>> > >> https://dist.apache.org/repos/dist/release/mesos/0.28.0
>> > >>
>> > >>
>> > >> It is recommended to use a mirror to download the release:
>> > >>
>> > >> http://www.apache.org/dyn/closer.cgi
>> > >>
>> > >>
>> > >> 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=0.28.0
>> > >>
>> > >>
>> > >> The mesos-0.28.0.jar has been released to:
>> > >>
>> > >> https://repository.apache.org
>> > >>
>> > >>
>> > >> The website (http://mesos.apache.org) will be updated shortly to
>> > reflect
>> > >> this release.
>> > >>
>> > >>
>> > >> Thanks,
>> > >>
>> > >
>> > >
>> > >
>> > > --
>> > >
>> > > https://github.com/mindscratch
>> > > https://www.google.com/+CraigWickesser
>> > > https://twitter.com/mind_scratch
>> > > https://twitter.com/craig_links
>> > >
>> > >
>> >
>>
>
>

Re: Deploying mesos software

2016-03-19 Thread Peter Steele

Thanks for the info. The mesosphere.com/downloads link does include the 
CentOS 7 RPMs I was looking for so I'm sticking with these for now.


Peter

On 03/17/2016 07:55 AM, Chris Baker wrote:

Peter,

I've had success packaging my own RPMs for Centos 6 and 7 using the 
following:

https://github.com/mesosphere/mesos-deb-packaging
In my particular case, I use it to package custom-built versions of mesos.

Chris

On Tue, Mar 15, 2016 at 5:58 PM Peter Steele > wrote:


Ah, I was apparently looking in the wrong place. This looks more
like what I need. Thanks very much.


Peter


On 03/15/2016 02:40 PM, Avinash Sridharan wrote:

There are Mesos packages available for various distributions at
the Mesosphere download page.

Would this work ?
https://mesosphere.com/downloads/



On Tue, Mar 15, 2016 at 2:37 PM, Peter Steele > wrote:

I've just downloaded and built mesos for the first time. Once
we figure things out, we'll want to install the mesos
software on hardware different than where it is built.
Ordinarily we'd have binary only tarballs for the software
we're installing on our servers but there doesn't appear to
be a binary only distribution available yet. What's the
recommended way to build in one place and install in another?

Peter




-- 
Avinash Sridharan, Mesosphere

+1 (323) 702 5245

Re: How to kill tasks when memory exceeds the cgroup limit?

2016-03-19 Thread Dick Davies

Great!

I'm not really sure why mesos even allows RSS limiting without VMEM,
it takes down slaves like the Black Death
if you accidentally deploy a 'leaker'. I'm sure there's a use case I'm
not seeing :)

On 18 March 2016 at 16:27, Shiyao Ma  wrote:
> Thanks. The limit_swap works.

Re: How to kill tasks when memory exceeds the cgroup limit?

2016-03-19 Thread Dick Davies

Last time I tried (not on the latest release) I also had to have
cgroups set to limit swap, otherwise
as soon as the process hit the RAM limit it would just start to consume swap.

try adding --cgroups_limit_swap to the slaves startup flags.

On 17 March 2016 at 16:21, Shiyao Ma  wrote:
> Hi,
>
>
> For the slave side:
> export MESOS_RESOURCES='cpus:4;mem:180'
> export MESOS_ISOLATION='cgroups/cpu,cgroups/mem'
>
> For the framework,
> It accepts the offer from the slave and sends tasks with memory spec less
> than offered.
>
>
> However, the task actually *deliberately* asks for an arbitrary large memory
> during runtime.
>
> My assumption is that the slave will kill the task.  However, it doesn't.
>
> So here goes my question. How does slave handle the 'runtime memory
> exceeding cgroup limit' behavior? Will any handlers be invoked?
>
>
>
> Regards.

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

2016-03-19 Thread Kapil Arya

+1 (binding).

You can find the links to rpm/deb files for this RC here:

http://open.mesosphere.com/downloads/mesos-rc/

On Thu, Mar 17, 2016 at 12:58 PM, Michael Park  wrote:

> +1 (binding)
>
> Internal CI results with the corresponding JIRA tickets for the failed
> tests:
>
> CentOS 6 (non-SSL):
> CentOS 6 (SSL):
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 )
>
> CentOS 7 (non-SSL):
>   - ProvisionerDockerRegistryPullerTest.ROOT_INTERNET_CURL_ShellCommand
> (MESOS-4810)
>
> CentOS 7 (SSL):
>   - LinuxFilesystemIsolatorTest.ROOT_MultipleContainers (Fixed in master)
> (MESOS-4912 )
>   - ProvisionerDockerRegistryPullerTest.ROOT_INTERNET_CURL_ShellCommand
> (MESOS-4810 )
>
> Debian 8 (non-SSL):
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 )
>
> Debian 8 (SSL):
>   - NsTest.ROOT_setns
> (MESOS-3000 )
>   - MemoryPressureMesosTest.CGROUPS_ROOT_SlaveRecovery
> (MESOS-4047 )
>
> Ubuntu 12 (non-SSL):
>   - HealthCheckTest.ROOT_DOCKER_DockerHealthStatusChange
> Failed with MESOS-2017
> 
>
> Ubuntu 12 (SSL): Success!
> Ubuntu 14 (non-SSL): Success!
> Ubuntu 14 (SSL): Success!
> Ubuntu 15 (non-SSL): Success!
> Ubuntu 15 (SSL): Success!
>
> On 11 March 2016 at 15:46, Vinod Kone  wrote:
>
> > Hi all,
> >
> >
> > Please vote on releasing the following candidate as Apache Mesos 0.28.0.
> >
> >
> > 0.28.0 includes the following:
> >
> >
> >
> 
> >
> > Release Notes - Mesos - Version 0.28.0
> >
> > 
> >
> > This release contains the following new features:
> >
> >   * [MESOS-4343] - A new cgroups isolator for enabling the net_cls
> > subsystem in
> >
> > Linux. The cgroups/net_cls isolator allows operators to provide
> network
> >
> > performance isolation and network segmentation for containers within
> a
> > Mesos
> >
> > cluster. To enable the cgroups/net_cls isolator, append
> > `cgroups/net_cls` to
> >
> > the `--isolation` flag when starting the slave. Please refer to
> >
> > docs/mesos-containerizer.md for more details.
> >
> >
> >   * [MESOS-4687] - The implementation of scalar resource values (e.g.,
> "2.5
> >
> > CPUs") has changed. Mesos now reliably supports resources with up to
> > three
> >
> > decimal digits of precision (e.g., "2.501 CPUs"); resources with more
> > than
> >
> > three decimal digits of precision will be rounded. Internally,
> resource
> > math
> >
> > is now done using a fixed-point format that supports three decimal
> > digits of
> >
> > precision, and then converted to/from floating point for input and
> > output,
> >
> > respectively. Frameworks that do their own resource math and
> manipulate
> >
> > fractional resources may observe differences in roundoff error and
> > numerical
> >
> > precision.
> >
> >
> >   * [MESOS-4479] - Reserved resources can now optionally include
> "labels".
> >
> > Labels are a set of key-value pairs that can be used to associate
> > metadata
> >
> > with a reserved resource. For example, frameworks can use this
> feature
> > to
> >
> > distinguish between two reservations for the same role at the same
> > agent
> >
> > that are intended for different purposes.
> >
> >
> >   * [MESOS-2840] - **Experimental** support for container images in Mesos
> >
> > containerizer (a.k.a. Unified Containerizer). This allows frameworks
> to
> >
> > launch Docker/Appc containers using Mesos containerizer without
> relying
> > on
> >
> > docker daemon (engine) or rkt. The isolation of the containers is
> done
> > using
> >
> > isolators. Please refer to docs/container-image.md for currently
> > supported
> >
> > features and limitations.
> >
> >
> >   * [MESOS-4793] - **Experimental** support for v1 Executor HTTP API.
> This
> >
> > allows executors to send HTTP requests to the /api/v1/executor agent
> >
> > endpoint without the need for an executor driver. Please refer to
> >
> > docs/executor-http-api.md for more details.
> >
> >
> >   * [MESOS-4370] Added support for service discovery of Docker containers
> > that
> >
> > use Docker Remote API v1.21.
> >
> >
> > Additional API Changes:
> >
> >   * [MESOS-4066] - Agent should not return partial state when a request
> is
> > made to /state endpoint during recovery.
> >
> >   * [MESOS-4547] - Introduce TASK_KILLING state.
> >
> >   * [MESOS-4712] - Remove 'force' field from the Subscribe Call in v1
> > Scheduler API.
> >
> >   * [MESOS-4591] - Change the object

Re: How to kill tasks when memory exceeds the cgroup limit?

2016-03-19 Thread haosdent

Does your oom killer enable? Could check by cat memory.oom_control file.

On Fri, Mar 18, 2016 at 12:21 AM, Shiyao Ma  wrote:

> Hi,
>
>
> For the slave side:
> export MESOS_RESOURCES='cpus:4;mem:180'
> export MESOS_ISOLATION='cgroups/cpu,cgroups/mem'
>
> For the framework,
> It accepts the offer from the slave and sends tasks with memory spec less
> than offered.
>
>
> However, the task actually *deliberately* asks for an arbitrary large
> memory during runtime.
>
> My assumption is that the slave will kill the task.  However, it doesn't.
>
> So here goes my question. How does slave handle the 'runtime memory
> exceeding cgroup limit' behavior? Will any handlers be invoked?
>
>
>
> Regards.
>



-- 
Best Regards,
Haosdent Huang

Resource Isolation per Framework

2016-03-19 Thread Pradeep Chhetri

Hello All,

I am looking for ways to isolate resources per framework basis. Basically
what i want to achieve is segregating machines on which tasks from a
framework can run and having a common set of machines which can be shared
across all frameworks. So I can think of assigning one role per framework
and one role as common for all frameworks. In my case, I will be having
roles: marathon, storm, jenkins, spark & common.

>From Roles & ACLs documentation: I can see that I can assign these roles to
mesos agents and define ACLs to allow frameworks to register with mesos
master with particular roles.

I have few questions:

1. Can I configure a mesos agent to be associated with multiple roles. I
can see that there is a parameter --default-role to assign role to a mesos
slave but I am not sure whether we can pass multiple roles as value.

2. From ACL documentation, I can provide authorization to a framework so
that it can register with multiple roles like this:


   1.

{
  "register_frameworks": [
   {
 "principals": {
   "values": ["marathon"]
 },
 "roles": {
   "values": ["marathon", "common"]
 }
   }
 ]
}



But I don't think if we can register a framework to mesos master with
multiple roles. I can see this open issue regarding this:
https://issues.apache.org/jira/browse/MESOS-1763

Can someone provide me some alternative way regarding what i am trying to
achieve.

--
Regards,
Pradeep Chhetri

Re: HTTP API

2016-03-19 Thread Zameer Manji

+1

I am also interested in knowing the state of the HTTP API. I have heard
that it stabilizing the API might be tied with Mesos 1.0 but I don't have a
source for that. Can a PMC member comment on what the plan is?

On Mon, Mar 14, 2016 at 2:30 PM, Dario Rexin  wrote:

> Hi all,
>
> since the introduction of the HTTP API in 0.24 around 7.5 months have
> passed. What are the plans to make this API stable? There are already
> features (inverse offers) that are exclusively available through this API,
> so it would be great to have a timeline, as I think for most people it’s
> impossible to use experimental features in production.
>
> Thanks,
> Dario
>
> --
> Zameer Manji
>
>

Re: What are the invalid-user.log files?

2016-03-19 Thread Pradeep Chhetri

I think it is an upstart issue. I am noticing this issue in Ubuntu 14.04
which uses upstart. This is what i can debug so far:


According to this documentation:
http://upstart.ubuntu.com/cookbook/#job-environment

When Upstart runs a job, it provides it with a very restrictive environment
which contains just two system variables:

   - TERM
   - PATH


These are the exact two variables i can notice in proc filesystem set as
well.

I will post if i find something more.


On Fri, Mar 18, 2016 at 2:54 PM, Peter Steele  wrote:

> Yes, I see that as well. Also the case for the mesos master. That explains
> the invalid-user, but why isn't these processes picking up $USER?
>
>
> On 03/18/2016 07:31 AM, Pradeep Chhetri wrote:
>
> I can see that USER environment variable is not set for mesos-slave
> process from /proc//environ.
>
> On Fri, Mar 18, 2016 at 2:19 PM, Pradeep Chhetri <
> pradeep.chhetr...@gmail.com> wrote:
>
>> My mesos cluster also produces logs
>> like mesos-slave.ip-172-31-45-33.invalid-user.log.ERROR. I guess log file
>> name shouldnt affect you all because generally you ship these logs in some
>> centralized logging system like logstash/splunk and search there by tags
>>
>> On Fri, Mar 18, 2016 at 1:46 PM, Peter Steele < 
>> pste...@peaxy.net> wrote:
>>
>>> What would you suggest to troubleshoot this? Clear something isn't quite
>>> right if my log files are called "invalid-user". That said, I have managed
>>> to get a containerized application up and running so whatever is wrong
>>> isn't fatal. Just ugly...
>>>
>>>
>>> On 03/17/2016 10:42 AM, haosdent wrote:
>>>
>>> Not sure why glog could not get USER environment variable correctly
>>> after looking its code. But should not affect you running mesos.
>>>
>>> On Fri, Mar 18, 2016 at 1:11 AM, haosdent < 
>>> haosd...@gmail.com> wrote:
>>>
 root should be fine.

 On Fri, Mar 18, 2016 at 12:53 AM, Peter Steele < 
 pste...@peaxy.net> wrote:

> My USER var is root. Do I need to create a non-root user for mesos to
> run under?
>
>
> On 03/17/2016 09:22 AM, haosdent wrote:
>
> glog get the user name by environment variable "USER" in Linux.
> 
> https://github.com/google/glog/blob/master/src/utilities.cc#L290-L302
> I think you could check the environment variable "USER" before you start
> Mesos slave.
>
> On Fri, Mar 18, 2016 at 12:19 AM, haosdent < 
> haosd...@gmail.com> wrote:
>
>> invalid-user is from glog
>> 
>> https://github.com/google/glog/blob/master/src/logging.cc#L1036
>>
>> >W0317 06:26:41.178268   915 authenticator.cpp:511] No credentials
>> provided, authentication requests will be refused
>> >which I'm thinking might be related. What am I missing?
>>
>> I think should not related. This is a warning message if you don't
>> pass `credentials` flag when start mesos master.
>>
>> On Thu, Mar 17, 2016 at 10:07 PM, Peter Steele < 
>> pste...@peaxy.net> wrote:
>>
>>> I'm testing out mesos for the first time and after installing the
>>> software I'm seeing numerous log files of the form
>>>
>>> mesos-slave..invalid-user.log.INFO.20160317-062640.918
>>>
>>> I don't see any errors in the logs themselves, but the fact that
>>> "invalid-user" is part of the name makes me think I'm missing something 
>>> in
>>> my config. The mesos-master.WARNING log has the message
>>>
>>> W0317 06:26:41.178268   915 authenticator.cpp:511] No credentials
>>> provided, authentication requests will be refused
>>>
>>> which I'm thinking might be related. What am I missing?
>>>
>>> Peter
>>>
>>>
>>
>>
>> --
>> Best Regards,
>> Haosdent Huang
>>
>
>
>
> --
> Best Regards,
> Haosdent Huang
>
>
>


 --
 Best Regards,
 Haosdent Huang

>>>
>>>
>>>
>>> --
>>> Best Regards,
>>> Haosdent Huang
>>>
>>>
>>>
>>
>>
>> --
>> Regards,
>> Pradeep Chhetri
>>
>
>
>
> --
> Regards,
> Pradeep Chhetri
>
>
>


-- 
Regards,
Pradeep Chhetri

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

2016-03-19 Thread Vinod Kone

On Wed, Mar 16, 2016 at 5:59 PM, Daniel Osborne <
daniel.osbo...@metaswitch.com> wrote:

> Is this issue a blocker? Are we moving to rc3 or proceeding with 0.28.0?
>

It was not marked as such, so I'm guessing not. @Jie and @Zhitao, can you
confirm?

Also, we still need some binding votes for this release to go official.
@committers: can you please vote?

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

2016-03-19 Thread Vinod Kone

+1 (binding)

Tested on ASF CI (ubuntu 14.04 w/ gcc and clang).

On Wed, Mar 16, 2016 at 6:07 PM, Vinod Kone  wrote:

>
> On Wed, Mar 16, 2016 at 5:59 PM, Daniel Osborne <
> daniel.osbo...@metaswitch.com> wrote:
>
>> Is this issue a blocker? Are we moving to rc3 or proceeding with 0.28.0?
>>
>
> It was not marked as such, so I'm guessing not. @Jie and @Zhitao, can you
> confirm?
>
> Also, we still need some binding votes for this release to go official.
> @committers: can you please vote?
>

Re: [RESULT][VOTE] Release Apache Mesos 0.28.0 (rc2)

2016-03-19 Thread Vinod Kone

The project itself doesn't officially release rpms/debs, but the community
members do.  For example, Mesosphere is planning to release rpms/debs
shortly.

On Thu, Mar 17, 2016 at 10:38 AM, craig w  wrote:

> Great news. Do the rpm's get automatically built and released or will they
> come later this week?
>
> On Thu, Mar 17, 2016 at 1:28 PM, Vinod Kone  wrote:
>
>> Hi all,
>>
>>
>> The vote for Mesos 0.28.0 (rc2) has passed with the
>>
>> following votes.
>>
>>
>> +1 (Binding)
>>
>> --
>>
>> Vinod Kone
>>
>> Michael Park
>>
>> Kapil Arya
>>
>>
>> +1 (Non-binding)
>>
>> --
>>
>> Greg Mann
>>
>> Daniel Osborne
>>
>> Jorg Schad
>>
>> Zhitao Li
>>
>>
>> There were no 0 or -1 votes.
>>
>>
>> Please find the release at:
>>
>> https://dist.apache.org/repos/dist/release/mesos/0.28.0
>>
>>
>> It is recommended to use a mirror to download the release:
>>
>> http://www.apache.org/dyn/closer.cgi
>>
>>
>> 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=0.28.0
>>
>>
>> The mesos-0.28.0.jar has been released to:
>>
>> https://repository.apache.org
>>
>>
>> The website (http://mesos.apache.org) will be updated shortly to reflect
>> this release.
>>
>>
>> Thanks,
>>
>
>
>
> --
>
> https://github.com/mindscratch
> https://www.google.com/+CraigWickesser
> https://twitter.com/mind_scratch
> https://twitter.com/craig_links
>
>

Re: Compute event at Twitter HQ - 03/31

2016-03-19 Thread haosdent

Would it have youtube live link?

On Thu, Mar 17, 2016 at 12:38 AM, Ian Downes  wrote:

> Hello everyone,
>
> I'd like to call attention to an event the Compute group at Twitter is
> holding at the end of the month where there will be a few
> Aurora/Mesos-related talks:
>
> 1. David Robinson, one of our SREs, will talk about how our small team
> of SREs manages what is possibly the largest Mesos cluster in
> existence.
> 2. David McLaughlin, Aurora committer/PMC member, will talk about
> Workflows, an internal tool we've built to orchestrate deployments
> across Aurora clusters.
> 3. David Hagar, Engineering Manager at TellApart, will talk about
> running Aurora/Mesos in AWS.
>
> On top of that there will be lots of other great talks about how we
> run the entirety of our compute infrastructure.
>
> The event is on the evening of March 31st at Twitter HQ in San
> Francisco. I hope to see many of you there!
>
> https://www.eventbrite.com/e/compute-tickets-22811196904
>
> Thanks,
>
> Ian
>
> Note: This is nearly a straight copy of an email that Joshua sent out
> to the Aurora mailing lists.
>



-- 
Best Regards,
Haosdent Huang

47 matches

Mail list logo