We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
1 parent d50098f commit da70387Copy full SHA for da70387
1 file changed
api/src/main/java/io/grpc/ManagedChannelBuilder.java
@@ -374,9 +374,17 @@ public T maxInboundMetadataSize(int bytes) {
374
* notice when they are causing excessive load. Clients are strongly encouraged to use only as
375
* small of a value as necessary.
376
*
377
+ * <p>When the channel implementation supports TCP_USER_TIMEOUT, enabling keepalive will also
378
+ * enable TCP_USER_TIMEOUT for the connection. This requires <em>all</em> sent packets to receive
379
+ * a TCP acknowledgement before the keepalive timeout. The keepalive time is not used for
380
+ * TCP_USER_TIMEOUT, except as a signal to enable the feature. grpc-netty supports
381
+ * TCP_USER_TIMEOUT on Linux platforms supported by netty-transport-native-epoll.
382
+ *
383
* @throws UnsupportedOperationException if unsupported
384
* @see <a href="https://github.com/grpc/proposal/blob/master/A8-client-side-keepalive.md">gRFC A8
385
* Client-side Keepalive</a>
386
+ * @see <a href="https://github.com/grpc/proposal/blob/master/A18-tcp-user-timeout.md">gRFC A18
387
+ * TCP User Timeout</a>
388
* @since 1.7.0
389
*/
390
public T keepAliveTime(long keepAliveTime, TimeUnit timeUnit) {
@@ -393,6 +401,8 @@ public T keepAliveTime(long keepAliveTime, TimeUnit timeUnit) {
393
401
394
402
395
403
404
405
396
406
397
407
398
408
public T keepAliveTimeout(long keepAliveTimeout, TimeUnit timeUnit) {
0 commit comments