Hi,
We were sold Jira DC under the pretence that it was a HA solution, but after working with it for half a year i have a problem calling it HA, or i simply have not found the functions that would make it call it High Available.
A few how-do-i's:
- How do i evict all user sessions established for a node to other nodes without them losing their session data, if i need to service a node? So far i can only shut down the node, but if a user was about to create a ticket and have filled out all forms but not not submitted the form, this data will be lost.
In lack of this very basic functionality, it would be great to know what users are on one node, so i can warn them manually to get off the node, but i can't find that functionality either? Is there a "List users on node X" functions i am missing?
- A user reports a internal server error 500 on Node1. How do i switch my session to that node, without open 10 incognito browsers and login until i by random hit the node?
IMO a rolling restart of a DC cluster will instead of losing a users data once, make them lose their data repeatedly because:
User A is on Node1. I restart node1. User loses their data, but the loadbalancer will soon move them on to node2. They start working there and then it's turn to restart node2. they once more lose their data and can now either be moved to node3, or node1 if already back up. How is this better than all users losing their sessions once?
Beside if a server dies, users can be falled over to another node (and lose their data) but be back in a new session on another server, but that's basically the only "HA" thing about Atlassian DataCenter products.
Kind regards
Jonas Andersson
