Reacquire shadow disk to read-only after changed to ready with long timeout #2764
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
drbasic
added
the
blockstore
drbasic
force-pushed
the
users/drbasic/reacquire-after-ready-with-long-timeout
branch
from
da24f35 to
e9ed27f
Compare
|
Завел тикет на flaky test test_resize_device ydb output: |
|
Note This is an automated comment that will be appended during run. 🔴 linux-x86_64-relwithdebinfo: some tests FAILED for commit e9ed27f.
🟢 linux-x86_64-relwithdebinfo: all tests PASSED for commit e9ed27f.
|
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.
Обнаружил проблему: после перехода теневого диска в состояние Ready мы производили перезахват диска, но использовали короткий таймаут, как будто записи на основной диск заблокированы. Однако это не так и нужно использовать длинный таймаут.