[
https://issues.apache.org/jira/browse/FLINK-28283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17686987#comment-17686987
]
zlzhang0122 edited comment on FLINK-28283 at 2/10/23 9:45 AM:
--------------------------------------------------------------
[~xtsong] Right you are, actually what I think is cache theses logs for some
short time and then aggregate and print it, but indeed this may cause some
problem such as timeliness and lose of logs, so this is fine with me to close
this ticket.
[~chesnay] Sure, we can hiding the log message via log4j filters.
was (Author: zlzhang0122):
[~xtsong] Right you are, actually what I think is cache theses logs for some
short time, but indeed this may cause some problem such as timeliness and lose
of logs, so this is fine with me to close this ticket.
[~chesnay] Sure, we can hiding the log message via log4j filters.
> Improving the log of flink when job start and deploy
> ----------------------------------------------------
>
> Key: FLINK-28283
> URL: https://issues.apache.org/jira/browse/FLINK-28283
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Task
> Affects Versions: 1.14.2
> Reporter: zlzhang0122
> Priority: Major
>
> When running a large job with many operators and subtasks on flink, the
> JobManager and TaskManager will have a huge logs about the subtask executing
> msg such as "XXX switched from CREATED to SCHEDULED、XXX switched from
> SCHEDULED to DEPLOYING 、XXX switched from DEPLOYING to RUNNING 、XXX switched
> from RUNNING to CANCELING、XXX switched from CANCELING to CANCELED", etc. .
> Maybe we can do some improvement about this, such as aggregate these msg to
> reduce the log, or change the log level and only logs the failure msg and
> subtask, etc. Not so sure about the solution, but these msg is really too
> much.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
