Hipchat Data Center FAQs

You've got questions, we've got answers!

このページの内容

Hipchat Data Center end of life

Atlassian is no longer offering team communications products to our customers. We have discontinued Hipchat Cloud, Hipchat Data Center, Hipchat Server, and Stride. You can learn about our new partnership with Slack at https://www.atlassian.com/partnerships/slack

If you have an active Hipchat Server or Hipchat Data Center license, you can continue to use Hipchat until the license expires or until the EOL dates below. 

You will not be able to renew any HipChat license past July 26th, 2019 since the product is being discontinued.


  • Hipchat Data Center (v3.0): June 22nd, 2019
  • Hipchat Data Center (v3.1): September 26th, 2019
  • Hipchat Server (v2.4): June 30th, 2020

Architecture and requirements

What changed with the launch of Hipchat Data Center? What new things do I need to deploy?

Hipchat Data Center does not ship as an appliance with data stores included. Instead, Hipchat Data Center ships as a VMWare image or AWS AMI with externalized data stores that you must deploy yourself. You will now bring your own database, data stores, and load balancer for both an AWS deployment and a VMWare deployment.

Check out the new Hipchat Data Center architecture, the Deployment options and sizing guidelines, and read more about Migrating from Hipchat Server to Hipchat Data Center.

When should I run Hipchat Data Center with multiple nodes?

If your Hipchat instance serves 1000 or more users, we highly recommend running on a three-node cluster for performance reasons. If the cluster serves 2000 or more users, you must run a three node cluster to support that scale.

See the Deployment options and sizing guidelines for Hipchat Data Center for more details.

Do I really need to deploy three nodes? Why not just two?

If you have enough users in your deployment that you need more than one node, you need a total of three nodes.

If you were to only deploy two nodes for a medium or large deployment, it would give you a false sense of security. If a single node in a two-node cluster fails, the remaining node would immediately be overwhelmed with traffic.

With a three-node cluster one node can fail and the remaining two can continue operating, even if their performance is reduced.

Do I really need a load balancer in my deployment? What if I only have one Hipchat node?

Hipchat Data Center assumes that it is installed on a secure private network, such as a VPC. Clients access Hipchat node(s) through a service which terminates SSL, regardless of deployment scale.

In an Enterprise-scale deployment this service is a load balancer, which distributes client connections among the Hipchat nodes. In a small-scale deployment all connections go to a single Hipchat node, so this service can be just a reverse proxy.

Several services (such as NGINX or Apache) can function as both a load balancer and a reverse proxy. If you use one of these for your small-scale deployment, you can quickly scale it up later by adding more Hipchat nodes.

Which AWS regions do you support?

We currently publish our AWS AMIs to the following regions:

  • eu-west-1 (Ireland)
  • eu-central-1 (Frankfurt)
  • us-east-1 (N. Virginia)
  • us-west-2 (Oregon)
  • ap-southeast-2 (Sydney)

Additional regions may be added later as support for EFS grows.

Why are there so few supported AWS regions?

For high-availability purposes, we limit Hipchat Data Center to only regions with three Availability Zones (or AZs) that also support all of the components required by the cluster. At this time, EFS is often the missing component.

When you use our AWS CloudFormation template to deploy an Enterprise scale Hipchat Data Center cluster, AWS deploys one Hipchat node to each AZ. This ensures high availability within your AWS region.

How many users does Hipchat Data Center support?Hipchat Data Center supports up to 20,000 named users and 10,000 concurrent active users.
What happens when the 10,001 concurrent user logs in?Users can continue to login, but you may experience performance issues.
How do I migrate to Hipchat Data Center if I have multiple Hipchat Server instances?We do not support consolidation of instances. You can connect to external user directories to make sure all the right users have access to Hipchat Data Center.

Support and timelines

Is Hipchat Data Center still supported?

Atlassian is no longer offering team communications products to our customers. We have discontinued Hipchat Cloud, Hipchat Data Center, Hipchat Server, and Stride. You can learn about our new partnership with Slack at https://www.atlassian.com/partnerships/slack

If you have an active Hipchat Server or Hipchat Data Center license, you can continue to use Hipchat until the license expires or until the EOL dates below. 

You will not be able to renew any HipChat license past July 26th, 2019 since the product is being discontinued.


  • Hipchat Data Center (v3.0): June 22nd, 2019
  • Hipchat Data Center (v3.1): September 26th, 2019
  • Hipchat Server (v2.1): December 8th, 2018
  • Hipchat Server(v2.2): May 30th, 2019 
  • Hipchat Server (v2.4): June 30th, 2020
What is the Hipchat Server EOL policy?Check out the Atlassian End of Life policy here.

What happens if I didn't transition to Hipchat Data Center?

We will support the Hipchat Server appliance model according to the rules in our end of life policy. During this support period, you'll only have access to critical security releases.

Is the support policy changing?

No, our support policy is not changing.

We will support Hipchat Data Center and Hipchat Server until the end of life date for each version as per the end-of-life policy.

ライセンス

You will not be able to renew any HipChat license past July 26th, 2019 since the product is being discontinued.


For licensing questions, see the FAQ at https://www.atlassian.com/partnerships/slack/faq


最終更新日 2019 年 7 月 26 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.