``tt replicaset status``: no clear error when incorrect orchestrator is forced
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 113
- Forks
- 18
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 23
Description
tt replicaset status shows a huge scary error trace when called with an explicit orchestrator that doesn't match the real orchestrator used on the cluster.
Environment: Ubuntu, tt-ee 2.2.1, Tarantool EE 3.0.0
Steps to reproduce:
- Create a vshard app from template, build it, and start.
- Check a replica set status forcing an incorrect orchestrator
--cartridge:
$ tt rs status shard-app/ --cartridge
Expected result: Concise and clear error message that the selected orchestrator is not used on the cluster
Actual result: A huge scary error stack trace takes up the entire screen. Here's a fragment:
Contributor guide
No contributing guide indexed for this repository
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
Begin at the tt rs status command and its --cartridge orchestrator-selection path. Reproduce the issue with the vshard template scenario, then trace error handling for a mismatched orchestrator. Done means the command emits a concise, clear error instead of the full stack trace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100