forked from facebook/mcrouter
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Introduce cmake #2
Closed
Closed
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
mszabo-wikia
force-pushed
the
introduce-cmake
branch
4 times, most recently
from
July 29, 2024 00:19
04d0531
to
a290cd6
Compare
Summary: [Mcrouter] Migrate `dynamic_cast`s from `TAsyncSSLSocket` to `folly::AsyncSSLSocket`. Reviewed By: Gownta Differential Revision: D22118708 fbshipit-source-id: 8e68ab24df7d26703d253c478999b6741134cd51
mszabo-wikia
force-pushed
the
introduce-cmake
branch
from
July 30, 2024 01:02
a290cd6
to
2eaecd4
Compare
Summary: Move McRateLimitedLogger and McConnectionLoggerBase to ucache dir and rename. Resolve build failures. Reviewed By: stuclar Differential Revision: D60397635 fbshipit-source-id: 51537466989c89cd9035843f5d428f2a3d26bc62
mszabo-wikia
force-pushed
the
introduce-cmake
branch
3 times, most recently
from
July 31, 2024 14:13
90964da
to
92cb3bd
Compare
mszabo-wikia
force-pushed
the
introduce-cmake
branch
from
July 31, 2024 15:56
92cb3bd
to
4d2a569
Compare
mszabo-wikia
pushed a commit
that referenced
this pull request
Dec 4, 2024
Summary: McRouter leaks the client instance if it encounters errors, like config failure, SMC unavailability, etc. This has caused [some issues](https://fb.workplace.com/groups/604299349618684/permalink/27403334835955105/) for us over the past year. **This diff:** Moving the client instance to the aux thread, so it can be auto-destructed after its SR dependencies are released. With the [context](https://fb.workplace.com/groups/604299349618684/posts/27403334835955105/?comment_id=27406017052353550&reply_comment_id=27406822342273021) disylh shared, I was curious to see if this approach might work, and what might be the gaps we need to tackle. I followed the discussion on the [previous attempt](https://www.internalfb.com/diff/D44641566?dst_version_fbid=1590697228110996&transaction_fbid=143930055086555) where this was discussed. Iiuc, #1 is addressed now as we manually do the SR deps release before destruction. I didn't quite follow #2, and why clearing the event base would cause the deadlock (maybe it wouldn't anymore, since we destruct from a different thread). But curious to hear opinions! Reviewed By: disylh Differential Revision: D66252318 fbshipit-source-id: 498ea74ab78c6dc0e70b1471a0779551002e27ac
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.
No description provided.