[ 
https://issues.apache.org/jira/browse/RATIS-2129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Duong updated RATIS-2129:
-------------------------
    Description: 
Today, the GrpcLogAppender thread makes a lot of calls that need RaftLog's 
readLock. In an active environment, RaftLog is always busy appending 
transactions from clients, thus writeLock is frequently busy. This makes the 
replication performance slow. 

See the [^dn_echo_leader_profile.html], or in the picture below, the purple is 
the time taken to acquire readLock from RaftLog.

!Screenshot 2024-07-22 at 3.12.03 PM.png|width=926,height=469!

So far, I'm not sure if this is a regression from a recent change in 
3.1.0/3.0.0, or it's been always the case. 

  was:Today, the GrpcLogAppender thread makes a lot of calls that need 
RaftLog's readLock. And in an active environment, RaftLog is always busy 
appending transactions from clients, thus writeLock is frequenly busy. This 
makes the Raft


> Low replication performance low because GrpcLogAppender is often blocked by 
> RaftLog's readLock
> ----------------------------------------------------------------------------------------------
>
>                 Key: RATIS-2129
>                 URL: https://issues.apache.org/jira/browse/RATIS-2129
>             Project: Ratis
>          Issue Type: Bug
>    Affects Versions: 3.1.0
>            Reporter: Duong
>            Priority: Major
>         Attachments: Screenshot 2024-07-22 at 3.12.03 PM.png, 
> dn_echo_leader_profile.html
>
>
> Today, the GrpcLogAppender thread makes a lot of calls that need RaftLog's 
> readLock. In an active environment, RaftLog is always busy appending 
> transactions from clients, thus writeLock is frequently busy. This makes the 
> replication performance slow. 
> See the [^dn_echo_leader_profile.html], or in the picture below, the purple 
> is the time taken to acquire readLock from RaftLog.
> !Screenshot 2024-07-22 at 3.12.03 PM.png|width=926,height=469!
> So far, I'm not sure if this is a regression from a recent change in 
> 3.1.0/3.0.0, or it's been always the case. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to