Skip to content

ClusterDisruptionIT#testSendingShardFailure fails on CI #32431

@javanna

Description

@javanna

This does not reproduce for me. I can see that the whole suite has trace logging on for more than a year, which is a signal that it was failing in the past. I didn't find this specific issue though in our repo.

https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+6.x+multijob-unix-compatibility/os=sles/1206

REPRODUCE WITH: ./gradlew :server:integTest -Dtests.seed=E77D94CFECE59A17 -Dtests.class=org.elasticsearch.discovery.ClusterDisruptionIT -Dtests.method="testSendingShardFailure" -Dtests.security.manager=true -Dtests.locale=sq -Dtests.timezone=PST8PDT

With all the trace logging I have not identified the exact cause of the failure. I did notice quite some "Connection reset by peer" errors in the logs, bu they may actually be expected. Somebody more familiar with this test is definitely going to understand more.

Metadata

Metadata

Assignees

No one assigned

    Labels

    :Distributed Coordination/AllocationAll issues relating to the decision making around placing a shard (both master logic & on the nodes)>test-failureTriaged test failures from CI

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions