[
https://issues.apache.org/jira/browse/HDDS-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16616696#comment-16616696
]
Lokesh Jain commented on HDDS-475:
----------------------------------
It appears that this might be happening only in the case of containers in OPEN
state. The code block which returns new BlockID for open containers is not
synchronized. [~nandakumar131] Why do we take a read lock in allocateBlock
call? This lock is never taken by any other function and may not be required
since we have already made the code blocks inside it synchronised?
> Block Allocation returns same BlockID on different keys creation
> ----------------------------------------------------------------
>
> Key: HDDS-475
> URL: https://issues.apache.org/jira/browse/HDDS-475
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Affects Versions: 0.2.1
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> Priority: Blocker
> Fix For: 0.2.1
>
>
> BlockManagerImpl#allocateBlock returns same BlockID. This leads to different
> key creations getting the same blockId.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
