[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-09-05 Thread Vladimir Ozerov (JIRA)


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

Vladimir Ozerov commented on IGNITE-7766:
-

[~ivan.glukos], [~dpavlov], [~ezagumennov], cancelling the patch for now as 
state of the ticket is not clear. 

1) We thought that IGNITE-8694 will fix that. Is this the case? if not - why? 
Do we understand the root cause correctly?

2) Where can I find the latest change? PR attached to the ticket seems to be 
outdated, as I see "ignite-7766-correct" branch in addition to "ignite-7766" 
from which PR is created.

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, sql-stability
>
> Ignite Queries 2 
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%)
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts 
>  Current failure: refs/heads/master #345 No changes 11 Feb 18 03:03
> junit.framework.AssertionFailedError: On large page size must retry.
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-08-14 Thread Vladimir Ozerov (JIRA)


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

Vladimir Ozerov commented on IGNITE-7766:
-

[~ivan.glukos], unfortunately tests still fail even after IGNITE-8694 merge.

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, sql-stability
>
> Ignite Queries 2 
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%)
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts 
>  Current failure: refs/heads/master #345 No changes 11 Feb 18 03:03
> junit.framework.AssertionFailedError: On large page size must retry.
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-06-04 Thread Ivan Rakov (JIRA)


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

Ivan Rakov commented on IGNITE-7766:


Please note that particular case of this issue is fixed under IGNITE-8694. Test 
from description should pass after IGNITE-8694 merge.

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Ignite Queries 2 
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%)
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts 
>  Current failure: refs/heads/master #345 No changes 11 Feb 18 03:03
> junit.framework.AssertionFailedError: On large page size must retry.
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-06-04 Thread Ilya Lantukh (JIRA)


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

Ilya Lantukh commented on IGNITE-7766:
--

Personally I consider proposed solution a dirty hack, that only solves problem 
for 1 specific case.
[~vozerov], can you please take a look as well?

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Ignite Queries 2 
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%)
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts 
>  Current failure: refs/heads/master #345 No changes 11 Feb 18 03:03
> junit.framework.AssertionFailedError: On large page size must retry.
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-06-04 Thread Ilya Lantukh (JIRA)


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

Ilya Lantukh commented on IGNITE-7766:
--

It is theoretically possible that 2 partitioned caches have the same affinity 
function and node filter, but different primary assignments. And so, there 
might be a node that is primary for some partitions of cache1, but isn't for 
cache2 - so it will present in *extraNodes*, but absent in *nodes*.

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Ignite Queries 2 
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%)
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts 
>  Current failure: refs/heads/master #345 No changes 11 Feb 18 03:03
> junit.framework.AssertionFailedError: On large page size must retry.
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-06-01 Thread Alexei Scherbakov (JIRA)


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

Alexei Scherbakov commented on IGNITE-7766:
---

Won't it be enough to specify partitioned cache first and set 
enforceJoinOrder=true to workaround the issue ?

[~agoncharuk],

I don't see any issues related to partitioned-partitioned joining in such 
scenario, could you please elaborate ?

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Ignite Queries 2 
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%)
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts 
>  Current failure: refs/heads/master #345 No changes 11 Feb 18 03:03
> junit.framework.AssertionFailedError: On large page size must retry.
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-06-01 Thread Alexey Goncharuk (JIRA)


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

Alexey Goncharuk commented on IGNITE-7766:
--

[~ezagumennov] I think the fix may be considered as a temporary workaround, but 
we still need to implement a proper fix for partitioned-partitioned cases.

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Ignite Queries 2 
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%)
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts 
>  Current failure: refs/heads/master #345 No changes 11 Feb 18 03:03
> junit.framework.AssertionFailedError: On large page size must retry.
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-06-01 Thread Evgenii Zagumennov (JIRA)


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

Evgenii Zagumennov commented on IGNITE-7766:


[~ilantukh], i've implemented your advice. Now, if the first cache in the 
cacheIds collection is not partitioned, we find it (if it is in cacheIds) and 
move to the index 0. 

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Ignite Queries 2 
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%)
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts 
>  Current failure: refs/heads/master #345 No changes 11 Feb 18 03:03
> junit.framework.AssertionFailedError: On large page size must retry.
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-05-31 Thread Ilya Lantukh (JIRA)


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

Ilya Lantukh commented on IGNITE-7766:
--

This fix doesn't look correct to me. I've debugged this test and can explain 
how this exception happens.

Take a look at GridReduceQueryExecutor.stableDataNodes(...) method. Assume that 
cacheIds.get(0) is ID of replicated cache, and cacheIds.get(1) is partitioned. 
Also, there is one node that has some partitions, but isn't primary for any of 
them.

{noformat}
if (extraCctx.isReplicated()) {
if (isReplicatedOnly) {
nodes.retainAll(extraNodes);

disjoint = map.isEmpty();
}
else
disjoint = !extraNodes.containsAll(nodes);
}
else
disjoint = !extraNodes.equals(nodes);

