Disabling archival not working

Community Support
1

We are noticing a high number of these errors

{"level":"error","ts":"2021-06-10T17:49:46.005Z","msg":"Fail to process task","service":"history","shard-id":192,"address":"10.228.45.11:7234","shard-item":"0xc0156fb600","component":"transfer-queue-processor","cluster-name":"active","shard-id":192,"queue-task-id":41955237,"queue-task-visibility-timestamp":1623347382999522608,"xdc-failover-version":0,"queue-task-type":"TransferWorkflowTask","wf-namespace-id":"8b2c494d-892b-4bd6-8a63-ec86be9ab0ec","wf-id":"6942a04b-183e-477f-9513-eafdc53702af","wf-run-id":"4d44351a-d097-4c8a-bfe4-d196171fe98b","error":"context deadline exceeded","lifecycle":"ProcessingFailed","logging-call-at":"taskProcessor.go:326","stacktrace":"go.temporal.io/server/common/log.(*zapLogger).Error
	/temporal/common/log/zap_logger.go:136
go.temporal.io/server/service/history.(*taskProcessor).handleTaskError
	/temporal/service/history/taskProcessor.go:326
go.temporal.io/server/service/history.(*taskProcessor).processTaskAndAck.func1
	/temporal/service/history/taskProcessor.go:212
go.temporal.io/server/common/backoff.Retry
	/temporal/common/backoff/retry.go:103
go.temporal.io/server/service/history.(*taskProcessor).processTaskAndAck
	/temporal/service/history/taskProcessor.go:238
go.temporal.io/server/service/history.(*taskProcessor).taskWorker
	/temporal/service/history/taskProcessor.go:161"}

We narrowed it down to archival and hence wanted to turn it off.
We tried using tctl and also configMap, but still the archival is still enabled on namespaces.
How can we force disable archival?

2

the error seems to suggest matching service is not up to speed, not archival.
can you check if your matching service is healthy?

and if you provide more metrics about matching service?