Updating temporal helm kubernetes cluster

Community Support
,
1

Hello Temporal Kube team, Thank you for all the wonderful work!
I was upgading my temporal cluster to v1.21.2 , Every thing went well except the history pod it is crash looping with below error. Look for the help to resolve this issue. Thank you!

{"level":"info","ts":"2023-07-17T12:10:45.766Z","msg":"none","shard-id":2,"address":"192.168.100.90:7234","lifecycle":"Started","component":"shard-context","logging-call-at":"controller_impl.go:321"}
panic: unable to find queue category by queye category ID: 5

goroutine 2244 [running]:
go.temporal.io/server/service/history/shard.loadShardInfoCompatibilityCheckWithoutReplication(0xc00051f6d0)
        /home/builder/temporal/service/history/shard/compatibility.go:65 +0x334
go.temporal.io/server/service/history/shard.loadShardInfoCompatibilityCheck({0x2bf50f0, 0xc0003ec0b0}, 0xc000752a80?)
        /home/builder/temporal/service/history/shard/compatibility.go:47 +0x3f
go.temporal.io/server/service/history/shard.(*ContextImpl).loadShardMetadata(0xc000221600, 0xc001187e87)
        /home/builder/temporal/service/history/shard/context_impl.go:1645 +0x195
go.temporal.io/server/service/history/shard.(*ContextImpl).acquireShard.func1()
        /home/builder/temporal/service/history/shard/context_impl.go:1779 +0x46
go.temporal.io/server/common/backoff.ThrottleRetry.func1({0x0, 0xc000e6b530})
        /home/builder/temporal/common/backoff/retry.go:119 +0x1b
go.temporal.io/server/common/backoff.ThrottleRetryContext({0x2be1980, 0xc000124000}, 0xc001187e30, {0x2bc7540, 0xc0001a93e0}, 0x28?)
        /home/builder/temporal/common/backoff/retry.go:145 +0x20a
go.temporal.io/server/common/backoff.ThrottleRetry(0x0?, {0x2bc7540?, 0xc0001a93e0?}, 0xc000e6b6a0?)
        /home/builder/temporal/common/backoff/retry.go:120 +0x59
go.temporal.io/server/service/history/shard.(*ContextImpl).acquireShard(0xc000221600)
        /home/builder/temporal/service/history/shard/context_impl.go:1847 +0x106
created by go.temporal.io/server/service/history/shard.(*ContextImpl).transition.func1
        /home/builder/temporal/service/history/shard/context_impl.go:1461 +0x65

temporal
temporal710×142 4.95 KB

2

The issue was, During upgrade I forgot to give the archival config. The correct upgrade command for us should be

   -f values/values.archival.s3.yaml \
   -f values/values.mysql.yaml \
   --set elasticsearch.enabled=false \
   --set grafana.enabled=false \
   --set prometheus.enabled=false \
   --set server.replicaCount=1 \
   . \
   --timeout 15m \
   --namespace temporal --create-namespace \
   --wait
3

Hey @Nishant_Pathak , what does archival do?