Re: [DISCUSS] Leave Apache and the Incubator

+1 > On Jan 2, 2020, at 11:51 PM, Javi Roman wrote: > > Please vote to retire Myriad from the ASF Incubator. My take is that > Myriad has failed to get adequate community traction in the ASF > Incubator and the administrative work of the ASF is more of a burden > than a benefit to the project.

[jira] [Assigned] (MYRIAD-238) Convert groovy-based unit tests to JUnit tests

[ https://issues.apache.org/jira/browse/MYRIAD-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost reassigned MYRIAD-238: Assignee: (was: John Yost) > Convert groovy-based unit tests to JUnit te

[jira] [Assigned] (MYRIAD-229) Put upper limit on FGS

[ https://issues.apache.org/jira/browse/MYRIAD-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost reassigned MYRIAD-229: Assignee: (was: John Yost) > Put upper limit on

[jira] [Assigned] (MYRIAD-237) SchedulerState getKillableTasks method mislabelled

[ https://issues.apache.org/jira/browse/MYRIAD-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost reassigned MYRIAD-237: Assignee: (was: John Yost) > SchedulerState getKillableTasks method mislabel

[jira] [Assigned] (MYRIAD-225) Loading state in MyriadStateStore leads to inconsistent unit test results

[ https://issues.apache.org/jira/browse/MYRIAD-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost reassigned MYRIAD-225: Assignee: (was: John Yost) > Loading state in MyriadStateStore leads to inconsistent u

[jira] [Assigned] (MYRIAD-239) Setting frameworkRole to * causes exception

[ https://issues.apache.org/jira/browse/MYRIAD-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost reassigned MYRIAD-239: Assignee: (was: John Yost) > Setting frameworkRole to * causes except

Re: [Vote] Retire Myriad

+1 On Tue, Jun 20, 2017 at 10:22 AM, Klaus Ma wrote: > +1 > > On Tue, Jun 20, 2017 at 10:13 PM Brandon Gulla > wrote: > > > +1 (if the vote is open to non-comitters) > > > > > > > > On Tue, Jun 20, 2017 at 9:22 AM, Darin Johnson

[jira] [Reopened] (MYRIAD-225) Loading state in MyriadStateStore leads to inconsistent unit test results

[ https://issues.apache.org/jira/browse/MYRIAD-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost reopened MYRIAD-225: -- Was able to recreate this issue following failed Travis CI build. > Loading state in MyriadStateSt

[jira] [Updated] (MYRIAD-240) Created lower limit on FGS

[ https://issues.apache.org/jira/browse/MYRIAD-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost updated MYRIAD-240: - Issue Type: New Feature (was: Improvement) > Created lower limit on

[jira] [Created] (MYRIAD-241) Create Docker container based upon Cloudera Hadoop distribution

John Yost created MYRIAD-241: Summary: Create Docker container based upon Cloudera Hadoop distribution Key: MYRIAD-241 URL: https://issues.apache.org/jira/browse/MYRIAD-241 Project: Myriad

[jira] [Created] (MYRIAD-240) Created lower limit on FGS

John Yost created MYRIAD-240: Summary: Created lower limit on FGS Key: MYRIAD-240 URL: https://issues.apache.org/jira/browse/MYRIAD-240 Project: Myriad Issue Type: Bug Reporter: John

[jira] [Commented] (MYRIAD-237) SchedulerState getKillableTasks method mislabelled

[ https://issues.apache.org/jira/browse/MYRIAD-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15431285#comment-15431285 ] John Yost commented on MYRIAD-237: -- In MYRIAD-229 PR > SchedulerState getKillableTasks met

[jira] [Closed] (MYRIAD-234) Increased JUnit Test Coverage

[ https://issues.apache.org/jira/browse/MYRIAD-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost closed MYRIAD-234. Merged into master by Darin > Increased JUnit Test Cover

[jira] [Resolved] (MYRIAD-225) Loading state in MyriadStateStore leads to inconsistent unit test results

[ https://issues.apache.org/jira/browse/MYRIAD-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost resolved MYRIAD-225. -- Resolution: Fixed Assignee: John Yost JUnit tests now pass repeatably > Loading st

Re: Resource manager error

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 <hokiege...@gmail.com> wrote: > The * is causing error within th

Re: Resource manager error

tthew J. Loppatto < > mloppa...@keywcorp.com > > 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 using openjdk1.7 or do I have to use Oracle jdk? > >

Re: Resource manager error

nv. Am I ok to be > using openjdk1.7 or do I have to use Oracle jdk? > > Matt > > -Original Message- > From: John Yost [mailto:hokiege...@gmail.com] > Sent: Wednesday, August 17, 2016 3:01 PM > To: dev@myriad.incubator.apache.org > Subject: Re: Resource manager error

Re: Resource manager error

ng something? > > Thanks! > Matt > > -Original Message- > From: John Yost [mailto:hokiege...@gmail.com] > Sent: Wednesday, August 17, 2016 2:38 PM > To: dev@myriad.incubator.apache.org > Subject: Re: Resource manager error > > Please uncomment frameworkRole and

Re: Resource manager error

JIRA ticket # 239 On Wed, Aug 17, 2016 at 2:21 PM, John Yost <hokiege...@gmail.com> 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 conf

[jira] [Created] (MYRIAD-239) Setting frameworkRole to * causes exception

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

Re: Resource manager error

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

[jira] [Created] (MYRIAD-238) Convert groovy-based unit tests to JUnit tests

John Yost created MYRIAD-238: Summary: Convert groovy-based unit tests to JUnit tests Key: MYRIAD-238 URL: https://issues.apache.org/jira/browse/MYRIAD-238 Project: Myriad Issue Type: Test

[jira] [Updated] (MYRIAD-236) YarnNodeCapacityManager--enable reset in setNodeCapacity or make setNodeCapacity protected/private

[ https://issues.apache.org/jira/browse/MYRIAD-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost updated MYRIAD-236: - Priority: Minor (was: Major) > YarnNodeCapacityManager--enable reset in setNodeCapacity or m

[jira] [Issue Comment Deleted] (MYRIAD-236) YarnNodeCapacityManager--enable reset in setNodeCapacity or make setNodeCapacity protected/private

[ https://issues.apache.org/jira/browse/MYRIAD-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost updated MYRIAD-236: - Comment: was deleted (was: Investigating this further, the incrementNodeCapacity

[jira] [Commented] (MYRIAD-236) YarnNodeCapacityManager--enable reset in setNodeCapacity or make setNodeCapacity protected/private

[ https://issues.apache.org/jira/browse/MYRIAD-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15407772#comment-15407772 ] John Yost commented on MYRIAD-236: -- Investigating this further, the incrementNodeCapacity

[jira] [Resolved] (MYRIAD-234) Increased JUnit Test Coverage

[ https://issues.apache.org/jira/browse/MYRIAD-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost resolved MYRIAD-234. -- Resolution: Fixed Code merged in from PR 86, work complete > Increased JUnit Test Cover

[jira] [Resolved] (MYRIAD-220) Improve reliability of kill task messaging

[ https://issues.apache.org/jira/browse/MYRIAD-220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost resolved MYRIAD-220. -- Resolution: Fixed Fix Version/s: Myriad 0.3.0 Development complete, tested on AWS cluster

[jira] [Resolved] (MYRIAD-200) Increase JUnit Test Coverage

[ https://issues.apache.org/jira/browse/MYRIAD-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost resolved MYRIAD-200. -- Resolution: Fixed Corresponding PR #78 integrated into master, issue resolved. > Increase JUnit T

[jira] [Closed] (MYRIAD-202) minimesos-based integration tests

[ https://issues.apache.org/jira/browse/MYRIAD-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost closed MYRIAD-202. Resolution: Won't Fix JUnit test coverage obviates the need for this story > minimesos-based integrat

[jira] [Created] (MYRIAD-234) Increased JUnit Test Coverage

John Yost created MYRIAD-234: Summary: Increased JUnit Test Coverage Key: MYRIAD-234 URL: https://issues.apache.org/jira/browse/MYRIAD-234 Project: Myriad Issue Type: Improvement

[jira] [Created] (MYRIAD-232) Display Flex Down/Up errors to UI

John Yost created MYRIAD-232: Summary: Display Flex Down/Up errors to UI Key: MYRIAD-232 URL: https://issues.apache.org/jira/browse/MYRIAD-232 Project: Myriad Issue Type: Improvement

[jira] [Created] (MYRIAD-227) Jersey-based exception prevents refresh of Myriad UI

John Yost created MYRIAD-227: Summary: Jersey-based exception prevents refresh of Myriad UI Key: MYRIAD-227 URL: https://issues.apache.org/jira/browse/MYRIAD-227 Project: Myriad Issue Type: Bug

[jira] [Created] (MYRIAD-226) Clean up missing generics parameters and unused object references

John Yost created MYRIAD-226: Summary: Clean up missing generics parameters and unused object references Key: MYRIAD-226 URL: https://issues.apache.org/jira/browse/MYRIAD-226 Project: Myriad

[jira] [Created] (MYRIAD-225) Loading state in MyriadStateStore leads to inconsistent unit test results

John Yost created MYRIAD-225: Summary: Loading state in MyriadStateStore leads to inconsistent unit test results Key: MYRIAD-225 URL: https://issues.apache.org/jira/browse/MYRIAD-225 Project: Myriad

[jira] [Created] (MYRIAD-222) Triage killable tasks to prevent retries on inaccessible nodes

John Yost created MYRIAD-222: Summary: Triage killable tasks to prevent retries on inaccessible nodes Key: MYRIAD-222 URL: https://issues.apache.org/jira/browse/MYRIAD-222 Project: Myriad Issue

[jira] [Updated] (MYRIAD-200) Increase JUnit Test Coverage

[ https://issues.apache.org/jira/browse/MYRIAD-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost updated MYRIAD-200: - Summary: Increase JUnit Test Coverage (was: Increased JUnit Test Coverage) > Increase JUnit T

[jira] [Created] (MYRIAD-216) Make OfferLifecycleManager thread safe

John Yost created MYRIAD-216: Summary: Make OfferLifecycleManager thread safe Key: MYRIAD-216 URL: https://issues.apache.org/jira/browse/MYRIAD-216 Project: Myriad Issue Type: Bug

[jira] [Updated] (MYRIAD-200) Increased JUnit Test Coverage

[ https://issues.apache.org/jira/browse/MYRIAD-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost updated MYRIAD-200: - Summary: Increased JUnit Test Coverage (was: Increased Unit Test and Integration Testing) > Increa

[jira] [Assigned] (MYRIAD-202) minimesos-based integration tests

[ https://issues.apache.org/jira/browse/MYRIAD-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Yost reassigned MYRIAD-202: Assignee: John Yost > minimesos-based integration te

[jira] [Created] (MYRIAD-210) Fully implement ZookeeperHealthCheck

John Yost created MYRIAD-210: Summary: Fully implement ZookeeperHealthCheck Key: MYRIAD-210 URL: https://issues.apache.org/jira/browse/MYRIAD-210 Project: Myriad Issue Type: Improvement

[jira] [Commented] (MYRIAD-86) Consider an API for desired # instances, rather than flex up/down

[ https://issues.apache.org/jira/browse/MYRIAD-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310798#comment-15310798 ] John Yost commented on MYRIAD-86: - I think this is a good idea, would recommend an integrated API where

[jira] [Created] (MYRIAD-209) Abstract Health API

John Yost created MYRIAD-209: Summary: Abstract Health API Key: MYRIAD-209 URL: https://issues.apache.org/jira/browse/MYRIAD-209 Project: Myriad Issue Type: Improvement Components

[jira] [Commented] (MYRIAD-134) Support Zookeeper based implementation of RMStateStore for storing Myriad state

[ https://issues.apache.org/jira/browse/MYRIAD-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15310555#comment-15310555 ] John Yost commented on MYRIAD-134: -- Good suggestion, and I recommend taking it a step further by enabling

request for write privileges for Myriad Confluence

Hi Everyone, I am working with Darin Johnson on Myriad and would like write access to our Confluence site to start adding FAQ topics. Thanks --John

Re: Spark and Flink

Cool! --John On Thu, May 19, 2016 at 1:05 PM, Darin Johnson wrote: > Just wanted to let people know I tried running a Spark and a Flink job > today on Myriad with zero sized node managers. It just worked! > > This shouldn't be interpreted as it's not going to had

[jira] [Commented] (MYRIAD-203) Update NodeTask constructor to ensure uniqueness

[ https://issues.apache.org/jira/browse/MYRIAD-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15287432#comment-15287432 ] John Yost commented on MYRIAD-203: -- This can be accomplished by retaining default equals method (returns

[jira] [Created] (MYRIAD-203) Update NodeTask constructor to ensure uniqueness

John Yost created MYRIAD-203: Summary: Update NodeTask constructor to ensure uniqueness Key: MYRIAD-203 URL: https://issues.apache.org/jira/browse/MYRIAD-203 Project: Myriad Issue Type: Bug

[jira] [Commented] (MYRIAD-198) Remove optionals when sane defaults are available

[ https://issues.apache.org/jira/browse/MYRIAD-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15287094#comment-15287094 ] John Yost commented on MYRIAD-198: -- Updated per feedback from Darin, returning empty Map objects

what should go in myriad-commons package, and do we need it?

Hi Everyone, I noticed there are only three classes and no JUnit tests in the myriad-commons sub-project. All three of those classes appear to be closely coupled to classes in myriad-executor and myriad-scheduler. Is there a definitive need for the myriad-commons sub-project? I can see where it

[jira] [Commented] (MYRIAD-200) Increased Unit Test and Integration Testing

[ https://issues.apache.org/jira/browse/MYRIAD-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15280028#comment-15280028 ] John Yost commented on MYRIAD-200: -- Hi Everyone, I just created a branch off of my fork (https

[jira] [Commented] (MYRIAD-198) Remove optionals when sane defaults are available

[ https://issues.apache.org/jira/browse/MYRIAD-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15279991#comment-15279991 ] John Yost commented on MYRIAD-198: -- Wrapped up work, submitted pull request > Remove optionals when s

[jira] [Commented] (MYRIAD-198) Remove optionals when sane defaults are available

[ https://issues.apache.org/jira/browse/MYRIAD-198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15274175#comment-15274175 ] John Yost commented on MYRIAD-198: -- Hi Everyone, I forked the project (https://github.com/hokiegeek2