You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Stephen O'Donnell (Jira)" <ji...@apache.org> on 2023/01/06 09:34:00 UTC

[jira] [Resolved] (HDDS-7727) EC: SCM unregistered event handler for DatanodeCommandCountUpdated

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

Stephen O'Donnell resolved HDDS-7727.
-------------------------------------
    Fix Version/s: 1.4.0
       Resolution: Fixed

> EC: SCM unregistered event handler for DatanodeCommandCountUpdated
> ------------------------------------------------------------------
>
>                 Key: HDDS-7727
>                 URL: https://issues.apache.org/jira/browse/HDDS-7727
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: SCM
>            Reporter: Stephen O'Donnell
>            Assignee: Attila Doroszlai
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.4.0
>
>
> In SCM I see logs like:
> {code}
> 2023-01-04 23:56:45,346 WARN org.apache.hadoop.hdds.server.events.EventQueue: No event handler registered for event TypedEvent{payloadType=DatanodeDetails, name='Datanode_Command_Queue_Updated'}
> {code}
> It seems an event handler was not registered correctly for the new events which are getting produced, which causes noise in the logs and perhaps the messages to build up in the queue and may result in memory issues.
> This event was created to notify RM when the queue is updated via a heartbeat so it can adjust replication load limits. The handler `DatanodeCommandCountUpdatedHandler` was for this purpose, but perhaps it is not wired up correctly.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org