Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-70153

Manage sessions within Jira DC

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Tracked Elsewhere
    • None
    • Data Center - Other
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Issue: Implementation of a Jira DC cluster requires a load balancer to store a persistence record of a users session so requests with the users session ID are routed to the specific Jira DC node where that session is present. In turn, an administrator is obliged to maintain this configuration on the load balancer as part of their Jira DC implementation. This is undesirable as it has both an implementation and operational overhead in addition to users being logged out if a node fails or is taken offline for maintenance.

      Goal: Session ID's are shared between Jira DC nodes eliminating the need for persistence records on a load balancer and in turn allow any http request to be served from any Jira DC node.

      Benefits:

      Reduction of Jira DC implementation complexity.

      Jira DC nodes can fail or be disabled without users loosing their sessions.

      Enhanced HA.

            [JRASERVER-70153] Manage sessions within Jira DC

            There are no comments yet on this issue.

              Unassigned Unassigned
              ca1ae9c207fb Matthew Oaks
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: