[jira] [Updated] (IGNITE-7472) Exchange initiated by custom disco events could hang in case of coordinator leave

2019-10-02 Thread Maxim Muzafarov (Jira) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Maxim Muzafarov updated IGNITE-7472:

Fix Version/s: (was: 2.8)

> Exchange initiated by custom disco events could hang in case of coordinator 
> leave
> -
>
> Key: IGNITE-7472
> URL: https://issues.apache.org/jira/browse/IGNITE-7472
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
>
> Reproducer: {{WalModeChangeAdvancedSelfTest.testServerRestartCoordinator}}
> WAL mode change operation initiates an exchange through custom discovery 
> event. The test does the following:
> 1) Initiate constant flow of such events from one node
> 2) Constantly stops current coordinator node and start another one sever node 
> Debug shows the following:
> 1) Remaining client nodes is on exchange X, waiting for new coordinator to 
> send affinity message
> 2) New coordinator is on exchange [X+1], waiting for client to send partition 
> message



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (IGNITE-7472) Exchange initiated by custom disco events could hang in case of coordinator leave

2018-09-27 Thread Vladimir Ozerov (JIRA) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7472:

Fix Version/s: (was: 2.7)
   2.8

> Exchange initiated by custom disco events could hang in case of coordinator 
> leave
> -
>
> Key: IGNITE-7472
> URL: https://issues.apache.org/jira/browse/IGNITE-7472
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Reproducer: {{WalModeChangeAdvancedSelfTest.testServerRestartCoordinator}}
> WAL mode change operation initiates an exchange through custom discovery 
> event. The test does the following:
> 1) Initiate constant flow of such events from one node
> 2) Constantly stops current coordinator node and start another one sever node 
> Debug shows the following:
> 1) Remaining client nodes is on exchange X, waiting for new coordinator to 
> send affinity message
> 2) New coordinator is on exchange [X+1], waiting for client to send partition 
> message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7472) Exchange initiated by custom disco events could hang in case of coordinator leave

2018-09-25 Thread Nikolay Izhikov (JIRA) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikolay Izhikov updated IGNITE-7472:

Fix Version/s: (was: 2.8)
   2.7

> Exchange initiated by custom disco events could hang in case of coordinator 
> leave
> -
>
> Key: IGNITE-7472
> URL: https://issues.apache.org/jira/browse/IGNITE-7472
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Reproducer: {{WalModeChangeAdvancedSelfTest.testServerRestartCoordinator}}
> WAL mode change operation initiates an exchange through custom discovery 
> event. The test does the following:
> 1) Initiate constant flow of such events from one node
> 2) Constantly stops current coordinator node and start another one sever node 
> Debug shows the following:
> 1) Remaining client nodes is on exchange X, waiting for new coordinator to 
> send affinity message
> 2) New coordinator is on exchange [X+1], waiting for client to send partition 
> message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7472) Exchange initiated by custom disco events could hang in case of coordinator leave

2018-09-24 Thread Nikolay Izhikov (JIRA) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nikolay Izhikov updated IGNITE-7472:

Fix Version/s: (was: 2.7)
   2.8

> Exchange initiated by custom disco events could hang in case of coordinator 
> leave
> -
>
> Key: IGNITE-7472
> URL: https://issues.apache.org/jira/browse/IGNITE-7472
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Reproducer: {{WalModeChangeAdvancedSelfTest.testServerRestartCoordinator}}
> WAL mode change operation initiates an exchange through custom discovery 
> event. The test does the following:
> 1) Initiate constant flow of such events from one node
> 2) Constantly stops current coordinator node and start another one sever node 
> Debug shows the following:
> 1) Remaining client nodes is on exchange X, waiting for new coordinator to 
> send affinity message
> 2) New coordinator is on exchange [X+1], waiting for client to send partition 
> message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7472) Exchange initiated by custom disco events could hang in case of coordinator leave

