[jira] [Updated] (FLINK-9151) standalone cluster scripts should pass FLINK_CONF_DIR to job manager and task managers
[ https://issues.apache.org/jira/browse/FLINK-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Ng updated FLINK-9151: -- Component/s: Startup Shell Scripts > standalone cluster scripts should pass FLINK_CONF_DIR to job manager and task > managers > -- > > Key: FLINK-9151 > URL: https://issues.apache.org/jira/browse/FLINK-9151 > Project: Flink > Issue Type: Improvement > Components: Startup Shell Scripts >Affects Versions: 1.4.1 >Reporter: Christopher Ng >Assignee: vinoyang >Priority: Minor > > At the moment FLINK_CONF_DIR is not passed to the job manager and task > manager when they are started over SSH. This means that if the user has a > locally set FLINK_CONF_DIR that is not configured by their login shell, it is > not used by the launched job manager and task manager which can result in > silently failing to launch if there are errors due to Flink not using the > correct config dir. > One particular inconsistency is that a TaskManagers may be launched locally > (without ssh) on localhost, but JobManagers are always launched over ssh. In > my particular case this meant that the TaskManager launched but the > JobManager silently failed to launch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FLINK-9151) standalone cluster scripts should pass FLINK_CONF_DIR to job manager and task managers
[ https://issues.apache.org/jira/browse/FLINK-9151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher Ng updated FLINK-9151: -- Affects Version/s: 1.4.1 > standalone cluster scripts should pass FLINK_CONF_DIR to job manager and task > managers > -- > > Key: FLINK-9151 > URL: https://issues.apache.org/jira/browse/FLINK-9151 > Project: Flink > Issue Type: Improvement >Affects Versions: 1.4.1 >Reporter: Christopher Ng >Priority: Minor > > At the moment FLINK_CONF_DIR is not passed to the job manager and task > manager when they are started over SSH. This means that if the user has a > locally set FLINK_CONF_DIR that is not configured by their login shell, it is > not used by the launched job manager and task manager which can result in > silently failing to launch if there are errors due to Flink not using the > correct config dir. > One particular inconsistency is that a TaskManagers may be launched locally > (without ssh) on localhost, but JobManagers are always launched over ssh. In > my particular case this meant that the TaskManager launched but the > JobManager silently failed to launch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
