Hi, Apache Thrift Community We Apache IoTDB Team encounter this problem( https://issues.apache.org/jira/browse/THRIFT-4847, https://issues.apache.org/jira/browse/THRIFT-5230)，and this problem makes the node unable to accept any more communication, which has a serious impact.
In fact, from my point of view, for TThreadedSelectorServer, even idling the selector thread consuming CPU is better than currently providing an unstable fix that could cause the selector thread to die entirely. We need to discuss how to improve this jvmbug fix, or maybe it's better not to do the rebuildSelector fix. For the above reasons, we will temporarily replace all servers of IoTDB with THsHaServer or TThreadPoolServer without the rebuildSelector function in TThreadedSelectorServer. The community contributor mrcjkb has currently submitted a PR. We look forward to working together to get this PR merged. Developers who are familiar with this area, please take some time to review the PR ( https://github.com/apache/thrift/pull/3010). Thank you very much! Best ------------------- Xinyu Tan Apache IoTDB PMC
