-
Suggestion
-
Resolution: Unresolved
-
None
-
27
-
1
-
When a user session is moved from one server to another, all session information is lost, including login credentials. When this happens, the user is forced to re-login in JIRA in order to create a new session.
Please implement user session replication between the nodes in order to avoid that.
- is duplicated by
-
- Closed
- is related to
-
- Gathering Interest
[JRASERVER-67647] Ability to have user session replication between the nodes in Jira Data Center (DC)
I have no experience with writing or configuring tomcat apps, so customizing how tomcat deploys Jira is outside of my skillset – if that's something that would work I'd be happy to try it, but I'd need some help figuring out how to set it up using the Atlassian Jira data center docker containers (on kubernetes). if it's that easy perhaps Atlassian could do a quick write-up of how to set it up? that would (IMO at least) satisfy the requirements for this ticket.
a18e59a95e41 did you try to investigate of Tomcat Cluster Redis session manager?
https://github.com/ran-jit/tomcat-cluster-redis-session-manager/wiki
Just curious is that possible to manage it?
I suppose Richard, you never used Enterprise HA Atlassian software?
I'm sorry, it only get's worse. Welcome to Atlassian landscape.
But hey, we have cakes here!
Wow.. just wow. a data center product designed for high availability that doesn't even support an optional form of shared sessions across servers? I mean, it's not even a hard thing to do... use memcache, redis, store them in postgresql, .... lots and lots of options and lots of open source implementations for each.
Yes, sticky connections technically work, but that means any time a node goes down anyone using it has to re-authenticate. I've literally never even seen a project before that was designed for high availability that didn't deal with that before literally anything else.
I'm literally baffled how this even has to be a suggestion, I had just assumed it would already be working as it is in every other piece of commercial software I've ever used. I'm not trying to be offensive, but something like this missing really does not inspire a lot of confidence in Jira Data Center as a product, and given how nice the software is otherwise I'm just ... sorry, my mind is blown.
4555db5a5f8f I tried to use the Redis session manager for Tomcat you suggested. At first it looked as if it worked - the details about the logged-in user were available to both cluster nodes from the shared session store. However, further tests showed that some plugins we use also store objects in the session and some of them do not implement Serializable, which leads to exceptions being thrown.