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

100T global sort on GCS is slow due to checking old BR object hierarchy #50533

Closed
lance6716 opened this issue Jan 18, 2024 · 2 comments · Fixed by #50534
Closed

100T global sort on GCS is slow due to checking old BR object hierarchy #50533

lance6716 opened this issue Jan 18, 2024 · 2 comments · Fixed by #50534

Comments

@lance6716
Copy link
Contributor

At the beginning of the ingest step
image
image

Don't know how long it will last

@kennytm
Copy link
Contributor

kennytm commented Feb 27, 2024

This check was created to fix pingcap/br#675 for BR v4.0.8. Given our compatibility strategy I think #50534 can be cherry-picked to v6.x.x the earliest?

We've got an issue where the customer using TiCDC v7.5 with GCS as redo log storage got a DeadlineExceeded error because this check takes over 5 minutes in total.

@lance6716
Copy link
Contributor Author

@kennytm I have created the cherry-pick PRs. Please notify the cherry-pick triage role of TiCDC to approve them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants