redpanda-data / redpanda-data/redpanda

cdt-infinite-retention job fails on a TimeoutError

Open
#14,835 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
12.6k
Forks
792
PR merge metrics
No merged PRs in 30d

Description

job fails to produce artifacts

error:

[WARNING - 2023-11-08 01:37:30,263 - infinite_retention_test - _iterative_retention_flow - lineno:740]: Exception detected while running scrub
[ERROR:2023-11-08 01:45:28,815]: Exception receiving message: <class 'ducktape.errors.TimeoutError'>: runner client unresponsive, active_tests:
 [TestKey(test_id='rptest.infinite_retention.infinite_retention_test.InfiniteRetentionTest.long_retention_with_spillover_test.rolling_restarts=False', test_index=1)]

related slack thread

JIRA Link: CORE-1568

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with rptest.infinite_retention.infinite_retention_test.InfiniteRetentionTest.long_retention_with_spillover_test and the _iterative_retention_flow location around line 740. Review the linked Buildkite failure and related Slack thread to determine why the scrub encounters a TimeoutError and leaves the runner unresponsive. Done means the cdt-infinite-retention job completes and produces its artifacts without this failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.