André Claro

+1 "Our latest cost analysis and performance benchmarks show that customers can realize cost savings of up to 23% and performance gains of up to 36% by deploying the GitLab...

So this is the first 1.14.x release supporting mainnet, right? Did you already try in your nodes?

the [release notes for 1.4.5](https://github.com/bnb-chain/bsc/releases/tag/v1.4.5) is confusing: `It is mainly for Testnet, if you wanna upgrade your node for mainnet Feynman hard fork, you'd better try [v1.3.13](https://github.com/bnb-chain/bsc/releases/tag/v1.3.13).`

The only way to resolve this issue is by: - Scaling down the temporal services to zero replicas - Clearing `cluster_membership` table - Scaling temporal services back up

So, Why are the temporal services using the old IP addresses and consequently causing these packet drops? 

it seems these old IP addresses are also stored in memory by each services and not removed when they are not longer reachable.

The drops are not going way... here is an example: 

I just think it doesn't make sense to be spamming the cluster with network connections that are dropped / not required. The old IPs should be invalidated from the cache/db...

last days - block height  last 12 hours - block height 

I see a few message like `Report 12D3KooWJW6iSkaD6DYV8h8V5pzzVdBsS6rHSpN8yL7toKPxrkDa: -2147483648 to -2147483648. Reason: Same block request multiple times. Banned, disconnecting.` Example: ``` Jun 19 11:00:17 m-acala-02 acala[3326290]: 2024-06-19 11:00:17 Report 12D3KooWJW6iSkaD6DYV8h8V5pzzVdBsS6rHSpN8yL7toKPxrkDa:...