[jira] [Comment Edited] (IGNITE-8048) Dynamic indexes are not stored to cache data on node join

2018-04-12 Thread Eduard Shangareev (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435749#comment-16435749
 ] 

Eduard Shangareev edited comment on IGNITE-8048 at 4/12/18 3:25 PM:


I have checked your changes. Please, check upsource.

Also, I should say that test coverage is not complete.

 
|Active cluster|Joining node|Result|Test|
| |+ INDEX / COLUMN|Node 
reject|testFailJoiningNodeBecauseNeedConfigUpdateOnActiveGrid|
| |--INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN| |Node join|testTakeChangedConfigOnActiveGrid|
|--INDEX / COLUMN| |Node join|No test|
|CONFLICT| |Node reject|No test|

 
|Inactive cluster|Joining node|Result|Test|
|+ INDEX / COLUMN| |Node join|testMergeChangedConfigOnCoordinator|
| |+ INDEX / COLUMN|Node join|No test|
|--INDEX / COLUMN| |Node join|testMergeChangedConfigOnInactiveGrid|
| |--INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN|+ INDEX / COLUMN|Node join|No test|
|--INDEX / COLUMN|--INDEX / COLUMN|Node join|No test|
|CONFLICT| |Node reject|testFailJoiningNodeBecauseDifferentSql|


was (Author: edshanggg):
I have checked your changes. Please, check upsource.

Also, I should say that test coverage is not complete.

 
|Active cluster|Joining node|Result|Test|
| |+ INDEX / COLUMN|Node 
reject|testFailJoiningNodeBecauseNeedConfigUpdateOnActiveGrid|
| |--INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN| |Node join|testTakeChangedConfigOnActiveGrid|
|--INDEX / COLUMN| |Node join|No test|
|CONFLICT| |Node reject|No test|

 
|Inactive cluster|Joining node|Result|Test|
|+ INDEX / COLUMN| |Node join|testMergeChangedConfigOnCoordinator|
| |+ INDEX / COLUMN|Node join|No test|
|--INDEX / COLUMN| |Node join|testMergeChangedConfigOnInactiveGrid|
| |--INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN|+ INDEX / COLUMN|Node join|No test|
|--INDEX / COLUMN|--INDEX / COLUMN|Node join|No test|
|CONFLICT|Node reject|testFailJoiningNodeBecauseDifferentSql|

> Dynamic indexes are not stored to cache data on node join
> -
>
> Key: IGNITE-8048
> URL: https://issues.apache.org/jira/browse/IGNITE-8048
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.4
>Reporter: Alexey Goncharuk
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.5
>
> Attachments: IgniteDynamicIndexRestoreTest.java
>
>
> Consider the following scenario:
> 1) Start nodes, add some data
> 2) Shutdown a node, create a dynamic index
> 3) Shutdown the whole cluster, startup with the absent node, activate from 
> the absent node
> 4) Since the absent node did not 'see' the create index, index will not be 
> active after cluster activation
> 5) Update some data in the cluster
> 6) Restart the cluster, but activate from the node which did 'see' the create 
> index
> 7) Attempt to update data. Depending on the updates in (5), this will either 
> hang or result in an exception



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


[jira] [Comment Edited] (IGNITE-8048) Dynamic indexes are not stored to cache data on node join

2018-04-12 Thread Eduard Shangareev (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435749#comment-16435749
 ] 

Eduard Shangareev edited comment on IGNITE-8048 at 4/12/18 3:25 PM:


I have checked your changes. Please, check upsource.

Also, I should say that test coverage is not complete.

 
|Active cluster|Joining node|Result|Test|
| |+ INDEX / COLUMN|Node 
reject|testFailJoiningNodeBecauseNeedConfigUpdateOnActiveGrid|
| |--INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN| |Node join|testTakeChangedConfigOnActiveGrid|
|--INDEX / COLUMN| |Node join|No test|
|CONFLICT| |Node reject|No test|

 
|Inactive cluster|Joining node|Result|Test|
|+ INDEX / COLUMN| |Node join|testMergeChangedConfigOnCoordinator|
| |+ INDEX / COLUMN|Node join|No test|
|--INDEX / COLUMN| |Node join|testMergeChangedConfigOnInactiveGrid|
| |--INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN|+ INDEX / COLUMN|Node join|No test|
|--INDEX / COLUMN|--INDEX / COLUMN|Node join|No test|
|CONFLICT|Node reject|testFailJoiningNodeBecauseDifferentSql|


