Add a test case for frequent upgrades and downgrades with massive numbers of changefeeds and tables.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 56
- Forks
- 63
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 34
Description
Design an extreme stress test to verify system stability under upgrade/downgrade scenario. The core scenario involves the system handling an extreme load of 200k tables and 10k changefeeds while undergoing frequent version rollbacks (e.g., continuous A->B->A version toggle cycles).
-
Use AI to generate 200k tables with random schemas and apply continuous read/write workload.
-
Trigger consecutive upgrade/downgrade cycles while the full load is running.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating existing stress tests and upgrade/downgrade harnesses, then determine how they generate tables, changefeeds, and workload. Done means a repeatable test covering 200k tables, 10k changefeeds, continuous reads and writes, and A→B→A cycles with stability results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases, testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100