You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vasilisa Sidorova (JIRA)" <ji...@apache.org> on 2015/06/05 21:13:00 UTC
[jira] [Assigned] (IGNITE-936) Wrong result for MemcacheRestExample
for specific scenario
[ https://issues.apache.org/jira/browse/IGNITE-936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vasilisa Sidorova reassigned IGNITE-936:
----------------------------------------
Assignee: Yakov Zhdanov (was: Vasilisa Sidorova)
Yakov, according to scenario, topology with one node is single MemcacheRestExampleNodeStartup, topology with 2 nodes is MemcacheRestExampleNodeStartup + MemcacheRestExample and MemcacheRestExample was running several times. Is it clear?
> Wrong result for MemcacheRestExample for specific scenario
> ----------------------------------------------------------
>
> Key: IGNITE-936
> URL: https://issues.apache.org/jira/browse/IGNITE-936
> Project: Ignite
> Issue Type: Bug
> Affects Versions: sprint-5
> Environment: Ubuntu 14.04, community version 1.0.6, build 22, rev. 4b4158f752ee1565539ca4977464f8d7ee6de40b
> Reporter: Vasilisa Sidorova
> Assignee: Yakov Zhdanov
> Fix For: sprint-5
>
> Attachments: example_node.log, remote_node.log
>
>
> ---------------------------------------------
> DESCRIPTION
> ---------------------------------------------
> The actual result of example is different from expected in case several nodes are started and example is running several times. If cluster isn't restarted after example execution then new atomic long value each example running increase on 2
> ---------------------------------------------
> STEPS FOR REPRODUCE
> ---------------------------------------------
> 1. Run at least one MemcacheRestExampleNodeStartup
> 2. Run MemcacheRestExample (actual result = expected)
> 3.Run example one more time
> ---------------------------------------------
> ACTUAL RESULT
> ---------------------------------------------
> Last two result lines have wrong atomic long value:
> {noformat}
> >>> New atomic long value: 18 (expected: 16).
> >>> New atomic long value: 14 (expected: 12).
> {noformat}
> Look at attached nodes logs
> ---------------------------------------------
> EXPECTED RESULT
> ---------------------------------------------
> Actual atomic long value = expected and independent of the example running's number in the one cluster
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)