Forum Discussion
We've been having the same issue in our environment since synchrony came out. If we enable collaborative editing, all access through the WIP starts to hang within minutes. Recovery requires shutting down all nodes, and starting them one at a time. However, we just verified that when this happens, the individual nodes are functional when accessed directly, and collaborative editing works with multiple users on different nodes in the cluster. This pretty much points to the F5 config as the issue.
Apparently there aren't many Confluence Datacenter clients trying to use collaborative editing yet, and Atlassian doesn't provide any support for the load balancing aspect. We will be playing with the F5 config and proving data back to Atlassian support to figure this out. I'll report whatever we find here.
Regarding questions in the last post: synchrony has its own URL and port. Our synchrony processes run on the same nodes as the confluence processes; as such they need a different port. Not sure what communication the user's browser has with synchrony. I do believe the issue has to do with session persistence, but I don't know what synchrony requires.