[jira] [Created] (FLINK-16548) [Requirement] Consistent id to identify jm/tm in different cluster modes

["hejianchao (Jira)" <ji...@apache.org>]

hejianchao created FLINK-16548:
----------------------------------

             Summary: [Requirement] Consistent id to identify jm/tm in different cluster modes
                 Key: FLINK-16548
                 URL: https://issues.apache.org/jira/browse/FLINK-16548
             Project: Flink
          Issue Type: Wish
          Components: Runtime / Configuration
            Reporter: hejianchao


Imagine that there is now s3-log-appender.jar, and logs can be written to s3 with proper configuration.


Then, in the same flink job, the exact same log4j configuration is used. How to make the key written to s3 for different jm / tm carry the id that uniquely identifies jm / tm? such as:
s3://bucket/flink-logs/jobId/${jm-id}/logfile
s3://bucket/flink-logs/jobId/${tm-1-id}/logfile
s3://bucket/flink-logs/jobId/${tm-2-id}/logfile

For the s3-log-appender here, it needs a way to sense the value of ${jm-id}/${tm-1-id}/${tm-2-id}, and it has the following claims :
1. This value can be used to locate the actual running jm, tm
2. The value is independent of cluster mode, whether standalone, yarn or kubernetes



--
This message was sent by Atlassian Jira
(v8.3.4#803005)