if (disjoint) {
if (isPreloadingActive(cacheIds))
return null; // Retry.
else
throw new CacheException("Caches have distinct sets of data nodes 
[cache1=" + cctx.name() +
", cache2=" + extraCacheName + "]");
}
{noformat}

Since extraCctx.isReplicated() == false, we check that node sets for both 
caches are equal. These sets are calculated in the 
GridReduceQueryExecutor.stableDataNodesMap(...) method. For replicated caches, 
it will return all data nodes, but for partitioned ones it will return only 
those nodes that are primary for at least one partition. So, *extraNodes* will 
contain that one node that isn't primary, but *nodes* will not, and so disjoint 
== true.

One way to fix it is to ensure that the first cache in the cacheIds collection 
is always partitioned. Another is to add *else if (cctx.isReplicated())* check. 
I'm not sure that such changes won't break any other query-related 
functionality though.

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Ignite Queries 2 
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%)
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts 
>  Current failure: refs/heads/master #345 No changes 11 Feb 18 03:03
> junit.framework.AssertionFailedError: On large page size must retry.
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-05-31 Thread Stanilovsky Evgeny (JIRA)


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

Stanilovsky Evgeny commented on IGNITE-7766:


Test fails only on PARTITIONED cache query operations, in case of unstable 
topology we need tries to repeat operation. instead of throwing CacheException 
"Caches have distinct sets of data nodes".

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Ignite Queries 2 
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%)
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts 
>  Current failure: refs/heads/master #345 No changes 11 Feb 18 03:03
> junit.framework.AssertionFailedError: On large page size must retry.
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-05-30 Thread Vladimir Ozerov (JIRA)


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

Vladimir Ozerov commented on IGNITE-7766:
-

[~ezagumennov], [~dpavlov], [~al.psc], 
At first glance fix looks wrong - what if we really have disjoint node? WIll 
your code be able to terminate? Could you please add a test with two caches and 
different node filters, spanning disjoint nodes. We need to ensure that it 
throws original error message.

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
>Ignite Queries 2  
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
>   Current failure:refs/heads/master   #345No changes  
> 11 Feb 18 03:03
>
> junit.framework.AssertionFailedError: On large page size must retry.
>  
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-05-29 Thread Dmitriy Pavlov (JIRA)


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

Dmitriy Pavlov commented on IGNITE-7766:


Hi [~al.psc], could you please look to the change?

It seems to be not complex, but I'm not able to do sign-off change because I 
don't understand risks of the fix.

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
>Ignite Queries 2  
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
>   Current failure:refs/heads/master   #345No changes  
> 11 Feb 18 03:03
>
> junit.framework.AssertionFailedError: On large page size must retry.
>  
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-05-29 Thread Evgenii Zagumennov (JIRA)


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

Evgenii Zagumennov commented on IGNITE-7766:


Hi, [~dpavlov]. Ok, got it. Moved to *Patch Available*

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
>Ignite Queries 2  
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
>   Current failure:refs/heads/master   #345No changes  
> 11 Feb 18 03:03
>
> junit.framework.AssertionFailedError: On large page size must retry.
>  
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-05-24 Thread Dmitriy Pavlov (JIRA)

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

Dmitriy Pavlov commented on IGNITE-7766:


Hi [~ezagumennov], why issue is resolved, but PR is open. Was this change 
merged? If not, issue should be in Patch Available state

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
>Ignite Queries 2  
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
>   Current failure:refs/heads/master   #345No changes  
> 11 Feb 18 03:03
>
> junit.framework.AssertionFailedError: On large page size must retry.
>  
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-05-21 Thread ASF GitHub Bot (JIRA)

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

ASF GitHub Bot commented on IGNITE-7766:


GitHub user ezagumennov opened a pull request:

https://github.com/apache/ignite/pull/4035

IGNITE-7766 test should retry, not fail



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/gridgain/apache-ignite ignite-7766

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ignite/pull/4035.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #4035


commit 0900e0aee3c82595881a268b9b7b9080e9b350b4
Author: ezagumennov 
Date:   2018-05-21T07:34:11Z

IGNITE-7766 test should retry, not fail




> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
>Ignite Queries 2  
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
>   Current failure:refs/heads/master   #345No changes  
> 11 Feb 18 03:03
>
> junit.framework.AssertionFailedError: On large page size must retry.
>  
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-05-06 Thread Evgenii Zagumennov (JIRA)

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

Evgenii Zagumennov commented on IGNITE-7766:


I've investigated the issue (with "git bisect"). This test started to fail 
after [IGNITE-7195|https://issues.apache.org/jira/browse/IGNITE-7195] was 
fixed. I think, the subject test 
(IgniteCacheQueryNodeRestartTxSelfTest.testRestarts) is not actual anymore.

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Evgenii Zagumennov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
>Ignite Queries 2  
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
>   Current failure:refs/heads/master   #345No changes  
> 11 Feb 18 03:03
>
> junit.framework.AssertionFailedError: On large page size must retry.
>  
> Last runs fails with 100% probability.



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


[jira] [Commented] (IGNITE-7766) Ignite Queries 2: Test always failed IgniteCacheQueryNodeRestartTxSelfTest.testRestarts

2018-03-14 Thread Dmitriy Pavlov (JIRA)

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

Dmitriy Pavlov commented on IGNITE-7766:


[~ascherbakov], are there any news here? What do you think about removal this 
test from run until it is re-engeneered as stable?

> Ignite Queries 2: Test always failed 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
> ---
>
> Key: IGNITE-7766
> URL: https://issues.apache.org/jira/browse/IGNITE-7766
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Dmitriy Pavlov
>Assignee: Alexei Scherbakov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
>Ignite Queries 2  
>  IgniteBinaryCacheQueryTestSuite2: 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts (fail rate 76,1%) 
> IgniteCacheQueryNodeRestartTxSelfTest.testRestarts
>   Current failure:refs/heads/master   #345No changes  
> 11 Feb 18 03:03
>
> junit.framework.AssertionFailedError: On large page size must retry.
>  
> Last runs fails with 100% probability.



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