elastic/elasticsearch

We should have some service disruption tests with security enabled

Open

#29,704 opened on Feb 10, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (25,882 forks)batch import
:Security/Security>testTeam:Securityhelp wanted

Repository metrics

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

Description

Original comment by @bleskes:

Security integrates deeply into ES and how it works. As we learned (LINK REDACTED) it have unexpected side effects. We should have some basic disruption testing going on while security is enabled. We don't have to go to the same lengths we do in ES proper, but I think we should have simple tests, like:

  • isolating a master and seeing the cluster successfully go through master election
  • isolating the primary of security indices and see that primary promotion goes well

Contributor guide

Research direction
Implement service disruption tests with security enabled, focusing on master election and primary promotion for security indices.
Tech stack
java
Domain
backend
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.
Half day
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.
Clear
Prerequisites
JavaGradleElasticsearch testing framework
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40