-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Porting reactor netty changes, NPE and minor fixes from v3 to v4 #5989
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
Porting reactor netty changes, NPE and minor fixes from v3 to v4 #5989
Conversation
Used Reactor-Core and Reactor-Netty latest release. New TCP Configurations with idle connection timeout, connect timeout, connection keep alive, etc. Used Reactor-Netty's response APIs to convert Flux / Mono to Flux / Mono
|
/azp run java - cosmos - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Port of: Azure#5804
|
/azp run java - cosmos - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
kushagraThapar
left a comment
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.
Thank you for porting these two changes.
I have added two comments, please make sure to change them the max_connection_pool_size everywhere to 1000. I missed that change in my reactor netty PR so had to do it later, but we can fix it here :)
sdk/cosmos/azure-cosmos/src/main/java/com/azure/data/cosmos/internal/Configs.java
Outdated
Show resolved
Hide resolved
...smos/azure-cosmos-benchmark/src/main/java/com/azure/data/cosmos/benchmark/Configuration.java
Outdated
Show resolved
Hide resolved
|
/azp run java - cosmos - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Ported reactor netty and NPE fixes from V3
Reactor netty port
ported from: #5185
NPE port:
ported from: #5804
Merge issues and unused imports:
ported from: #5862