yugabyte/yugabyte-db

[docdb] Test that tablet server survives a failure in OpenTablet during remote bootstrap

Open

#204 opened on Apr 23, 2018

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C (8,229 stars) (1,003 forks)batch import
area/docdbgood first issuekind/enhancementpriority/medium

Description

Jira Link: DB-1565 Reported by @hectorgcr.

Add new test to verify that a failure between call to RemoteBootstrapClient::Finish() and OpenTablet doesn't leave the tablet server in an invalid state. Ideally, since the tablet gets tombstoned, the tablet server should be remote bootstrapped again by the leader, and the tablet server should reject any requests to participate in raft consensus rounds.

Contributor guide

Tech stack
cpp
Domain
databasetestingbackend
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C++ programmingDistributed systemsRemote bootstrap concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Look at existing remote bootstrap tests in the docdb directory, such as tablet server test.cc or similar. The test should simulate a crash or failure after RemoteBootstrapClient::Finish() and before OpenTablet, then check that the tablet server remains in a valid state and can be re bootstrapped. Investigate the RemoteBootstrapClient class and OpenTablet function to understand the failure point.