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
fix: lost messages when clickhouse closes while sending messages #10997
Merged
kjellwinblad
merged 3 commits into
emqx:release-51
from
kjellwinblad:kjell/fix/clickhouse_lost_messages/EMQX-10217
Jun 9, 2023
Merged
fix: lost messages when clickhouse closes while sending messages #10997
kjellwinblad
merged 3 commits into
emqx:release-51
from
kjellwinblad:kjell/fix/clickhouse_lost_messages/EMQX-10217
Jun 9, 2023
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
thalesmg
approved these changes
Jun 9, 2023
sstrigler
reviewed
Jun 9, 2023
{error, {closed, PartialBody}} -> | ||
{error, {recoverable_error, {closed_partial_body, PartialBody}}}; | ||
{error, disconnected} -> | ||
{error, {recoverable_error, disconnected}}; | ||
_ -> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
case is_recoverable_error(ClickhouseErrorResult) of
true ->
to_recoverable_error(ClickHouseErrorResult):
false ->
{error, ClickhouseErrorResult} // not sure, but doesn't that end up as a double wrapped error?
end.
is_recoverable_error({error, Reason}) ->
is_recoverable_error_reason(Reason).
is_recoverable_error_reason(...) ->
// fill in all clauses from above
true;
is_recoverable_error_reason(_) ->
false.
to_recoverable_error({error, Reason}) ->
{error, {recoverable_error, Reason}}.
#nit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Fixed in commit below
Bug Fixes
|
修复
|
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.
I think this can be merged without test case so that it gets into the 5.1 release. I can create a follow up PR with a test case.
Fixes:
https://emqx.atlassian.net/browse/EMQX-10217
Summary
🤖 Generated by Copilot at 61488ec
Improve error handling in
emqx_bridge_clickhouse_connector.erl
by distinguishing recoverable and fatal errors when sending queries to clickhouse. Add a TODO comment for future improvement.PR Checklist
Please convert it to a draft if any of the following conditions are not met. Reviewers may skip over until all the items are checked:
changes/{ce,ee}/(feat|perf|fix)-<PR-id>.en.md
files