[
https://issues.apache.org/jira/browse/IGNITE-7984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16404673#comment-16404673
]
ASF GitHub Bot commented on IGNITE-7984:
----------------------------------------
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/3655
IGNITE-7984
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-7984
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3655.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3655
----
----
> DML: improve deadlock handling
> -------------------------------
>
> Key: IGNITE-7984
> URL: https://issues.apache.org/jira/browse/IGNITE-7984
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 2.4
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Priority: Major
> Fix For: 2.5
>
>
> Current DML implementation is not transactional. It groups keys in batches by
> their affinity, and then flushes that batches synchronously. This could lead
> to deadlocks easily.
> This could be improved if we sort key within a batch. However, this would
> require new comparison function for {{BinaryObjectImpl}}, as it is not
> comparable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
