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

cli: Add rangelog info to debug zip #28396

Merged
merged 1 commit into from Aug 9, 2018

Conversation

a-robinson
Copy link
Contributor

Using the rangelog admin server endpoint, which currently grabs the
entire rangelog without an ORDER BY or LIMIT clause due to the
performance reasons outlined in #18159.

Release note (cli change): The file generated by running debug zip
now contains the contents of the system.rangelog table, which is a
record of range splits and rebalances in the cluster.

Using the rangelog admin server endpoint, which currently grabs the
entire rangelog without an ORDER BY or LIMIT clause due to the
performance reasons outlined in cockroachdb#18159.

Release note (cli change): The file generated by running debug zip
now contains the contents of the system.rangelog table, which is a
record of range splits and rebalances in the cluster.
@a-robinson a-robinson requested a review from a team as a code owner August 8, 2018 21:53
@cockroach-teamcity
Copy link
Member

This change is Reviewable

Copy link
Member

@bdarnell bdarnell left a comment

Choose a reason for hiding this comment

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

But #18159 is closed, so can't we use a limit now?

Copy link
Contributor Author

@a-robinson a-robinson left a comment

Choose a reason for hiding this comment

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

The underlying problems haven't been fixed as far as I know. #18159 was closed when we defaulted the admin server endpoint to not use an ORDER BY or LIMIT in (#18376), not because we made the query with ORDER BY and/or LIMIT clauses faster.

The core problems IIRC were reverse scans being much slower than forward scans (#14228), the lack of a column family on the rangelog table (#17901), and the LIMIT clause disabling DistSQL.

@a-robinson
Copy link
Contributor Author

bors r+

craig bot pushed a commit that referenced this pull request Aug 9, 2018
28396: cli: Add rangelog info to debug zip r=a-robinson a=a-robinson

Using the rangelog admin server endpoint, which currently grabs the
entire rangelog without an ORDER BY or LIMIT clause due to the
performance reasons outlined in #18159.

Release note (cli change): The file generated by running debug zip
now contains the contents of the system.rangelog table, which is a
record of range splits and rebalances in the cluster.

Co-authored-by: Alex Robinson <alexdwanerobinson@gmail.com>
@craig
Copy link
Contributor

craig bot commented Aug 9, 2018

Build succeeded

@craig craig bot merged commit 7009897 into cockroachdb:master Aug 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants