`tiup cluster replay` doesn't work for `cluster reload` , because `cluster reload` doesn't generate audit record.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Bug Report
Please answer these questions before submitting your issue. Thanks!
- What did you do?
tiup cluster display tidb-test
tiup cluster reload tidb-test -R tikv
cirl -C
tiup cluster audit
-
What did you expect to see?
ID Time Command
-- ---- -------
xxxxxxxxxxxx 2021-08-13T02:42:08Z /root/.tiup/components/cluster/v1.5.2/tiup-cluster reload tidb-test -R tikv
fGPJGGtP4sH 2021-08-13T02:42:08Z /root/.tiup/components/cluster/v1.5.2/tiup-cluster display tidb-test -
What did you see instead?
ID Time Command
-- ---- -------
fGPJGGtP4sH 2021-08-13T02:42:08Z /root/.tiup/components/cluster/v1.5.2/tiup-cluster display tidb-test -
What version of TiUP are you using (
tiup --version)?
v1.5.2
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
Start by reproducing the listed tiup cluster display, reload, and audit commands with TiUP v1.5.2, then trace the cluster reload entry point and the audit-record generation path. Done means a reload command appears in tiup cluster audit output alongside the existing display record.
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
- Mostly clear
- Newbie friendliness
- 45/100