[jira] [Updated] (IGNITE-26973) IndexProcessor: ConcurrentHashMap under RW-lock; reconsider redundant idxDefs map

["Ignite TC Bot (Jira)" <ji...@apache.org>]

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

Ignite TC Bot updated IGNITE-26973:
-----------------------------------
    Ignite Flags:   (was: Release Notes Required)

> IndexProcessor: ConcurrentHashMap under RW-lock; reconsider redundant idxDefs map
> ---------------------------------------------------------------------------------
>
>                 Key: IGNITE-26973
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26973
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vsevolod Kovalev
>            Assignee: Vsevolod Kovalev
>            Priority: Major
>             Fix For: 2.18
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> {{_*IndexProcessor*_}} guards access with a {_}{{ReentrantReadWriteLock}}{_}, yet both {{_cacheToIdx_}} and {{_idxDefs_}} are {{{}_ConcurrentHashMap_{}}}. This likely adds overhead without benefit.
> Additionally, {{_idxDefs_}} ({{{}_UUID → IndexDefinition_{}}}) appears redundant because Index already holds its {{_IndexDefinition_}} and exposes the {{{}_UUID_{}}}.
> *Action items:*
>  * Audit read/write paths to confirm lock coverage.
>  * If confirmed, replace both with plain HashMap.
>  * Evaluate removing idxDefs in favor of retrieving IndexDefinition from Index; refactor call sites if feasible.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)