Skip to content

Proper way to upgrade external modules? #4309

Answered by badlop
ggyurchev asked this question in Questions
Discussion options

You must be logged in to vote

Questions to "Soft upgrade process":

That long procedure is not needed in your case, as you only modified a few erlang modules to fix bugs that don't require module restart to take effect right (no mnesia or ets changes, no changes to records/tuples/internal state). Instead of "soft upgrade procedure", you probably can use "module upgrade process".


S.1. Before running leave_cluster, we should stop all connections to that node, right? My gut tells me bad things will happen if clients continue to connect through that node.

You are right.

During the time (few seconds) that passes between step "run leave_cluster on node B" and "stop old node B", some clients may modify the node B databas…

Replies: 2 comments 2 replies

Comment options

You must be logged in to vote
0 replies
Answer selected by ggyurchev
Comment options

You must be logged in to vote
2 replies
@badlop
Comment options

@ggyurchev
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants