informalsystems / informalsystems/tm-load-test

Allow for a preconfigured number of Tendermint node failures

Open
#43 0 comments 0 reactions 0 assignees View on GitHub
help wanted
Dominant language
Go
Stars
47
Forks
33
PR merge metrics
No merged PRs in 30d

Description

We have a long-term requirement coming from [GoT](https://github.com/interchainio/got) where experiments will need to be conducted under load where some nodes might fail. At present, the default behaviour of `tm-load-test` is to fail the entire load test completely.

We need `tm-load-test` to:

1. be configurable in the number of Tendermint node failures it can tolerate, and
2. have the ability to keep retrying to connect to failed Tendermint node endpoints.

This functionality needs to apply to both master/slave mode and standalone mode.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing how tm-load-test handles Tendermint node connection failures in standalone mode and master/slave mode. Identify the configuration entry point and connection retry path, then verify that both modes tolerate the configured number of failures and keep retrying failed endpoints without aborting the load test.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.