You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2025/04/22 17:03:00 UTC
[jira] [Reopened] (HDDS-9585) Fix import/export messages in container log
[ https://issues.apache.org/jira/browse/HDDS-9585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ethan Rose reopened HDDS-9585:
------------------------------
Hi [~kostacie], the log entries you referenced are for the datanode application logs, found in files usually named {{ozone-datanode-*.log}}. This Jira is for the container logs, which are similar to audit logs for the states and events that happen to container replicas on datanodes. These are written to a files named like {{dn-container-*.log}}. This different type of log is designed to track container events over a long period of time without rolling off.
See the [ContainerLogger|https://github.com/apache/ozone/blob/b34c537940bce95470f2a6af6b0aa4abbbabfb0d/hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/utils/ContainerLogger.java#L41] class to get started making changes in this area. It may be difficult to get the source/target node information into the container log due to the code structure, but if we can even add a message indicating that the container was imported or exported that would still be an improvement.
> Fix import/export messages in container log
> -------------------------------------------
>
> Key: HDDS-9585
> URL: https://issues.apache.org/jira/browse/HDDS-9585
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Ethan Rose
> Assignee: Anastasia Kostryukova
> Priority: Major
>
> Right now logging for container import and export in the container log does not add a message to distinguish these events. It just shows up as another container close entry. In addition to adding these messages, it would be good to also log where the container was sent or where it was retrieved from. This part of the change would be more involved because the current place in the code where the container logger is invoked does not have access to this information.
--
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