-
Notifications
You must be signed in to change notification settings - Fork 87
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
Changes from 7 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
cdb6e49
First draft on TSDB 2.3 and PG 11 deprecation.
4257e3e
Merge branch 'latest' into timescaledb-2.3-release-notes
5da1dfa
Update timescaledb/overview/release-notes/index.md
d6ed99a
Update timescaledb/overview/release-notes/index.md
41484e7
Update timescaledb/overview/release-notes/index.md
8ffa13d
Update timescaledb/overview/release-notes/index.md
2aa88d7
Update timescaledb/overview/release-notes/index.md
62c1eef
Update timescaledb/overview/release-notes/index.md
fc8dd03
Update timescaledb/overview/release-notes/index.md
8b2fe42
Apply suggestions from code review
5b8d547
Merge branch 'latest' into timescaledb-2.3-release-notes
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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".