You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Yaroslav Molochkov (Jira)" <ji...@apache.org> on 2021/01/01 13:32:00 UTC

[jira] [Created] (IGNITE-13949) Insufficient synchronisation in PartitionUpdateCounterTrackingImpl

Yaroslav Molochkov created IGNITE-13949:
-------------------------------------------

             Summary: Insufficient synchronisation in PartitionUpdateCounterTrackingImpl
                 Key: IGNITE-13949
                 URL: https://issues.apache.org/jira/browse/IGNITE-13949
             Project: Ignite
          Issue Type: Bug
    Affects Versions: 2.9.1
            Reporter: Yaroslav Molochkov
            Assignee: Yaroslav Molochkov


Right now org.apache.ignite.internal.processors.cache.PartitionUpdateCounterTrackingImpl has 2 AtomicLong variables, cntr and reserveCntr, but there are some methods, that are unsynchronised, e.g. next:
{code:java}
@Override public long next() {
    long next = cntr.incrementAndGet();

    reserveCntr.set(next);

    return next;
} {code}

Even though both are AtomicLong, operation like "get then set" is a composite one and should be atomic in the context of an object that holds these variables.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)