You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Tsz-wo Sze (Jira)" <ji...@apache.org> on 2022/07/12 04:11:00 UTC

[jira] [Assigned] (RATIS-1622) High cpu usage of LogAppenderDaemon

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

Tsz-wo Sze reassigned RATIS-1622:
---------------------------------

    Assignee: Riguz Lee  (was: Tsz-wo Sze)

[~riguz], assigned this to you.  Thanks.

BTW, this can be fixed as below.  Could you test if it would work for your case?
{code}
+++ b/ratis-server-api/src/main/java/org/apache/ratis/server/RaftServer.java
@@ -67,9 +67,7 @@ public interface RaftServer extends Closeable, RpcType.Get,
 
     /** @return the {@link RaftPeer} for this division. */
     default RaftPeer getPeer() {
-      return Optional.ofNullable(getGroup())
-          .map(g -> g.getPeer(getId()))
-          .orElseGet(() -> getRaftServer().getPeer());
+      return getRaftConf().getPeer(getId());
     }
{code}

> High cpu usage of LogAppenderDaemon
> -----------------------------------
>
>                 Key: RATIS-1622
>                 URL: https://issues.apache.org/jira/browse/RATIS-1622
>             Project: Ratis
>          Issue Type: Improvement
>          Components: server
>            Reporter: Tsz-wo Sze
>            Assignee: Riguz Lee
>            Priority: Major
>
> As reported by Riguz Lee in  https://lists.apache.org/thread/p5hq3nr1zqpkgd3fr0vyx9j5d2lx6gf9 , LogAppenderDaemon has a high cpu usage.



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