2018-06-26 Thread Dmitriy Pavlov (JIRA) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dmitriy Pavlov updated IGNITE-7472:
---
Fix Version/s: (was: 2.6)
   2.7

> Exchange initiated by custom disco events could hang in case of coordinator 
> leave
> -
>
> Key: IGNITE-7472
> URL: https://issues.apache.org/jira/browse/IGNITE-7472
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.7
>
>
> Reproducer: {{WalModeChangeAdvancedSelfTest.testServerRestartCoordinator}}
> WAL mode change operation initiates an exchange through custom discovery 
> event. The test does the following:
> 1) Initiate constant flow of such events from one node
> 2) Constantly stops current coordinator node and start another one sever node 
> Debug shows the following:
> 1) Remaining client nodes is on exchange X, waiting for new coordinator to 
> send affinity message
> 2) New coordinator is on exchange [X+1], waiting for client to send partition 
> message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7472) Exchange initiated by custom disco events could hang in case of coordinator leave

2018-06-18 Thread Vladimir Ozerov (JIRA) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7472:

Priority: Critical  (was: Major)

> Exchange initiated by custom disco events could hang in case of coordinator 
> leave
> -
>
> Key: IGNITE-7472
> URL: https://issues.apache.org/jira/browse/IGNITE-7472
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Reproducer: {{WalModeChangeAdvancedSelfTest.testServerRestartCoordinator}}
> WAL mode change operation initiates an exchange through custom discovery 
> event. The test does the following:
> 1) Initiate constant flow of such events from one node
> 2) Constantly stops current coordinator node and start another one sever node 
> Debug shows the following:
> 1) Remaining client nodes is on exchange X, waiting for new coordinator to 
> send affinity message
> 2) New coordinator is on exchange [X+1], waiting for client to send partition 
> message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7472) Exchange initiated by custom disco events could hang in case of coordinator leave

2018-06-18 Thread Vladimir Ozerov (JIRA) 


 [ 
https://issues.apache.org/jira/browse/IGNITE-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vladimir Ozerov updated IGNITE-7472:

Labels: MakeTeamcityGreenAgain  (was: )

> Exchange initiated by custom disco events could hang in case of coordinator 
> leave
> -
>
> Key: IGNITE-7472
> URL: https://issues.apache.org/jira/browse/IGNITE-7472
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Reproducer: {{WalModeChangeAdvancedSelfTest.testServerRestartCoordinator}}
> WAL mode change operation initiates an exchange through custom discovery 
> event. The test does the following:
> 1) Initiate constant flow of such events from one node
> 2) Constantly stops current coordinator node and start another one sever node 
> Debug shows the following:
> 1) Remaining client nodes is on exchange X, waiting for new coordinator to 
> send affinity message
> 2) New coordinator is on exchange [X+1], waiting for client to send partition 
> message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7472) Exchange initiated by custom disco events could hang in case of coordinator leave

2018-04-18 Thread Andrey Gura (JIRA) 

 [ 
https://issues.apache.org/jira/browse/IGNITE-7472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Gura updated IGNITE-7472:

Fix Version/s: (was: 2.5)
   2.6

> Exchange initiated by custom disco events could hang in case of coordinator 
> leave
> -
>
> Key: IGNITE-7472
> URL: https://issues.apache.org/jira/browse/IGNITE-7472
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.4
>Reporter: Vladimir Ozerov
>Priority: Major
> Fix For: 2.6
>
>
> Reproducer: {{WalModeChangeAdvancedSelfTest.testServerRestartCoordinator}}
> WAL mode change operation initiates an exchange through custom discovery 
> event. The test does the following:
> 1) Initiate constant flow of such events from one node
> 2) Constantly stops current coordinator node and start another one sever node 
> Debug shows the following:
> 1) Remaining client nodes is on exchange X, waiting for new coordinator to 
> send affinity message
> 2) New coordinator is on exchange [X+1], waiting for client to send partition 
> message



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)