linkedin / linkedin/ambry

testDataChunkFailure[1] failed intermittently on travis.

Open
#962 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.8k
Forks
298
Avg merge
21h 43m
Merged PRs (30d)
9

Description

The failure:

com.github.ambry.router.GetBlobOperationTest > testDataChunkFailure[1] FAILED
    java.util.concurrent.ExecutionException: com.github.ambry.router.RouterException: Prepare for sending failed Error: UnexpectedInternalError
        at com.github.ambry.router.FutureResult.resultOrThrow(FutureResult.java:113)
        at com.github.ambry.router.FutureResult.get(FutureResult.java:99)
        at com.github.ambry.router.GetBlobOperationTest.doPut(GetBlobOperationTest.java:222)
        at com.github.ambry.router.GetBlobOperationTest.testDataChunkError(GetBlobOperationTest.java:862)
        at com.github.ambry.router.GetBlobOperationTest.testDataChunkFailure(GetBlobOperationTest.java:557)
        Caused by:
        com.github.ambry.router.RouterException: Prepare for sending failed Error: UnexpectedInternalError
            Caused by:
            java.lang.IllegalArgumentException: Total Replica count 1 is less than success target 2

Contributor guide

No contributing guide indexed for this repository

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 by running GetBlobOperationTest.testDataChunkFailure[1] and review the stack-trace locations in GetBlobOperationTest.java:222, 557, and 862. Trace why the data-chunk failure reaches an UnexpectedInternalError with a success target larger than the replica count. Done means the intermittent Travis failure is resolved and the test passes without that exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
distributed-systems, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.