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

QLTransactionTest.RemoteBootstrap fails in master #2428

spolitov opened this issue Sep 25, 2019 · 0 comments

QLTransactionTest.RemoteBootstrap fails in master #2428

spolitov opened this issue Sep 25, 2019 · 0 comments


Copy link

@spolitov spolitov commented Sep 25, 2019

No description provided.

@spolitov spolitov added the area/docdb label Sep 25, 2019
@spolitov spolitov self-assigned this Sep 25, 2019
@spolitov spolitov added this to To Do in YBase features via automation Sep 25, 2019
spolitov added a commit that referenced this issue Sep 27, 2019
There are 3 issues with QLTransactionTest.RemoteBootstrap test:
1) When remote shutdown happens concurrently with remote bootstrap, it could hang on
   waiting for a tablet peer to shut down.
   Fixed by avoiding wait in remote bootstrap when tablet has already been shut down.
2) Concurrent access to FLAGS_log_min_seconds_to_retain.
   Fixed by moving assignment to test setup.
3) Catalog manager could ignore information about tablet leader.
   If new leader was in starting state, update where it became leader is ignored by catalog manager.
   Fixed by changing update logic.

Test Plan: ybd debug --gtest_filter QLTransactionTest.RemoteBootstrap -n 100

Reviewers: mikhail, hector

Reviewed By: hector

Subscribers: ybase, bogdan

Differential Revision:
@bmatican bmatican moved this from To Do to In progress in YBase features Oct 8, 2019
@spolitov spolitov closed this Oct 12, 2019
YBase features automation moved this from In progress to Done Oct 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
1 participant
You can’t perform that action at this time.