Bugzilla – Bug 6146
HA new session conflict code unnecessary or incomplete
Last modified: 2017-01-31 10:40:53
You need to
before you can comment on or make changes to this bug.
We have a section in the HA handling that deals with the case that a new
session reported from the other node is in conflict with an existing session.
We determine this conflict by looking at the agent/display pair.
However there are some questions here:
a) When can this ever occur? We haven't come up with any scenarios.
b) Is this even a problem? Reconnecting will verify and purge any broken
sessions, so the only problem is one extra consumed license until the periodic
check reaps it.
c) We only look at sessions for the same user as the incoming new session.
However a display can conflict from a different user. This scenario is also
easy to trigger if someone logs out and someone else logs in right after.
Let start with A).
(In reply to comment #1)
> Let start with A).
We decided to leave this bug on '---' for further discussions next week.