[
https://issues.apache.org/jira/browse/IGNITE-23388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17890224#comment-17890224
]
Maksim Timonin commented on IGNITE-23388:
-----------------------------------------
TC RunAll for ignite-extensions is successfull
[https://ci2.ignite.apache.org/buildConfiguration/IgniteExtensions_Tests_Cdc/8115618?buildTab=changes&showFiles=false&expandRevisionsSection=true&showBuilds=true&showGraph=true]
> Deadlock in transactions started by IgniteToIgniteCdcStreamer
> -------------------------------------------------------------
>
> Key: IGNITE-23388
> URL: https://issues.apache.org/jira/browse/IGNITE-23388
> Project: Ignite
> Issue Type: Bug
> Reporter: Maksim Timonin
> Assignee: Maksim Timonin
> Priority: Major
> Labels: ise
> Fix For: 2.17
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> IgniteToIgniteCdcStreamer collects changes in batch size (configured with
> maxBatchSize). Then all updates put to target cluster with `putAllConflict`.
> This call creates transaction that covers all entries, primary and backups.
> Then 2 streamer on different nodes might have crossing set of entries
> (primary and backups). The set is not ordered and inserted as ordinary
> HashMap. It leads to deadlock.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
