-
Notifications
You must be signed in to change notification settings - Fork 218
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
In the CassandraStorage, remove repair run table scans #105
Merged
michaelsembwever
merged 0 commits into
mck/cassandra-improvements-94
from
mck/cassandra-remove-repair-run-table-scans
Jun 1, 2017
Merged
In the CassandraStorage, remove repair run table scans #105
michaelsembwever
merged 0 commits into
mck/cassandra-improvements-94
from
mck/cassandra-remove-repair-run-table-scans
Jun 1, 2017
Conversation
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
michaelsembwever
force-pushed
the
mck/cassandra-remove-repair-run-table-scans
branch
from
May 26, 2017 04:58
64315d0
to
791c6a8
Compare
michaelsembwever
added a commit
that referenced
this pull request
May 26, 2017
…nc break-down of per cluster run-throughs of known run IDs. ref: #105
return repairRuns; | ||
return getClusters().stream() | ||
// Grab all ids for the given cluster name | ||
.map((cluster) -> getRepairRunIdsForCluster(cluster.getName())) |
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.
// Grab repair runs asynchronously for all the ids returned by the index table | ||
.flatMap((Collection<UUID> repairRunIds) | ||
-> repairRunIds.stream() | ||
.map((repairRunId) -> session.executeAsync(getRepairRunPrepStmt.bind(repairRunId)))) |
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.
michaelsembwever
force-pushed
the
mck/cassandra-remove-batch-statements
branch
from
May 28, 2017 05:25
b49248e
to
9e26043
Compare
michaelsembwever
force-pushed
the
mck/cassandra-remove-repair-run-table-scans
branch
from
May 28, 2017 05:26
791c6a8
to
34a48f5
Compare
michaelsembwever
added a commit
that referenced
this pull request
May 28, 2017
…nc break-down of per cluster run-throughs of known run IDs. ref: #105
michaelsembwever
force-pushed
the
mck/cassandra-remove-batch-statements
branch
from
June 1, 2017 03:36
9e26043
to
4441ea7
Compare
michaelsembwever
changed the base branch from
mck/cassandra-remove-batch-statements
to
mck/cassandra-improvements-94
June 1, 2017 06:58
michaelsembwever
force-pushed
the
mck/cassandra-remove-repair-run-table-scans
branch
from
June 1, 2017 07:52
34a48f5
to
10f0e6b
Compare
michaelsembwever
added a commit
that referenced
this pull request
Jun 1, 2017
…nc break-down of per cluster run-throughs of known run IDs. ref: #105
michaelsembwever
force-pushed
the
mck/cassandra-remove-repair-run-table-scans
branch
from
June 1, 2017 07:55
10f0e6b
to
3cf5733
Compare
michaelsembwever
force-pushed
the
mck/cassandra-improvements-94
branch
from
June 1, 2017 09:22
f2e57ce
to
3cf5733
Compare
adejanovski
added a commit
that referenced
this pull request
Jun 1, 2017
* Cassandra performance: Replace sequence ids with time-based UUIDs Makes the schema changes in a separate migration step, so that data in the repair_unit and repair_schedule tables can be migrated over. ref: - #99 - #94 - #99 (comment) * Simplify the creation of repair runs and their segments. Repair runs and their segments are one unit of work in concept and the persistence layer should be designed accordingly. Previous they were separated because the concern of sequence generation for IDs were exposed in the code. This is now encapsulated within storage implementations. This work allows the CassandraStorage to implement segments as clustering keys within the repair_run table. ref: - #94 - #101 * In CassandraStorage implement segments as clustering keys within the repair_run table. Change required in IStorage so to identify a segment both by runId and segmentId. ref: - #94 - #102 * Fix number of parallel repair computation Downgrade to Dropwizard 1.0.7 and Guava 19.0 to fix dependency issues Make repair manager schedule cycle configurable (was 30s hardcoded) ref: #108 * In CassandraStorage replace the table scan on `repair_run` with a async break-down of per cluster run-throughs of known run IDs. ref: #105
adejanovski
pushed a commit
that referenced
this pull request
Jun 26, 2017
…nc break-down of per cluster run-throughs of known run IDs. ref: #105
michaelsembwever
pushed a commit
that referenced
this pull request
Jun 27, 2017
* Cassandra performance: Replace sequence ids with time-based UUIDs Makes the schema changes in a separate migration step, so that data in the repair_unit and repair_schedule tables can be migrated over. ref: - #99 - #94 - #99 (comment) * Simplify the creation of repair runs and their segments. Repair runs and their segments are one unit of work in concept and the persistence layer should be designed accordingly. Previous they were separated because the concern of sequence generation for IDs were exposed in the code. This is now encapsulated within storage implementations. This work allows the CassandraStorage to implement segments as clustering keys within the repair_run table. ref: - #94 - #101 * In CassandraStorage implement segments as clustering keys within the repair_run table. Change required in IStorage so to identify a segment both by runId and segmentId. ref: - #94 - #102 * Fix number of parallel repair computation Downgrade to Dropwizard 1.0.7 and Guava 19.0 to fix dependency issues Make repair manager schedule cycle configurable (was 30s hardcoded) ref: #108 * In CassandraStorage replace the table scan on `repair_run` with a async break-down of per cluster run-throughs of known run IDs. ref: #105
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In CassandraStorage replace the table scan on
repair_run
with a async break-down of per cluster run-throughs of known run IDs.