[jira] [Commented] (FLINK-7687) Clarify the master and slaves files are not necessary unless using the cluster start/stop scripts
[ https://issues.apache.org/jira/browse/FLINK-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17329760#comment-17329760 ] Flink Jira Bot commented on FLINK-7687: --- This issue has been labeled "stale-minor" for 7 days. It is closed now. If you are still affected by this or would like to raise the priority of this ticket please re-open, removing the label "auto-closed" and raise the ticket priority accordingly. > Clarify the master and slaves files are not necessary unless using the > cluster start/stop scripts > - > > Key: FLINK-7687 > URL: https://issues.apache.org/jira/browse/FLINK-7687 > Project: Flink > Issue Type: Improvement > Components: Deployment / Scripts, Documentation >Affects Versions: 1.3.2 >Reporter: Elias Levy >Priority: Minor > Labels: stale-minor > > It would be helpful if the documentation was clearer on the fact that the > master/slaves config files are not needed when configured in > high-availability mode unless you are using the provided scripts to start and > shutdown the cluster over SSH. If you are using some other mechanism to > manage Flink instances (configuration management tools such as Chef or > Ansible, or container management frameworks like Docker Compose or > Kubernetes), these files are unnecessary. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLINK-7687) Clarify the master and slaves files are not necessary unless using the cluster start/stop scripts
[ https://issues.apache.org/jira/browse/FLINK-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321626#comment-17321626 ] Flink Jira Bot commented on FLINK-7687: --- This issue and all of its Sub-Tasks have not been updated for 180 days. So, it has been labeled "stale-minor". If you are still affected by this bug or are still interested in this issue, please give an update and remove the label. In 7 days the issue will be closed automatically. > Clarify the master and slaves files are not necessary unless using the > cluster start/stop scripts > - > > Key: FLINK-7687 > URL: https://issues.apache.org/jira/browse/FLINK-7687 > Project: Flink > Issue Type: Improvement > Components: Deployment / Scripts, Documentation >Affects Versions: 1.3.2 >Reporter: Elias Levy >Priority: Minor > Labels: stale-minor > > It would be helpful if the documentation was clearer on the fact that the > master/slaves config files are not needed when configured in > high-availability mode unless you are using the provided scripts to start and > shutdown the cluster over SSH. If you are using some other mechanism to > manage Flink instances (configuration management tools such as Chef or > Ansible, or container management frameworks like Docker Compose or > Kubernetes), these files are unnecessary. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FLINK-7687) Clarify the master and slaves files are not necessary unless using the cluster start/stop scripts
[ https://issues.apache.org/jira/browse/FLINK-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191552#comment-16191552 ] Elias Levy commented on FLINK-7687: --- And? > Clarify the master and slaves files are not necessary unless using the > cluster start/stop scripts > - > > Key: FLINK-7687 > URL: https://issues.apache.org/jira/browse/FLINK-7687 > Project: Flink > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.3.2 >Reporter: Elias Levy >Priority: Minor > > It would be helpful if the documentation was clearer on the fact that the > master/slaves config files are not needed when configured in > high-availability mode unless you are using the provided scripts to start and > shutdown the cluster over SSH. If you are using some other mechanism to > manage Flink instances (configuration management tools such as Chef or > Ansible, or container management frameworks like Docker Compose or > Kubernetes), these files are unnecessary. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FLINK-7687) Clarify the master and slaves files are not necessary unless using the cluster start/stop scripts
[ https://issues.apache.org/jira/browse/FLINK-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191504#comment-16191504 ] Greg Hogan commented on FLINK-7687: --- The quoted text is in the section "Standalone Cluster High Availability". > Clarify the master and slaves files are not necessary unless using the > cluster start/stop scripts > - > > Key: FLINK-7687 > URL: https://issues.apache.org/jira/browse/FLINK-7687 > Project: Flink > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.3.2 >Reporter: Elias Levy >Priority: Minor > > It would be helpful if the documentation was clearer on the fact that the > master/slaves config files are not needed when configured in > high-availability mode unless you are using the provided scripts to start and > shutdown the cluster over SSH. If you are using some other mechanism to > manage Flink instances (configuration management tools such as Chef or > Ansible, or container management frameworks like Docker Compose or > Kubernetes), these files are unnecessary. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FLINK-7687) Clarify the master and slaves files are not necessary unless using the cluster start/stop scripts
[ https://issues.apache.org/jira/browse/FLINK-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191491#comment-16191491 ] Elias Levy commented on FLINK-7687: --- The [The JobManager High-Availability|https://ci.apache.org/projects/flink/flink-docs-release-1.3/setup/jobmanager_high_availability.html] page. bq. To enable JobManager High Availability you have to set the high-availability mode to zookeeper, configure a ZooKeeper quorum and set up a masters file with all JobManagers hosts and their web UI ports. The page mentions that you must configure the masters file to use the cluster start-up scripts, but it is no clear the masters file is not used for other purposes and is not needed if you don't use the cluster scripts. > Clarify the master and slaves files are not necessary unless using the > cluster start/stop scripts > - > > Key: FLINK-7687 > URL: https://issues.apache.org/jira/browse/FLINK-7687 > Project: Flink > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.3.2 >Reporter: Elias Levy >Priority: Minor > > It would be helpful if the documentation was clearer on the fact that the > master/slaves config files are not needed when configured in > high-availability mode unless you are using the provided scripts to start and > shutdown the cluster over SSH. If you are using some other mechanism to > manage Flink instances (configuration management tools such as Chef or > Ansible, or container management frameworks like Docker Compose or > Kubernetes), these files are unnecessary. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (FLINK-7687) Clarify the master and slaves files are not necessary unless using the cluster start/stop scripts
[ https://issues.apache.org/jira/browse/FLINK-7687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16189845#comment-16189845 ] Greg Hogan commented on FLINK-7687: --- [~elevy] is there a specific page or pages where this is unclear? > Clarify the master and slaves files are not necessary unless using the > cluster start/stop scripts > - > > Key: FLINK-7687 > URL: https://issues.apache.org/jira/browse/FLINK-7687 > Project: Flink > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.3.2 >Reporter: Elias Levy >Priority: Minor > > It would be helpful if the documentation was clearer on the fact that the > master/slaves config files are not needed when configured in > high-availability mode unless you are using the provided scripts to start and > shutdown the cluster over SSH. If you are using some other mechanism to > manage Flink instances (configuration management tools such as Chef or > Ansible, or container management frameworks like Docker Compose or > Kubernetes), these files are unnecessary. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
