[jira] [Created] (AURORA-1895) Expose stats on ZooKeeperClient connection state

2017-02-25 Thread Mehrdad Nurolahzade (JIRA)
Mehrdad Nurolahzade created AURORA-1895:
---

 Summary: 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
Priority: Minor


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.3.15#6346)


[jira] [Commented] (AURORA-1871) Client should reject tasks with duplicate process names

2017-02-25 Thread Pradyumna Kaushik (JIRA)

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

Pradyumna Kaushik commented on AURORA-1871:
---

[~joshua.cohen] Just a clarification -- Should the client just fail, in the 
sense that we throw an error indicating a faulty config file or should the job 
with tasks that contain duplicate task names be ignored and the others 
scheduled?

> Client should reject tasks with duplicate process names
> ---
>
> Key: AURORA-1871
> URL: https://issues.apache.org/jira/browse/AURORA-1871
> Project: Aurora
>  Issue Type: Task
>  Components: Client
>Reporter: Joshua Cohen
>
> If a user creates a job that contains tasks with the same process name, that 
> info is happily passed on to thermos, which will happily run one of those 
> processes, but maybe display a separate one in the UI. In general the 
> behavior in this case is non-deterministic and can lead to hard to track down 
> bugs.
> We should just short circuit and fail in the client if we detect multiple 
> processes with the same name.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)