elastic/elasticsearch

REST test against clusters with dedicated master nodes

Open

#34,563 opened on Oct 17, 2018

View on GitHub
 (14 comments) (0 reactions) (0 assignees)Java (25,882 forks)batch import
:Delivery/Build>enhancementTeam:Deliveryhelp wanted

Repository metrics

Stars
 (76,700 stars)
PR merge metrics
 (Avg merge 2d) (1,000 merged PRs in 30d)

Description

Today we run our REST tests against clusters with nodes that are both data nodes and master-eligible nodes. We therefore miss tests against the (recommended) configuration of dedicated master nodes and separate data nodes, and this includes things like tests of the rolling upgrade procedure which may be sensitive to the order in which nodes are upgraded.

Thanks to Armin for spotting this in https://github.com/elastic/elasticsearch/pull/34560#discussion_r225992140.

Contributor guide

Research direction
Set up a dedicated master node cluster configuration and modify the REST test suite to include tests that cover the rolling upgrade procedure and other operations that might be sensitive to node roles.
Tech stack
java
Domain
testingdevops
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
JavaGradle
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30