[
https://issues.apache.org/jira/browse/HDDS-16129?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-16129:
-------------------------------
Description:
If a key is already deleted in the leader, but the local lease follower read
still reads the key in the follower, by the time the client reads the blocks,
it found that the blocks are already deleted.
We might need to handle this either by delaying the OM key delete blocks for a
configurable time or set up some kind of upper bound time when a block can be
safely deleted.
was:
If a key is already deleted in the leader, but the local lease follower read
still reads the key in the follower, by the time the client reads the blocks,
it found that the blocks are already deleted.
We might need to handle this either by delaying the OM key delete blocks for a
configurable time.
> Follower read for deleted keys should be able to read the blocks
> ----------------------------------------------------------------
>
> Key: HDDS-16129
> URL: https://issues.apache.org/jira/browse/HDDS-16129
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> If a key is already deleted in the leader, but the local lease follower read
> still reads the key in the follower, by the time the client reads the blocks,
> it found that the blocks are already deleted.
> We might need to handle this either by delaying the OM key delete blocks for
> a configurable time or set up some kind of upper bound time when a block can
> be safely deleted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
