Okay, "*" or '*' works fine, which is slightly less horrible, so I can
update the myriad-config-default.yml accordingly to put quotes around * for
frameworkRole.
--John
On Wed, Aug 17, 2016 at 3:44 PM, John Yost wrote:
> The * is causing error within the yaml parsing (see
The * is causing error within the yaml parsing (see yaml special characters
issues @http://bit.ly/2b507G3) I "fixed" this by setting frameworkRole =
/* and then updating MyriadConfiguration.getFrameworkRole() to strip off
the /. Blech. We can do this or put in a constant like ANY_ROLE or
Ah that worked! I'll let you know if I run into any more issues but it looks
like its good now. Thanks for the help!
Matt
-Original Message-
From: Darin Johnson [mailto:dbjohnson1...@gmail.com]
Sent: Wednesday, August 17, 2016 3:18 PM
To: Dev
Subject: Re: Resource manager error
Take
Odd, please send screen shot of executor startup.
--John
On Wed, Aug 17, 2016 at 3:13 PM, Matthew J. Loppatto wrote:
> I'm running the resource manager as the root user. Checking a few of my
> nodes, JAVA_HOME is set on all of them for the root env. Am I ok to be
>
Take a look at your myriad configuration under yarnEnvironment. You can
set JAVA_HOME there, should solve the issue. See below.
yarnEnvironment:
YARN_HOME: /usr/local/hadoop
#HADOOP_CONF_DIR=config
#HADOOP_TMP_DIR=$MESOS_SANDBOX
#YARN_HOME: hadoop-2.7.0 #this should be relative if nodeManagerUri
Progress is nice! What user are you running myriad as? root? yarn? If it is
the former and you are running via sudo, I've seen this type of error. If
so, sudo to the root user and then launch. Otherwise, please type in env if
you are on linux box and confirm you see JAVA_HOME for the user you are
Hey John,
I set up a role for myriad, restarted mesos-master, and now I'm seeing RMs
starting on the Mesos UI, but they fail with the message "lost with exit
status: 256". The executor log says "Error: JAVA_HOME is not set and could not
be found." $JAVA_HOME is set on all my slaves as far as
JIRA ticket # 239
On Wed, Aug 17, 2016 at 2:21 PM, John Yost wrote:
> Hi Guys,
>
> Sorry, just checked email, setting role to * does indeed cause this
> error. Matt -> if you set it to nothing or whatever role you have your
> mesos slaves configured as, that will fix
John Yost created MYRIAD-239:
Summary: Setting frameworkRole to * causes exception
Key: MYRIAD-239
URL: https://issues.apache.org/jira/browse/MYRIAD-239
Project: Myriad
Issue Type: Bug
Hey Darin,
Commenting out myriadFrameworkRole got rid of the log message about the missing
role, but I'm still seeing the "n must be positive" exception.
The only other thing of interest I see in the log is WARN
fair.AllocationFileLoaderService: fair-scheduler.xml not found on the
classpath.
Hi Guys,
Sorry, just checked email, setting role to * does indeed cause this error.
Matt -> if you set it to nothing or whatever role you have your mesos
slaves configured as, that will fix this. My apologies for failing to log
and fix this. Darin -> I will enter a JIRA ticket for this.
To echo
11 matches
Mail list logo