[
https://issues.apache.org/jira/browse/FLINK-17977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17133346#comment-17133346
]
Till Rohrmann edited comment on FLINK-17977 at 6/11/20, 3:43 PM:
-----------------------------------------------------------------
I like [~chesnay] proposed improvements.
Concerning the "JobManagerRunner already shutdown." I would suggest to make it
a debug message and say "JobManagerRunner cannot be granted leadership because
it is already shut down." in {{JobManagerRunnerImpl.grantLeadership}} and
"Ignoring revoking leadership because JobManagerRunner is already shut down."
in {{JobManagerRunnerImpl.revokeLeadership}}.
was (Author: till.rohrmann):
I like [~chesnay] proposed improvements.
Concerning the {{"JobManagerRunner already shutdown."}} I would suggest to make
it a debug message and say {{"JobManagerRunner cannot be granted leadership
because it is already shut down."}} in {{JobManagerRunnerImpl.grantLeadership}}
and {{"Ignoring revoking leadership because JobManagerRunner is already shut
down."}} in {{JobManagerRunnerImpl.revokeLeadership}}.
> Check log sanity
> ----------------
>
> Key: FLINK-17977
> URL: https://issues.apache.org/jira/browse/FLINK-17977
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.11.0
> Reporter: Till Rohrmann
> Priority: Critical
> Labels: release-testing
> Fix For: 1.11.0
>
>
> Run a normal Flink workload (e.g. job with fixed number of failures on
> session cluster) and check that the produced Flink logs make sense and don't
> contain confusing statements.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
