ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Lang (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-7081) Increase in partition count silently breaks persistent cache reads and writes
Date Thu, 30 Nov 2017 15:57:00 GMT
Joel Lang created IGNITE-7081:
---------------------------------

             Summary: Increase in partition count silently breaks persistent cache reads and
writes
                 Key: IGNITE-7081
                 URL: https://issues.apache.org/jira/browse/IGNITE-7081
             Project: Ignite
          Issue Type: Bug
          Components: persistence
    Affects Versions: 2.3
            Reporter: Joel Lang
            Priority: Minor


An increase in the partition count for a cache to even out distribution between nodes lead
to bad, inconsistent behavior in the cache.

Gets on known keys would return null due to the partition number being different even as SQL
queries would still find the cache entry through its own means.

Removals of these cache entries using SQL would also fail.

It took several hours to track down the issue because of the inconsistency of the behavior
between SQL queries and a call to get().

Changing the partition count would not have been an issue before we used native persistence
but now it is.

I believe the solution is to have a more rigid verification of the stored cache configuration
against the live cache configuration when the cache starts. It should fail if any configuration
changes are made that would cause problems. It also makes me wonder what other changes are
safe or not to make to a cache configuration that is persistent.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message