Some questions about "zero down time" upgrade for confluence

Niklas Klein [Communardo]

Hey everyone,

I already had a read on 

• https://confluence.atlassian.com/doc/upgrade-confluence-without-downtime-1027127923.html
• https://confluence.atlassian.com/doc/upgrade-a-confluence-cluster-manually-without-downtime-1027127924.html
• https://jira.atlassian.com/browse/CONFSERVER-52686?error=login_required&error_description=Login+required&state=6f0c6118-58de-43ab-8d10-e755f98596e7

and have some additional questions about the behaviour during "zero-down-time" upgrade (which probably go into other topics aswell)

1. If a node goes down and someone was e.g. creating a page as a draft, can he lose some of his progress?
2. If multiple people are working collborative on a page and one of them is connected with a node that is going down, what happens?
3. Should I update my plugins before or after I do the ZDU update of the confluence version or does it not matter at all? Also, plugin updates are "always" zero-down-time, right?

Brant Schroeder

@Niklas Klein [Communardo] 

1. If a node goes down and someone was e.g. creating a page as a draft, can he lose some of his progress? If the draft save has not yet synced they would loose it.  
2. If multiple people are working collaborativly on a page and one of them is connected with a node that is going down, what happens? It would have to reconnect to the page but the user might not even notice.
3. Should I update my plugins before or after I do the ZDU update of the confluence version or does it not matter at all? Also, plugin updates are "always" zero-down-time, right? We usually do it before to ensure compatibility.