temporalio / temporalio/temporal
Unable to start 1.21.4 cluster with archival disabled
Open
Nobody has claimed this yet.
potential-bug
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Expected Behavior
Able to upgrade temporal cluster from 1.20.4 to 1.21.4 with archival disabled
Actual Behavior
Server crash after upgrading to 1.21.4
Steps to Reproduce the Problem
- Start cluster 1.20 with the bellow config
- Let's the cluster run for a while
- Upgrade cluster to 1.21.4
archival:
history:
state: "disabled"
visibility:
state: "disabled"
Specifications
- Version: 1.21.4
- Platform: Linux
Suspect related issue: https://github.com/temporalio/temporal/issues/4638
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
Reproduce the upgrade from a 1.20 cluster to 1.21.4 using the archival-disabled configuration shown in the issue, then capture the server crash and inspect the related archival startup path. Compare the behavior with the suspected issue #4638; done means the cluster upgrades and starts successfully with both history and visibility archival disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100