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

Anton Vinogradov updated IGNITE-12969:
--------------------------------------
    Description: 
Currently, tx recovery may be delayed because it starts at a low priority 
discovery listener.
Tx recovery listener now 16th position at discovery listeners list.
List size is 35 and execution time between lsnrs[0] and lsnrs[34] may be 
greater than 300 ms according to local benchmarks.
This does not mean that currently tx recovery may be delayed by 300 ms, but it 
already delayed for some time (up to 50ms according to local benchmarks) and 
this delay may grow from version to version.
A good case is to implement this listener as HighPriorityListener, this will 
guarantee priority for further versions.

  was:Currently, tx recovery delayed for 300+ ms because it starts at a low 
priority discovery listener.


> TxRecovery discovery listener should implement HighPriorityListener
> -------------------------------------------------------------------
>
>                 Key: IGNITE-12969
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12969
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Anton Vinogradov
>            Assignee: Anton Vinogradov
>            Priority: Major
>              Labels: iep-45
>             Fix For: 2.9
>
>
> Currently, tx recovery may be delayed because it starts at a low priority 
> discovery listener.
> Tx recovery listener now 16th position at discovery listeners list.
> List size is 35 and execution time between lsnrs[0] and lsnrs[34] may be 
> greater than 300 ms according to local benchmarks.
> This does not mean that currently tx recovery may be delayed by 300 ms, but 
> it already delayed for some time (up to 50ms according to local benchmarks) 
> and this delay may grow from version to version.
> A good case is to implement this listener as HighPriorityListener, this will 
> guarantee priority for further versions.



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

Reply via email to