[jira] [Updated] (FLINK-5505) Harmonize ZooKeeper configuration parameters

2018-11-18 Thread Till Rohrmann (JIRA) 


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

Till Rohrmann updated FLINK-5505:
-
Fix Version/s: (was: 1.7.0)

> Harmonize ZooKeeper configuration parameters
> 
>
> Key: FLINK-5505
> URL: https://issues.apache.org/jira/browse/FLINK-5505
> Project: Flink
>  Issue Type: Improvement
>  Components: Mesos
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Till Rohrmann
>Assignee: vinoyang
>Priority: Trivial
> Fix For: 1.8.0
>
>
> Since Flink users don't necessarily know all of the Mesos terminology and a 
> JobManager runs also as a task, I would like to rename some of Flink's Mesos 
> configuration parameters. I would propose the following changes:
> {{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
> {{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
> {{mesos.resourcemanager.artifactserver.\*}} => {{mesos.artifactserver.*}}
> {{mesos.resourcemanager.framework.\*}} => {{mesos.framework.*}}
> {{mesos.resourcemanager.tasks.\*}} => {{mesos.taskmanager.*}}
> {{recovery.zookeeper.path.mesos-workers}} => 
> {{mesos.high-availability.zookeeper.path.mesos-workers}}
> What do you think [~eronwright]?



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

[jira] [Updated] (FLINK-5505) Harmonize ZooKeeper configuration parameters

2018-11-18 Thread Till Rohrmann (JIRA) 


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

Till Rohrmann updated FLINK-5505:
-
Fix Version/s: 1.8.0

> Harmonize ZooKeeper configuration parameters
> 
>
> Key: FLINK-5505
> URL: https://issues.apache.org/jira/browse/FLINK-5505
> Project: Flink
>  Issue Type: Improvement
>  Components: Mesos
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Till Rohrmann
>Assignee: vinoyang
>Priority: Trivial
> Fix For: 1.7.0, 1.8.0
>
>
> Since Flink users don't necessarily know all of the Mesos terminology and a 
> JobManager runs also as a task, I would like to rename some of Flink's Mesos 
> configuration parameters. I would propose the following changes:
> {{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
> {{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
> {{mesos.resourcemanager.artifactserver.\*}} => {{mesos.artifactserver.*}}
> {{mesos.resourcemanager.framework.\*}} => {{mesos.framework.*}}
> {{mesos.resourcemanager.tasks.\*}} => {{mesos.taskmanager.*}}
> {{recovery.zookeeper.path.mesos-workers}} => 
> {{mesos.high-availability.zookeeper.path.mesos-workers}}
> What do you think [~eronwright]?



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

[jira] [Updated] (FLINK-5505) Harmonize ZooKeeper configuration parameters

2018-08-06 Thread Till Rohrmann (JIRA) 


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

Till Rohrmann updated FLINK-5505:
-
Fix Version/s: (was: 1.6.0)
   1.7.0

> Harmonize ZooKeeper configuration parameters
> 
>
> Key: FLINK-5505
> URL: https://issues.apache.org/jira/browse/FLINK-5505
> Project: Flink
>  Issue Type: Improvement
>  Components: Mesos
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Till Rohrmann
>Assignee: vinoyang
>Priority: Trivial
> Fix For: 1.7.0
>
>
> Since Flink users don't necessarily know all of the Mesos terminology and a 
> JobManager runs also as a task, I would like to rename some of Flink's Mesos 
> configuration parameters. I would propose the following changes:
> {{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
> {{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
> {{mesos.resourcemanager.artifactserver.\*}} => {{mesos.artifactserver.*}}
> {{mesos.resourcemanager.framework.\*}} => {{mesos.framework.*}}
> {{mesos.resourcemanager.tasks.\*}} => {{mesos.taskmanager.*}}
> {{recovery.zookeeper.path.mesos-workers}} => 
> {{mesos.high-availability.zookeeper.path.mesos-workers}}
> What do you think [~eronwright]?



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

[jira] [Updated] (FLINK-5505) Harmonize ZooKeeper configuration parameters

2018-05-25 Thread Till Rohrmann (JIRA) 

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

Till Rohrmann updated FLINK-5505:
-
Fix Version/s: (was: 1.5.0)
   1.5.1

> Harmonize ZooKeeper configuration parameters
> 
>
> Key: FLINK-5505
> URL: https://issues.apache.org/jira/browse/FLINK-5505
> Project: Flink
>  Issue Type: Improvement
>  Components: Mesos
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Till Rohrmann
>Priority: Trivial
> Fix For: 1.5.1
>
>
> Since Flink users don't necessarily know all of the Mesos terminology and a 
> JobManager runs also as a task, I would like to rename some of Flink's Mesos 
> configuration parameters. I would propose the following changes:
> {{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
> {{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
> {{mesos.resourcemanager.artifactserver.\*}} => {{mesos.artifactserver.*}}
> {{mesos.resourcemanager.framework.\*}} => {{mesos.framework.*}}
> {{mesos.resourcemanager.tasks.\*}} => {{mesos.taskmanager.*}}
> {{recovery.zookeeper.path.mesos-workers}} => 
> {{mesos.high-availability.zookeeper.path.mesos-workers}}
> What do you think [~eronwright]?



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

[jira] [Updated] (FLINK-5505) Harmonize ZooKeeper configuration parameters

2017-11-15 Thread Chesnay Schepler (JIRA) 

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

Chesnay Schepler updated FLINK-5505:

Fix Version/s: (was: 1.4.0)
   1.5.0

> Harmonize ZooKeeper configuration parameters
> 
>
> Key: FLINK-5505
> URL: https://issues.apache.org/jira/browse/FLINK-5505
> Project: Flink
>  Issue Type: Improvement
>  Components: Mesos
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Till Rohrmann
>Priority: Trivial
> Fix For: 1.5.0
>
>
> Since Flink users don't necessarily know all of the Mesos terminology and a 
> JobManager runs also as a task, I would like to rename some of Flink's Mesos 
> configuration parameters. I would propose the following changes:
> {{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
> {{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
> {{mesos.resourcemanager.artifactserver.\*}} => {{mesos.artifactserver.*}}
> {{mesos.resourcemanager.framework.\*}} => {{mesos.framework.*}}
> {{mesos.resourcemanager.tasks.\*}} => {{mesos.taskmanager.*}}
> {{recovery.zookeeper.path.mesos-workers}} => 
> {{mesos.high-availability.zookeeper.path.mesos-workers}}
> What do you think [~eronwright]?



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (FLINK-5505) Harmonize ZooKeeper configuration parameters

2017-05-31 Thread Robert Metzger (JIRA) 

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

Robert Metzger updated FLINK-5505:
--
Fix Version/s: (was: 1.3.0)
   1.4.0

> Harmonize ZooKeeper configuration parameters
> 
>
> Key: FLINK-5505
> URL: https://issues.apache.org/jira/browse/FLINK-5505
> Project: Flink
>  Issue Type: Improvement
>  Components: Mesos
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Till Rohrmann
>Priority: Trivial
> Fix For: 1.4.0
>
>
> Since Flink users don't necessarily know all of the Mesos terminology and a 
> JobManager runs also as a task, I would like to rename some of Flink's Mesos 
> configuration parameters. I would propose the following changes:
> {{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
> {{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
> {{mesos.resourcemanager.artifactserver.\*}} => {{mesos.artifactserver.*}}
> {{mesos.resourcemanager.framework.\*}} => {{mesos.framework.*}}
> {{mesos.resourcemanager.tasks.\*}} => {{mesos.taskmanager.*}}
> {{recovery.zookeeper.path.mesos-workers}} => 
> {{mesos.high-availability.zookeeper.path.mesos-workers}}
> What do you think [~eronwright]?



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

[jira] [Updated] (FLINK-5505) Harmonize ZooKeeper configuration parameters

2017-01-19 Thread Till Rohrmann (JIRA) 

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

Till Rohrmann updated FLINK-5505:
-
Description: 
Since Flink users don't necessarily know all of the Mesos terminology and a 
JobManager runs also as a task, I would like to rename some of Flink's Mesos 
configuration parameters. I would propose the following changes:

{{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
{{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
{{mesos.resourcemanager.artifactserver.\*}} => {{mesos.artifactserver.*}}
{{mesos.resourcemanager.framework.*}} => {{mesos.framework.*}}
{{mesos.resourcemanager.tasks.*}} => {{mesos.taskmanager.*}}

{{recovery.zookeeper.path.mesos-workers}} => 
{{mesos.high-availability.zookeeper.path.mesos-workers}}

What do you think [~eronwright]?

  was:
Since Flink users don't necessarily know all of the Mesos terminology and a 
JobManager runs also as a task, I would like to rename some of Flink's Mesos 
configuration parameters. I would propose the following changes:

{{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
{{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
{{mesos.resourcemanager.artifactserver.*}} => {{mesos.artifactserver.*}}
{{mesos.resourcemanager.framework.*}} => {{mesos.framework.*}}
{{mesos.resourcemanager.tasks.*}} => {{mesos.taskmanager.*}}

{{recovery.zookeeper.path.mesos-workers}} => 
{{mesos.high-availability.zookeeper.path.mesos-workers}}

What do you think [~eronwright]?


> Harmonize ZooKeeper configuration parameters
> 
>
> Key: FLINK-5505
> URL: https://issues.apache.org/jira/browse/FLINK-5505
> Project: Flink
>  Issue Type: Improvement
>  Components: Mesos
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Till Rohrmann
>Priority: Trivial
> Fix For: 1.3.0
>
>
> Since Flink users don't necessarily know all of the Mesos terminology and a 
> JobManager runs also as a task, I would like to rename some of Flink's Mesos 
> configuration parameters. I would propose the following changes:
> {{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
> {{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
> {{mesos.resourcemanager.artifactserver.\*}} => {{mesos.artifactserver.*}}
> {{mesos.resourcemanager.framework.*}} => {{mesos.framework.*}}
> {{mesos.resourcemanager.tasks.*}} => {{mesos.taskmanager.*}}
> {{recovery.zookeeper.path.mesos-workers}} => 
> {{mesos.high-availability.zookeeper.path.mesos-workers}}
> What do you think [~eronwright]?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FLINK-5505) Harmonize ZooKeeper configuration parameters

2017-01-19 Thread Till Rohrmann (JIRA) 

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

Till Rohrmann updated FLINK-5505:
-
Description: 
Since Flink users don't necessarily know all of the Mesos terminology and a 
JobManager runs also as a task, I would like to rename some of Flink's Mesos 
configuration parameters. I would propose the following changes:

{{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
{{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
{{mesos.resourcemanager.artifactserver.\*}} => {{mesos.artifactserver.*}}
{{mesos.resourcemanager.framework.\*}} => {{mesos.framework.*}}
{{mesos.resourcemanager.tasks.\*}} => {{mesos.taskmanager.*}}

{{recovery.zookeeper.path.mesos-workers}} => 
{{mesos.high-availability.zookeeper.path.mesos-workers}}

What do you think [~eronwright]?

  was:
Since Flink users don't necessarily know all of the Mesos terminology and a 
JobManager runs also as a task, I would like to rename some of Flink's Mesos 
configuration parameters. I would propose the following changes:

{{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
{{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
{{mesos.resourcemanager.artifactserver.\*}} => {{mesos.artifactserver.*}}
{{mesos.resourcemanager.framework.*}} => {{mesos.framework.*}}
{{mesos.resourcemanager.tasks.*}} => {{mesos.taskmanager.*}}

{{recovery.zookeeper.path.mesos-workers}} => 
{{mesos.high-availability.zookeeper.path.mesos-workers}}

What do you think [~eronwright]?


> Harmonize ZooKeeper configuration parameters
> 
>
> Key: FLINK-5505
> URL: https://issues.apache.org/jira/browse/FLINK-5505
> Project: Flink
>  Issue Type: Improvement
>  Components: Mesos
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Till Rohrmann
>Priority: Trivial
> Fix For: 1.3.0
>
>
> Since Flink users don't necessarily know all of the Mesos terminology and a 
> JobManager runs also as a task, I would like to rename some of Flink's Mesos 
> configuration parameters. I would propose the following changes:
> {{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
> {{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
> {{mesos.resourcemanager.artifactserver.\*}} => {{mesos.artifactserver.*}}
> {{mesos.resourcemanager.framework.\*}} => {{mesos.framework.*}}
> {{mesos.resourcemanager.tasks.\*}} => {{mesos.taskmanager.*}}
> {{recovery.zookeeper.path.mesos-workers}} => 
> {{mesos.high-availability.zookeeper.path.mesos-workers}}
> What do you think [~eronwright]?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FLINK-5505) Harmonize ZooKeeper configuration parameters

2017-01-19 Thread Till Rohrmann (JIRA) 

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

Till Rohrmann updated FLINK-5505:
-
Description: 
Since Flink users don't necessarily know all of the Mesos terminology and a 
JobManager runs also as a task, I would like to rename some of Flink's Mesos 
configuration parameters. I would propose the following changes:

{{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
{{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
{{mesos.resourcemanager.artifactserver.*}} => {{mesos.artifactserver.*}}
{{mesos.resourcemanager.framework.*}} => {{mesos.framework.*}}
{{mesos.resourcemanager.tasks.*}} => {{mesos.taskmanager.*}}

{{recovery.zookeeper.path.mesos-workers}} => 
{{mesos.high-availability.zookeeper.path.mesos-workers}}

What do you think [~eronwright]?

  was:In order to harmonize configuration parameter names I think we should 
rename {{recovery.zookeeper.path.mesos-workers}} into 
{{high-availability.zookeeper.path.mesos-workers}}.


> Harmonize ZooKeeper configuration parameters
> 
>
> Key: FLINK-5505
> URL: https://issues.apache.org/jira/browse/FLINK-5505
> Project: Flink
>  Issue Type: Improvement
>  Components: Mesos
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Till Rohrmann
>Assignee: Till Rohrmann
>Priority: Trivial
> Fix For: 1.3.0
>
>
> Since Flink users don't necessarily know all of the Mesos terminology and a 
> JobManager runs also as a task, I would like to rename some of Flink's Mesos 
> configuration parameters. I would propose the following changes:
> {{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
> {{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
> {{mesos.resourcemanager.artifactserver.*}} => {{mesos.artifactserver.*}}
> {{mesos.resourcemanager.framework.*}} => {{mesos.framework.*}}
> {{mesos.resourcemanager.tasks.*}} => {{mesos.taskmanager.*}}
> {{recovery.zookeeper.path.mesos-workers}} => 
> {{mesos.high-availability.zookeeper.path.mesos-workers}}
> What do you think [~eronwright]?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FLINK-5505) Harmonize ZooKeeper configuration parameters

2017-01-19 Thread Till Rohrmann (JIRA) 

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

Till Rohrmann updated FLINK-5505:
-
Assignee: (was: Till Rohrmann)

> Harmonize ZooKeeper configuration parameters
> 
>
> Key: FLINK-5505
> URL: https://issues.apache.org/jira/browse/FLINK-5505
> Project: Flink
>  Issue Type: Improvement
>  Components: Mesos
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Till Rohrmann
>Priority: Trivial
> Fix For: 1.3.0
>
>
> Since Flink users don't necessarily know all of the Mesos terminology and a 
> JobManager runs also as a task, I would like to rename some of Flink's Mesos 
> configuration parameters. I would propose the following changes:
> {{mesos.initial-tasks}} => {{mesos.initial-taskmanagers}}
> {{mesos.maximum-failed-tasks}} => {{mesos.maximum-failed-taskmanagers}}
> {{mesos.resourcemanager.artifactserver.*}} => {{mesos.artifactserver.*}}
> {{mesos.resourcemanager.framework.*}} => {{mesos.framework.*}}
> {{mesos.resourcemanager.tasks.*}} => {{mesos.taskmanager.*}}
> {{recovery.zookeeper.path.mesos-workers}} => 
> {{mesos.high-availability.zookeeper.path.mesos-workers}}
> What do you think [~eronwright]?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FLINK-5505) Harmonize ZooKeeper configuration parameters

2017-01-18 Thread Till Rohrmann (JIRA) 

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

Till Rohrmann updated FLINK-5505:
-
Summary: Harmonize ZooKeeper configuration parameters  (was: Rename 
recovery.zookeeper.path.mesos-workers into 
high-availability.zookeeper.path.mesos-workers)

> Harmonize ZooKeeper configuration parameters
> 
>
> Key: FLINK-5505
> URL: https://issues.apache.org/jira/browse/FLINK-5505
> Project: Flink
>  Issue Type: Improvement
>  Components: Mesos
>Affects Versions: 1.2.0, 1.3.0
>Reporter: Till Rohrmann
>Assignee: Till Rohrmann
>Priority: Trivial
> Fix For: 1.3.0
>
>
> In order to harmonize configuration parameter names I think we should rename 
> {{recovery.zookeeper.path.mesos-workers}} into 
> {{high-availability.zookeeper.path.mesos-workers}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)