[FLINK-34289] Release Testing Instructions: Verify FLINK-33695 Introduce TraceReporter and use it to create checkpointing and recovery traces

• Type: Sub-task
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.19.0
• Fix Version/s: 1.19.0
• Component/s: Runtime / Metrics
• Assignee: Piotr Nowojski
• Reporter: lincoln lee
• Created: 30/Jan/24 13:05
• Updated: 08/Feb/24 17:00
• Resolved: 06/Feb/24 08:58

Description

This ticket covers testing three related features: FLINK-33695, FLINK-33735 and FLINK-33696.

Instructions:

1. Configure Flink to use Slf4jTraceReporter and with enabled INFO level logging (can be to console or to a file, doesn't matter).
2. Start a streaming job with enabled checkpointing.
3. Let it run for a couple of checkpoints.
4. Verify presence of a single JobInitialization [1] trace logged just after job start up.
5. 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

Issue Links

• is a clone of: FLINK-34288 Release Testing Instructions: Verify FLINK-33735 Improve the exponential-delay restart-strategy
• is cloned by: FLINK-34290 Release Testing Instructions: Verify FLINK-33696 Add OpenTelemetryTraceReporter and OpenTelemetryMetricReporter
• is cloned by: FLINK-34387 Release Testing: Verify FLINK-33695 Introduce TraceReporter and use it to create checkpointing and recovery traces