[
https://issues.apache.org/jira/browse/IGNITE-12656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17052091#comment-17052091
]
Alexey Goncharuk commented on IGNITE-12656:
-------------------------------------------
[~slava.koptilin] can you check the LocalAffinityFunction concern? I think we
can either keep it for compatibility reasons, or keep a placeholder which will
delegate to a moved class.
> 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)
