[jira] [Updated] (HDDS-4372) Datanode delete operations should not impact rocksDB cache

["Ethan Rose (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HDDS-4372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ethan Rose updated HDDS-4372:
-----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> Datanode delete operations should not impact rocksDB cache
> ----------------------------------------------------------
>
>                 Key: HDDS-4372
>                 URL: https://issues.apache.org/jira/browse/HDDS-4372
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: Ozone Datanode
>            Reporter: Lokesh Jain
>            Priority: Major
>
> Currently datanode accesses container rockDB while processing delete transactions received from SCM and when deleting service deletes the blocks. During these accesses delete operations can end up evicting RocksDB cache instances used for read/write. It is better to avoid evicting the cache entries.
> It also needs to be made sure that there is only one rocksDB instance for a particular container at any time.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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