ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Rakov (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-11465) Multiple client leave/join events may wipe affinity assignment history and cause transactions fail
Date Sat, 02 Mar 2019 20:55:00 GMT
Ivan Rakov created IGNITE-11465:
-----------------------------------

             Summary: Multiple client leave/join events may wipe affinity assignment history
and cause transactions fail
                 Key: IGNITE-11465
                 URL: https://issues.apache.org/jira/browse/IGNITE-11465
             Project: Ignite
          Issue Type: Bug
            Reporter: Ivan Rakov
            Assignee: Ivan Rakov
             Fix For: 2.8


We keep history of GridAffinityAssignmentCache#MAX_HIST_SIZE affinity assignments, however
flood of client joins/leaves may wipe it out entirely and cause fail/hang of transaction that
was started before the flood:
{code:java}
            if (cache == null || cache.topologyVersion().compareTo(topVer) > 0) {
                throw new IllegalStateException("Getting affinity for topology version earlier
than affinity is " +
                    "calculated [locNode=" + ctx.discovery().localNode() +
                    ", grp=" + cacheOrGrpName +
                    ", topVer=" + topVer +
                    ", head=" + head.get().topologyVersion() +
                    ", history=" + affCache.keySet() +
                    ']');
            }
{code}
History is limited in order to prevent JVM heap overflow. At the same time, only "server event"
affinity assignments are heavy: "client event" assignments are just shallow copies of "server
event" assignments.
I suggest to limit history by the number of "server event" assignments.
Also, consider the provided fix, I don't see any need to keep 500 items in history. I changed
history size to 40.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message