You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Istvan Fajth (Jira)" <ji...@apache.org> on 2019/12/09 16:09:00 UTC
[jira] [Created] (HDDS-2697) SCM log is flooded with block deletion
txId mismatch messages
Istvan Fajth created HDDS-2697:
----------------------------------
Summary: 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
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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org