You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Jing Ge (Jira)" <ji...@apache.org> on 2022/02/09 07:05:00 UTC

[jira] [Created] (FLINK-26032) log job info in the ContextEnvironment

Jing Ge created FLINK-26032:
-------------------------------

             Summary: log job info in the ContextEnvironment
                 Key: FLINK-26032
                 URL: https://issues.apache.org/jira/browse/FLINK-26032
             Project: Flink
          Issue Type: Improvement
          Components: Client / Job Submission
            Reporter: Jing Ge
            Assignee: Jing Ge


In Flink codebase, the {{org.apache.flink.client.program.ContextEnvironment}} has a static [Logger|https://github.com/apache/flink/blob/7f9587c723057e2b6cbaf748181c8c80a7f6703d/flink-clients/src/main/java/org/apache/flink/client/program/ContextEnvironment.java#L47] defined in the class, however, it doesn’t use it to print any logs. Instead, it prints logs with {{System.out}} and passes the Logger to {{ShutdownHookUtil.addShutdownHook}} and {{jobExecutionResultFuture.whenComplete}} for logging any hook errors.  If customer integrated the CLI (‘FlinkYarnSessionCli’ in their case) into a multi-threaded program to submit jobs in parallel, does it lead to any logs missing/override/disorder problems? 

It is always helpful to log the status information during the job submit process.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)