You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Lokesh Jain (Jira)" <ji...@apache.org> on 2020/04/02 11:58:00 UTC
[jira] [Comment Edited] (HDDS-3329) Ozone cluster expansion: Block
deletion mismatch
[ https://issues.apache.org/jira/browse/HDDS-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17073661#comment-17073661 ]
Lokesh Jain edited comment on HDDS-3329 at 4/2/20, 11:57 AM:
-------------------------------------------------------------
[~timmylicheng] Thanks for raising the issue! The log suggests that there are a few delete block transactions which have not yet executed on these datanodes for the corresponding containers. Couple of questions regarding the issue.
# Is the mismatch seen for the new datanodes added?
# containerID 314 and other containers for which the log is seen - Are these containers replicated to these new datanodes via ReplicationManager?
was (Author: ljain):
[~timmylicheng] Thanks for raising the issue! Couple of questions regarding it. The log suggests that there are a few delete block transactions which have not yet executed on these datanodes for the corresponding containers.
# Is the mismatch seen for the new datanodes added?
# containerID 314 and other containers for which the log is seen - Are these containers replicated to these new datanodes via ReplicationManager?
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org