[
https://issues.apache.org/jira/browse/HDDS-12819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tejaskriya Madhan updated HDDS-12819:
-------------------------------------
Description:
Having a background service that triggers bottommost compaction for keyTable,
fileTable, directoryTable, deletedTable, deletedDirectoryTable,
multipartInfoTable (all the tables that can potentially be of a very large
size) at a large interval like 6hours can help combat performance issues caused
in the rocksDB layer. This can be turned off using a config.
This would be a fallback approach until HDDS-12518 design and implementation is
completed.
was:Having a background service that triggers bottommost compaction for
keyTable, fileTable, directoryTable, deletedTable, deletedDirectoryTable,
multipartInfoTable (all the tables that can potentially be of a very large
size) at a large interval like 6hours can help combat performance issues caused
in the rocksDB layer. This can be turned off using a config.
> Auto-compact tables which can tend to be large in size at intervals
> -------------------------------------------------------------------
>
> Key: HDDS-12819
> URL: https://issues.apache.org/jira/browse/HDDS-12819
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Tejaskriya Madhan
> Assignee: Tejaskriya Madhan
> Priority: Major
>
> Having a background service that triggers bottommost compaction for keyTable,
> fileTable, directoryTable, deletedTable, deletedDirectoryTable,
> multipartInfoTable (all the tables that can potentially be of a very large
> size) at a large interval like 6hours can help combat performance issues
> caused in the rocksDB layer. This can be turned off using a config.
> This would be a fallback approach until HDDS-12518 design and implementation
> is completed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
