[jira] [Updated] (HDDS-3329) Ozone cluster expansion: Block deletion mismatch

2020-06-22 Thread Lokesh Jain (Jira)


 [ 
https://issues.apache.org/jira/browse/HDDS-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lokesh Jain updated HDDS-3329:
--
Target Version/s: 0.7.0  (was: 0.6.0)

> 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: Ozone Datanode
>Affects Versions: 0.4.1
>Reporter: Li Cheng
>Assignee: Lokesh Jain
>Priority: Major
>  Labels: TriagePending
> Attachments: hadoop-ozoneadmin-scm.log, ozone-scm-dn-log.tar.gz
>
>
> 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



[jira] [Updated] (HDDS-3329) Ozone cluster expansion: Block deletion mismatch

2020-06-22 Thread Lokesh Jain (Jira)


 [ 
https://issues.apache.org/jira/browse/HDDS-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lokesh Jain updated HDDS-3329:
--
Component/s: (was: SCM)
 Ozone Datanode

> 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: Ozone Datanode
>Affects Versions: 0.4.1
>Reporter: Li Cheng
>Assignee: Lokesh Jain
>Priority: Major
>  Labels: TriagePending
> Attachments: hadoop-ozoneadmin-scm.log, ozone-scm-dn-log.tar.gz
>
>
> 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



[jira] [Updated] (HDDS-3329) Ozone cluster expansion: Block deletion mismatch

2020-06-01 Thread Arpit Agarwal (Jira)


 [ 
https://issues.apache.org/jira/browse/HDDS-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arpit Agarwal updated HDDS-3329:

Target Version/s: 0.6.0
  Labels: TriagePending  (was: )

> 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
>  Labels: TriagePending
> Attachments: hadoop-ozoneadmin-scm.log, ozone-scm-dn-log.tar.gz
>
>
> 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



[jira] [Updated] (HDDS-3329) Ozone cluster expansion: Block deletion mismatch

2020-04-06 Thread Simon Su (Jira)


 [ 
https://issues.apache.org/jira/browse/HDDS-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Su updated HDDS-3329:
---
Attachment: ozone-scm-dn-log.tar.gz

> 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
> Attachments: hadoop-ozoneadmin-scm.log, ozone-scm-dn-log.tar.gz
>
>
> 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



[jira] [Updated] (HDDS-3329) Ozone cluster expansion: Block deletion mismatch

2020-04-03 Thread Simon Su (Jira)


 [ 
https://issues.apache.org/jira/browse/HDDS-3329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Su updated HDDS-3329:
---
Attachment: hadoop-ozoneadmin-scm.log

> 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
> Attachments: hadoop-ozoneadmin-scm.log
>
>
> 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