Splice 0.4.20
Fix a bug where the setting the affinity for the splice-cometbft and splice-global-domain helm charts would remove the anti affinity for the cometbft and the sequencer deployment. This ensures that if multiple SVs are…
- A newer release in the 0.4 line: Splice 0.4.25
- Newest Splice: Splice 0.9.4
Open the release notes (opens in a new tab)docs.canton.network
- Deployment
- Fix a bug where the setting the affinity for the
splice-cometbftandsplice-global-domainhelm charts would remove the anti affinity for thecometbftand thesequencerdeployment. This ensures that if multiple SVs are run on the same nodes, not more than onecometbftpod can be deployed on the same node and that no more than onesequencerpod can be deployed to the same node (acometbftpod can still share a node with asequencerpod). This can be disabled by setting theenableAntiAffinityhelm value tofalse(defaulttrue). - Replace
-Dscala.concurrent.context.minThreads=8with-Dscala.concurrent.context.numThreads=8and set-XX:ActiveProcessorCount=8in thedefaultJvmOptionsfor all the helm charts that deploy scala apps. This should ensure that the internal execution contexts spawn 8 threads to handle processing and that the JVM is configured for 8 CPUs as well. The previous behavior would spawn up to number of available processors, which can be up to the number of CPUs on the actual node if no CPU limit is set. This should avoid overloading the nodes during heavy processing.
- Fix a bug where the setting the affinity for the
- SV
- UI
- Add the ability to specify a validator party hint when generating onboarding secrets.
- The UI now provides a formatted message for easily sharing onboarding details with validator operators.
- UI