[
https://issues.apache.org/jira/browse/KUDU-2977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adar Dembo resolved KUDU-2977.
------------------------------
Fix Version/s: 1.12.0
Resolution: Fixed
> Sharding block map of LogBlockManager
> -------------------------------------
>
> Key: KUDU-2977
> URL: https://issues.apache.org/jira/browse/KUDU-2977
> Project: Kudu
> Issue Type: Improvement
> Components: fs
> Reporter: Yingchun Lai
> Assignee: Yingchun Lai
> Priority: Major
> Fix For: 1.12.0
>
>
> I found LBM may manage a very large block map when tserver hold large scale
> data, metric like:
> {code:java}
> {
> "name": "log_block_manager_blocks_under_management",
>
>
> "value": 7014790
> }
> {code}
> LogBlock get/add should hold map's lock first, this is costly and will slow
> down statup time.
> [~tlipcon] also mentioned in https://issues.apache.org/jira/browse/KUDU-2014.
>
> We can improve it by sharding this big map.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
