[
https://issues.apache.org/jira/browse/HBASE-30550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on HBASE-30550 started by Vladimir Rodionov.
-------------------------------------------------
> Make cache admission decisions tier-aware
> -----------------------------------------
>
> Key: HBASE-30550
> URL: https://issues.apache.org/jira/browse/HBASE-30550
> Project: HBase
> Issue Type: New Feature
> Components: BlockCache
> Affects Versions: 4.0.0-alpha-1
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Priority: Major
> Fix For: 4.0.0-alpha-1
>
>
> *Title*
> Make cache admission decisions tier-aware
> *Description*
> {{CachePlacementAdmissionPolicy.shouldAdmit()}} currently makes a
> service-wide admission decision before cache tier placement is evaluated.
> This model is insufficient for tiered cache topologies because different
> tiers may have different admission requirements. For example, an L1 cache may
> reject a block while L2 should still accept it.
> Refactor cache insertion so that placement and admission have separate
> responsibilities:
> * {{selectTier()}} determines the target cache tier or tiers.
> * {{shouldAdmit()}} makes an admission decision for a specific selected tier.
> * {{TopologyBackedCacheAccessService}} performs tier selection first, then
> evaluates admission independently for each selected tier.
> * Admission policies such as {{AdaptiveLruCachePlacementAdmissionPolicy}}
> should no longer modify tier placement to implement admission behavior.
> * Update affected tests to reflect per-tier admission semantics.
> The {{CachePlacementAdmissionPolicy.shouldAdmit()}} API should include the
> target {{{}CacheTier{}}}.
> This preserves the intended semantics for all topology types:
> * {{{}SINGLE_TIER{}}}: admission applies to {{{}SINGLE{}}}.
> * {{{}TIERED_EXCLUSIVE{}}}: placement selects one tier, then that tier
> evaluates admission.
> * {{{}TIERED_INCLUSIVE{}}}: placement may select both L1 and L2, and each
> tier independently evaluates admission.
> This refactoring is required to support policies where L1 and L2 have
> different admission behavior without coupling admission decisions to topology
> placement.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)