• Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Update - 18 August 2017

      Hi everyone,

      Thanks for all your votes and comments on this suggestion. Your voice means a lot to us.

      We're excited to announce that from now on clustering is officially supported and available for everyone in Crowd Data Center.

      This is the newest addition to Atlassian's Data Center family, which brings you high availability and uninterrupted access as well as all the features of Crowd Server.

      Crowd DC is also great at scaling – you can easily expand your DC with extra nodes that will pull all the necessary configuration from the shared file system, and join the cluster without any extra setup.

      Crowd Data Center is delivered in the Crowd 3.0 release together with support for Microsoft Azure Active Directory.

      We highly recommend you to upgrade your current Crowd version to the latest one. In case if you will require any help or assistance in setting up Crowd Data Center or have further questions please don't hesitate to get in touch with me directly at mradochonski@atlassian.com

      Please read the upgrade notes for important information about this release before installing the newest version.

      To learn more about Crowd Data Center, check out our technical documentation, technical FAQ, and licensing FAQ.

      You can download Crowd 3.0 from here.

      If you are ready to get started then get a Crowd Data Center license, or try it out for free.

      Thanks,

      Marek Radochonski

      Senior Product Manager, Crowd

      mradochonski@atlassian.com

      Atlassian Status as of 27 April 2011

      Hi folks,

      Thanks for your feedback and continued support. We wanted to give you an update on the status of this issue.

      Over the medium term, the direction we're taking with Crowd is to focus on scalability, reliability and performance. Exciting development has occurred and is going to continue within this space. This feature is a strong candidate for a future release. We can't promise a specific release, but we'll update the issue when we have more concrete information.

      Regards,
      Eugene Mak
      Atlassian Product Management

          Form Name

            [CWD-266] Clusterable Crowd Documentation

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3389132 ] New: JAC Suggestion Workflow 3 [ 3628560 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1392396 ] New: JAC Suggestion Workflow [ 3389132 ]
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Marek Radochonski (Inactive) made changes -
            Description Original: {panel:title=Atlassian Status as of 27 April 2011|borderStyle=solid|borderColor=#3C78B5| titleBGColor=#3C78B5| bgColor=#E7F4FA}

            Hi folks,
             
            Thanks for your feedback and continued support. We wanted to give you an update on the status of this issue.

            Over the medium term, the direction we're taking with Crowd is to focus on scalability, reliability and performance. Exciting development has occurred and is going to continue within this space. This feature is a strong candidate for a future release. We can't promise a specific release, but we'll update the issue when we have more concrete information.
             
            Regards,
            Eugene Mak
            Atlassian Product Management

            {panel}
            New: {panel:title=Atlassian Update - 18 August 2017|borderStyle=solid|borderColor=#3c78b5|titleBGColor=#3c78b5|bgColor=#e7f4fa}
            Hi everyone,

            Thanks for all your votes and comments on this suggestion. Your voice means a lot to us.

            We're excited to announce that from now on clustering is officially supported and available for everyone in [Crowd Data Center|https://www.atlassian.com/software/crowd/enterprise/data-center].

            This is the newest addition to Atlassian's Data Center family, which brings you high availability and uninterrupted access as well as all the features of Crowd Server.

            Crowd DC is also great at scaling – you can easily expand your DC with extra nodes that will pull all the necessary configuration from the shared file system, and join the cluster without any extra setup.

            Crowd Data Center is delivered in the [Crowd 3.0 release|https://confluence.atlassian.com/crowd/crowd-3-0-release-notes-934719586.html] together with support for Microsoft Azure Active Directory.

            We highly recommend you to upgrade your current Crowd version to the latest one. In case if you will require any help or assistance in setting up Crowd Data Center or have further questions please don't hesitate to get in touch with me directly at [mailto:mradochonski@atlassian.com]

            Please read the [upgrade notes|https://confluence.atlassian.com/crowd/crowd-3-0-upgrade-notes-905088628.html] for important information about this release before installing the newest version.

            To learn more about Crowd Data Center, check out our [technical documentation|https://confluence.atlassian.com/enterprise/crowd-data-center-933084126.html], [technical FAQ|https://confluence.atlassian.com/enterprise/crowd-data-center-faq-933092399.html], and [licensing FAQ|https://www.atlassian.com/licensing/crowd].

            You can download Crowd 3.0 from [here|https://www.atlassian.com/software/crowd/download?_ga=2.208081878.591644698.1502852955-2041459945.1501489427].

            If you are ready to get started then [get a Crowd Data Center license|https://www.atlassian.com/purchase/product/crowd.data-center], or [try it out for free|https://my.atlassian.com/license/evaluation].

            Thanks,

            Marek Radochonski

            Senior Product Manager, Crowd

            [mailto:mradochonski@atlassian.com]
            {panel}




            {panel:title=Atlassian Status as of 27 April 2011|borderStyle=solid|borderColor=#3c78b5|titleBGColor=#3c78b5|bgColor=#e7f4fa}
            Hi folks,

            Thanks for your feedback and continued support. We wanted to give you an update on the status of this issue.

            Over the medium term, the direction we're taking with Crowd is to focus on scalability, reliability and performance. Exciting development has occurred and is going to continue within this space. This feature is a strong candidate for a future release. We can't promise a specific release, but we'll update the issue when we have more concrete information.

            Regards,
            Eugene Mak
            Atlassian Product Management
            {panel}
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 273640 ] New: Simplified Crowd Development Workflow v2 [ 1392396 ]
            joe made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 104909 ]

            Helen,

            Can we have have any visibility into why Atlasssian has decided to not explore this bit of functionality? It is too technically challenging? Do you not have the resources you require to write a high availability application?

            The document you point to from one of your certified expert partners says it it possible and details the steps to approximate a high availability version of Crowd. It seems strange that out of one side of your mouth you are pointing to a solution from an organization under the Atlasssian umbrella and with the other you are saying that it is not a priority.

            It is great that you are looking to provide tighter integrations with your other products, but this is of little solace when your single monolithic Crowd instance tanks and now your 20,000 users can't log in. This message makes it seem that Atlassian is glibly accepting of the fact they are building software with single points of failure. Not only that there is no visibility into WHY this decision is being made. High availably applications are hardly a new technology. Why is Atlassian purposely deciding to build non scalable software?

            Daniel Borcherding added a comment - Helen, Can we have have any visibility into why Atlasssian has decided to not explore this bit of functionality? It is too technically challenging? Do you not have the resources you require to write a high availability application? The document you point to from one of your certified expert partners says it it possible and details the steps to approximate a high availability version of Crowd. It seems strange that out of one side of your mouth you are pointing to a solution from an organization under the Atlasssian umbrella and with the other you are saying that it is not a priority. It is great that you are looking to provide tighter integrations with your other products, but this is of little solace when your single monolithic Crowd instance tanks and now your 20,000 users can't log in. This message makes it seem that Atlassian is glibly accepting of the fact they are building software with single points of failure. Not only that there is no visibility into WHY this decision is being made. High availably applications are hardly a new technology. Why is Atlassian purposely deciding to build non scalable software?
            Helen Hung (Inactive) made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]
            Helen Hung (Inactive) made changes -
            Link New: This issue is blocked by CWD-1053 [ CWD-1053 ]

            Helen Hung (Inactive) added a comment - - edited

            Hi everyone,
            Thank you for your votes and comments over the years on this documentation request.

            Ideally we would like to be able to meet everyone's requirements and needs for Crowd, but the reality is that this is not always possible. Unfortunately, this is one of those cases, particularly since we don't provide support for Crowd clustering.

            Closing issues that have a fair share of votes and comments is not an easy decision to make. However given that this has been open for several years now and we don't have any foreseeable plans to implement this, we've decided to make this clear so you know sooner rather than later.

            If you'd like to read more information and discussion of Crowd clustering, have a look at https://jira.atlassian.com/browse/CWD-1053

            If you have any questions, feel free to leave a comment or contact me on helen@atlassian.com

            Cheers,
            Helen Hung
            Atlassian Product Management

            Helen Hung (Inactive) added a comment - - edited Hi everyone, Thank you for your votes and comments over the years on this documentation request. Ideally we would like to be able to meet everyone's requirements and needs for Crowd, but the reality is that this is not always possible. Unfortunately, this is one of those cases, particularly since we don't provide support for Crowd clustering. Closing issues that have a fair share of votes and comments is not an easy decision to make. However given that this has been open for several years now and we don't have any foreseeable plans to implement this, we've decided to make this clear so you know sooner rather than later. If you'd like to read more information and discussion of Crowd clustering, have a look at https://jira.atlassian.com/browse/CWD-1053 If you have any questions, feel free to leave a comment or contact me on helen@atlassian.com Cheers, Helen Hung Atlassian Product Management

            Hi Caspar,

            We're running around in circles here. I found all of these links before plus some slides. And that's it.

            There is no documentation currently online (read: indexed by google.com or archive.org), besides what's in CWD-2925, on the actual tweaks needed, e.g., to enable Tomcat Clustering and actual session replication (using the <distributable /> tag in web.xml). And possibly additional tweaks necessary for Hibernate. I've actually managed to get session replication to work now, and according to our tests it seems to work with and without sticky routes on the reverse-proxies, so that is good. However, what I would like is to check with the old "documentation" there was, whether I've missed anything.

            Your first two links give no configuration details, just a high level overview. That's for management. I'm a system administrator and already got beyond the point where I'm drawing pretty diagrams. I'm testing it in the field.

            Regarding Crowd load-balancing and Load balancing Crowd on Atlassian Answers are the only threads on that subject and they both link back to the original forum post as:

            For the benefit of everyone else, I'm going to post an update to CWD-2925 with what we have so far and maybe to kick off the discussion again.

            Uwe Stuehler added a comment - Hi Caspar, We're running around in circles here. I found all of these links before plus some slides . And that's it . There is no documentation currently online (read: indexed by google.com or archive.org), besides what's in CWD-2925 , on the actual tweaks needed, e.g., to enable Tomcat Clustering and actual session replication (using the <distributable /> tag in web.xml ). And possibly additional tweaks necessary for Hibernate. I've actually managed to get session replication to work now, and according to our tests it seems to work with and without sticky routes on the reverse-proxies, so that is good. However, what I would like is to check with the old "documentation" there was, whether I've missed anything. Your first two links give no configuration details, just a high level overview. That's for management. I'm a system administrator and already got beyond the point where I'm drawing pretty diagrams. I'm testing it in the field. Regarding Crowd load-balancing and Load balancing Crowd on Atlassian Answers are the only threads on that subject and they both link back to the original forum post as: 'Actual' current documentation: http://forums.atlassian.com/thread.jspa?forumID=104&threadID=25359 For the benefit of everyone else, I'm going to post an update to CWD-2925 with what we have so far and maybe to kick off the discussion again.

              Unassigned Unassigned
              justen.stepka@atlassian.com Justen Stepka [Atlassian]
              Votes:
              23 Vote for this issue
              Watchers:
              19 Start watching this issue

                Created:
                Updated:
                Resolved: