[jira] [Resolved] (AURORA-1669) Kill twitter/commons ZK libs when Curator replacements are vetted
[
https://issues.apache.org/jira/browse/AURORA-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Erb resolved AURORA-1669.
-
Resolution: Fixed
Assignee: Bill Farner (was: John Sirois)
> Kill twitter/commons ZK libs when Curator replacements are vetted
> -
>
> Key: AURORA-1669
> URL: https://issues.apache.org/jira/browse/AURORA-1669
> Project: Aurora
> Issue Type: Task
>Reporter: John Sirois
>Assignee: Bill Farner
>
> Once we have reports from production users that the Curator zk plumbing
> introduced in AURORA-1468 is working well, the {{-zk_use_curator}} flag
> should be deprecated and then the flag and commons code killed. If the
> vetting happens before the next release ({{0.14.0}}), we can dispense with a
> deprecation cycle.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AURORA-1669) Kill twitter/commons ZK libs when Curator replacements are vetted
[
https://issues.apache.org/jira/browse/AURORA-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215965#comment-16215965
]
Stephan Erb commented on AURORA-1669:
-
https://reviews.apache.org/r/62652/ has landed
> Kill twitter/commons ZK libs when Curator replacements are vetted
> -
>
> Key: AURORA-1669
> URL: https://issues.apache.org/jira/browse/AURORA-1669
> Project: Aurora
> Issue Type: Task
>Reporter: John Sirois
>Assignee: John Sirois
>
> Once we have reports from production users that the Curator zk plumbing
> introduced in AURORA-1468 is working well, the {{-zk_use_curator}} flag
> should be deprecated and then the flag and commons code killed. If the
> vetting happens before the next release ({{0.14.0}}), we can dispense with a
> deprecation cycle.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (AURORA-1895) Expose stats on ZooKeeperClient connection state
[
https://issues.apache.org/jira/browse/AURORA-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215956#comment-16215956
]
Stephan Erb commented on AURORA-1895:
-
https://reviews.apache.org/r/62652/ has landed, dropping legacy ZK
> Expose stats on ZooKeeperClient connection state
>
>
> Key: AURORA-1895
> URL: https://issues.apache.org/jira/browse/AURORA-1895
> Project: Aurora
> Issue Type: Story
> Components: Scheduler
>Reporter: Mehrdad Nurolahzade
>Assignee: Mehrdad Nurolahzade
>Priority: Minor
> Labels: newbie
>
> Expose stats on the connection state of the {{ZooKeeperClient}} in
> {{CommonsServiceDiscoveryModule}}. This can be through the ZooKeeper client
> [Watcher|https://zookeeper.apache.org/doc/r3.4.8/api/org/apache/zookeeper/Watcher.html]
> interface.
> [AURORA-1838] exposed ZooKeeper stats for {{CuratorServiceDiscoveryModule}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (AURORA-319) Allow job environments other than prod, devel, test or staging
[ https://issues.apache.org/jira/browse/AURORA-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stephan Erb resolved AURORA-319. Resolution: Fixed Assignee: (was: Benjamin Staffin) > Allow job environments other than prod, devel, test or staging > -- > > Key: AURORA-319 > URL: https://issues.apache.org/jira/browse/AURORA-319 > Project: Aurora > Issue Type: Story > Components: Client >Reporter: Jay Buffington >Priority: Minor > > git commit bcabfce6 introduced limitations on what job environments must be > named. Are these names arbitrary or is there some policy attached to these > names? > I suspect they are not arbitrary because I believe aurora will preempt tasks > that are not in the prod environment to make room for jobs that are. > What would the ramifications be of removing the "_validate_environment_name" > function from src/main/python/apache/aurora/client/config.py ? Are there > reasons why this was introduced in the first place? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AURORA-319) Allow job environments other than prod, devel, test or staging
[ https://issues.apache.org/jira/browse/AURORA-319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215853#comment-16215853 ] Stephan Erb commented on AURORA-319: This has now been submitted https://reviews.apache.org/r/62692/ Thanks for the contribution! > Allow job environments other than prod, devel, test or staging > -- > > Key: AURORA-319 > URL: https://issues.apache.org/jira/browse/AURORA-319 > Project: Aurora > Issue Type: Story > Components: Client >Reporter: Jay Buffington >Assignee: Benjamin Staffin >Priority: Minor > > git commit bcabfce6 introduced limitations on what job environments must be > named. Are these names arbitrary or is there some policy attached to these > names? > I suspect they are not arbitrary because I believe aurora will preempt tasks > that are not in the prod environment to make room for jobs that are. > What would the ramifications be of removing the "_validate_environment_name" > function from src/main/python/apache/aurora/client/config.py ? Are there > reasons why this was introduced in the first place? -- This message was sent by Atlassian JIRA (v6.4.14#64029)
