GH-48637: [C++][FlightRPC] ODBC: Disable absl deadlock detection
#48747
+4
−0
Conversation
This file contains hidden or 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
`absl::SetMutexDeadlockDetectionMode(absl::OnDeadlockCycle::kIgnore);` fixes ODBC deadlock issue. We turn off the detection as the deadlock originated from upstream projects.
|
|
github-actions
bot
added
Component: C++
Component: FlightRPC
awaiting review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Rationale for this change
#48637
Arrow Flight SQL ODBC gets
potential deadlockerror during tests because this error is happening at Arrow Flight SQL (see #48714). Arrow doesn't useabsl::Mutexdirectly, andabsl::Mutexis used by upstream projects gRPC/Protobuf, so Arrow itself likely did not cause the potential deadlock. We can disable the deadlock detection for now.What changes are included in this PR?
absldeadlock detection inside ODBC, so potential deadlock detection from upstream projects don't get picked up in the tests.Are these changes tested?
Are there any user-facing changes?
N/A