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

Posted to issues@kudu.apache.org by "Yingchun Lai (Jira)" <ji...@apache.org> on 2019/10/17 09:06:00 UTC

[jira] [Created] (KUDU-2977) Sharding block map of LogBlockManager

Yingchun Lai created KUDU-2977:
----------------------------------

             Summary: 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


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)