was (Author: edshanggg):
I have checked your changes. Please, check upsource.

Also, I should say that test coverage is not complete.

 
|Active cluster|Joining node|Result|Test|
| |+ INDEX / COLUMN|Node 
reject|testFailJoiningNodeBecauseNeedConfigUpdateOnActiveGrid|
| | - INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN| |Node join|testTakeChangedConfigOnActiveGrid|
|- INDEX / COLUMN| |Node join|No test|
|CONFLICT| |Node reject|No test|

 
|Inactive cluster|Joining node|Result|Test|
|+ INDEX / COLUMN| |Node join|testMergeChangedConfigOnCoordinator|
| |+ INDEX / COLUMN|Node join|No test|
|- INDEX / COLUMN| |Node join|testMergeChangedConfigOnInactiveGrid|
| |- INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN|+ INDEX / COLUMN|Node join|No test|
|- INDEX / COLUMN|- INDEX / COLUMN|Node join|No test|
|CONFLICT|Node reject|testFailJoiningNodeBecauseDifferentSql|

> Dynamic indexes are not stored to cache data on node join
> -
>
> Key: IGNITE-8048
> URL: https://issues.apache.org/jira/browse/IGNITE-8048
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.4
>Reporter: Alexey Goncharuk
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.5
>
> Attachments: IgniteDynamicIndexRestoreTest.java
>
>
> Consider the following scenario:
> 1) Start nodes, add some data
> 2) Shutdown a node, create a dynamic index
> 3) Shutdown the whole cluster, startup with the absent node, activate from 
> the absent node
> 4) Since the absent node did not 'see' the create index, index will not be 
> active after cluster activation
> 5) Update some data in the cluster
> 6) Restart the cluster, but activate from the node which did 'see' the create 
> index
> 7) Attempt to update data. Depending on the updates in (5), this will either 
> hang or result in an exception



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


[jira] [Comment Edited] (IGNITE-8048) Dynamic indexes are not stored to cache data on node join

2018-04-12 Thread Eduard Shangareev (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435749#comment-16435749
 ] 

Eduard Shangareev edited comment on IGNITE-8048 at 4/12/18 3:24 PM:


I have checked your changes. Please, check upsource.

Also, I should say that test coverage is not complete.

 
|Active cluster|Joining node|Result|Test|
| |+ INDEX / COLUMN|Node 
reject|testFailJoiningNodeBecauseNeedConfigUpdateOnActiveGrid|
| | - INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN| |Node join|testTakeChangedConfigOnActiveGrid|
| - INDEX / COLUMN| |Node join|No test|
|CONFLICT| |Node reject|No test|

 
|Inactive cluster|Joining node|Result|Test|
|+ INDEX / COLUMN| |Node join|testMergeChangedConfigOnCoordinator|
| |+ INDEX / COLUMN|Node join|No test|
| - INDEX / COLUMN| |Node join|testMergeChangedConfigOnInactiveGrid|
| | - INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN|+ INDEX / COLUMN|Node join|No test|
| - INDEX / COLUMN| - INDEX / COLUMN|Node join|No test|
|CONFLICT|Node reject|testFailJoiningNodeBecauseDifferentSql|


was (Author: edshanggg):
I have checked your changes. Please, check upsource.

Also, I should say that test coverage is not complete.

 
|Active cluster|Joining node|Result|Test|
| |+ INDEX / COLUMN|Node 
reject|testFailJoiningNodeBecauseNeedConfigUpdateOnActiveGrid|
| |- INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN| |Node join|testTakeChangedConfigOnActiveGrid|
|- INDEX / COLUMN| |Node join|No test|
|CONFLICT|Node reject|No test|

 
|Inactive cluster|Joining node|Result|Test|
|+ INDEX / COLUMN| |Node join|testMergeChangedConfigOnCoordinator|
| |+ INDEX / COLUMN|Node join|No test|
|- INDEX / COLUMN| |Node join|testMergeChangedConfigOnInactiveGrid|
| |- INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN|+ INDEX / COLUMN|Node join|No test|
|- INDEX / COLUMN|- INDEX / COLUMN|Node join|No test|
|CONFLICT|Node reject|testFailJoiningNodeBecauseDifferentSql|

