[GitHub] [incubator-iotdb] Ring-k removed a comment on pull request #1526: Separate read and write configurations

[GitBox]

Ring-k removed a comment on pull request #1526:
URL: https://github.com/apache/incubator-iotdb/pull/1526#issuecomment-661132896


   > > These two configurations are thresholds for read and write requests from 
user's view. When it reaches the threshold, the execution should terminate and 
the user should be informed. What this pull request do is to separate the read 
and write constraints from `connection_timeout_ms` to improve flexibility of 
the configurations.
   > 
   > In async mode, it seems that there are more places which should be 
controlled by these configurations.Such as a raft broadcast in 
`sendLogToFollowers`,please make some checks to cover all~
   > 
![image](https://user-images.githubusercontent.com/32640567/87954491-05ad9080-cadf-11ea-9c61-44217ca525e0.png)
   > In sync mode,how are you going to apply these configurations?
   
   I see. But the `connection_time_ms` is not totally replaced by 
`write_operation_timeout_ms` and `read_operation_timeout_ms`.  It is still used 
in heartbeat among nodes, or async mode. Is it really necessary to separate 
read and write there?


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org