That showed me what wasn't working. If you start the mesos agent at all
before setting attributes (or if you change attributes) you need to make
sure it doesn't recover old live executors.
The error:
Failed to perform recovery: Incompatible agent info detected.
The solution:
Step 1: rm -f
Unfortunately we log termination messages to stderr rather than the logging
files. Can you show stderr? I suspect we're printing the exit message there.
See: https://issues.apache.org/jira/browse/MESOS-5854
On Fri, Jul 29, 2016 at 5:57 PM, Douglas Nelson wrote:
> It might
It might be an issue with the mesos-init-wrapper? I'm using that to set the
flag via config files. I'll have to look through it and see exactly what
it's doing when it sets the attributes flag.
On Fri, Jul 29, 2016 at 6:48 PM, Douglas Nelson wrote:
> I'm pretty sure I set
I'm pretty sure I set the flag right. Here is the agent's info:
Log file created at: 2016/07/29 18:25:16
Running on machine: lubuntu
Log line format: [IWEF]mmdd hh:mm:ss.uu threadid file:line] msg
I0729 18:25:16.494326 4559 logging.cpp:194] INFO level logging started!
I0729 18:25:16.496150
Works fine for me. Make sure the agent isn't just complaining about
invalid flags.
i.e. This is invalid:
--attributes="something"
This is valid:
--attributes="something:foo"
--attributes="something:foo; nothing:bar"
And make sure your agent's work directory doesn't contain info from an
agent
When I set any attributes for the agent node it fails to run. No
mesos-slave.ERROR log is created. I am using mesos 1.0.0 from the
mesosphere package, but I also tried building it and had the same issue.
As soon as I remove the --attributes flag the agent runs normally and
registers itself with
6 matches
Mail list logo