[
https://issues.apache.org/jira/browse/IGNITE-29272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18142876#comment-18142876
]
Ignite TC Bot commented on IGNITE-29272:
----------------------------------------
{panel:title=Branch: [pull/13812/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13812/head] Base: [master] : No new tests
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9487903&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9487903
rerunBuildIds=none{color}
> Remove unused code from cache entry locking
> -------------------------------------------
>
> Key: IGNITE-29272
> URL: https://issues.apache.org/jira/browse/IGNITE-29272
> Project: Ignite
> Issue Type: Task
> Reporter: Nikita Amelchev
> Assignee: Nikita Amelchev
> Priority: Minor
> Fix For: 2.20
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Since LOCAL caches were removed, entry lock candidates are never reentries,
> but the entry MVCC code still handles them. Earlier refactorings have also
> left several lock API parameters and helper methods unused or always called
> with the same value. This dead code makes the locking path harder to follow
> and can be removed without changing behavior.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
