[jira] [Commented] (IGNITE-3897) Test transactional behaviour of caches during rolling restart
[ https://issues.apache.org/jira/browse/IGNITE-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15581787#comment-15581787 ] John Levey commented on IGNITE-3897: Hi Yakov, [~yzhdanov] I replied to your comments on github and updated the pull request with your feedback and fixes. Let me know if there's anything else that should be addressed. Thanks! John > Test transactional behaviour of caches during rolling restart > - > > Key: IGNITE-3897 > URL: https://issues.apache.org/jira/browse/IGNITE-3897 > Project: Ignite > Issue Type: Test > Components: cache >Affects Versions: 1.7 >Reporter: John Levey >Assignee: John Levey > > Create a test that validates the following conditions against a running > cluster that is undergoing a rolling restart: > * Validate a continuous aggregate sum against the cluster during restarts > * Validate transaction handling against the cluster during restarts > See also https://issues.apache.org/jira/browse/IGNITE-3456 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3897) Test transactional behaviour of caches during rolling restart
[ https://issues.apache.org/jira/browse/IGNITE-3897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496261#comment-15496261 ] John Levey commented on IGNITE-3897: New tests pass, but test plan has muted failures related to https://issues.apache.org/jira/browse/IGNITE-1731 See: http://149.202.210.143:8111/viewLog.html?buildId=316424&tab=buildResultsDiv&buildTypeId=IgniteTests_IgniteDataGridFailover > Test transactional behaviour of caches during rolling restart > - > > Key: IGNITE-3897 > URL: https://issues.apache.org/jira/browse/IGNITE-3897 > Project: Ignite > Issue Type: Test > Components: cache >Affects Versions: 1.7 >Reporter: John Levey >Assignee: John Levey > > Create a test that validates the following conditions against a running > cluster that is undergoing a rolling restart: > * Validate a continuous aggregate sum against the cluster during restarts > * Validate transaction handling against the cluster during restarts > See also https://issues.apache.org/jira/browse/IGNITE-3456 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (IGNITE-3897) Test transactional behaviour of caches during rolling restart
John Levey created IGNITE-3897: -- Summary: Test transactional behaviour of caches during rolling restart Key: IGNITE-3897 URL: https://issues.apache.org/jira/browse/IGNITE-3897 Project: Ignite Issue Type: Test Components: cache Affects Versions: 1.7 Reporter: John Levey Assignee: John Levey Create a test that validates the following conditions against a running cluster that is undergoing a rolling restart: * Validate a continuous aggregate sum against the cluster during restarts * Validate transaction handling against the cluster during restarts See also https://issues.apache.org/jira/browse/IGNITE-3456 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (IGNITE-3152) Client node's addresses are registered in IP finder
[ https://issues.apache.org/jira/browse/IGNITE-3152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286923#comment-15286923 ] John Levey commented on IGNITE-3152: >From testing it seems the client is connecting to the grid, and then a server >node is registering the client's addresses with Zookeeper - the client itself >was not responsible for the addresses being registered with Zookeeper. Even >after the client disconnects, the addresses are persisted because the server >which registered them is still connected to Zookeeper. > Client node's addresses are registered in IP finder > --- > > Key: IGNITE-3152 > URL: https://issues.apache.org/jira/browse/IGNITE-3152 > Project: Ignite > Issue Type: Bug > Components: general >Affects Versions: 1.5.0.final >Reporter: Valentin Kulichenko > Labels: important > Fix For: 1.7 > > Attachments: Test.java > > > Currently client node register its addresses in IP finder and never > deregisters them. Also looks like coordinator address is also not removed. > The simple test that shows this behavior is attached. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
