Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

First draft on TSDB 2.3 and PG 11 deprecation. #71

Merged
merged 11 commits into from
May 25, 2021
23 changes: 13 additions & 10 deletions timescaledb/overview/release-notes/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,11 +15,11 @@ we welcome you to visit our Github repo or join our [Slack community](https://sl

For our next release, we plan to add:

- Compression policies on distributed hypertables
- Partially mutable compressed chunks to support INSERTs into a compressed hypertable.
- Downgrading between Timescale DB 2.x versions.
- High Availability: Adding nodes to a multinode cluster.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that the next version is focusing on elasticity and specifically rebalancing load when adding new DNs, not high availability?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Draft PR, so WIP. But yes.

Copy link
Contributor Author

@NunoFilipeSantos NunoFilipeSantos May 25, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Acceptance Criteria

A data node can be added to the multi-node cluster
Data is written to the new data node after it is added
Old data/chunks are moved from existing nodes to the new nodes to free up space and immediately make use of the new capacity
(Optional) All the steps can be automated

Tasks

Ability to add a data node to a multi-node cluster
Ability to move chunks to the new data node to make use of it immediately. This need not mean a "balanced" cluster.
A way to find candidate chunks to move. For example, based on number of chunks on a node (move from the node with the most chunks), least disk space, and/or based on recent/old chunks.

Reference: https://github.com/timescale/product/issues/2

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While this functionality is useful for HA, and is part of the larger HA story, it is a bit misleading to label it High Availability for this release. I agree with @mfreed that we should label this "Elasticity".

NunoFilipeSantos marked this conversation as resolved.
Show resolved Hide resolved
- Various bug fixes.

The current GA (Generally Available) version is 2.2.1.
The current GA (Generally Available) version is 2.3.0
NunoFilipeSantos marked this conversation as resolved.
Show resolved Hide resolved

You can read more about our architecture and design for distributed hypertables
[here][distributed-hypertables].
Expand All @@ -33,7 +33,7 @@ functionality works, and, as a result, made APIs simpler and more consistent,
while also empowering users with more control and flexibility to customize
behaviors to suit your needs. Some of these API updates are **breaking changes**.
NunoFilipeSantos marked this conversation as resolved.
Show resolved Hide resolved

### What's new in TimescaleDB 2.2.1:
### What's new in TimescaleDB 2.3.0:

Skip Scan optimization on single node and multinode. This feature offers significant
improvements in performance of `SELECT` queries with `DISTINCT ON`.
Expand All @@ -49,14 +49,14 @@ planning, compression, and policies.

**PostgreSQL 11 deprecation announcement**

Timescale is working hard on our next exciting features. To make that
possible, we require functionality that is unfortunately absent on
PostgreSQL 11. For this reason, we will continue supporting PostgreSQL
11 until mid-June 2021. Sooner to that time, we will announce the
specific version of TimescaleDB in which PostgreSQL 11 support will be removed.
Timescale is working hard on our next exciting features.
To make that possible, we require functionality that is unfortunately absent on
PostgreSQL 11.
NunoFilipeSantos marked this conversation as resolved.
Show resolved Hide resolved
For this reason, Timescale DB 2.3 will be the last version supporting PostgreSQL 11.
From TimescaleDB 2.4 forward we will no longer support PostgreSQL 11.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Timescale is working hard on our next exciting features.
To make that possible, we require functionality that is unfortunately absent on
PostgreSQL 11.
For this reason, Timescale DB 2.3 will be the last version supporting PostgreSQL 11.
From TimescaleDB 2.4 forward we will no longer support PostgreSQL 11.
Timescale is working hard on our next exciting features. To make that
possible, we require functionality that is unfortunately absent on
PostgreSQL 11. For this reason, TimescaleDB 2.3 will be the final
version that supports PostgreSQL 11. TimescaleDB 2.4 will require
PostgreSQL 12 or 13.

NunoFilipeSantos marked this conversation as resolved.
Show resolved Hide resolved

<highlight type="tip">
TimescaleDB 2.2.1 is currently GA, and we encourage
TimescaleDB 2.3 is currently GA, and we encourage
users to upgrade in testing environments to gain experience and provide feedback on
new and updated features.

Expand All @@ -76,6 +76,9 @@ accidentally triggering the load of a previous DB version.**

## Unreleased

## 2.3.0 (2021-05-25)
TBD

NunoFilipeSantos marked this conversation as resolved.
Show resolved Hide resolved
## 2.2.1 (2021-05-05)

This maintenance release contains bugfixes since the 2.2.0 release. We
Expand Down