[
https://issues.apache.org/jira/browse/FLINK-34289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814837#comment-17814837
]
lincoln lee commented on FLINK-34289:
-------------------------------------
[~pnowojski] Don't get me wrong :) I'm trying to add what this adjustment is
trying to address, because if an old flinker will confuse as well, then the
process really should still be improved in later releases, so as a 1.19 release
manager, I'm wondering what part of the description could be clearer? (I
should have asked this directly in my previous reply)
> Release Testing Instructions: Verify FLINK-33695 Introduce TraceReporter and
> use it to create checkpointing and recovery traces
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: FLINK-34289
> URL: https://issues.apache.org/jira/browse/FLINK-34289
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Metrics
> Affects Versions: 1.19.0
> Reporter: lincoln lee
> Assignee: Piotr Nowojski
> Priority: Blocker
> Fix For: 1.19.0
>
> Attachments: screenshot-1.png
>
>
> This ticket covers testing three related features: FLINK-33695, FLINK-33735
> and FLINK-33696.
> Instructions:
> # Configure Flink to use
> [Slf4jTraceReporter|https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/trace_reporters/#slf4j]
> and with enabled *INFO* level logging (can be to console or to a file,
> doesn't matter).
> # Start a streaming job with enabled checkpointing.
> # Let it run for a couple of checkpoints.
> # Verify presence of a single *JobInitialization* [1] trace logged just after
> job start up.
> # Verify presence of a couple of *Checkpoint* [1] traces logged after each
> successful or failed checkpoint.
> [1]
> https://nightlies.apache.org/flink/flink-docs-master/docs/ops/traces/#checkpointing-and-initialization
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
