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

Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2020/02/28 16:44:00 UTC

[jira] [Resolved] (IGNITE-12656) Cleanup GridCacheProcessor from functionality not related to its responsibility

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

Vyacheslav Koptilin resolved IGNITE-12656.
------------------------------------------
    Resolution: Fixed

merged to master

> Cleanup GridCacheProcessor from functionality not related to its responsibility
> -------------------------------------------------------------------------------
>
>                 Key: IGNITE-12656
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12656
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 2.8
>            Reporter: Vyacheslav Koptilin
>            Assignee: Vyacheslav Koptilin
>            Priority: Major
>             Fix For: 2.9
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, we have a couple of functionality in GridCacheProcessor not directly related to its responsibility, like:
> * initQueryStructuresForNotStartedCache
> * addRemovedItemsCleanupTask
> * setTxOwnerDumpRequestsAllowed
> * longTransactionTimeDumpThreshold
> * transactionTimeDumpSamplesCoefficient
> * longTransactionTimeDumpSamplesPerSecondLimit
> * broadcastToNodesSupportingFeature
> * LocalAffinityFunction
> * RemovedItemsCleanupTask
> * TxTimeoutOnPartitionMapExchangeChangeFuture
> * enableRebalance
> We need to move them to the right places and make GridCacheProcessor code cleaner.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)