[
https://issues.apache.org/jira/browse/HDDS-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marton Elek updated HDDS-2697:
------------------------------
Target Version/s: 0.7.0 (was: 0.6.0)
> SCM log is flooded with block deletion txId mismatch messages
> -------------------------------------------------------------
>
> Key: HDDS-2697
> URL: https://issues.apache.org/jira/browse/HDDS-2697
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Components: SCM
> Reporter: Istvan Fajth
> Assignee: Istvan Fajth
> Priority: Major
> Labels: TriagePending
>
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org
