[
https://issues.apache.org/jira/browse/HDFS-11951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042478#comment-16042478
]
Yiqun Lin edited comment on HDFS-11951 at 6/8/17 9:54 AM:
----------------------------------------------------------
[~cheersyang], I am thinking this corner case will not be happened actually.
{{BucketManagerImpl}} holds the readLock before doing list buckets operation,
and {{ReadLock}}, {{WriteLock}} are mutual exclusive. So during this time, the
delete key operations should not be happened since delete operation will
require the write lock.
Correct me if I am wrong, :).
was (Author: linyiqun):
[~cheersyang], I am thinking this corner case will not be happen actually.
{{BucketManagerImpl}} holds the readLock before doing list buckets operation,
and {{ReadLock}}, {{WriteLock}} are mutual exclusive. So during this time, the
delete key operations should not be happened since delete operation will
require the write lock.
Correct me if I am wrong, :).
> Ozone: Handle potential inconsistent states while listing keys
> --------------------------------------------------------------
>
> Key: HDFS-11951
> URL: https://issues.apache.org/jira/browse/HDFS-11951
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Affects Versions: HDFS-7240
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
>
> In the discussions in HDFS-11779, there might be a corner case we running
> into the situation that some key are deleted while we are listing them. For
> example
> 1. A list call is made say from key1 to key100 is returned.
> 2. Someone deletes the key100
> 3. A list continue call is made with startKey=key100.
> We need to investigate this case and make sure this is properly handled in
> ozone. See more discussion from [here |
> https://issues.apache.org/jira/browse/HDFS-11779?focusedCommentId=16042356&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16042356].
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
