ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Artem Shutak (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1635) Cache.invoke() can work wrong in a failover scenario
Date Tue, 13 Oct 2015 18:56:05 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955467#comment-14955467
] 

Artem Shutak commented on IGNITE-1635:
--------------------------------------

Added a unit-test to reproduce the issue. 
Please, review.

> Cache.invoke() can work wrong in a failover scenario
> ----------------------------------------------------
>
>                 Key: IGNITE-1635
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1635
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Artem Shutak
>            Assignee: Artem Shutak
>             Fix For: 1.5
>
>         Attachments: logsAndEtc.zip
>
>
> In process of working on IGNITE-1397 (Load/consistency test framework) I've faced with
a wrong cache state after Cache.invoke().
> Configuration:
> - 1 client node
> - 3 server nodes (1 backup)
> - duration - 3 hours
> - one random server node is killed every 10 min and after 2 minutes started again
> h5. Transactional invoke retry consistency
> Each client generates a random integer K in a limited range (say, [0, 100000]) and creates
a batch of 5 (may be configured) keys in the form 'key-' + K + '-' + n + '-1', 'key-' + K
+ '-' + n + '-2', ... where n is a unique sequence number assigned to the client. Each client
maintains a local map that it updates together with cache. Client invokes an increment closure
for all generated keys (no explicit transaction is used) and atomically increments value for
corresponding keys in the local map. No exceptions must be thrown to the user code. To validate
cache contents, all writes from the client should be stopped, values in the local map must
be equal to the values in the cache.
> After 25 min in logs of client: {{Got different values [key='key-89611-0-3', cacheVal=213,
localMapVal=214]}}.
> All other "key-89611-0-*" keys in cache have value 214. For the key 'key-89611-0-3' incremental
cache invoke didn't happen.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message