[Polkadot Wiki Migration] Upgrade Your Node

[CrackTheCode016]

This page was migrated from https://wiki.polkadot.network/docs/maintain-guides-how-to-upgrade

[dawnkelly09]

Scan for Vale false positives. Resolved convos = made it on the update list and should go away now. I left comments for the legit flags with suggested edits. Thank you!

[dawnkelly09]

I did some formatting/grammar edits and moved terminal to snippets, etc.
@polkadot-developers/docs-content-team please see my comments on content needs --- make sure you check out the snippet for the terminal output because it is missing the command. Please request new format review after updates. Thanks!

[dawnkelly09]

Is this meant to be a quick overview of which steps are needed with a more extensive tutorial somewhere else? If there isn't a more detailed tutorial to go with this, then some of these steps should have more detail. What commands do I use to start a second node? How do I generate session keys? etc. This section has a nice amount of "what" but almost no "how"

[eshaben]

These are steps they most likely (if not, someone on their team) would have already gone through when setting up the original validator.

I would just add a link to the onboarding page, which will include how to get a node up and running and how to generate session keys

[eshaben]

Another note: I think this page will get heavily updated at some point, so I would link to other places for now where needed

[CrackTheCode016]

I linked the "How to Validate" page, which covers this as a prerequisite. We can definitely make it flow a little better, though.

[dawnkelly09]

Same question as above. Do we need more how in here or will there be tutorial(s) to link out to?

[dawnkelly09]

Please add some things the user should already be familiar with, might want to read first, stuff to ensure they have installed, etc., before continuing with this guide.

[eshaben]

This is a great place to add that they'll need to set up a secondary validator

[eshaben]

This is a great place to add that they'll need to set up a secondary validator

[0xLucca]

Hey @CrackTheCode016,

I'd like to clarify the objective of this section. The current process seems to involve:

1. Spinning up an additional validator (B)
2. Applying fixes and upgrades to the original validator (A)
3. Restarting validator A

Wouldn't it be more efficient to apply all changes to the server of validator B before starting it? This reduces the process time from (N+3) * 2 sessions to N+3 sessions

Could you please elaborate on the rationale behind the current method? Maybe there are specific advantages to this approach that I might be overlooking

[CrackTheCode016]

@0xLucca This appears to me like it would work, I'll ping infra and get a final answer before making any changes.

[BulatSaif]

Good to go! I like that you emphasized the importance of waiting for 2 full sessions—it’s really important.