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
Do not mark file for distributed send as broken on EOF #19290
Merged
alexey-milovidov
merged 2 commits into
ClickHouse:master
from
azat:dist-broken-on-EOF-fix
Jan 21, 2021
Merged
Do not mark file for distributed send as broken on EOF #19290
alexey-milovidov
merged 2 commits into
ClickHouse:master
from
azat:dist-broken-on-EOF-fix
Jan 21, 2021
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
robot-clickhouse
added
the
pr-bugfix
Pull request with bugfix, not backported by default
label
Jan 19, 2021
Ok, I see them now (tons of |
- the sender will got ATTEMPT_TO_READ_AFTER_EOF (added in 946c275) when the client just go away, i.e. server had been restarted, and this is incorrect to mark the file as broken in this case. - since ClickHouse#18853 the file will be checked on the sender locally, and in case the file was truncated CANNOT_READ_ALL_DATA will be thrown. But before ClickHouse#18853 the sender will not receive ATTEMPT_TO_READ_AFTER_EOF from the client in case of file was truncated on the sender, since the client will just wait for more data, IOW just hang. - and I don't see how ATTEMPT_TO_READ_AFTER_EOF can be received while reading local file.
azat
force-pushed
the
dist-broken-on-EOF-fix
branch
from
January 19, 2021 22:11
d106c59
to
8a00816
Compare
alexey-milovidov
approved these changes
Jan 21, 2021
|
This was referenced Jan 21, 2021
vitlibar
pushed a commit
that referenced
this pull request
Feb 1, 2021
…94f500ff2ed55f45936f65a16c224c Cherry pick #19290 to 20.12: Do not mark file for distributed send as broken on EOF
vitlibar
pushed a commit
that referenced
this pull request
Feb 1, 2021
…94f500ff2ed55f45936f65a16c224c Cherry pick #19290 to 20.11: Do not mark file for distributed send as broken on EOF
vitlibar
pushed a commit
that referenced
this pull request
Feb 1, 2021
…4f500ff2ed55f45936f65a16c224c Cherry pick #19290 to 21.1: Do not mark file for distributed send as broken on EOF
robot-clickhouse
pushed a commit
that referenced
this pull request
Feb 17, 2021
This was referenced Feb 17, 2021
robot-clickhouse
pushed a commit
that referenced
this pull request
Feb 17, 2021
This was referenced Feb 17, 2021
robot-clickhouse
pushed a commit
that referenced
this pull request
Feb 17, 2021
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.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Do not mark file for distributed send as broken on EOF
Detailed description / Documentation draft:
ATTEMPT_TO_READ_AFTER_EOF should not be ignored if we receive it from remote (receiver), since:
i.e. server had been restarted
if there is something wrong with the file itself, we will receive
ATTEMPT_TO_READ_AFTER_EOF not from the remote at first
and mark batch as broken.
Cc: @alexey-milovidov (maybe you have some details on why
ATTEMPT_TO_READ_AFTER_EOF
has been added?)