flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rmetzger <...@git.apache.org>
Subject [GitHub] flink issue #2085: [FLINK-3937] programmatic resuming of clusters
Date Fri, 10 Jun 2016 16:47:18 GMT
Github user rmetzger commented on the issue:

    I quickly tried your changes.
    Some notes
    (1)  When listing the yarn-session.sh cli options, I could not see the newly added argument
    2016-06-10 09:28:37,186 ERROR org.apache.flink.yarn.cli.FlinkYarnSessionCli          
      - Missing required argument n
         -n,--container <arg>   Number of YARN container to allocate (=Number of Task
         -D <arg>                        Dynamic properties
         -d,--detached                   Start detached
         -jm,--jobManagerMemory <arg>    Memory for JobManager Container [in MB]
         -nm,--name <arg>                Set a custom name for the application on YARN
         -q,--query                      Display available YARN resources (memory, cores)
         -qu,--queue <arg>               Specify YARN queue.
         -s,--slots <arg>                Number of slots per TaskManager
         -st,--streaming                 Start Flink in streaming mode
         -tm,--taskManagerMemory <arg>   Memory per TaskManager Container [in MB]
    Error while starting the YARN Client. Please check log output!
    (2) Starting a YARN session works. Also, connecting with a second YARN session works.
However, if I'm stopping the session from the second session client, the first one does not
notice this.
    It would be good if all connected clients receive the messages, instead of the last one

If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message