[
https://issues.apache.org/jira/browse/HDFS-11951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156132#comment-16156132
]
Anu Engineer commented on HDFS-11951:
-------------------------------------
This is a race condition that we might just document. I am marking this as
ozone post merge for time being. Please let me know if you think this needs to
be fixed before trunk merge.
> 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
> Labels: OzonePostMerge
>
> 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.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
