You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Ivan Andika (Jira)" <ji...@apache.org> on 2025/08/20 02:00:00 UTC

[jira] [Created] (HDDS-13596) Revisit ListKeys and ListStatus consistency guarantees

Ivan Andika created HDDS-13596:
----------------------------------

             Summary: Revisit ListKeys and ListStatus consistency guarantees
                 Key: HDDS-13596
                 URL: https://issues.apache.org/jira/browse/HDDS-13596
             Project: Apache Ozone
          Issue Type: Improvement
            Reporter: Ivan Andika


This is a ticket to revisit and document listKeys and listStatus consistency guarantee. Currently, listKeys does not seem to hold any bucket locks and listStatus seem to only hold keys when retrieving OM key table cache iterator. During that time, OM DB flush or cache evictions can happen which affect the list results.

There are concerns raised in HDDS-1986 and HDDS-1987 that seem to be unaddressed. This includes
 * Calling OM DB flush before the list
 * Using a generational stamp (shared between cache and DB)
 ** This might be achieved using updateID (or transactionLogIndex)
 * Holding lock during the list
 ** This will simplify the consistency but will cause large performance hit 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org