Skip to content

Conversation

@mbhaskar
Copy link
Member

@mbhaskar mbhaskar commented Oct 22, 2019

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

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
@mbhaskar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@mbhaskar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

Copy link
Member

@kushagraThapar kushagraThapar left a 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 :)

@mbhaskar mbhaskar changed the title Porting reactor netty changes from v3 to v4 Porting reactor netty changes, NPE and minor fixes from v3 to v4 Oct 22, 2019
@mbhaskar
Copy link
Member Author

/azp run java - cosmos - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@kushagraThapar kushagraThapar merged commit b0e0c2e into Azure:feature/cosmos/v4 Oct 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants