[
https://issues.apache.org/jira/browse/HDFS-11779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16042371#comment-16042371
]
Weiwei Yang commented on HDFS-11779:
------------------------------------
Yeah, you are right. I think you are talking about a client side pagination
implementation based on rest call. That could happen, as listBuckets in
{{MetadataManagerImpl}} only holds a read lock. So in the case you mentioned,
step 3 will fail with key not found error. Client side will need to handle this
and decide how to proceed, maybe throw an inconsistent state exception. I will
file a JIRA to track this. Thank you.
> Ozone: KSM: add listBuckets
> ---------------------------
>
> Key: HDFS-11779
> URL: https://issues.apache.org/jira/browse/HDFS-11779
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ozone
> Affects Versions: HDFS-7240
> Reporter: Anu Engineer
> Assignee: Weiwei Yang
> Attachments: HDFS-11779-HDFS-7240.001.patch,
> HDFS-11779-HDFS-7240.002.patch, HDFS-11779-HDFS-7240.003.patch,
> HDFS-11779-HDFS-7240.004.patch, HDFS-11779-HDFS-7240.005.patch,
> HDFS-11779-HDFS-7240.006.patch, HDFS-11779-HDFS-7240.007.patch,
> HDFS-11779-HDFS-7240.008.patch, HDFS-11779-HDFS-7240.009.patch,
> HDFS-11779-HDFS-7240.010.patch, HDFS-11779-HDFS-7240.011.patch,
> HDFS-11779-HDFS-7240.012.patch, HDFS-11779-HDFS-7240.013.patch,
> HDFS-11779-HDFS-7240.014.patch
>
>
> Lists buckets of a given volume. Similar to listVolumes, paging supported via
> prevKey, prefix and maxKeys.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