> Dynamic indexes are not stored to cache data on node join
> -
>
> Key: IGNITE-8048
> URL: https://issues.apache.org/jira/browse/IGNITE-8048
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.4
>Reporter: Alexey Goncharuk
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.5
>
> Attachments: IgniteDynamicIndexRestoreTest.java
>
>
> Consider the following scenario:
> 1) Start nodes, add some data
> 2) Shutdown a node, create a dynamic index
> 3) Shutdown the whole cluster, startup with the absent node, activate from 
> the absent node
> 4) Since the absent node did not 'see' the create index, index will not be 
> active after cluster activation
> 5) Update some data in the cluster
> 6) Restart the cluster, but activate from the node which did 'see' the create 
> index
> 7) Attempt to update data. Depending on the updates in (5), this will either 
> hang or result in an exception



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


[jira] [Comment Edited] (IGNITE-8048) Dynamic indexes are not stored to cache data on node join

2018-04-12 Thread Eduard Shangareev (JIRA)

[ 
https://issues.apache.org/jira/browse/IGNITE-8048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16435749#comment-16435749
 ] 

Eduard Shangareev edited comment on IGNITE-8048 at 4/12/18 3:24 PM:


I have checked your changes. Please, check upsource.

Also, I should say that test coverage is not complete.

 
|Active cluster|Joining node|Result|Test|
| |+ INDEX / COLUMN|Node 
reject|testFailJoiningNodeBecauseNeedConfigUpdateOnActiveGrid|
| | - INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN| |Node join|testTakeChangedConfigOnActiveGrid|
|- INDEX / COLUMN| |Node join|No test|
|CONFLICT| |Node reject|No test|

 
|Inactive cluster|Joining node|Result|Test|
|+ INDEX / COLUMN| |Node join|testMergeChangedConfigOnCoordinator|
| |+ INDEX / COLUMN|Node join|No test|
|- INDEX / COLUMN| |Node join|testMergeChangedConfigOnInactiveGrid|
| |- INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN|+ INDEX / COLUMN|Node join|No test|
|- INDEX / COLUMN|- INDEX / COLUMN|Node join|No test|
|CONFLICT|Node reject|testFailJoiningNodeBecauseDifferentSql|


was (Author: edshanggg):
I have checked your changes. Please, check upsource.

Also, I should say that test coverage is not complete.

 
|Active cluster|Joining node|Result|Test|
| |+ INDEX / COLUMN|Node 
reject|testFailJoiningNodeBecauseNeedConfigUpdateOnActiveGrid|
| | - INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN| |Node join|testTakeChangedConfigOnActiveGrid|
| - INDEX / COLUMN| |Node join|No test|
|CONFLICT| |Node reject|No test|

 
|Inactive cluster|Joining node|Result|Test|
|+ INDEX / COLUMN| |Node join|testMergeChangedConfigOnCoordinator|
| |+ INDEX / COLUMN|Node join|No test|
| - INDEX / COLUMN| |Node join|testMergeChangedConfigOnInactiveGrid|
| | - INDEX / COLUMN|Node join|No test|
|+ INDEX / COLUMN|+ INDEX / COLUMN|Node join|No test|
| - INDEX / COLUMN| - INDEX / COLUMN|Node join|No test|
|CONFLICT|Node reject|testFailJoiningNodeBecauseDifferentSql|

> Dynamic indexes are not stored to cache data on node join
> -
>
> Key: IGNITE-8048
> URL: https://issues.apache.org/jira/browse/IGNITE-8048
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.4
>Reporter: Alexey Goncharuk
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.5
>
> Attachments: IgniteDynamicIndexRestoreTest.java
>
>
> Consider the following scenario:
> 1) Start nodes, add some data
> 2) Shutdown a node, create a dynamic index
> 3) Shutdown the whole cluster, startup with the absent node, activate from 
> the absent node
> 4) Since the absent node did not 'see' the create index, index will not be 
> active after cluster activation
> 5) Update some data in the cluster
> 6) Restart the cluster, but activate from the node which did 'see' the create 
> index
> 7) Attempt to update data. Depending on the updates in (5), this will either 
> hang or result in an exception



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