[
https://issues.apache.org/jira/browse/IGNITE-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14569248#comment-14569248
]
Yakov Zhdanov commented on IGNITE-936:
--------------------------------------
I see several topology changes:
{code}
[14:45:32,633][WARN ][ignite-update-notifier-timer][GridUpdateNotifier] New
version is available at
http://www.gridgain.com/download/editions/#enterprise-edition: 7.0.5
[14:45:33,263][INFO ][disco-event-worker-#46%null%][GridDiscoveryManager] Added
new node to topology: TcpDiscoveryNode
[id=75885fb9-4694-4b79-9afc-e30cb362b70f, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2, loc=false,
ver=1.0.6#20150520-sha1:4b4158f7, isClient=false]
[14:45:33,264][INFO ][disco-event-worker-#46%null%][GridDiscoveryManager]
Topology snapshot [ver=2, nodes=2, CPUs=8, heap=6.9GB]
[14:45:34,855][INFO ][disco-event-worker-#46%null%][GridDiscoveryManager] Node
left topology: TcpDiscoveryNode [id=75885fb9-4694-4b79-9afc-e30cb362b70f,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2,
intOrder=2, loc=false, ver=1.0.6#20150520-sha1:4b4158f7, isClient=false]
[14:45:34,856][INFO ][disco-event-worker-#46%null%][GridDiscoveryManager]
Topology snapshot [ver=3, nodes=1, CPUs=8, heap=3.5GB]
[14:45:34,862][WARN ][grid-nio-worker-0-#35%null%][TcpDiscoverySpi] Failed to
ping node (status check will be initiated): 75885fb9-4694-4b79-9afc-e30cb362b70f
[14:45:47,934][INFO ][disco-event-worker-#46%null%][GridDiscoveryManager] Added
new node to topology: TcpDiscoveryNode
[id=3f1e6bf8-5ff6-4a61-9ec6-99963bed1b10, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:47501], discPort=47501, order=4, intOrder=3, loc=false,
ver=1.0.6#20150520-sha1:4b4158f7, isClient=false]
[14:45:47,935][INFO ][disco-event-worker-#46%null%][GridDiscoveryManager]
Topology snapshot [ver=4, nodes=2, CPUs=8, heap=6.9GB]
[14:45:49,198][INFO ][disco-event-worker-#46%null%][GridDiscoveryManager] Node
left topology: TcpDiscoveryNode [id=3f1e6bf8-5ff6-4a61-9ec6-99963bed1b10,
addrs=[127.0.0.1], sockAddrs=[/127.0.0.1:47501], discPort=47501, order=4,
intOrder=3, loc=false, ver=1.0.6#20150520-sha1:4b4158f7, isClient=false]
[14:45:49,201][INFO ][disco-event-worker-#46%null%][GridDiscoveryManager]
Topology snapshot [ver=5, nodes=1, CPUs=8, heap=3.5GB]
{code}
Please advice
> 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)
