Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update upstream dependency to polkadot-v0.9.42 #1553

Closed
8 tasks
Kailai-Wang opened this issue Mar 30, 2023 · 4 comments · Fixed by #2173
Closed
8 tasks

Update upstream dependency to polkadot-v0.9.42 #1553

Kailai-Wang opened this issue Mar 30, 2023 · 4 comments · Fixed by #2173
Assignees
Labels
D3-chore tasks that need to be completed but don’t provide any additional features/functionality I2-medium should be completed within 10 working days

Comments

@Kailai-Wang
Copy link
Collaborator

This is an issue to track the update of the upstream dependency.

parachain dependency

  • Update local polkadot/substrate dependencies (helper script: ./scripts/bump-code-versions.sh)
  • Fix any compilation/test issues
  • Optionally roll out the client/runtime update

tee-worker dependency

@Kailai-Wang Kailai-Wang added I2-medium should be completed within 10 working days D3-chore tasks that need to be completed but don’t provide any additional features/functionality labels Mar 30, 2023
@Kailai-Wang Kailai-Wang changed the title Update upstream dependency to polkadot-v0.9.40 Update upstream dependency to polkadot-v0.9.41 Apr 5, 2023
@Kailai-Wang Kailai-Wang changed the title Update upstream dependency to polkadot-v0.9.41 Update upstream dependency to polkadot-v0.9.42 May 4, 2023
@Kailai-Wang
Copy link
Collaborator Author

⚠️ A note for node operators: ⚠️

At times, Polkadot/Kusama can be become overloaded with users. This can be observed indirectly by best and finalized block getting stuck at some number and after release v0.9.42, it can be observed as peer count being lower than what was specified (--num-in + --num-out). This happens because there is a limited number of inbound slots on publicly reachable nodes and as more and more people connect to the network, these slots can get fully occupied.

To remedy this, we have adjusted the in/out peer rations to allow nodes to consume fewer outbound slots. At the same time the number of inbound slots has been increased to allow the node to still maintain 40 connections. If the node is run behind a NAT, it won't automatically be able to accept inbound connections because those dialing attempts are being blocked. If you're experiencing issues with low peer counts/syncing stalling, consider opening the P2P port in your NAT to allow inbound connections.

We are working on adding support for hole punching that would take the extra configuration of opening a port for inbound connections out of the equation and allow nodes to seamlessly establish connections to other nodes who are behind NATs but that feature is still work in progress.

cc @niteshb3495

@github-actions
Copy link
Contributor

github-actions bot commented Jul 4, 2023

❗ This issue is stale because it has been open for 60 days with no activity.
Remove Stale label or update it, otherwise this issue will be closed in 7 days.
@litentry/parachain

@github-actions github-actions bot added the Stale label Jul 4, 2023
@Kailai-Wang Kailai-Wang removed the Stale label Sep 6, 2023
@Kailai-Wang
Copy link
Collaborator Author

How hard is it to update the worker only while leaving the logic update of pallets unchanged? (pallet dependency is still needed) @BillyWooo

@Kailai-Wang
Copy link
Collaborator Author

Done via #2173

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
D3-chore tasks that need to be completed but don’t provide any additional features/functionality I2-medium should be completed within 10 working days
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants