ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Pavlov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-6804) Print a warning if HashMap is passed into bulk update operations
Date Tue, 31 Oct 2017 19:42:00 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-6804?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitriy Pavlov updated IGNITE-6804:
-----------------------------------
    Description: 
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

  was:
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 HashMap 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.

More details are here:
http://apache-ignite-developers.2346864.n4.nabble.com/Re-Ignite-2-0-0-GridUnsafe-unmonitor-td23706.html


> 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
>      Security Level: Public(Viewable by anyone) 
>          Components: cache
>            Reporter: Denis Magda
>            Priority: Critical
>              Labels: usability
>             Fix For: 2.4
>
>
> 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
(v6.4.14#64029)

Mime
View raw message