Hi folks,
We will try BlueJeans VC (https://bluejeans.com/272369669) this time (today
3 PM PST) for our monthly community sync.
Agenda (tentative)
Optimistic offers
Fetcher cache
Release cadence
Review process
Committership
See you in a few hours,
Vinod
P.S: If
Hi,
Parameters in the mesos-master specifically for authorization and
authentication
--acls=/root/acl.json --authenticate --credentials=/root/passwd_file
--roles=apps,dev-ops --quorum=2
Parameters I pass in marathon
--mesos_role apps --framework_name marathon
--mesos_authentication_principal
All the nodes has the credentials and authentication_secret_file where the
mesos-master and marathon pick it from a standard location.
On Fri, Mar 6, 2015 at 12:15 PM, Sivaram Kannan sivara...@gmail.com wrote:
Hi,
Parameters in the mesos-master specifically for authorization and
Anyone out there have a logstash config for Mesos log format they'd like to
share? I'm finding the date format stubbornly difficult to map to timestamp.
I'm not very familiar with Marathon, but the 'user' in the 'run_tasks' ACL
is the unix user that the executor/run process runs as. This user is set by
frameworks by setting 'CommandInfo.user'.
On Thu, Mar 5, 2015 at 9:06 AM, Sivaram Kannan sivara...@gmail.com wrote:
Hi,
The user that is
Hi,
The user that is defined as part of Mesos's Authorization ACL, which user
is it? Taking marathon framework as example, the users defined as part of
run_tasks principal, is it the user that is used to run marathon executable
or the unix user available in the mesos-slave's?
Documentation in
Hi,
I have a 3 node mesos-master cluster. Say if node-1 is elected as
mesos-master and if I run a framework(Marathon) in the same node,
authentication succeeds. But if I run the framework from the node-2,
authentication for the framework fails. The machines are all similarly
configured in terms
Got it working with LIBPROCESS_IP parameter in the marathon. Thanks a lot
for pointing out.
On Fri, Mar 6, 2015 at 12:50 PM, Sivaram Kannan sivara...@gmail.com wrote:
Opps. You are right on target. These are all run as containers. The
mesos-master is unable to reach the marathon when it is in
This is the config we use for mesos logs
MESOSTIMESTAMP %{MONTHNUM}%{MONTHDAY} %{HOUR}:%{MINUTE}:%{SECOND}
MESOSLOG
%{DATA:loglevel}%{MESOSTIMESTAMP:timestamp}\s+%{POSINT:pid}\s+%{NOTSPACE:class}:
in logstash config
if [type] == mesos {
grok {
patterns_dir = [path to your patterns
Opps. You are right on target. These are all run as containers. The
mesos-master is unable to reach the marathon when it is in another node.
Did not see the master logs what it is complaining about.
I0305 17:31:52.01963516 authenticator.hpp:166] Creating new server SASL
connection
W0305
Hi!
Is there any documentation or points you can suggest for fine tuning Mesos?
I am running a small cluster and I am noticing delays on staging and
running the hadoop task trackers that are added last. I actually had to
increase the executor_registration_timeout since it is taking more than a
11 matches
Mail list logo