[
https://issues.apache.org/jira/browse/FLINK-9335?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471680#comment-16471680
]
Chesnay Schepler commented on FLINK-9335:
-----------------------------------------
As i understand it he isn't using the UI to submit jobs but the command-line
client. For this case I don't see a reasonable way to implement this feature.
Library-style deployment would inherently cover this issue.
If the job were submitted through the UI the logging output should show up in
the logs.
> Expose client logs via Flink UI
> -------------------------------
>
> Key: FLINK-9335
> URL: https://issues.apache.org/jira/browse/FLINK-9335
> Project: Flink
> Issue Type: New Feature
> Reporter: Juho Autio
> Priority: Minor
>
> The logs logged by my Flink job jar _before_ *env.execute* can't be found in
> jobmanager log in Flink UI.
> In my case they seem to be going to
> /+home/hadoop/flink-1.5-SNAPSHOT/log/flink-hadoop-client-ip-10-0-10-29.log,+
> for example.
> [~fhueske] said:
> {quote}It seems like good feature request to include the client logs.
> {quote}
> Implementing this may not be as trivial as just reading another log file
> though. As [~fhueske] commented:
> {quote}I assume that these logs are generated from a different process, i.e.,
> the client process and not the JM or TM process.
> Hence, they end up in a different log file and are not covered by the log
> collection of the UI.
> The reason is that *this process might also be run on a machine outside of
> the cluster. So the client log file might not be accessible from the UI
> process*.
> {quote}
> This was discussed on the user mailing list:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Application-logs-missing-from-jobmanager-log-tp19830p19882.html
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
