ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dmitry Pavlov <dpavlov....@gmail.com>
Subject Re: Ignite 2.0.0 GridUnsafe unmonitor
Date Tue, 31 Oct 2017 10:55:55 GMT
I agree with Denis, if we don't have such warning we should continiously
warn users in wiki pages/blogs/presentations. It is simpler to warn from
code.

What do you think if we will issue warning only if size > 1. HashMap with 1
item will not cause deadlock. Moreover where can be some custom singleton
Map provided by user.

Sincerely,
Dmitriy Pavlov

вт, 31 окт. 2017 г. в 7:18, Dmitriy Setrakyan <dsetrakyan@apache.org>:

> Denis,
>
> We should definitely print out a thorough warning if HashMap is passed into
> a bulk method (instead of SortedMap). However, we should make sure that we
> only print that warning once and not ever time the API is called.
>
> Can you please file a ticket for 2.4?
>
> D.
>
> On Thu, Oct 26, 2017 at 11:05 AM, Denis Magda <dmagda@apache.org> wrote:
>
> > + dev list
> >
> > Igniters, that’s a relevant point below. Newcomers to Ignite tend to
> > stumble on deadlocks simply because the keys are passed in an unordered
> > HashMap. Propose to do the following:
> > - update bulk operations Java doc.
> > - print out a warning if a HashMap is used and its exceeds one element.
>
>
> > Thoughts?
> >
> > —
> > Denis
> >
> > > On Oct 21, 2017, at 6:16 PM, dark <ekdxhrl0096@gmail.com> wrote:
> > >
> > > Many people seem to be more likely to send Cache entries in bulk via a
> > > HashMap.
> > > How do you expose a warning statement by checking if the TreeMap is
> > putAll
> > > inside the code?
> > >
> > >
> > >
> > >
> > > --
> > > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
> >
> >
>

Mime
View raw message