Skip to content

Conversation

@SteNicholas
Copy link
Member

@SteNicholas SteNicholas commented Apr 19, 2024

What changes were proposed in this pull request?

TransportClientFactory should regard as zero for negative celeborn.<module>.io.connectTimeout and celeborn.<module>.io.connectionTimeout.

Why are the changes needed?

When celeborn.<module>.io.connectionTimeout is 0 that means unlimited to netty, ChannelFuture.await(0) fails directly and inappropriately. Meanwhile, whhen celeborn.<module>.io.connectionTimeout is less than 0 that causes meaningless transport client reconnections and endless reconstructions.

Backport:

Does this PR introduce any user-facing change?

No.

How was this patch tested?

TransportClientFactorySuiteJ#unlimitedConnectAndConnectionTimeouts

…tive celeborn.<module>.io.connectTimeout/connectionTimeout
Copy link
Member

@yaooqinn yaooqinn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@FMX FMX left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Merged into main(v0.5.0).

@FMX FMX closed this in 8e4ddaa Apr 19, 2024
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.

4 participants