You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following phenomena were found in our test environment
Three nodes, one node down, unable to select a leader. We found one of the DLedger nodes cannot process any rpc requests (it is candidate role), and all NettyServerPublicExecutor threads are stuck in the handlePush method
The number of queued tasks is increasing, but the number of completed tasks has not changed
The thread stuck in here, because the blocking queue is already full.
However, since it is a candidate, it will no longer peek data from the blocking queue
The text was updated successfully, but these errors were encountered:
* Fix the issue that DLedger RPC Service thread stuck
* Fix the issue that DLedger RPC Service thread stuck
* Fix the issue that DLedger RPC Service thread stuck
* Fix the issue that DLedger RPC Service thread stuck
The following phenomena were found in our test environment
Three nodes, one node down, unable to select a leader. We found one of the DLedger nodes cannot process any rpc requests (it is candidate role), and all NettyServerPublicExecutor threads are stuck in the handlePush method
The number of queued tasks is increasing, but the number of completed tasks has not changed
The thread stuck in here, because the blocking queue is already full.
However, since it is a candidate, it will no longer peek data from the blocking queue
The text was updated successfully, but these errors were encountered: