[ 
https://issues.apache.org/jira/browse/HDDS-1625?focusedWorklogId=252105&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-252105
 ]

ASF GitHub Bot logged work on HDDS-1625:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 31/May/19 22:33
            Start Date: 31/May/19 22:33
    Worklog Time Spent: 10m 
      Work Description: avijayanhwx commented on pull request #883: HDDS-1625 : 
ConcurrentModificationException when SCM has containers o…
URL: https://github.com/apache/hadoop/pull/883
 
 
   …f different owners.
   
   SCMBlockProtocolServer#allocateBlock throws ConcurrentModificationException 
when SCM has containers of different owners.
   
   `2019-05-31 13:53:16,808 WARN 
org.apache.hadoop.hdds.scm.container.SCMContainerManager: Container allocation 
failed for pipeline=Pipeline[ Id: 3e0eec4d-67d1-4582-a9e9-e68b0a340de6, Nodes: 
abaea3d2-a8c1-47de-8cdb-7cc5ed8f23a6{ip: 10.17.219.50, host: v
   c1340.halxg.cloudera.com, certSerialId: null}, Type:RATIS, Factor:ONE, 
State:OPEN] requiredSize=268435456 {}
   java.util.ConcurrentModificationException
           at 
java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1211)
           at java.util.TreeMap$KeyIterator.next(TreeMap.java:1265)
           at 
org.apache.hadoop.hdds.scm.container.SCMContainerManager.getContainersForOwner(SCMContainerManager.java:473)
           at 
org.apache.hadoop.hdds.scm.container.SCMContainerManager.getMatchingContainer(SCMContainerManager.java:394)
           at 
org.apache.hadoop.hdds.scm.block.BlockManagerImpl.allocateBlock(BlockManagerImpl.java:203)
           at 
org.apache.hadoop.hdds.scm.server.SCMBlockProtocolServer.allocateBlock(SCMBlockProtocolServer.java:172)`
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

            Worklog Id:     (was: 252105)
            Time Spent: 10m
    Remaining Estimate: 0h

> ConcurrentModificationException when SCM has containers of different owners
> ---------------------------------------------------------------------------
>
>                 Key: HDDS-1625
>                 URL: https://issues.apache.org/jira/browse/HDDS-1625
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Aravindan Vijayan
>            Assignee: Aravindan Vijayan
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> {{SCMBlockProtocolServer#allocateBlock}} throws 
> {{ConcurrentModificationException}} when SCM has containers of different 
> owners.
> {code}
> 2019-05-31 13:53:16,808 WARN 
> org.apache.hadoop.hdds.scm.container.SCMContainerManager: Container 
> allocation failed for pipeline=Pipeline[ Id: 
> 3e0eec4d-67d1-4582-a9e9-e68b0a340de6, Nodes: 
> abaea3d2-a8c1-47de-8cdb-7cc5ed8f23a6{ip: 10.17.219.50, host: v
> c1340.halxg.cloudera.com, certSerialId: null}, Type:RATIS, Factor:ONE, 
> State:OPEN] requiredSize=268435456 {}
> java.util.ConcurrentModificationException
>         at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1211)
>         at java.util.TreeMap$KeyIterator.next(TreeMap.java:1265)
>         at 
> org.apache.hadoop.hdds.scm.container.SCMContainerManager.getContainersForOwner(SCMContainerManager.java:473)
>         at 
> org.apache.hadoop.hdds.scm.container.SCMContainerManager.getMatchingContainer(SCMContainerManager.java:394)
>         at 
> org.apache.hadoop.hdds.scm.block.BlockManagerImpl.allocateBlock(BlockManagerImpl.java:203)
>         at 
> org.apache.hadoop.hdds.scm.server.SCMBlockProtocolServer.allocateBlock(SCMBlockProtocolServer.java:172)
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to