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

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

Verified merged PR #13817 / commit 6cc1855d36 against the Ignite 2 checkout. 
The change is limited to internal transaction lock-future timeout handling and 
tests; it adds no user-facing API, configuration, command, or documentation 
behavior. Removing Docs Required only.

> 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