You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (Jira)" <ji...@apache.org> on 2020/05/12 20:16:00 UTC

[jira] [Commented] (IGNITE-12969) TxRecovery discovery listener should implement HighPriorityListener

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

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

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

> 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
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)