You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (JIRA)" <ji...@apache.org> on 2019/02/01 03:25:00 UTC

[jira] [Updated] (HBASE-15648) Reduce number of concurrent region location lookups when MetaCache entry is cleared

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

Guanghao Zhang updated HBASE-15648:
-----------------------------------
    Fix Version/s:     (was: 2.2.0)
                   2.3.0

> Reduce number of concurrent region location lookups when MetaCache entry is cleared
> -----------------------------------------------------------------------------------
>
>                 Key: HBASE-15648
>                 URL: https://issues.apache.org/jira/browse/HBASE-15648
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Client
>    Affects Versions: 1.2.0, 1.3.0
>            Reporter: Mikhail Antonov
>            Assignee: Mikhail Antonov
>            Priority: Major
>             Fix For: 3.0.0, 1.5.0, 2.3.0
>
>         Attachments: HBASE-15648-branch-1.3.v1.patch
>
>
> It seems in HConnectionImplementation#locateRegionInMeta if region location is removed from the cache, with large number of client threads we could have many of them getting cache miss and doing meta scan, which looks unnecessary - we could empty mechanism similar to what we have in IdLock in HFileReader to fetch the block to cache, do ensure that if one thread is already looking up location for region R1, other threads who need it's location wait until first thread finishes his work.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)