Ryan Blough created HDDS-15787:
----------------------------------

             Summary: SCM should log deletion requests from OM at INFO level
                 Key: HDDS-15787
                 URL: https://issues.apache.org/jira/browse/HDDS-15787
             Project: Apache Ozone
          Issue Type: Improvement
          Components: SCM
            Reporter: Ryan Blough


SCM logs the delete requests it receives from OM in the 
SCMBlockProtocolServer.java file:

[https://github.com/apache/ozone/blob/21c7219707f1004077686e4067f673115f059dc8/hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/server/SCMBlockProtocolServer.java#L272]

[https://github.com/apache/ozone/blob/21c7219707f1004077686e4067f673115f059dc8/hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/server/SCMBlockProtocolServer.java#L287]

But these logs are at the DEBUG level. The OM block deletions sent to SCM are 
logged at the INFO level on the OM side, and so are the SCM block deletions 
sent to DNs, and so are the block deletions received by the DNs. The SCM-side 
of the OM>SCM delete procedure is the only gap.

We should promote these two DEBUG logs to INFO level, completing the entire 
block deletion chain from end to end by default.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to