ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ilya Kasnacheev (Jira)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6804) Print a warning if HashMap is passed into bulk update operations
Date Wed, 16 Oct 2019 09:11:00 GMT

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

Ilya Kasnacheev commented on IGNITE-6804:

[~ptupitsyn]If you have exactly the same number of same keys every time, it will work. If
you have different sets of keys, deadlock.

> Print a warning if HashMap is passed into bulk update operations
> ----------------------------------------------------------------
>                 Key: IGNITE-6804
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6804
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>            Reporter: Denis A. Magda
>            Assignee: Ilya Kasnacheev
>            Priority: Critical
>              Labels: usability
>          Time Spent: 10m
>  Remaining Estimate: 0h
> Ignite newcomers tend to stumble on deadlocks simply because the keys are passed in an
unordered HashMap. Propose to do the following:
> * update bulk operations Java docs.
> * print out a warning if not SortedMap (e.g. HashMap, Weak/Identity/Concurrent/Linked
HashMap etc) is passed into
> a bulk method (instead of SortedMap) and contains more than 1 element. However, we should
make sure that we only print that warning once and not every time the API is called.
> * do not produce warning for explicit optimistic transactions
> More details are here:
> http://apache-ignite-developers.2346864.n4.nabble.com/Re-Ignite-2-0-0-GridUnsafe-unmonitor-td23706.html

This message was sent by Atlassian Jira

View raw message