pan3793 commented on code in PR #3039:
URL: https://github.com/apache/celeborn/pull/3039#discussion_r1899340272


##########
docs/configuration/network.md:
##########
@@ -29,7 +29,7 @@ license: |
 | celeborn.<module>.io.enableVerboseMetrics | false | false | Whether to 
track Netty memory detailed metrics. If true, the detailed metrics of Netty 
PoolByteBufAllocator will be gotten, otherwise only general memory usage will 
be tracked. |  |  | 
 | celeborn.<module>.io.lazyFD | true | false | Whether to initialize 
FileDescriptor lazily or not. If true, file descriptors are created only when 
data is going to be transferred. This can reduce the number of open files. If 
setting <module> to `fetch`, it works for worker fetch server. |  |  | 
 | celeborn.&lt;module&gt;.io.maxRetries | 3 | false | Max number of times we 
will try IO exceptions (such as connection timeouts) per request. If set to 0, 
we will not do any retries. If setting <module> to `data`, it works for shuffle 
client push and fetch data. If setting <module> to `replicate`, it works for 
replicate client of worker replicating data to peer worker. If setting <module> 
to `push`, it works for Flink shuffle client push data. |  |  | 
-| celeborn.&lt;module&gt;.io.mode | EPOLL | false | Netty EventLoopGroup 
backend, available options: NIO, EPOLL. If epoll mode is available, the default 
IO mode is EPOLL; otherwise, the default is NIO. |  |  | 
+| celeborn.&lt;module&gt;.io.mode | NIO | false | Netty EventLoopGroup 
backend, available options: NIO, EPOLL. If epoll mode is available, the default 
IO mode is EPOLL; otherwise, the default is NIO. |  |  | 

Review Comment:
   @SteNicholas could you please change it to optional and explain default 
behavior in desc?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to