[jira] [Commented] (HDDS-2697) SCM log is flooded with block deletion txId mismatch messages

["Ritesh H Shukla (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HDDS-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17687708#comment-17687708 ] 

Ritesh H Shukla commented on HDDS-2697:
---------------------------------------

Cleaning up Jiras to keep Critical and Blockers to be immediate attention/release blocker jiras only. This Jirashould be taken up by a volunteer to revisit.

> SCM log is flooded with block deletion txId mismatch messages
> -------------------------------------------------------------
>
>                 Key: HDDS-2697
>                 URL: https://issues.apache.org/jira/browse/HDDS-2697
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: SCM
>            Reporter: István Fajth
>            Priority: Critical
>              Labels: TriagePending, ozone-jira-volunteer, ozone-moved-out-critical
>
> When you run Hive queries on the cluster, but I think this is true for other MapReduce stuff as well, then the interim and temporary data is created and deleted quite often.
> This leads to the flood of similar messages in the SCM log:
> {code}
> 2019-12-07 05:00:41,112 INFO org.apache.hadoop.hdds.scm.block.SCMBlockDeletingService: Block deletion txnID mismatch in datanode e590d08a-4a4e-428a-82e8-80f7221f639e for containerID 307. Datanode delete txnID: 25145, SCM txnID: 25148
> {code}
> Either we need to decrease the log level of this messages, or we need to get rid of the cause of the message. In a single log file I see over 21k lines containing this message from ~37k lines of log.



--
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