[
https://issues.apache.org/jira/browse/FLINK-34289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17814787#comment-17814787
]
Piotr Nowojski commented on FLINK-34289:
----------------------------------------
Thanks for cleaning this up. Indeed I was confused what to do and decided to
follow an example from someone else.
Anyway, after giving it a second thought, I think there is no need to cross
team test this feature. I've closed FLINK-34387.
> 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)
