[ 
https://issues.apache.org/jira/browse/IGNITE-12656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17044538#comment-17044538
 ] 

Ignite TC Bot commented on IGNITE-12656:
----------------------------------------

{panel:title=Branch: [pull/7467/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5077782&buildTypeId=IgniteTests24Java8_RunAll]

> 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)

Reply via email to