[jira] [Updated] (AURORA-1467) Replace org.apache.aurora.common.args with a standard third-party library

2018-03-27 Thread Renan DelValle (JIRA)

 [ 
https://issues.apache.org/jira/browse/AURORA-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Renan DelValle updated AURORA-1467:
---
Fix Version/s: 0.19.1

> Replace org.apache.aurora.common.args with a standard third-party library
> -
>
> Key: AURORA-1467
> URL: https://issues.apache.org/jira/browse/AURORA-1467
> Project: Aurora
>  Issue Type: Task
>  Components: Scheduler
>Reporter: Bill Farner
>Assignee: Bill Farner
>Priority: Major
>  Labels: newbie
> Fix For: 0.19.1
>
>
> Our args parsing/processing system was inherited from Twitter Commons and 
> should be considered for replacement.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (AURORA-1825) Enable async logging by default

2018-03-27 Thread Renan DelValle (JIRA)

[ 
https://issues.apache.org/jira/browse/AURORA-1825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16416329#comment-16416329
 ] 

Renan DelValle commented on AURORA-1825:


[~jingc] I see that you closed this issue as Done, can you provide a link to 
the review as well as the version this landed in? 

Thanks!

> Enable async logging by default
> ---
>
> Key: AURORA-1825
> URL: https://issues.apache.org/jira/browse/AURORA-1825
> Project: Aurora
>  Issue Type: Task
>Reporter: Zameer Manji
>Assignee: Jing Chen
>Priority: Minor
>
> Based on my experience while working on AURORA-1823 and [~StephanErb]'s work 
> on logging recently, I think it would be best if we enabled async logging.
> For example if one attempts to parallelize the work inside 
> {{StateManagerImpl}} there isn't much benefit because all of the state 
> transitions are logged and all of the threads would contend for the lock.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (AURORA-1981) Add support for choosing task Executor using Aurora DSL

2018-03-27 Thread Renan DelValle (JIRA)

 [ 
https://issues.apache.org/jira/browse/AURORA-1981?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Renan DelValle updated AURORA-1981:
---
Fix Version/s: (was: 0.21.0)
   0.20.0

> Add support for choosing task Executor using Aurora DSL
> ---
>
> Key: AURORA-1981
> URL: https://issues.apache.org/jira/browse/AURORA-1981
> Project: Aurora
>  Issue Type: Sub-task
>  Components: Client
>Reporter: Renan DelValle
>Assignee: Renan DelValle
>Priority: Major
> Fix For: 0.20.0
>
>
> The Aurora scheduler supports launching tasks using custom executors. 
> However, there is currently no way to change the executor used for launching 
> a Job's tasks using the Aurora DSL.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (AURORA-1974) Update sample Docker jobs for Vagrant tutorial

2018-03-27 Thread Renan DelValle (JIRA)

 [ 
https://issues.apache.org/jira/browse/AURORA-1974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Renan DelValle resolved AURORA-1974.

   Resolution: Fixed
Fix Version/s: 0.20.0

Fixed by 
https://github.com/apache/aurora/commit/b6e898b5e9f70b13db42db366b6d98c5baadcb57

> Update sample Docker jobs for Vagrant tutorial
> --
>
> Key: AURORA-1974
> URL: https://issues.apache.org/jira/browse/AURORA-1974
> Project: Aurora
>  Issue Type: Task
>  Components: Docker, Documentation
>Affects Versions: 0.19.1
>Reporter: Mathias Sulser
>Assignee: Renan DelValle
>Priority: Trivial
> Fix For: 0.20.0
>
>
> h2. Problem
> As discussed with [~rdelvalle] on Slack, I am filing what is likely a 
> regression caused by the recent Vagrant upgrade in 
> [https://github.com/apache/aurora/commit/c52137e20bd2863234dc09116e1339364ffed77a]
> As of now, submitting any jobs in 
> {{examples/jobs/hello_docker_engine.aurora}} or 
> {{examples/jobs/hello_docker_image.aurora}} will fail due to the following 
> error:
> {code:java}
> Traceback (most recent call last):
> File "apache/aurora/executor/bin/thermos_executor_main.py", line 47, in 
> 
> from mesos.executor import MesosExecutorDriver
> File 
> "/root/.pex/install/mesos.executor-1.4.0-py2.7-linux-x86_64.egg.bf19bd50eea04a23374924ed382340b7a2557be3/mesos.executor-1.4.0-py2.7-linux-x86_64.egg/mesos/executor/_init_.py",
>  line 17, in 
> from ._executor import MesosExecutorDriverImpl as MesosExecutorDriver
> ImportError: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version 
> `GLIBCXX_3.4.21' not found (required by 
> /root/.pex/install/mesos.executor-1.4.0-py2.7-linux-x86_64.egg.bf19bd50eea04a23374924ed382340b7a2557be3/mesos.executor-1.4.0-py2.7-linux-x86_64.egg/mesos/executor/_executor.so)
> {code}
> h2. Solution
> Changing the docker image from {{python:2.7}} to {{python:2.7-slim-stretch}} 
> will fix this.
>  
> Hat-tip to [~rdelvalle] for figuring this out so quickly (y)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)