8000 Clarify space partitioning due to multi-node by k-rus · Pull Request #564 · timescale/docs.timescale.com-content · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Clarify space partitioning due to multi-node #564

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 8000 . We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 28, 2020
Merged

Clarify space partitioning due to multi-node #564

merged 1 commit into from
Oct 28, 2020

Conversation

k-rus
Copy link
Contributor
@k-rus k-rus commented Oct 27, 2020

Space partitioning is rare case for non-distributed hypertables, but is
important for multi-node to be effective. This commit clarifies this.

@k-rus k-rus added multinode Multinode-related content add-to-branches PRs that need to be added to version branches 2.0 labels Oct 27, 2020
@k-rus k-rus requested review from mfreed, pmwkaa and WireBaron October 27, 2020 12:56
@mfreed mfreed changed the title Clarify space partitioning due to mulitnode Clarify space partitioning due to multi-node Oct 27, 2020
@k-rus k-rus requested a review from mfreed October 28, 2020 08:48
api.md Outdated
**Space partitions**: Using space partitions is highly recommended
for [distributed hypertables](#create_distributed_hypertable) to achieve
efficient scale-out performance. For [regular hypertables](#create_hypertable)
that exist only a single node, the use of additional partitioning is a
Copy link
Contributor

Choose a reason for hiding this comment

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

only on a?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I improved this place.

across multiple disks within the same time interval
(in the case of single-node deployments).

### Parallelizing queries across multiple data nodes [](add_dimension-multi_node)
Copy link
Contributor

Choose a reason for hiding this comment

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

Curious if we should move this sections somewhere else, like performance or optimization

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I suggest to discuss and consider this outside this PR.

Space partitioning is rare case for non-distributed hypertables, but is
important for multi-node to be effective. This commit clarifies this.
@k-rus k-rus merged commit 62fabab into timescale:master Oct 28, 2020
@k-rus k-rus deleted the space-partition-warning branch October 29, 2020 06:55
@solugebefola solugebefola added added-to-branches and removed add-to-branches PRs that need to be added to version branches labels Oct 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.0 added-to-branches multinode Multinode-related content
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
0