We’re using Temporal and have an issue with the numHistoryShards configuration setting. We initially set it to 512, but have found it to be too high for our needs. Can we simply modify the configuration and restart the Temporal service to apply the changes?
Unfortunately no, if you change number of shards after your cluster is provisioned you would have to stand up a new one (one idea is to keep the old one running until all workflows have completed and route client calls for new executions to newly provisioned one with updated shard count).
Does the extra shards cause issues for you? 512 is typically not considered a large amount.