You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@iotdb.apache.org by GitBox <gi...@apache.org> on 2022/10/19 03:20:27 UTC

[GitHub] [iotdb] SzyWilliam opened a new pull request, #7655: [IOTDB-4689] Use seperate channel for heartbeat / appendEntries

SzyWilliam opened a new pull request, #7655:
URL: https://github.com/apache/iotdb/pull/7655

   # original design
   Currently, AppendEntries and Heartbeat uses the same gRPC channel.
   Under heavy workloads, AppendEntries with lots of logs will consume a lot of processing time, so the follower may respond to this AppendEntries after a long latency. The leader would consider this long latency abnormal and step down.
   So uses a separate channel can avoid heartbeat being blocked by AppendEntries.
   
   # What's the downside?
   We need two channels which means we have to establish a new http2 connection.


-- 
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: reviews-unsubscribe@iotdb.apache.org

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


[GitHub] [iotdb] JackieTien97 merged pull request #7655: [IOTDB-4689] Use seperate channel for heartbeat / appendEntries

Posted by GitBox <gi...@apache.org>.
JackieTien97 merged PR #7655:
URL: https://github.com/apache/iotdb/pull/7655


-- 
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: reviews-unsubscribe@iotdb.apache.org

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