[
https://issues.apache.org/jira/browse/HDDS-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073654#comment-17073654
]
Li Cheng commented on HDDS-3329:
--------------------------------
We were having different network-config for topology between SCM and datanode
and we modified it on datanode following with a restart. Not sure if it matters.
> Ozone cluster expansion: Block deletion mismatch
> ------------------------------------------------
>
> Key: HDDS-3329
> URL: https://issues.apache.org/jira/browse/HDDS-3329
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: SCM
> Affects Versions: 0.4.1
> Reporter: Li Cheng
> Assignee: Lokesh Jain
> Priority: Major
>
> SCM logs keep printing this when we expand Ozone cluster with more datanodes.
>
> 2020-04-02 19:45:42,745
> [EventQueue-PendingDeleteStatusForPendingDeleteHandler] INFO
> org.apache.hadoop.hdds.scm.block.SCMBlockDeletingService: Block deletion
> txnID mismatch in datanode 1eacbd89-a835-438e-aa4b-5bc78adb7c8c for
> containerID 314. Datanode delete txnID: 0, SCM txnID: 1208
> 2020-04-02 19:45:42,745
> [EventQueue-PendingDeleteStatusForPendingDeleteHandler] INFO
> org.apache.hadoop.hdds.scm.block.SCMBlockDeletingService: Block deletion
> txnID mismatch in datanode 1eacbd89-a835-438e-aa4b-5bc78adb7c8c for
> containerID 351. Datanode delete txnID: 0, SCM txnID: 662
> 2020-04-02 19:45:42,745
> [EventQueue-PendingDeleteStatusForPendingDeleteHandler] INFO
> org.apache.hadoop.hdds.scm.block.SCMBlockDeletingService: Block deletion
> txnID mismatch in datanode 1eacbd89-a835-438e-aa4b-5bc78adb7c8c for
> containerID 352. Datanode delete txnID: 0, SCM txnID: 1085
--
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
