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

moves finding split points into FATE #4178

Merged
merged 11 commits into from
Feb 21, 2024

Conversation

keith-turner
Copy link
Contributor

  1. Moves finding split points from tablet from a custom thread pool in the manager into FATE. This is done by the new Repo named FindSplits.
  2. Stops tracking what splits are running in manager memory and moves this into FATE. This is not implemented yet, plan to do that in another PR
  3. Stops tracking what tablets are unsplittable in manager memory. This should be tracked in metadata table per Move tracking of unsplittable tablets from manager memory to metadata table #4177. This change can be in its own commit. In this commit the in memory tracking is simply removed.

These changes will reduce manager memory usage. These changes also will make splitting tablets work much better if FATE is distributed for two reasons. First it allows the computation to spread over multiple manager processes. Second it allows tracking of what is splitting to move from memory to persisted storage and not rely on a map in a single process.

This is a WIP commit because it requires FATE changes. The needed FATE changes were stubbed out in this PR and implemented with a in memory set that would need to be persisted.

 1. Moves finding split points from tablet from a custom thread pool in
    the manager into FATE.  This is done by the new Repo named FindSplits.
 2. Stops tracking what splits are running in manager memory and moves
    this into FATE.  This is not implemented yet, plan to do that in
    another PR
 3. Stops tracking what tablets are unsplittable in manager memory. This
    should be tracked in metadata table per apache#4177.  This change can be
    in its own commit.  In this commit the in memory tracking is simply
    removed.

These changes will reduce manager memory usage. These changes also will
make splitting tablets work much better if FATE is distributed for two
reasons.  First it allows the computation to spread over multiple
manager processes.  Second it allows tracking of what is splitting to
move from memory to persisted storage and not rely on a map in a single
process.

This is a WIP commit because it requires FATE changes.  The needed FATE
changes were stubbed out in this PR and implemented with a in memory set
that would need to be persisted.
@keith-turner keith-turner marked this pull request as ready for review February 15, 2024 16:23
@keith-turner keith-turner changed the title WIP moves finding split points into FATE moves finding split points into FATE Feb 16, 2024
Copy link
Contributor

@cshannon cshannon left a comment

Choose a reason for hiding this comment

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

The changes here LGTM. The new FindSplits repo looks idempotent to me (it will just recompute the splits if fails) and I didn't see any other issues with the changes.

@keith-turner keith-turner merged commit 5d8d9cd into apache:elasticity Feb 21, 2024
8 checks passed
@keith-turner keith-turner deleted the find-splits-in-fate branch February 21, 2024 22:37
@ctubbsii ctubbsii added this to the 4.0.0 milestone Jul 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants