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

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

{panel:title=Branch: [pull/13817/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/13817/head] Base: [master] : No new tests 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}{panel}
[TeamCity *--> Run :: All* 
Results|https://ci2.ignite.apache.org/viewLog.html?buildId=9489487&buildTypeId=IgniteTests24Java8_RunAll]
{color:#ffffff}tcbot-analysis-comment chainBuildId=9489487 
rerunBuildIds=none{color}

> Enforce transactional lock wait timeouts on primary nodes
> ---------------------------------------------------------
>
>                 Key: IGNITE-29279
>                 URL: https://issues.apache.org/jira/browse/IGNITE-29279
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladislav Pyatkov
>            Assignee: Vladislav Pyatkov
>            Priority: Major
>             Fix For: 2.20
>
>          Time Spent: 2h 50m
>  Remaining Estimate: 0h
>
> The coordinator can report a lock wait timeout even when the primary has 
> already acquired the locks but its response is delayed.
> Enforce the lock wait timeout on primary nodes and only the transaction 
> timeout on the coordinator. Share one wait budget across sequential primary 
> batches, and use waitTimeout=0 for ordinary cache operations so that they 
> remain bounded by the transaction timeout.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to