migrating active editing sessions?

[wkloucek]

In the following I'm referring the state of release/1.2.0 branch with OO 8.2.0-rc25

I have 3 documentserver pods and one active document editing session.

I then do a kubectl rollout restart deploy -n onlyoffice documentserver.

What happens afterwards is:

• the two pods which don't have an active editing sessions are quickly "replaced" by new pods
• the one pod which hosts the active editing session is in "terminating" state for approximately 60 minutes. When the pod is gone, the editing session aborts and the user gets a warning / error message about the connection to be interrupted.

I wonder if there isn't supposed to be a mechanism that "migrates" the active edition session from one pod to another one without the user to reopen the document manually?

[wkloucek]

@alexanderonlyoffice is my expectation wrong?

[alexonlyoffice]

@wkloucek,

I wonder if there isn't supposed to be a mechanism that "migrates" the active edition session from one pod to another one without the user to reopen the document manually?

this is a good question. we will think about if and how it can be implemented.

[dj4oC]

@alexonlyoffice any update on that? I see that as a blocker to use Shards Helm

[alexonlyoffice]

@dj4oC, we are still discussing your request. this is a one of the main topics.

[wkloucek]

@dj4oC, we are still discussing your request. this is a one of the main topics.

Was there a outcome that you could already share with us?