[
https://issues.apache.org/jira/browse/IGNITE-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955448#comment-14955448
]
ASF GitHub Bot commented on IGNITE-1635:
----------------------------------------
GitHub user ashutakGG opened a pull request:
https://github.com/apache/ignite/pull/152
IGNITE-1635 Added reproduciable unit-test for the bug
https://issues.apache.org/jira/browse/IGNITE-1635
Added reproduciable unit-test for the bug.
Also added test for https://issues.apache.org/jira/browse/IGNITE-1616, but
test do not reproduce the issue.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ashutakGG/incubator-ignite ignite-1635-test
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/152.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #152
----
commit c399b99a9890d348a610af820dbbae515e2e1173
Author: ashutak <ashu...@gridgain.com>
Date: 2015-10-13T16:07:44Z
IgniteFailoverSelfTest
commit 7146a964d83070a28295ba52b31e0422c3f8721e
Author: ashutak <ashu...@gridgain.com>
Date: 2015-10-13T17:28:14Z
extract abstract restart test
commit e2fe9ae094dfaef6e030ff6135a063b5c7e2a2aa
Author: ashutak <ashu...@gridgain.com>
Date: 2015-10-13T18:37:48Z
add CacheNearDisabledTransactionalWriteReadRestartSelfTest
commit ed0873f78872978412354e635ddb82d05903a7f9
Author: ashutak <ashu...@gridgain.com>
Date: 2015-10-13T18:38:41Z
typo
commit 3d182a9cb2288b95af43884e3e03fe248415325c
Author: ashutak <ashu...@gridgain.com>
Date: 2015-10-13T18:43:41Z
add test suite
----
> 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)
