[jira] [Created] (IGNITE-5981) IgniteContext starts server nodes on executors

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-5981:
---

 Summary: IgniteContext starts server nodes on executors
 Key: IGNITE-5981
 URL: https://issues.apache.org/jira/browse/IGNITE-5981
 Project: Ignite
  Issue Type: Bug
  Components: spark
Affects Versions: 2.1
Reporter: Valentin Kulichenko
 Fix For: 2.2


Currently {{IgniteContext#ignite()}} method creates client node only if it is 
invoked on driver. However, in case standalone mode is used, this should happen 
also executors (or basically anywhere within Spark).

Most likely, it would be enough to replace this line:
{code}
if (sparkContext != null) igniteCfg.setClientMode(true)
{code}
with this:
{code}
if (standalone || sparkContext != null) igniteCfg.setClientMode(true)
{code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5980) [Test Failed] IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5980:
-

 Summary: [Test Failed]  
IgniteAtomicLongChangingTopologySelfTest.testClientAtomicLongCreateCloseFailover
 Key: IGNITE-5980
 URL: https://issues.apache.org/jira/browse/IGNITE-5980
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Example of failing
http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId-4067536648656067727



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5979) [Test Failed] GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5979:
-

 Summary: [Test Failed]  
GridCacheAtomicInvalidPartitionHandlingSelfTest.testPrimaryFullAsync 
 Key: IGNITE-5979
 URL: https://issues.apache.org/jira/browse/IGNITE-5979
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Example of failing  - 
http://ci.ignite.apache.org/viewLog.html?buildId=760709=buildResultsDiv=Ignite20Tests_IgniteDataGridFailover#testNameId6248548165747570497



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5978) [Test Failed] IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode1

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-5978:
--
Labels: MakeTeamcityGreenAgain  (was: )

> [Test Failed] IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode1
> -
>
> Key: IGNITE-5978
> URL: https://issues.apache.org/jira/browse/IGNITE-5978
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Fails locally.
> Example of failing - 
> http://ci.ignite.apache.org/viewLog.html?buildId=759891=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId677264269171099154.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5978) [Test Failed] IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode1

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5978:
-

 Summary: [Test Failed] 
IgnitePartitionedCountDownLatchSelfTest.testLatchMultinode1
 Key: IGNITE-5978
 URL: https://issues.apache.org/jira/browse/IGNITE-5978
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Fails locally.
Example of failing - 
http://ci.ignite.apache.org/viewLog.html?buildId=759891=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId677264269171099154.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5977) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5977:
-

 Summary: [Test Failed]  
IgniteClientDiscoveryDataStructuresTest.testSequence
 Key: IGNITE-5977
 URL: https://issues.apache.org/jira/browse/IGNITE-5977
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Fails locally.
Example of failing 
http://ci.ignite.apache.org/viewLog.html?buildId=758964=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId4310032017507935311.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5977) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSequence

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-5977:
--
Description: 
Fails locally.
Example of failing 
http://ci.ignite.apache.org/viewLog.html?buildId=760759=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId2829619862655631000

  was:
Fails locally.
Example of failing 
http://ci.ignite.apache.org/viewLog.html?buildId=758964=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId4310032017507935311.


> [Test Failed]  IgniteClientDiscoveryDataStructuresTest.testSequence
> ---
>
> Key: IGNITE-5977
> URL: https://issues.apache.org/jira/browse/IGNITE-5977
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Fails locally.
> Example of failing 
> http://ci.ignite.apache.org/viewLog.html?buildId=760759=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId2829619862655631000



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5976) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testReentrantLock

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5976:
-

 Summary: [Test Failed]  
IgniteClientDiscoveryDataStructuresTest.testReentrantLock
 Key: IGNITE-5976
 URL: https://issues.apache.org/jira/browse/IGNITE-5976
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Fails locally.
Example of failing 
http://ci.ignite.apache.org/viewLog.html?buildId=758964=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId4310032017507935311.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5975) [Test Failed] GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreSingleNodeFailure

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5975:
-

 Summary: [Test Failed] 
GridCachePartitionedDataStructuresFailoverSelfTest.testSemaphoreSingleNodeFailure
 Key: IGNITE-5975
 URL: https://issues.apache.org/jira/browse/IGNITE-5975
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Fails locally.
Example of failing - 
http://ci.ignite.apache.org/viewLog.html?buildId=758964=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId-2988875689386264427.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5974) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testSemaphore

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5974:
-

 Summary: [Test Failed] 
IgniteClientDiscoveryDataStructuresTest.testSemaphore
 Key: IGNITE-5974
 URL: https://issues.apache.org/jira/browse/IGNITE-5974
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev
 Fix For: 2.2


Fails locally.
Example of failing - 
http://ci.ignite.apache.org/viewLog.html?buildId=755824=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId-6847798749379612181



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5973) [Test Failed] GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5973:
-

 Summary: [Test Failed] 
GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
 Key: IGNITE-5973
 URL: https://issues.apache.org/jira/browse/IGNITE-5973
 Project: Ignite
  Issue Type: Bug
Reporter: Eduard Shangareev
 Fix For: 2.1


Success right is 93.3%. Fails locally.
Example of failing - 
http://ci.ignite.apache.org/viewLog.html?buildId=757906=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId-979977708202725050



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5973) [Test Failed] GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-5973:
--
Affects Version/s: 2.1

> [Test Failed] 
> GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
> --
>
> Key: IGNITE-5973
> URL: https://issues.apache.org/jira/browse/IGNITE-5973
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Success right is 93.3%. Fails locally.
> Example of failing - 
> http://ci.ignite.apache.org/viewLog.html?buildId=757906=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId-979977708202725050



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5973) [Test Failed] GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-5973:
--
Fix Version/s: (was: 2.1)
   2.2

> [Test Failed] 
> GridCacheAbstractDataStructuresFailoverSelfTest.testSemaphoreNonFailoverSafe
> --
>
> Key: IGNITE-5973
> URL: https://issues.apache.org/jira/browse/IGNITE-5973
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Success right is 93.3%. Fails locally.
> Example of failing - 
> http://ci.ignite.apache.org/viewLog.html?buildId=757906=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId-979977708202725050



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-170) A call of IgniteSet.iterator().next() can produce ClusterTopologyCheckedException on killing a node in topology.

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-170:
-
Labels: MakeTeamcityGreenAgain  (was: )

> A call of IgniteSet.iterator().next() can produce 
> ClusterTopologyCheckedException on killing a node in topology.
> 
>
> Key: IGNITE-170
> URL: https://issues.apache.org/jira/browse/IGNITE-170
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Irina Vasilinets
>Assignee: Semen Boikov
>  Labels: MakeTeamcityGreenAgain
>
> h3. Original description.
> GridCachePartitionedAtomicSetFailoverSelfTest.testNodeRestart fails sometimes.
> h3. Updated description.
> A call of the method next() on an IgniteSet iterator can produce 
> 'javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
> Query execution failed' exception caused by 'ClusterTopologyCheckedException: 
> Remote node has left topology' exception (see the full stack trace in 
> comments). 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5972) [Test Failed] IgniteCountDownLatchAbstractSelfTest.testLatchBroadcast

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-5972:
--
Fix Version/s: 2.2

> [Test Failed] IgniteCountDownLatchAbstractSelfTest.testLatchBroadcast
> -
>
> Key: IGNITE-5972
> URL: https://issues.apache.org/jira/browse/IGNITE-5972
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Fails locally. Flaky one.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5972) [Test Failed] IgniteCountDownLatchAbstractSelfTest.testLatchBroadcast

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5972:
-

 Summary: [Test Failed] 
IgniteCountDownLatchAbstractSelfTest.testLatchBroadcast
 Key: IGNITE-5972
 URL: https://issues.apache.org/jira/browse/IGNITE-5972
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Eduard Shangareev


Fails locally. Flaky one.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5971) Ignite Continuous Query 2: Flaky failure of #testMultiThreadedFailover

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-5971:
---
Description: 
Bunch of tests inherited from CacheContinuousQueryFailoverAbstractSelfTest have 
flaky #testMultiThreadedFailover test. It fails from time to time in all 
inherited test classes.
CacheContinuousQueryAsyncFailoverAtomicSelfTest.testFailoverStartStopBackup 
fails with problem that looks the same.
{noformat}
junit.framework.AssertionFailedError: Lose events, see log for details.

at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.TestCase.fail(TestCase.java:227)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryFailoverAbstractSelfTest.checkEvents(CacheContinuousQueryFailoverAbstractSelfTest.java:1225)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryFailoverAbstractSelfTest.access$3600(CacheContinuousQueryFailoverAbstractSelfTest.java:117)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryFailoverAbstractSelfTest$22$3.run(CacheContinuousQueryFailoverAbstractSelfTest.java:1962)
at java.util.concurrent.CyclicBarrier.dowait(CyclicBarrier.java:220)
at java.util.concurrent.CyclicBarrier.await(CyclicBarrier.java:435)
at 
org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryFailoverAbstractSelfTest$23.run(CacheContinuousQueryFailoverAbstractSelfTest.java:2025)
at 
org.apache.ignite.testframework.GridTestUtils$9.call(GridTestUtils.java:1236)
at 
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)

{noformat}

  was:
Bunch of tests inherited from CacheContinuousQueryFailoverAbstractSelfTest have 
flaky #testMultiThreadedFailover test. It fails from time to time in all 
inherited test classes.
CacheContinuousQueryAsyncFailoverAtomicSelfTest.testFailoverStartStopBackup 
fails with problem that looks the same.


> Ignite Continuous Query 2: Flaky failure of #testMultiThreadedFailover
> --
>
> Key: IGNITE-5971
> URL: https://issues.apache.org/jira/browse/IGNITE-5971
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Bunch of tests inherited from CacheContinuousQueryFailoverAbstractSelfTest 
> have flaky #testMultiThreadedFailover test. It fails from time to time in all 
> inherited test classes.
> CacheContinuousQueryAsyncFailoverAtomicSelfTest.testFailoverStartStopBackup 
> fails with problem that looks the same.
> {noformat}
> junit.framework.AssertionFailedError: Lose events, see log for details.
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.TestCase.fail(TestCase.java:227)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryFailoverAbstractSelfTest.checkEvents(CacheContinuousQueryFailoverAbstractSelfTest.java:1225)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryFailoverAbstractSelfTest.access$3600(CacheContinuousQueryFailoverAbstractSelfTest.java:117)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryFailoverAbstractSelfTest$22$3.run(CacheContinuousQueryFailoverAbstractSelfTest.java:1962)
>   at java.util.concurrent.CyclicBarrier.dowait(CyclicBarrier.java:220)
>   at java.util.concurrent.CyclicBarrier.await(CyclicBarrier.java:435)
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryFailoverAbstractSelfTest$23.run(CacheContinuousQueryFailoverAbstractSelfTest.java:2025)
>   at 
> org.apache.ignite.testframework.GridTestUtils$9.call(GridTestUtils.java:1236)
>   at 
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5971) Ignite Continuous Query 2: Flaky failure of #testMultiThreadedFailover

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-5971:
---
Description: 
Bunch of tests inherited from CacheContinuousQueryFailoverAbstractSelfTest have 
flaky #testMultiThreadedFailover test. It fails from time to time in all 
inherited test classes.
CacheContinuousQueryAsyncFailoverAtomicSelfTest.testFailoverStartStopBackup 
fails with problem that looks the same.

  was:Bunch of tests inherited from 
CacheContinuousQueryFailoverAbstractSelfTest have flaky 
#testMultiThreadedFailover test. It fails from time to time in all inherited 
test classes.


> Ignite Continuous Query 2: Flaky failure of #testMultiThreadedFailover
> --
>
> Key: IGNITE-5971
> URL: https://issues.apache.org/jira/browse/IGNITE-5971
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Bunch of tests inherited from CacheContinuousQueryFailoverAbstractSelfTest 
> have flaky #testMultiThreadedFailover test. It fails from time to time in all 
> inherited test classes.
> CacheContinuousQueryAsyncFailoverAtomicSelfTest.testFailoverStartStopBackup 
> fails with problem that looks the same.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5971) Ignite Continuous Query 2: Flaky failure of #testMultiThreadedFailover

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-5971:
--

 Summary: Ignite Continuous Query 2: Flaky failure of 
#testMultiThreadedFailover
 Key: IGNITE-5971
 URL: https://issues.apache.org/jira/browse/IGNITE-5971
 Project: Ignite
  Issue Type: Test
Affects Versions: 2.1
Reporter: Ivan Rakov
 Fix For: 2.2


Bunch of tests inherited from CacheContinuousQueryFailoverAbstractSelfTest have 
flaky #testMultiThreadedFailover test. It fails from time to time in all 
inherited test classes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5732) Provide API to test compatibility with old releases

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5732:


Github user daradurvs closed the pull request at:

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


> Provide API to test compatibility with old releases
> ---
>
> Key: IGNITE-5732
> URL: https://issues.apache.org/jira/browse/IGNITE-5732
> Project: Ignite
>  Issue Type: Test
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>
> Need to provide an opportunity to test compatibility with old releases.
> The main idea is the method {code}startGrid(ver){code} in the testing 
> framework, which would start an instance via downloaded "jar" from the Maven 
> repo.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5732) Provide API to test compatibility with old releases

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5732:


GitHub user daradurvs opened a pull request:

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

IGNITE-5732 Provide API to test compatibility with old releases



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

$ git pull https://github.com/daradurvs/ignite ignite-5732-module

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

https://github.com/apache/ignite/pull/2410.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 #2410






> Provide API to test compatibility with old releases
> ---
>
> Key: IGNITE-5732
> URL: https://issues.apache.org/jira/browse/IGNITE-5732
> Project: Ignite
>  Issue Type: Test
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>
> Need to provide an opportunity to test compatibility with old releases.
> The main idea is the method {code}startGrid(ver){code} in the testing 
> framework, which would start an instance via downloaded "jar" from the Maven 
> repo.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5966) IgniteCache#get() fails with "Requesting mapping from grid failed" when deserialising binary object loaded from CacheJdbcPojoStoreFactory

[Alexey Kukushkin (JIRA)]

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

Alexey Kukushkin updated IGNITE-5966:
-
Fix Version/s: 2.2

> IgniteCache#get() fails with "Requesting mapping from grid failed" when 
> deserialising binary object loaded from CacheJdbcPojoStoreFactory
> -
>
> Key: IGNITE-5966
> URL: https://issues.apache.org/jira/browse/IGNITE-5966
> Project: Ignite
>  Issue Type: Bug
> Environment: Ignite 2.1.4
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
> Fix For: 2.2
>
>
> STEPS TO REPRODUCE
> 1. A running MySQL database with at least one table with an Integer key and 
> some data
> 2. Use WebConsole to automatically generate an Ignite project from the RDBMS. 
> In the WebConsole add a cache for the table containing data
> 3. Build the project
> 4. Start the cluster (run ServerNodeSpringStartup)
> 5. Load the data (run LoadCaches)
> 6. Run simple "get data" code against the running cluster with the data 
> loaded. Make sure you do NOT keep binary and do NOT put anything to the cache 
> except loading data on step #5. For example, if the cache is "AircraftCache", 
> the type is "Aircraft" and a row with ID 1 exists in the DB, then:
> IgniteCache aircraftCache = 
> ignite.getOrCreateCache("AircraftCache");
> System.out.format("1->%s\n", aircraftCache.get(1));
> EXPECTED:
> 1...5: Project is generated, cluster runs, data is loaded
> 6: The entry with ID 1 is output to the console
> ACTUAL:"
> 1..5: As expected
> 6: javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Requesting mapping from grid failed 
> for [platformId=0, typeId=-1267085398]
> ANALYSIS
> The “typeId -> MappedName” mappings are stored in the 
> MarshallerContextImpl$allCaches[platformId] map.
> My understanding is according to the existing implementations it is expected 
> the mapping will always be registered when BinaryContext#descriptorForClass() 
> -> MarshallerContextImpl#registerClassName(typeId) is called either from 
> BinaryWriterExImpl or BinaryReaderExImpl.
> However, that mechanism is never called when 
> CacheJdbcPojoStore@buildBinaryObject builds the object, calling 
> BinaryObjectBuilderImpl#build(). The latter method still requests 
> BinaryContext#updateMetadata, which updates 
> CacheObjectBinaryProcessorImpl#metadataFileStore on all server nodes. But the 
> metadataFileStore is not the place where MarshallerContextImpl get mappings 
> from.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5970) Ignite Binary Objects Simple Mapper Basic: Flaky failure of org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-5970:
---
Description: 
Can't reproduce locally on Win 10.
On TC test has 50% success rate: 
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=3101872679882751520=testDetails_Ignite20Tests=%3Cdefault%3E
{noformat}
org.apache.ignite.internal.IgniteDeploymentCheckedException: Task not deployed: 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$TestClosure
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:712)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:448)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:673)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:478)
at 
org.apache.ignite.internal.IgniteComputeImpl.callAsync0(IgniteComputeImpl.java:809)
at 
org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:785)
at 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:240)
at 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:235)
at 
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
{noformat}

  was:
Can't reproduce locally on Win 10.
On TC test has 50% success rate.
{noformat}
org.apache.ignite.internal.IgniteDeploymentCheckedException: Task not deployed: 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$TestClosure
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:712)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:448)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:673)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:478)
at 
org.apache.ignite.internal.IgniteComputeImpl.callAsync0(IgniteComputeImpl.java:809)
at 
org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:785)
at 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:240)
at 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:235)
at 
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
{noformat}


> Ignite Binary Objects Simple Mapper Basic: Flaky failure of 
> org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader
> --
>
> Key: IGNITE-5970
> URL: https://issues.apache.org/jira/browse/IGNITE-5970
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Can't reproduce locally on Win 10.
> On TC test has 50% success rate: 
> http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=3101872679882751520=testDetails_Ignite20Tests=%3Cdefault%3E
> {noformat}
> org.apache.ignite.internal.IgniteDeploymentCheckedException: Task not 
> deployed: org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$TestClosure
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:712)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:448)
> at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:673)
> at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:478)
> at 
> org.apache.ignite.internal.IgniteComputeImpl.callAsync0(IgniteComputeImpl.java:809)
> at 
> org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:785)
> at 
> org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:240)
> at 
> org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:235)
> at 
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5970) Flaky failure of org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-5970:
---
Summary: Flaky failure of 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader
  (was: Ignite Binary Objects Simple Mapper Basic: Flaky failure of 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader)

> Flaky failure of 
> org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader
> ---
>
> Key: IGNITE-5970
> URL: https://issues.apache.org/jira/browse/IGNITE-5970
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Can't reproduce locally on Win 10.
> On TC test has 50% success rate: 
> http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=3101872679882751520=testDetails_Ignite20Tests=%3Cdefault%3E
> {noformat}
> org.apache.ignite.internal.IgniteDeploymentCheckedException: Task not 
> deployed: org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$TestClosure
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:712)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:448)
> at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:673)
> at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:478)
> at 
> org.apache.ignite.internal.IgniteComputeImpl.callAsync0(IgniteComputeImpl.java:809)
> at 
> org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:785)
> at 
> org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:240)
> at 
> org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:235)
> at 
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5970) Ignite Binary Objects Simple Mapper Basic: Flaky failure of org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5970:
---
Labels: MakeTeamcityGreenAgain  (was: )

> Ignite Binary Objects Simple Mapper Basic: Flaky failure of 
> org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader
> --
>
> Key: IGNITE-5970
> URL: https://issues.apache.org/jira/browse/IGNITE-5970
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Can't reproduce locally on Win 10.
> On TC test has 50% success rate.
> {noformat}
> org.apache.ignite.internal.IgniteDeploymentCheckedException: Task not 
> deployed: org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$TestClosure
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:712)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:448)
> at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:673)
> at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:478)
> at 
> org.apache.ignite.internal.IgniteComputeImpl.callAsync0(IgniteComputeImpl.java:809)
> at 
> org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:785)
> at 
> org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:240)
> at 
> org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:235)
> at 
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5970) Ignite Binary Objects Simple Mapper Basic: Flaky failure of org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-5970:
--

 Summary: Ignite Binary Objects Simple Mapper Basic: Flaky failure 
of 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest#testConcurrentDeploymentWithDelegatingClassloader
 Key: IGNITE-5970
 URL: https://issues.apache.org/jira/browse/IGNITE-5970
 Project: Ignite
  Issue Type: Test
Affects Versions: 2.1
Reporter: Ivan Rakov
 Fix For: 2.2


Can't reproduce locally on Win 10.
On TC test has 50% success rate.
{noformat}
org.apache.ignite.internal.IgniteDeploymentCheckedException: Task not deployed: 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$TestClosure
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.startTask(GridTaskProcessor.java:712)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.execute(GridTaskProcessor.java:448)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:673)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor.callAsync(GridClosureProcessor.java:478)
at 
org.apache.ignite.internal.IgniteComputeImpl.callAsync0(IgniteComputeImpl.java:809)
at 
org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:785)
at 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:240)
at 
org.apache.ignite.p2p.GridP2PLocalDeploymentSelfTest$1.call(GridP2PLocalDeploymentSelfTest.java:235)
at 
org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5969) Test fail in Ignite Cache 2:CacheLoadingConcurrentGridStartSelfTest.testLoadCacheWithDataStreamerSequentialWithConfigAndRestarts

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5969:
---
Affects Version/s: 2.1

> Test fail in Ignite Cache 
> 2:CacheLoadingConcurrentGridStartSelfTest.testLoadCacheWithDataStreamerSequentialWithConfigAndRestarts
>  
> -
>
> Key: IGNITE-5969
> URL: https://issues.apache.org/jira/browse/IGNITE-5969
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Dmitriy Govorukhin
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> java.lang.AssertionError: Some failed keys: [398500, 398511, 398553, 399442, 
> 399457, 399491, 399524, 399535, 399577, 399636, 400466, 400481, 400515]
> at 
> org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest.loadCacheWithDataStreamerSequential(CacheLoadingConcurrentGridStartSelfTest.java:319)
> at 
> org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest.testLoadCacheWithDataStreamerSequentialWithConfigAndRestarts(CacheLoadingConcurrentGridStartSelfTest.java:205)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5968) Test fail in Ignite Cache 2: GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5968:
---
Affects Version/s: 2.1

> Test fail in Ignite Cache 2: 
> GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead
> --
>
> Key: IGNITE-5968
> URL: https://issues.apache.org/jira/browse/IGNITE-5968
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Dmitriy Govorukhin
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> java.util.concurrent.TimeoutException: Test has been timed out 
> [test=testPrimaryAndBackupDead, timeout=30]
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1949)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5969) Test fail in Ignite Cache 2:CacheLoadingConcurrentGridStartSelfTest.testLoadCacheWithDataStreamerSequentialWithConfigAndRestarts

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-5969:
---
Labels: MakeTeamcityGreenAgain  (was: )

> Test fail in Ignite Cache 
> 2:CacheLoadingConcurrentGridStartSelfTest.testLoadCacheWithDataStreamerSequentialWithConfigAndRestarts
>  
> -
>
> Key: IGNITE-5969
> URL: https://issues.apache.org/jira/browse/IGNITE-5969
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Govorukhin
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> java.lang.AssertionError: Some failed keys: [398500, 398511, 398553, 399442, 
> 399457, 399491, 399524, 399535, 399577, 399636, 400466, 400481, 400515]
> at 
> org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest.loadCacheWithDataStreamerSequential(CacheLoadingConcurrentGridStartSelfTest.java:319)
> at 
> org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest.testLoadCacheWithDataStreamerSequentialWithConfigAndRestarts(CacheLoadingConcurrentGridStartSelfTest.java:205)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5969) Test fail in Ignite Cache 2:CacheLoadingConcurrentGridStartSelfTest.testLoadCacheWithDataStreamerSequentialWithConfigAndRestarts

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-5969:
--

 Summary: Test fail in Ignite Cache 
2:CacheLoadingConcurrentGridStartSelfTest.testLoadCacheWithDataStreamerSequentialWithConfigAndRestarts
 
 Key: IGNITE-5969
 URL: https://issues.apache.org/jira/browse/IGNITE-5969
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Govorukhin
 Fix For: 2.2


java.lang.AssertionError: Some failed keys: [398500, 398511, 398553, 399442, 
399457, 399491, 399524, 399535, 399577, 399636, 400466, 400481, 400515]
at 
org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest.loadCacheWithDataStreamerSequential(CacheLoadingConcurrentGridStartSelfTest.java:319)
at 
org.apache.ignite.internal.processors.cache.distributed.CacheLoadingConcurrentGridStartSelfTest.testLoadCacheWithDataStreamerSequentialWithConfigAndRestarts(CacheLoadingConcurrentGridStartSelfTest.java:205)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5968) Test fail in Ignite Cache 2: GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-5968:
---
Labels: MakeTeamcityGreenAgain  (was: )

> Test fail in Ignite Cache 2: 
> GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead
> --
>
> Key: IGNITE-5968
> URL: https://issues.apache.org/jira/browse/IGNITE-5968
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Govorukhin
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> java.util.concurrent.TimeoutException: Test has been timed out 
> [test=testPrimaryAndBackupDead, timeout=30]
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1949)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5968) Test fail in Ignite Cache 2: GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-5968:
--

 Summary: Test fail in Ignite Cache 2: 
GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead
 Key: IGNITE-5968
 URL: https://issues.apache.org/jira/browse/IGNITE-5968
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Govorukhin
 Fix For: 2.2


java.util.concurrent.TimeoutException: Test has been timed out 
[test=testPrimaryAndBackupDead, timeout=30]
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTest(GridAbstractTest.java:1949)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at 
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5967) Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5967:
---
Affects Version/s: 2.1

> Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet 
> -
>
> Key: IGNITE-5967
> URL: https://issues.apache.org/jira/browse/IGNITE-5967
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Dmitriy Govorukhin
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> RedisProtocolStringSelfTest.testGetSet 
> redis.clients.jedis.exceptions.JedisConnectionException: Unexpected end of 
> stream.
> at 
> redis.clients.util.RedisInputStream.ensureFill(RedisInputStream.java:199)
> at redis.clients.util.RedisInputStream.readByte(RedisInputStream.java:40)
> at redis.clients.jedis.Protocol.process(Protocol.java:151)
> at redis.clients.jedis.Protocol.read(Protocol.java:215)
> at 
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
> at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:259)
> at redis.clients.jedis.Connection.getBulkReply(Connection.java:248)
> at redis.clients.jedis.Jedis.get(Jedis.java:153)
> at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.RedisProtocolStringSelfTest.testGetSet(RedisProtocolStringSelfTest.java:62)
> --- Stdout: ---
> [2017-08-07 06:28:44,379][INFO ][main][root] >>> Starting test: 
> RedisProtocolStringSelfTest#testGetSet <<<
> [2017-08-07 06:28:52,390][INFO ][main][root] >>> Stopping test: 
> RedisProtocolStringSelfTest#testGetSet in 8010 ms <<<
> --- Stderr: ---
> [2017-08-07 06:28:52,389][ERROR][main][root] Test failed.
> redis.clients.jedis.exceptions.JedisConnectionException: Unexpected end of 
> stream.
> at 
> redis.clients.util.RedisInputStream.ensureFill(RedisInputStream.java:199)
> at redis.clients.util.RedisInputStream.readByte(RedisInputStream.java:40)
> at redis.clients.jedis.Protocol.process(Protocol.java:151)
> at redis.clients.jedis.Protocol.read(Protocol.java:215)
> at 
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
> at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:259)
> at redis.clients.jedis.Connection.getBulkReply(Connection.java:248)
> at redis.clients.jedis.Jedis.get(Jedis.java:153)
> at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.RedisProtocolStringSelfTest.testGetSet(RedisProtocolStringSelfTest.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5967) Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-5967:
---
Labels: MakeTeamcityGreenAgain  (was: )

> Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet 
> -
>
> Key: IGNITE-5967
> URL: https://issues.apache.org/jira/browse/IGNITE-5967
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> RedisProtocolStringSelfTest.testGetSet 
> redis.clients.jedis.exceptions.JedisConnectionException: Unexpected end of 
> stream.
> at 
> redis.clients.util.RedisInputStream.ensureFill(RedisInputStream.java:199)
> at redis.clients.util.RedisInputStream.readByte(RedisInputStream.java:40)
> at redis.clients.jedis.Protocol.process(Protocol.java:151)
> at redis.clients.jedis.Protocol.read(Protocol.java:215)
> at 
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
> at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:259)
> at redis.clients.jedis.Connection.getBulkReply(Connection.java:248)
> at redis.clients.jedis.Jedis.get(Jedis.java:153)
> at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.RedisProtocolStringSelfTest.testGetSet(RedisProtocolStringSelfTest.java:62)
> --- Stdout: ---
> [2017-08-07 06:28:44,379][INFO ][main][root] >>> Starting test: 
> RedisProtocolStringSelfTest#testGetSet <<<
> [2017-08-07 06:28:52,390][INFO ][main][root] >>> Stopping test: 
> RedisProtocolStringSelfTest#testGetSet in 8010 ms <<<
> --- Stderr: ---
> [2017-08-07 06:28:52,389][ERROR][main][root] Test failed.
> redis.clients.jedis.exceptions.JedisConnectionException: Unexpected end of 
> stream.
> at 
> redis.clients.util.RedisInputStream.ensureFill(RedisInputStream.java:199)
> at redis.clients.util.RedisInputStream.readByte(RedisInputStream.java:40)
> at redis.clients.jedis.Protocol.process(Protocol.java:151)
> at redis.clients.jedis.Protocol.read(Protocol.java:215)
> at 
> redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
> at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:259)
> at redis.clients.jedis.Connection.getBulkReply(Connection.java:248)
> at redis.clients.jedis.Jedis.get(Jedis.java:153)
> at 
> org.apache.ignite.internal.processors.rest.protocols.tcp.redis.RedisProtocolStringSelfTest.testGetSet(RedisProtocolStringSelfTest.java:62)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5967) Flaky fail in Ignite Java Client: RedisProtocolStringSelfTest.testGetSet

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-5967:
--

 Summary: Flaky fail in Ignite Java Client: 
RedisProtocolStringSelfTest.testGetSet 
 Key: IGNITE-5967
 URL: https://issues.apache.org/jira/browse/IGNITE-5967
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Govorukhin
 Fix For: 2.2


RedisProtocolStringSelfTest.testGetSet 

redis.clients.jedis.exceptions.JedisConnectionException: Unexpected end of 
stream.
at redis.clients.util.RedisInputStream.ensureFill(RedisInputStream.java:199)
at redis.clients.util.RedisInputStream.readByte(RedisInputStream.java:40)
at redis.clients.jedis.Protocol.process(Protocol.java:151)
at redis.clients.jedis.Protocol.read(Protocol.java:215)
at 
redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:259)
at redis.clients.jedis.Connection.getBulkReply(Connection.java:248)
at redis.clients.jedis.Jedis.get(Jedis.java:153)
at 
org.apache.ignite.internal.processors.rest.protocols.tcp.redis.RedisProtocolStringSelfTest.testGetSet(RedisProtocolStringSelfTest.java:62)
--- Stdout: ---
[2017-08-07 06:28:44,379][INFO ][main][root] >>> Starting test: 
RedisProtocolStringSelfTest#testGetSet <<<
[2017-08-07 06:28:52,390][INFO ][main][root] >>> Stopping test: 
RedisProtocolStringSelfTest#testGetSet in 8010 ms <<<
--- Stderr: ---
[2017-08-07 06:28:52,389][ERROR][main][root] Test failed.
redis.clients.jedis.exceptions.JedisConnectionException: Unexpected end of 
stream.
at redis.clients.util.RedisInputStream.ensureFill(RedisInputStream.java:199)
at redis.clients.util.RedisInputStream.readByte(RedisInputStream.java:40)
at redis.clients.jedis.Protocol.process(Protocol.java:151)
at redis.clients.jedis.Protocol.read(Protocol.java:215)
at 
redis.clients.jedis.Connection.readProtocolWithCheckingBroken(Connection.java:340)
at redis.clients.jedis.Connection.getBinaryBulkReply(Connection.java:259)
at redis.clients.jedis.Connection.getBulkReply(Connection.java:248)
at redis.clients.jedis.Jedis.get(Jedis.java:153)
at 
org.apache.ignite.internal.processors.rest.protocols.tcp.redis.RedisProtocolStringSelfTest.testGetSet(RedisProtocolStringSelfTest.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-585) [Test] Need to test and fix continuous processor on discovery data exchange with P2P deployment

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-585:
--
Labels: MakeTeamcityGreenAgain Muted  (was: Muted_test)

> [Test] Need to test and fix continuous processor on discovery data exchange 
> with P2P deployment
> ---
>
> Key: IGNITE-585
> URL: https://issues.apache.org/jira/browse/IGNITE-585
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: MakeTeamcityGreenAgain
>
> see GG-6730
> Next test(s) should be unmuted on TC: GridEventConsumeSelfTest # 
> testNodeJoinWithP2P



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-585) [Test] Need to test and fix continuous processor on discovery data exchange with P2P deployment

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-585:
--
Labels: MakeTeamcityGreenAgain  (was: MakeTeamcityGreenAgain Muted)

> [Test] Need to test and fix continuous processor on discovery data exchange 
> with P2P deployment
> ---
>
> Key: IGNITE-585
> URL: https://issues.apache.org/jira/browse/IGNITE-585
> Project: Ignite
>  Issue Type: Bug
>Reporter: Artem Shutak
>  Labels: MakeTeamcityGreenAgain
>
> see GG-6730
> Next test(s) should be unmuted on TC: GridEventConsumeSelfTest # 
> testNodeJoinWithP2P



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5966) IgniteCache#get() fails with "Requesting mapping from grid failed" when deserialising binary object loaded from CacheJdbcPojoStoreFactory

[Alexey Kukushkin (JIRA)]

Alexey Kukushkin created IGNITE-5966:


 Summary: IgniteCache#get() fails with "Requesting mapping from 
grid failed" when deserialising binary object loaded from 
CacheJdbcPojoStoreFactory
 Key: IGNITE-5966
 URL: https://issues.apache.org/jira/browse/IGNITE-5966
 Project: Ignite
  Issue Type: Bug
 Environment: Ignite 2.1.4
Reporter: Alexey Kukushkin
Assignee: Alexey Kukushkin


STEPS TO REPRODUCE
1. A running MySQL database with at least one table with an Integer key and 
some data
2. Use WebConsole to automatically generate an Ignite project from the RDBMS. 
In the WebConsole add a cache for the table containing data
3. Build the project
4. Start the cluster (run ServerNodeSpringStartup)
5. Load the data (run LoadCaches)
6. Run simple "get data" code against the running cluster with the data loaded. 
Make sure you do NOT keep binary and do NOT put anything to the cache except 
loading data on step #5. For example, if the cache is "AircraftCache", the type 
is "Aircraft" and a row with ID 1 exists in the DB, then:
IgniteCache aircraftCache = 
ignite.getOrCreateCache("AircraftCache");
System.out.format("1->%s\n", aircraftCache.get(1));
EXPECTED:
1...5: Project is generated, cluster runs, data is loaded
6: The entry with ID 1 is output to the console
ACTUAL:"
1..5: As expected
6: javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
Requesting mapping from grid failed for [platformId=0, typeId=-1267085398]
ANALYSIS
The “typeId -> MappedName” mappings are stored in the 
MarshallerContextImpl$allCaches[platformId] map.
My understanding is according to the existing implementations it is expected 
the mapping will always be registered when BinaryContext#descriptorForClass() 
-> MarshallerContextImpl#registerClassName(typeId) is called either from 
BinaryWriterExImpl or BinaryReaderExImpl.
However, that mechanism is never called when 
CacheJdbcPojoStore@buildBinaryObject builds the object, calling 
BinaryObjectBuilderImpl#build(). The latter method still requests 
BinaryContext#updateMetadata, which updates 
CacheObjectBinaryProcessorImpl#metadataFileStore on all server nodes. But the 
metadataFileStore is not the place where MarshallerContextImpl get mappings 
from.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5965) Ignite Basic: Flaky failure of GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5965:
---
Labels: MakeTeamcityGreenAgain  (was: )

> Ignite Basic: Flaky failure of  
> GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology
> --
>
> Key: IGNITE-5965
> URL: https://issues.apache.org/jira/browse/IGNITE-5965
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Test has 85% success rate in master:
> http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-2642357454043293898=testDetails_Ignite20Tests=%3Cdefault%3E
> Flaky failure is reproduced locally with similar success rate (24/30, Win 10).
> {noformat}
> junit.framework.AssertionFailedError: 
> Expected :4
> Actual   :5
>  
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessorAbstractSelfTest.checkCount(GridServiceProcessorAbstractSelfTest.java:765)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessorMultiNodeConfigSelfTest.checkDeployOnEachNodeUpdateTopology(GridServiceProcessorMultiNodeConfigSelfTest.java:287)
>   at 
> org.apache.ignite.internal.processors.service.GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology(GridServiceProcessorMultiNodeConfigSelfTest.java:144)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5965) Ignite Basic: Flaky failure of GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-5965:
--

 Summary: Ignite Basic: Flaky failure of  
GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology
 Key: IGNITE-5965
 URL: https://issues.apache.org/jira/browse/IGNITE-5965
 Project: Ignite
  Issue Type: Test
Affects Versions: 2.1
Reporter: Ivan Rakov
 Fix For: 2.2


Test has 85% success rate in master:
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-2642357454043293898=testDetails_Ignite20Tests=%3Cdefault%3E
Flaky failure is reproduced locally with similar success rate (24/30, Win 10).
{noformat}
junit.framework.AssertionFailedError: 
Expected :4
Actual   :5
 


at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at junit.framework.TestCase.assertEquals(TestCase.java:409)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessorAbstractSelfTest.checkCount(GridServiceProcessorAbstractSelfTest.java:765)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessorMultiNodeConfigSelfTest.checkDeployOnEachNodeUpdateTopology(GridServiceProcessorMultiNodeConfigSelfTest.java:287)
at 
org.apache.ignite.internal.processors.service.GridServiceProcessorMultiNodeConfigSelfTest.testDeployOnEachNodeUpdateTopology(GridServiceProcessorMultiNodeConfigSelfTest.java:144)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)


{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5964) test fail: TcpClientDiscoverySpiSelfTest (disconnectLatch timeout)

[Konstantin Dudkov (JIRA)]

Konstantin Dudkov created IGNITE-5964:
-

 Summary: test fail: TcpClientDiscoverySpiSelfTest (disconnectLatch 
timeout)
 Key: IGNITE-5964
 URL: https://issues.apache.org/jira/browse/IGNITE-5964
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Konstantin Dudkov
 Fix For: 2.2


flake tests: testReconnectAfterFailTopologyChanged, 
testReconnectAfterTopologyChanged

disconnectLatch timeout

{code:java}
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:55)
at junit.framework.Assert.assertTrue(Assert.java:22)
at junit.framework.Assert.assertTrue(Assert.java:31)
at junit.framework.TestCase.assertTrue(TestCase.java:201)
at 
org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.reconnectAfterFail(TcpClientDiscoverySpiSelfTest.java:1422)
at 
org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.testReconnectAfterFailTopologyChanged(TcpClientDiscoverySpiSelfTest.java:1331)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
{code}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5880) BLAS integration phase 2

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5880:


Github user ybabak closed the pull request at:

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


> BLAS integration phase 2
> 
>
> Key: IGNITE-5880
> URL: https://issues.apache.org/jira/browse/IGNITE-5880
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.2
>
>
> The second phase of BLAS integration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5963) Ignite Cache 6: Flaky failure IgniteOptimisticTxSuspendResumeMultiServerTest.testTxTimeoutOnSuspend on TC

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5963:
---
Fix Version/s: 2.2

>  Ignite Cache 6: Flaky failure 
> IgniteOptimisticTxSuspendResumeMultiServerTest.testTxTimeoutOnSuspend on TC
> --
>
> Key: IGNITE-5963
> URL: https://issues.apache.org/jira/browse/IGNITE-5963
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Test sometimes fails on teamcity, please see
> http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-6026696383836355176=testDetails
> {noformat}
> java.lang.AssertionError: Exception has not been thrown.
> at 
> org.apache.ignite.testframework.GridTestUtils.assertThrowsWithCause(GridTestUtils.java:425)
> at 
> org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest$15.applyx(IgniteOptimisticTxSuspendResumeTest.java:464)
> at 
> org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest$15.applyx(IgniteOptimisticTxSuspendResumeTest.java:455)
> at 
> org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest$CI2Exc.apply(IgniteOptimisticTxSuspendResumeTest.java:697)
> at 
> org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest.executeTestForAllCaches(IgniteOptimisticTxSuspendResumeTest.java:669)
> at 
> org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest.testTxTimeoutOnSuspend(IgniteOptimisticTxSuspendResumeTest.java:455)
> {noformat}
> Test was created under issue IGNITE-5712
> Does not reprocuced locally (30 runs on Win10).
> But on CI server success rate is 94%



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5963) Ignite Cache 6: Flaky failure IgniteOptimisticTxSuspendResumeMultiServerTest.testTxTimeoutOnSuspend on TC

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5963:
---
Affects Version/s: 2.1

>  Ignite Cache 6: Flaky failure 
> IgniteOptimisticTxSuspendResumeMultiServerTest.testTxTimeoutOnSuspend on TC
> --
>
> Key: IGNITE-5963
> URL: https://issues.apache.org/jira/browse/IGNITE-5963
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Test sometimes fails on teamcity, please see
> http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-6026696383836355176=testDetails
> {noformat}
> java.lang.AssertionError: Exception has not been thrown.
> at 
> org.apache.ignite.testframework.GridTestUtils.assertThrowsWithCause(GridTestUtils.java:425)
> at 
> org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest$15.applyx(IgniteOptimisticTxSuspendResumeTest.java:464)
> at 
> org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest$15.applyx(IgniteOptimisticTxSuspendResumeTest.java:455)
> at 
> org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest$CI2Exc.apply(IgniteOptimisticTxSuspendResumeTest.java:697)
> at 
> org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest.executeTestForAllCaches(IgniteOptimisticTxSuspendResumeTest.java:669)
> at 
> org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest.testTxTimeoutOnSuspend(IgniteOptimisticTxSuspendResumeTest.java:455)
> {noformat}
> Test was created under issue IGNITE-5712
> Does not reprocuced locally (30 runs on Win10).
> But on CI server success rate is 94%



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5963) Ignite Cache 6: Flaky failure IgniteOptimisticTxSuspendResumeMultiServerTest.testTxTimeoutOnSuspend on TC

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-5963:
--

 Summary:  Ignite Cache 6: Flaky failure 
IgniteOptimisticTxSuspendResumeMultiServerTest.testTxTimeoutOnSuspend on TC
 Key: IGNITE-5963
 URL: https://issues.apache.org/jira/browse/IGNITE-5963
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Pavlov


Test sometimes fails on teamcity, please see
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-6026696383836355176=testDetails

{noformat}
java.lang.AssertionError: Exception has not been thrown.
at 
org.apache.ignite.testframework.GridTestUtils.assertThrowsWithCause(GridTestUtils.java:425)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest$15.applyx(IgniteOptimisticTxSuspendResumeTest.java:464)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest$15.applyx(IgniteOptimisticTxSuspendResumeTest.java:455)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest$CI2Exc.apply(IgniteOptimisticTxSuspendResumeTest.java:697)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest.executeTestForAllCaches(IgniteOptimisticTxSuspendResumeTest.java:669)
at 
org.apache.ignite.internal.processors.cache.distributed.IgniteOptimisticTxSuspendResumeTest.testTxTimeoutOnSuspend(IgniteOptimisticTxSuspendResumeTest.java:455)
{noformat}

Test was created under issue IGNITE-5712

Does not reprocuced locally (30 runs on Win10).

But on CI server success rate is 94%



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5962) Increase max length of index name

[Ilya Lantukh (JIRA)]

Ilya Lantukh created IGNITE-5962:


 Summary: Increase max length of index name
 Key: IGNITE-5962
 URL: https://issues.apache.org/jira/browse/IGNITE-5962
 Project: Ignite
  Issue Type: Improvement
  Components: general, sql
Affects Versions: 2.1
Reporter: Ilya Lantukh


In https://issues.apache.org/jira/browse/IGNITE-5941 max index name length was 
reduced from 768 to 256 bytes. If we need to support longer names, we need to 
change format of metastore data pages.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5941) Index with long name stores incorrect

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh reassigned IGNITE-5941:


Assignee: Alexey Goncharuk  (was: Ilya Lantukh)

> Index with long name stores incorrect
> -
>
> Key: IGNITE-5941
> URL: https://issues.apache.org/jira/browse/IGNITE-5941
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Assignee: Alexey Goncharuk
> Attachments: LongIndexNameTest.java
>
>
> SQL query by Index with long name return inconsistent result after cluster 
> restart and recover from storage. At the same time a query by other index 
> (with more shorter name) works correctly before and after recovery.
> For example long index name:
> {code}
> QueryIndex index = new QueryIndex("name", true, 
> "COM.SBT.AZIMUTH_PSI.PUBLISHER.ENTITIES.PUB.PARTICLES.CARPORT#MODELCOM.SBT.AZIMUTH_PSI.PUBLISHER.ENTITIES.PUB.PARTICLES.CARPORT");
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-5549) Ignite Cache Failover2: test suite hands up from CacheAsyncOperationsFailoverTxTest.testAsyncFailover()

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov edited comment on IGNITE-5549 at 8/7/17 2:21 PM:


Latest timeout
http://ci.ignite.apache.org/viewLog.html?buildId=744034=buildResultsDiv=Ignite20Tests_IgniteCacheFailover2


was (Author: dpavlov):
Latest timeout
http://ci.ignite.apache.org/viewLog.html?buildId=744034=buildResultsDiv=Ignite20Tests_IgniteCacheFailover2

> Ignite Cache Failover2: test suite hands up from 
> CacheAsyncOperationsFailoverTxTest.testAsyncFailover()
> ---
>
> Key: IGNITE-5549
> URL: https://issues.apache.org/jira/browse/IGNITE-5549
> Project: Ignite
>  Issue Type: Test
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain, test-fail
> Fix For: 2.2
>
> Attachments: ThreadDump0.log
>
>
> Timeout came from CacheAsyncOperationsFailoverTxTest.testAsyncFailover() test:
> http://ci.ignite.apache.org/viewLog.html?buildId=756819=Ignite20Tests_IgniteCacheFailover2=buildResultsDiv
> {noformat}
> ransaction has been already completed.
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:787)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:727)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:683)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:95)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:165)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:163)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1042)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:561)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1097)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:485)
> [16:29:30]W:   [org.apache.ignite:ignite-core]at 
> java.lang.Thread.run(Thread.java:745)
> [16:29:30]W:   [org.apache.ignite:ignite-core] 
> java.lang.AssertionError: Invalid threadId [this=GridCacheMvccCandidate 
> [nodeId=d6f0c17e-68b3-4da7-bd02-914ada70, ver=GridCacheVersion 
> [topVer=11427, order=1501856691702, nodeOrder=1], threadId=211336, 
> id=30502322, topVer=AffinityTopologyVersion [topVer=126, minorTopVer=0], 
> reentry=null, otherNodeId=d6f0c17e-68b3-4da7-bd02-914ada70, 
> otherVer=GridCacheVersion [topVer=11427, order=1501856691702, 
> 

[jira] [Updated] (IGNITE-5961) Align pages in LFS partition files to pageSize

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-5961:
---
Description: 
We store 17 bytes of header at the start of every partition file:
{noformat}
/** Allocated field offset. */
static final int HEADER_SIZE = 8/*SIGNATURE*/ + 4/*VERSION*/ + 1/*type*/ + 
4/*page size*/;
{noformat}
Even if pageSize is equal to OS page cache size and equal to SSD disk page size 
(which is best scenario), we generate two dirty pages instead of one. This is 
suboptimal and can be a bottleneck of checkpoint write speed. 

  was:
We store 17 bytes of header at the start of every partition file:
{noformat}
/** Allocated field offset. */
static final int HEADER_SIZE = 8/*SIGNATURE*/ + 4/*VERSION*/ + 1/*type*/ + 
4/*page size*/;
{noformat}
Even if pageSize is equal to OS page cache size and equal to SSD disk page size 
(which is best scenario), when generate two dirty pages insteadf of one. This 
is suboptimal and can be a bottleneck of checkpoint write speed. 


> Align pages in LFS partition files to pageSize
> --
>
> Key: IGNITE-5961
> URL: https://issues.apache.org/jira/browse/IGNITE-5961
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Ivan Rakov
>Assignee: Ivan Rakov
>Priority: Critical
> Fix For: 2.2
>
>
> We store 17 bytes of header at the start of every partition file:
> {noformat}
> /** Allocated field offset. */
> static final int HEADER_SIZE = 8/*SIGNATURE*/ + 4/*VERSION*/ + 1/*type*/ 
> + 4/*page size*/;
> {noformat}
> Even if pageSize is equal to OS page cache size and equal to SSD disk page 
> size (which is best scenario), we generate two dirty pages instead of one. 
> This is suboptimal and can be a bottleneck of checkpoint write speed. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5961) Align pages in LFS partition files to pageSize

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-5961:
--

 Summary: Align pages in LFS partition files to pageSize
 Key: IGNITE-5961
 URL: https://issues.apache.org/jira/browse/IGNITE-5961
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Affects Versions: 2.1
Reporter: Ivan Rakov
Assignee: Ivan Rakov
Priority: Critical
 Fix For: 2.2


We store 17 bytes of header at the start of every partition file:
{noformat}
/** Allocated field offset. */
static final int HEADER_SIZE = 8/*SIGNATURE*/ + 4/*VERSION*/ + 1/*type*/ + 
4/*page size*/;
{noformat}
Even if pageSize is equal to OS page cache size and equal to SSD disk page size 
(which is best scenario), when generate two dirty pages insteadf of one. This 
is suboptimal and can be a bottleneck of checkpoint write speed. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5880) BLAS integration phase 2

[Artem Malykh (JIRA)]

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

Artem Malykh commented on IGNITE-5880:
--

[~chief] Looks good for me

> BLAS integration phase 2
> 
>
> Key: IGNITE-5880
> URL: https://issues.apache.org/jira/browse/IGNITE-5880
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.2
>
>
> The second phase of BLAS integration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5959) Ignite Hadoop: testClientReconnect and testClientReconnectMultithreaded fail

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5959:
---
Affects Version/s: 2.1

> Ignite Hadoop: testClientReconnect and testClientReconnectMultithreaded fail
> 
>
> Key: IGNITE-5959
> URL: https://issues.apache.org/jira/browse/IGNITE-5959
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Kovalenko
>  Labels: MakeTeamcityGreenAgain, test-failure
> Fix For: 2.2
>
>
> Tests are flaky. Failure ratio ~ 30%
> IgniteHadoopFileSystemClientBasedDualSyncSelfTest.testClientReconnectMultithreaded
> 
> IgniteHadoopFileSystemClientBasedDualAsyncSelfTest.testClientReconnect
> IgniteHadoopFileSystemClientBasedDualAsyncSelfTest.testClientReconnectMultithreaded
>
> IgniteHadoopFileSystemClientBasedPrimarySelfTest.testClientReconnectMultithreaded
>  
> IgniteHadoopFileSystemClientBasedProxySelfTest.testClientReconnect 
> Common case - test fails when tries to stop Ignite node:
> {noformat}
> [2017-08-07 03:29:26,089][ERROR][test-runner-#23774%grid%][root] Failed to 
> stop grid [igniteInstanceName=grid3, cancel=false]
> class org.apache.ignite.IgniteClientDisconnectedException: Client node 
> disconnected: test-IGFS-cli
> at 
> org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:92)
> at org.apache.ignite.internal.IgniteKernal.guard(IgniteKernal.java:3707)
> at org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3423)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.awaitTopologyChange(GridAbstractTest.java:2105)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1030)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1006)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1289)
> at 
> org.apache.ignite.internal.processors.hadoop.impl.igfs.IgniteHadoopFileSystemClientBasedAbstractSelfTest.restartServerNodesExceptOne(IgniteHadoopFileSystemClientBasedAbstractSelfTest.java:166)
> at 
> org.apache.ignite.internal.processors.hadoop.impl.igfs.IgniteHadoopFileSystemClientBasedAbstractSelfTest.testClientReconnectMultithreaded(IgniteHadoopFileSystemClientBasedAbstractSelfTest.java:134)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5960) Ignite Continuous Query (Queries 3): CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic is flaky

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5960:
---

 Summary: Ignite Continuous Query (Queries 3): 
CacheContinuousQueryConcurrentPartitionUpdateTest::testConcurrentUpdatesAndQueryStartAtomic
 is flaky
 Key: IGNITE-5960
 URL: https://issues.apache.org/jira/browse/IGNITE-5960
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Sergey Chugunov
 Fix For: 2.2


According to [TC 
history|http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=6546112007182082024=testDetails_Ignite20Tests=%3Cdefault%3E]
 test is flaky.

It is possible to reproduce it locally, sample run shows 9 failed tests out of 
30 overall executed.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5959) Ignite Hadoop: testClientReconnect and testClientReconnectMultithreaded fail

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-5959:
---

 Summary: Ignite Hadoop: testClientReconnect and 
testClientReconnectMultithreaded fail
 Key: IGNITE-5959
 URL: https://issues.apache.org/jira/browse/IGNITE-5959
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Kovalenko
 Fix For: 2.2


Tests are flaky. Failure ratio ~ 30%

IgniteHadoopFileSystemClientBasedDualSyncSelfTest.testClientReconnectMultithreaded
  
IgniteHadoopFileSystemClientBasedDualAsyncSelfTest.testClientReconnect  
IgniteHadoopFileSystemClientBasedDualAsyncSelfTest.testClientReconnectMultithreaded
 
IgniteHadoopFileSystemClientBasedPrimarySelfTest.testClientReconnectMultithreaded
   
IgniteHadoopFileSystemClientBasedProxySelfTest.testClientReconnect 

Common case - test fails when tries to stop Ignite node:

{noformat}
[2017-08-07 03:29:26,089][ERROR][test-runner-#23774%grid%][root] Failed to stop 
grid [igniteInstanceName=grid3, cancel=false]
class org.apache.ignite.IgniteClientDisconnectedException: Client node 
disconnected: test-IGFS-cli
at 
org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:92)
at org.apache.ignite.internal.IgniteKernal.guard(IgniteKernal.java:3707)
at org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3423)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.awaitTopologyChange(GridAbstractTest.java:2105)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1030)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1006)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1289)
at 
org.apache.ignite.internal.processors.hadoop.impl.igfs.IgniteHadoopFileSystemClientBasedAbstractSelfTest.restartServerNodesExceptOne(IgniteHadoopFileSystemClientBasedAbstractSelfTest.java:166)
at 
org.apache.ignite.internal.processors.hadoop.impl.igfs.IgniteHadoopFileSystemClientBasedAbstractSelfTest.testClientReconnectMultithreaded(IgniteHadoopFileSystemClientBasedAbstractSelfTest.java:134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5958) Ignite Cache 3: IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5958:
---
Fix Version/s: 2.2

> Ignite Cache 3: 
> IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator  fails
> --
>
> Key: IGNITE-5958
> URL: https://issues.apache.org/jira/browse/IGNITE-5958
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Kovalenko
>  Labels: MakeTeamcityGreenAgain, test-failure
> Fix For: 2.2
>
>
> Failure ratio ~90%.
> No additional errors or exceptions in test.
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
> Failed to perform cache operation (cache topology is not valid): test0
> at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1318)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1672)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1032)
> at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:872)
> at 
> org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.tryPut(IgniteTopologyValidatorGridSplitCacheTest.java:230)
> at 
> org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator(IgniteTopologyValidatorGridSplitCacheTest.java:161)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to perform 
> cache operation (cache topology is not valid): test0
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTopologyFutureAdapter.validateCache(GridDhtTopologyFutureAdapter.java:104)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:415)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1167)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:656)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2334)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2311)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1029)
> ... 12 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5958) Ignite Cache 3: IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5958:
---
Affects Version/s: 2.1

> Ignite Cache 3: 
> IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator  fails
> --
>
> Key: IGNITE-5958
> URL: https://issues.apache.org/jira/browse/IGNITE-5958
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Kovalenko
>  Labels: MakeTeamcityGreenAgain, test-failure
> Fix For: 2.2
>
>
> Failure ratio ~90%.
> No additional errors or exceptions in test.
> {noformat}
> javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
> Failed to perform cache operation (cache topology is not valid): test0
> at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1318)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1672)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1032)
> at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:872)
> at 
> org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.tryPut(IgniteTopologyValidatorGridSplitCacheTest.java:230)
> at 
> org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator(IgniteTopologyValidatorGridSplitCacheTest.java:161)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to perform 
> cache operation (cache topology is not valid): test0
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTopologyFutureAdapter.validateCache(GridDhtTopologyFutureAdapter.java:104)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:415)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1167)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:656)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2334)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2311)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1029)
> ... 12 more
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5958) Ignite Cache 3: IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator fails

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-5958:
---

 Summary: Ignite Cache 3: 
IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator  fails
 Key: IGNITE-5958
 URL: https://issues.apache.org/jira/browse/IGNITE-5958
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Kovalenko


Failure ratio ~90%.
No additional errors or exceptions in test.

{noformat}
javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: 
Failed to perform cache operation (cache topology is not valid): test0
at 
org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1318)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.cacheException(IgniteCacheProxyImpl.java:1672)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1032)
at 
org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:872)
at 
org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.tryPut(IgniteTopologyValidatorGridSplitCacheTest.java:230)
at 
org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorGridSplitCacheTest.testTopologyValidator(IgniteTopologyValidatorGridSplitCacheTest.java:161)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to perform 
cache operation (cache topology is not valid): test0
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTopologyFutureAdapter.validateCache(GridDhtTopologyFutureAdapter.java:104)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.mapOnTopology(GridNearAtomicSingleUpdateFuture.java:415)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.map(GridNearAtomicAbstractUpdateFuture.java:248)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.update0(GridDhtAtomicCache.java:1167)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.put0(GridDhtAtomicCache.java:656)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2334)
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.put(GridCacheAdapter.java:2311)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl.put(IgniteCacheProxyImpl.java:1029)
... 12 more
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5957) Ignite IGFS: IgfsStreamsSelfTest.testCreateFileColocated fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5957:
---
Fix Version/s: 2.2

> Ignite IGFS: IgfsStreamsSelfTest.testCreateFileColocated fails
> --
>
> Key: IGNITE-5957
> URL: https://issues.apache.org/jira/browse/IGNITE-5957
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Kovalenko
>  Labels: MakeTeamcityGreenAgain, test-failure
> Fix For: 2.2
>
>
> Test is flaky. Success ratio ~50%.
> Exception:
> {noformat}
> junit.framework.AssertionFailedError: expected:<1> but was:<2>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsStreamsSelfTest.testCreateFileColocated(IgfsStreamsSelfTest.java:213)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5957) Ignite IGFS: IgfsStreamsSelfTest.testCreateFileColocated fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5957:
---
Affects Version/s: 2.1

> Ignite IGFS: IgfsStreamsSelfTest.testCreateFileColocated fails
> --
>
> Key: IGNITE-5957
> URL: https://issues.apache.org/jira/browse/IGNITE-5957
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Pavel Kovalenko
>  Labels: MakeTeamcityGreenAgain, test-failure
> Fix For: 2.2
>
>
> Test is flaky. Success ratio ~50%.
> Exception:
> {noformat}
> junit.framework.AssertionFailedError: expected:<1> but was:<2>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:234)
> at junit.framework.Assert.assertEquals(Assert.java:241)
> at junit.framework.TestCase.assertEquals(TestCase.java:409)
> at 
> org.apache.ignite.internal.processors.igfs.IgfsStreamsSelfTest.testCreateFileColocated(IgfsStreamsSelfTest.java:213)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5957) Ignite IGFS: IgfsStreamsSelfTest.testCreateFileColocated fails

[Pavel Kovalenko (JIRA)]

Pavel Kovalenko created IGNITE-5957:
---

 Summary: Ignite IGFS: IgfsStreamsSelfTest.testCreateFileColocated 
fails
 Key: IGNITE-5957
 URL: https://issues.apache.org/jira/browse/IGNITE-5957
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Kovalenko


Test is flaky. Success ratio ~50%.

Exception:

{noformat}
junit.framework.AssertionFailedError: expected:<1> but was:<2>
at junit.framework.Assert.fail(Assert.java:57)
at junit.framework.Assert.failNotEquals(Assert.java:329)
at junit.framework.Assert.assertEquals(Assert.java:78)
at junit.framework.Assert.assertEquals(Assert.java:234)
at junit.framework.Assert.assertEquals(Assert.java:241)
at junit.framework.TestCase.assertEquals(TestCase.java:409)
at 
org.apache.ignite.internal.processors.igfs.IgfsStreamsSelfTest.testCreateFileColocated(IgfsStreamsSelfTest.java:213)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
{noformat}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5897) Ignite Cache Full API Multi JVM: 7 test failed in master

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-5897:
-

[~ntikhonov]
[~ntikho...@apache.org]

Did you have a chance to look at my pull request?

PR - https://github.com/apache/ignite/pull/2384
TC - 
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests_Ignite20Tests=pull%2F2384%2Fhead
US - http://reviews.ignite.apache.org/ignite/review/IGNT-CR-265

> Ignite Cache Full API Multi JVM: 7 test failed in master
> 
>
> Key: IGNITE-5897
> URL: https://issues.apache.org/jira/browse/IGNITE-5897
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Dmitriy Pavlov
>Assignee: Nikolay Izhikov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Failure on TC: 
> http://ci.ignite.apache.org/viewLog.html?buildId=749671=buildResultsDiv=Ignite20Tests_IgniteCacheFullApiMultiJvm#testNameId-6305397409161667157
> org.apache.ignite.internal.processors.cache.multijvm (7)
> - 
> GridCachePartitionedNearDisabledMultiJvmFullApiSelfTest.testTransformResourceInjection
>   
> - 
> GridCachePartitionedNearDisabledMultiJvmP2PDisabledFullApiSelfTest.testTransformResourceInjection
>
> - 
> GridCachePartitionedNearDisabledOnheapMultiJvmFullApiSelfTest.testTransformResourceInjection
> 
> - GridCacheReplicatedMultiJvmFullApiSelfTest.testTransformResourceInjection   
> - 
> GridCacheReplicatedMultiJvmP2PDisabledFullApiSelfTest.testTransformResourceInjection
> 
> - 
> GridCacheReplicatedNearOnlyMultiJvmFullApiSelfTest.testTransformResourceInjection
>
> - 
> GridCacheReplicatedOnheapMultiJvmFullApiSelfTest.testTransformResourceInjection
>  
> Stable reproducible locally
> First failure changes:
> http://ci.ignite.apache.org/viewLog.html?buildId=727280=buildChangesDiv=Ignite20Tests_IgniteCacheFullApiMultiJvm
> {noformat}
> IGNITE-5753: CPP Memory leak fixed.   Igor Sapego 
> IGNITE-5444: Collections.singletonList is not properly serialized by binary 
> marshaller. This closes #2217.andrey.mashenkov 
> ignite-5722 Cache entries stay in onheap after scan query execution for 
> OFFHEAP_TIRED cache with expiry policyAndrey Gura 
> ignite-5489 Fixed possible connection leaks when loadPreviousValue set to 
> truetikhonovnicolay 
> IGNITE-4831: Add an option to disable MBeans. This closes #2265.  
> andrey.mashenkov   
> {noformat}
> Stacktrace: 
> {noformat}
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea] class 
> org.apache.ignite.IgniteCheckedException: java.lang.NullPointerException
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadFromStore(GridCacheStoreManagerAdapter.java:327)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.load(GridCacheStoreManagerAdapter.java:282)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.readThrough(GridCacheMapEntry.java:445)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet0(GridCacheMapEntry.java:699)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerGet(GridCacheMapEntry.java:461)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.onEntriesLocked(GridDhtTxPrepareFuture.java:389)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare0(GridDhtTxPrepareFuture.java:1213)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.mapIfLocked(GridDhtTxPrepareFuture.java:668)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxPrepareFuture.prepare(GridDhtTxPrepareFuture.java:1034)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxLocal.prepareAsync(GridDhtTxLocal.java:410)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.prepareNearTx(IgniteTxHandler.java:459)
> [2017-08-01 16:27:28,330][INFO ][Thread-4][jvm-fe4cadea]  at 
> 

[jira] [Commented] (IGNITE-5211) Classes based constructor for QueryEntities

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-5211:
--

Waits for [test 
results|https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2407%2Fhead]

> Classes based constructor for QueryEntities
> ---
>
> Key: IGNITE-5211
> URL: https://issues.apache.org/jira/browse/IGNITE-5211
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
>Priority: Critical
> Fix For: 2.2
>
>
> We need to add constructor {{QueryEntity(Class keyType, Class valueType)}} to 
> query entities class and deprecate {{CacheConfiguration.setIndexedTypes(…)}} 
> method.
> Otherwise, there is no easy way for people who define SQL scheme with the 
> annotations to do advanced settings like names of key and value objects, 
> table name, etc.
> See this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/SQL-setting-key-field-name-for-types-registered-via-CacheConfiguration-setIndexedTypes-td17603.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5956) Ignite Continuous Query (Queries 3): IgniteCacheDistributedJoinPartitionedAndReplicatedTest fails

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5956:
---

 Summary: Ignite Continuous Query (Queries 3): 
IgniteCacheDistributedJoinPartitionedAndReplicatedTest fails
 Key: IGNITE-5956
 URL: https://issues.apache.org/jira/browse/IGNITE-5956
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Sergey Chugunov
 Fix For: 2.2


Reproducible locally.

May be broken by commit *70eed75422ea*.

Fails with exception:
{noformat}
javax.cache.CacheException: Failed to execute query: for distributed join all 
REPLICATED caches must be at the end of the joined tables list.

at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2CollocationModel.isCollocated(GridH2CollocationModel.java:704)
at 
org.apache.ignite.internal.processors.query.h2.sql.GridSqlQuerySplitter.split(GridSqlQuerySplitter.java:239)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1309)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1804)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor$5.applyx(GridQueryProcessor.java:1802)
at 
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2282)
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:1809)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:788)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxy.query(IgniteCacheProxy.java:758)
at 
org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.queryPlan(GridCommonAbstractTest.java:1650)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheDistributedJoinPartitionedAndReplicatedTest.checkQuery(IgniteCacheDistributedJoinPartitionedAndReplicatedTest.java:389)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheDistributedJoinPartitionedAndReplicatedTest.checkQueries(IgniteCacheDistributedJoinPartitionedAndReplicatedTest.java:364)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheDistributedJoinPartitionedAndReplicatedTest.join(IgniteCacheDistributedJoinPartitionedAndReplicatedTest.java:283)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheDistributedJoinPartitionedAndReplicatedTest.testJoin2(IgniteCacheDistributedJoinPartitionedAndReplicatedTest.java:197)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1980)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:131)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1895)
at java.lang.Thread.run(Thread.java:745)
{noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5211) Classes based constructor for QueryEntities

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-5211:
--

Fixed. [~vozerov] please review the changes.

> Classes based constructor for QueryEntities
> ---
>
> Key: IGNITE-5211
> URL: https://issues.apache.org/jira/browse/IGNITE-5211
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
>Priority: Critical
> Fix For: 2.2
>
>
> We need to add constructor {{QueryEntity(Class keyType, Class valueType)}} to 
> query entities class and deprecate {{CacheConfiguration.setIndexedTypes(…)}} 
> method.
> Otherwise, there is no easy way for people who define SQL scheme with the 
> annotations to do advanced settings like names of key and value objects, 
> table name, etc.
> See this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/SQL-setting-key-field-name-for-types-registered-via-CacheConfiguration-setIndexedTypes-td17603.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5941) Index with long name stores incorrect

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh reassigned IGNITE-5941:


Assignee: Ilya Lantukh

> Index with long name stores incorrect
> -
>
> Key: IGNITE-5941
> URL: https://issues.apache.org/jira/browse/IGNITE-5941
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Assignee: Ilya Lantukh
> Attachments: LongIndexNameTest.java
>
>
> SQL query by Index with long name return inconsistent result after cluster 
> restart and recover from storage. At the same time a query by other index 
> (with more shorter name) works correctly before and after recovery.
> For example long index name:
> {code}
> QueryIndex index = new QueryIndex("name", true, 
> "COM.SBT.AZIMUTH_PSI.PUBLISHER.ENTITIES.PUB.PARTICLES.CARPORT#MODELCOM.SBT.AZIMUTH_PSI.PUBLISHER.ENTITIES.PUB.PARTICLES.CARPORT");
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5955) Ignite Continuous Query (Queries 3): IgniteCacheContinuousQueryClientReconnectTest fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5955:
---
Affects Version/s: 2.1

> Ignite Continuous Query (Queries 3): 
> IgniteCacheContinuousQueryClientReconnectTest fails
> 
>
> Key: IGNITE-5955
> URL: https://issues.apache.org/jira/browse/IGNITE-5955
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>  Labels: MakeTeamcityGreenAgain, test-failure
> Fix For: 2.2
>
>
> Reproducible locally with the same exception as on TC.
> In test log there is the following exception:
> {noformat}
> [2017-08-07 
> 03:24:05,694][ERROR][test-runner-#10587%continuous.IgniteCacheContinuousQueryClientReconnectTest%][root]
>  Failed to stop grid 
> [igniteInstanceName=continuous.IgniteCacheContinuousQueryClientReconnectTest0,
>  cancel=true]
> class org.apache.ignite.IgniteClientDisconnectedException: Client node 
> disconnected: continuous.IgniteCacheContinuousQueryClientReconnectTest4
> at 
> org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:92)
> at org.apache.ignite.internal.IgniteKernal.guard(IgniteKernal.java:3707)
> at org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3423)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.awaitTopologyChange(GridAbstractTest.java:2105)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1030)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1006)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:997)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.access$200(IgniteCacheContinuousQueryClientReconnectTest.java:42)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest$1.run(IgniteCacheContinuousQueryClientReconnectTest.java:151)
> at 
> org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNodes(IgniteClientReconnectAbstractTest.java:290)
> at 
> org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNode(IgniteClientReconnectAbstractTest.java:221)
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.testReconnectClientAndLeftRouter(IgniteCacheContinuousQueryClientReconnectTest.java:149)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> According to [TC 
> history|https://ci.ignite.apache.org/project.html?tab=testDetails_Ignite20Tests=%3Cdefault%3E=Ignite20Tests=9004507841514895830=5]
>  is failing since mid of April.
> Last commit where test has been passing is *b6b3d3754849*.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5954) Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5954:
---
Affects Version/s: 2.1

> Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove 
> fails
> --
>
> Key: IGNITE-5954
> URL: https://issues.apache.org/jira/browse/IGNITE-5954
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Probably, it's broken after IGNITE-5272.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5233) JDBC thin Driver: implement metadata support

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-5233:


[~tledkov-gridgain]
My comments:

1. {{JdbcRequestHandler.matches()}}
using {{toUpperCase}} in {{matches()}} seems wrong. Don't we store escaped 
table names in original case?

2. {{JdbcRequestHandler.getColumnsMeta()}}
{{req.cacheName()}} is passed to {{JdbcColumnMeta}} constructor, but in the 
beginning of the method you had to split {{req.tableName()}} in order to get 
{{cacheName}}.

3. {{JdbcRequestHandler.getColumnsMeta()}} and 
{{JdbcRequestHandler.getIndexesMeta()}}
The corresponding JDBC api allows {{null}} for parameters {{schema}} and 
{{table}}.
I see no checks for {{null}} for {{tableName()}} before calling 
{{contains(".")}}.

4. {{JdbcRequestHandler.getPrimaryKeys()}}
It seems that logic for using {{_KEY}} or {{table.getKeyFieldName()}} is not 
correct.
{{table.getKeyFieldName()}} may be {{null}} even if there are fields that are 
marked as key constituents.
Moreover, the field with name {{table.getKeyFieldName()}} will also return 
{{true}} for {{key()}}.

Also, error message text in the exception handler is wrong.

5. {{JdbcRequestHandler.getSchemas()}}
Wrong error message.

6. {{JdbcResult}}
Misprint in javadoc: JDBS->JDBC
Wrong javadoc for {{META_SCHEMAS}} static field.

7. {{JdbcMetaindexResult}}
default constructor assigns meta to itself.

8. {{JdbcThinParameterMetaData}}
Wrong javadoc for class header.

9. {{JdbcThinDatabaseMetadata.readonly()}}
Why we declare database read-only?

10. {{JdbcThinDatabaseMetadata.supportsMixedCaseQuotedIdentifiers()}}, 
{{JdbcThinDatabaseMetadata.storesUpperCaseQuotedIdentifiers()}} seems to return 
incorrect value.

11. {{JdbcThinDatabaseMetadata.getIdentifierQuoteString()}} 
Shouldn't it return "\"" instead of " " ?


> JDBC thin Driver: implement metadata support 
> -
>
> Key: IGNITE-5233
> URL: https://issues.apache.org/jira/browse/IGNITE-5233
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.0
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.2
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5954) Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5954:
---
Fix Version/s: 2.2

> Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove 
> fails
> --
>
> Key: IGNITE-5954
> URL: https://issues.apache.org/jira/browse/IGNITE-5954
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Probably, it's broken after IGNITE-5272.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5691) IgniteHadoopFileSystemShmemExternalDualAsyncSelfTest sometimes hangs on TC

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5691:
---
Fix Version/s: 2.2

> IgniteHadoopFileSystemShmemExternalDualAsyncSelfTest sometimes hangs on TC
> --
>
> Key: IGNITE-5691
> URL: https://issues.apache.org/jira/browse/IGNITE-5691
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Fix For: 2.2
>
> Attachments: Ignite_2.0_Tests_Ignite_IGFS_Linux_and_MacOS_444.log.zip
>
>
> Hangs when output stream is closed:
> {noformat}
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] Thread 
> [name="test-runner-#15168%grid%", id=24808, state=WAITING, blockCnt=0, 
> waitCnt=3]
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> sun.misc.Unsafe.park(Native Method)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:315)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.i.processors.hadoop.impl.igfs.HadoopIgfsOutProc.closeStream(HadoopIgfsOutProc.java:446)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.i.processors.hadoop.impl.igfs.HadoopIgfsOutputStream.close(HadoopIgfsOutputStream.java:142)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> java.io.FilterOutputStream.close(FilterOutputStream.java:160)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> org.apache.hadoop.fs.FSDataOutputStream$PositionCache.close(FSDataOutputStream.java:70)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> org.apache.hadoop.fs.FSDataOutputStream.close(FSDataOutputStream.java:103)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.i.processors.hadoop.impl.igfs.IgniteHadoopFileSystemAbstractSelfTest.testDeleteSuccessfulIfPathIsOpenedToRead(IgniteHadoopFileSystemAbstractSelfTest.java:752)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> java.lang.reflect.Method.invoke(Method.java:606)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> junit.framework.TestCase.runTest(TestCase.java:176)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5691) IgniteHadoopFileSystemShmemExternalDualAsyncSelfTest sometimes hangs on TC

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5691:
---
Priority: Critical  (was: Major)

> IgniteHadoopFileSystemShmemExternalDualAsyncSelfTest sometimes hangs on TC
> --
>
> Key: IGNITE-5691
> URL: https://issues.apache.org/jira/browse/IGNITE-5691
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
> Fix For: 2.2
>
> Attachments: Ignite_2.0_Tests_Ignite_IGFS_Linux_and_MacOS_444.log.zip
>
>
> Hangs when output stream is closed:
> {noformat}
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] Thread 
> [name="test-runner-#15168%grid%", id=24808, state=WAITING, blockCnt=0, 
> waitCnt=3]
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> sun.misc.Unsafe.park(Native Method)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> java.util.concurrent.locks.LockSupport.park(LockSupport.java:315)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.i.processors.hadoop.impl.igfs.HadoopIgfsOutProc.closeStream(HadoopIgfsOutProc.java:446)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.i.processors.hadoop.impl.igfs.HadoopIgfsOutputStream.close(HadoopIgfsOutputStream.java:142)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> java.io.FilterOutputStream.close(FilterOutputStream.java:160)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> org.apache.hadoop.fs.FSDataOutputStream$PositionCache.close(FSDataOutputStream.java:70)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> org.apache.hadoop.fs.FSDataOutputStream.close(FSDataOutputStream.java:103)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.i.processors.hadoop.impl.igfs.IgniteHadoopFileSystemAbstractSelfTest.testDeleteSuccessfulIfPathIsOpenedToRead(IgniteHadoopFileSystemAbstractSelfTest.java:752)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> java.lang.reflect.Method.invoke(Method.java:606)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> junit.framework.TestCase.runTest(TestCase.java:176)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> o.a.i.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
> [12:38:39]W:   [org.apache.ignite:ignite-hadoop] at 
> java.lang.Thread.run(Thread.java:745)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5953) Missed off-heap unswapping in GridCacheMap.versionedValue()

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-5953:

Fix Version/s: (was: 2.2)
   2.0

> Missed off-heap unswapping in GridCacheMap.versionedValue()
> ---
>
> Key: IGNITE-5953
> URL: https://issues.apache.org/jira/browse/IGNITE-5953
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-5953) Missed off-heap unswapping in GridCacheMap.versionedValue()

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev resolved IGNITE-5953.
-
Resolution: Duplicate

> Missed off-heap unswapping in GridCacheMap.versionedValue()
> ---
>
> Key: IGNITE-5953
> URL: https://issues.apache.org/jira/browse/IGNITE-5953
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.9
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.2
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5751) In TcpCommunicationSpi.createTcpClient U.filterReachable waits all addresses to check if they are reachable

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev updated IGNITE-5751:
--
Priority: Trivial  (was: Critical)

> In TcpCommunicationSpi.createTcpClient U.filterReachable waits all addresses 
> to check if they are reachable
> ---
>
> Key: IGNITE-5751
> URL: https://issues.apache.org/jira/browse/IGNITE-5751
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.1
>Reporter: Evgenii Zhuravlev
>Priority: Trivial
> Fix For: 2.2
>
>
> In TcpCommunicationSpi.createTcpClient replace U.filterReachable with 
> filtering first reachable address



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5955) Ignite Continuous Query (Queries 3): IgniteCacheContinuousQueryClientReconnectTest fails

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov updated IGNITE-5955:

Description: 
Reproducible locally with the same exception as on TC.

In test log there is the following exception:
{noformat}
[2017-08-07 
03:24:05,694][ERROR][test-runner-#10587%continuous.IgniteCacheContinuousQueryClientReconnectTest%][root]
 Failed to stop grid 
[igniteInstanceName=continuous.IgniteCacheContinuousQueryClientReconnectTest0, 
cancel=true]
class org.apache.ignite.IgniteClientDisconnectedException: Client node 
disconnected: continuous.IgniteCacheContinuousQueryClientReconnectTest4
at 
org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:92)
at org.apache.ignite.internal.IgniteKernal.guard(IgniteKernal.java:3707)
at org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3423)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.awaitTopologyChange(GridAbstractTest.java:2105)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1030)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1006)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:997)
at 
org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.access$200(IgniteCacheContinuousQueryClientReconnectTest.java:42)
at 
org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest$1.run(IgniteCacheContinuousQueryClientReconnectTest.java:151)
at 
org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNodes(IgniteClientReconnectAbstractTest.java:290)
at 
org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNode(IgniteClientReconnectAbstractTest.java:221)
at 
org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.testReconnectClientAndLeftRouter(IgniteCacheContinuousQueryClientReconnectTest.java:149)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
{noformat}

According to [TC 
history|https://ci.ignite.apache.org/project.html?tab=testDetails_Ignite20Tests=%3Cdefault%3E=Ignite20Tests=9004507841514895830=5]
 is failing since mid of April.

Last commit where test has been passing is *b6b3d3754849*.



  was:
Reproducible locally with the same exception as on TC.

In test log there is the following exception:
{noformat}
[2017-08-07 
03:24:05,694][ERROR][test-runner-#10587%continuous.IgniteCacheContinuousQueryClientReconnectTest%][root]
 Failed to stop grid 
[igniteInstanceName=continuous.IgniteCacheContinuousQueryClientReconnectTest0, 
cancel=true]
class org.apache.ignite.IgniteClientDisconnectedException: Client node 
disconnected: continuous.IgniteCacheContinuousQueryClientReconnectTest4
at 
org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:92)
at org.apache.ignite.internal.IgniteKernal.guard(IgniteKernal.java:3707)
at org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3423)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.awaitTopologyChange(GridAbstractTest.java:2105)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1030)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1006)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:997)
at 
org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.access$200(IgniteCacheContinuousQueryClientReconnectTest.java:42)
at 
org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest$1.run(IgniteCacheContinuousQueryClientReconnectTest.java:151)
at 
org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNodes(IgniteClientReconnectAbstractTest.java:290)
at 
org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNode(IgniteClientReconnectAbstractTest.java:221)
at 

[jira] [Updated] (IGNITE-5955) Ignite Continuous Query (Queries 3): IgniteCacheContinuousQueryClientReconnectTest fails

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov updated IGNITE-5955:

Description: 
Reproducible locally with the same exception as on TC.

In test log is the following exception:
{noformat}
[2017-08-07 
03:24:05,694][ERROR][test-runner-#10587%continuous.IgniteCacheContinuousQueryClientReconnectTest%][root]
 Failed to stop grid 
[igniteInstanceName=continuous.IgniteCacheContinuousQueryClientReconnectTest0, 
cancel=true]
class org.apache.ignite.IgniteClientDisconnectedException: Client node 
disconnected: continuous.IgniteCacheContinuousQueryClientReconnectTest4
at 
org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:92)
at org.apache.ignite.internal.IgniteKernal.guard(IgniteKernal.java:3707)
at org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3423)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.awaitTopologyChange(GridAbstractTest.java:2105)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1030)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:1006)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.stopGrid(GridAbstractTest.java:997)
at 
org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.access$200(IgniteCacheContinuousQueryClientReconnectTest.java:42)
at 
org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest$1.run(IgniteCacheContinuousQueryClientReconnectTest.java:151)
at 
org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNodes(IgniteClientReconnectAbstractTest.java:290)
at 
org.apache.ignite.internal.IgniteClientReconnectAbstractTest.reconnectClientNode(IgniteClientReconnectAbstractTest.java:221)
at 
org.apache.ignite.internal.processors.cache.query.continuous.IgniteCacheContinuousQueryClientReconnectTest.testReconnectClientAndLeftRouter(IgniteCacheContinuousQueryClientReconnectTest.java:149)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
at java.lang.Thread.run(Thread.java:745)
{noformat}

According to [TC 
history|https://ci.ignite.apache.org/project.html?tab=testDetails_Ignite20Tests=%3Cdefault%3E=Ignite20Tests=9004507841514895830=5]
 is failing since mid of April.

Last commit where test has been passing is *b6b3d3754849*. After it test 
started failing, but on different line than that it is failing on now.



  was:
Reproducible locally with the same exception as on TC.

According to [TC 
history|https://ci.ignite.apache.org/project.html?tab=testDetails_Ignite20Tests=%3Cdefault%3E=Ignite20Tests=9004507841514895830=5]
 is failing since mid of April.

Last commit where test has been passing is *b6b3d3754849*. After it test 
started failing, but on different line than that it is failing on now.




> Ignite Continuous Query (Queries 3): 
> IgniteCacheContinuousQueryClientReconnectTest fails
> 
>
> Key: IGNITE-5955
> URL: https://issues.apache.org/jira/browse/IGNITE-5955
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Chugunov
>  Labels: MakeTeamcityGreenAgain, test-failure
>
> Reproducible locally with the same exception as on TC.
> In test log is the following exception:
> {noformat}
> [2017-08-07 
> 03:24:05,694][ERROR][test-runner-#10587%continuous.IgniteCacheContinuousQueryClientReconnectTest%][root]
>  Failed to stop grid 
> [igniteInstanceName=continuous.IgniteCacheContinuousQueryClientReconnectTest0,
>  cancel=true]
> class org.apache.ignite.IgniteClientDisconnectedException: Client node 
> disconnected: continuous.IgniteCacheContinuousQueryClientReconnectTest4
> at 
> org.apache.ignite.internal.GridKernalGatewayImpl.readLock(GridKernalGatewayImpl.java:92)
> at org.apache.ignite.internal.IgniteKernal.guard(IgniteKernal.java:3707)
> at org.apache.ignite.internal.IgniteKernal.active(IgniteKernal.java:3423)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.awaitTopologyChange(GridAbstractTest.java:2105)
> at 
> 

[jira] [Updated] (IGNITE-1793) [Failed Test] IgnitePartitionedCountDownLatchSelfTest.testLatch hangs on TC sometimes

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-1793:
--
Labels: MakeTeamcityGreenAgain Muted_test  (was: Muted_test)

> [Failed Test] IgnitePartitionedCountDownLatchSelfTest.testLatch   hangs 
> on TC sometimes
> -
>
> Key: IGNITE-1793
> URL: https://issues.apache.org/jira/browse/IGNITE-1793
> Project: Ignite
>  Issue Type: Test
>Reporter: Artem Shutak
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.2
>
> Attachments: test.logs
>
>
> IgnitePartitionedCountDownLatchSelfTest.testLatch hangs on TC sometimes.
> Test hangs on IgniteCountDownLatch.count() method.
> {noformat}
> Thread [name="test-runner", id=24157, state=WAITING, blockCnt=0, waitCnt=96]
> Lock [object=o.a.i.i.util.future.GridFutureAdapter$ChainFuture@1e542154, 
> ownerName=null, ownerId=-1]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at 
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
> at 
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at 
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4525)
> at 
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1544)
> at 
> o.a.i.i.processors.datastructures.GridCacheCountDownLatchImpl$GetCountCallable.call(GridCacheCountDownLatchImpl.java:348)
> at 
> o.a.i.i.processors.datastructures.GridCacheCountDownLatchImpl$GetCountCallable.call(GridCacheCountDownLatchImpl.java:342)
> at 
> o.a.i.i.processors.cache.GridCacheUtils.outTx(GridCacheUtils.java:962)
> at 
> o.a.i.i.processors.datastructures.GridCacheCountDownLatchImpl.count(GridCacheCountDownLatchImpl.java:143)
> at 
> o.a.i.i.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest.checkRemovedLatch(IgniteCountDownLatchAbstractSelfTest.java:159)
> at 
> o.a.i.i.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest.checkCountDown(IgniteCountDownLatchAbstractSelfTest.java:232)
> at 
> o.a.i.i.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest.checkLatch(IgniteCountDownLatchAbstractSelfTest.java:84)
> at 
> o.a.i.i.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest.testLatch(IgniteCountDownLatchAbstractSelfTest.java:72)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> o.a.i.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1658)
> at 
> o.a.i.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:112)
> at 
> o.a.i.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1596)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-584) Need to make sure that scan query returns consistent results on topology changes

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-584:
-
Labels: MakeTeamcityGreenAgain Muted_test  (was: Muted_test)

> Need to make sure that scan query returns consistent results on topology 
> changes
> 
>
> Key: IGNITE-584
> URL: https://issues.apache.org/jira/browse/IGNITE-584
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Artem Shutak
>  Labels: MakeTeamcityGreenAgain, Muted_test
>
> Consistent results on topology changes was implemented for sql queries, but 
> looks like it still does not work for scan queries.
> This affects 'cache set' tests since set uses scan query for set iteration 
> (to be unmuted on TC): 
> GridCacheSetAbstractSelfTest testNodeJoinsAndLeaves and 
> testNodeJoinsAndLeavesCollocated; 
> Also see todos here GridCacheSetFailoverAbstractSelfTest



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5949) DDL: Support ALTER TABLE DROP COLUMN

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko updated IGNITE-5949:

Description: Ignite should support {{DROP COLUMN}} operation for {{ALTER 
TABLE}} command.  (was: Ignite should supports {{DROP COLUMN}} operation for 
{{ALTER TABLE}} command.)

> DDL: Support ALTER TABLE DROP COLUMN
> 
>
> Key: IGNITE-5949
> URL: https://issues.apache.org/jira/browse/IGNITE-5949
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Andrew Mashenkov
>
> Ignite should support {{DROP COLUMN}} operation for {{ALTER TABLE}} command.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5954) Ignite Cache Failover: GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails

[Eduard Shangareev (JIRA)]

Eduard Shangareev created IGNITE-5954:
-

 Summary: Ignite Cache Failover: 
GridCacheAtomicNearRemoveFailureTest.testPutAndRemove fails
 Key: IGNITE-5954
 URL: https://issues.apache.org/jira/browse/IGNITE-5954
 Project: Ignite
  Issue Type: Bug
Reporter: Eduard Shangareev


Probably, it's broken after IGNITE-5272.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5384) JDBC Driver: implement ResultSet#getDate(int, Calendar)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5384:


Github user tledkov-gridgain closed the pull request at:

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


> JDBC Driver: implement ResultSet#getDate(int, Calendar)
> ---
>
> Key: IGNITE-5384
> URL: https://issues.apache.org/jira/browse/IGNITE-5384
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.2
>
>
> Current implementation doesn't use Calendar object to convert the date.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Issue Comment Deleted] (IGNITE-5384) JDBC Driver: implement ResultSet#getDate(int, Calendar)

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-5384:
-
Comment: was deleted

(was: The patch  contains code cleanup for {{getDate(int. Calendar)}})

> JDBC Driver: implement ResultSet#getDate(int, Calendar)
> ---
>
> Key: IGNITE-5384
> URL: https://issues.apache.org/jira/browse/IGNITE-5384
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.2
>
>
> Current implementation doesn't use Calendar object to convert the date.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-5384) JDBC Driver: implement ResultSet#getDate(int, Calendar)

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-5384 at 8/7/17 10:18 AM:
---

The patch  contains code cleanup for {{getDate(int. Calendar)}}


was (Author: tledkov-gridgain):
The patch  contains code cleanup for {{getDate(int. Calendar)}}


> JDBC Driver: implement ResultSet#getDate(int, Calendar)
> ---
>
> Key: IGNITE-5384
> URL: https://issues.apache.org/jira/browse/IGNITE-5384
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.2
>
>
> Current implementation doesn't use Calendar object to convert the date.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5384) JDBC Driver: implement ResultSet#getDate(int, Calendar)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5384:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-5384: cleanup



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

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

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

https://github.com/apache/ignite/pull/2405.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 #2405


commit 99da2607e14f25c7e14cdc5d8266a82f593afe84
Author: tledkov-gridgain 
Date:   2017-08-07T10:16:10Z

IGNITE-5384: cleanup




> JDBC Driver: implement ResultSet#getDate(int, Calendar)
> ---
>
> Key: IGNITE-5384
> URL: https://issues.apache.org/jira/browse/IGNITE-5384
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc
>Affects Versions: 2.1
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.2
>
>
> Current implementation doesn't use Calendar object to convert the date.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5953) Missed off-heap unswapping in GridCacheMap.versionedValue()

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-5953:
---

 Summary: Missed off-heap unswapping in 
GridCacheMap.versionedValue()
 Key: IGNITE-5953
 URL: https://issues.apache.org/jira/browse/IGNITE-5953
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.9
Reporter: Dmitry Karachentsev
Assignee: Dmitry Karachentsev
 Fix For: 2.2






--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5912) [Redis] EXPIRE/PEXPIRE on keys

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-5912:


It's ok for me, please check tests on CI server.

> [Redis] EXPIRE/PEXPIRE on keys
> --
>
> Key: IGNITE-5912
> URL: https://issues.apache.org/jira/browse/IGNITE-5912
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> https://redis.io/commands/expire
> https://redis.io/commands/pexpire



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5211) Classes based constructor for QueryEntities

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5211:
-

[~tledkov-gridgain], my comments:
1) I do not see reverts of {{queryEntity}} setter. There should not be 3-4 
changed classes in patch, not 100.
2) New classes are query-specific, and hence should reside in query internal 
package, not inside {{cache.configuration}}.

> Classes based constructor for QueryEntities
> ---
>
> Key: IGNITE-5211
> URL: https://issues.apache.org/jira/browse/IGNITE-5211
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
>Priority: Critical
> Fix For: 2.2
>
>
> We need to add constructor {{QueryEntity(Class keyType, Class valueType)}} to 
> query entities class and deprecate {{CacheConfiguration.setIndexedTypes(…)}} 
> method.
> Otherwise, there is no easy way for people who define SQL scheme with the 
> annotations to do advanced settings like names of key and value objects, 
> table name, etc.
> See this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/SQL-setting-key-field-name-for-types-registered-via-CacheConfiguration-setIndexedTypes-td17603.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5952) Need to refactor IgniteSystemProperties

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-5952:
-

 Summary: Need to refactor IgniteSystemProperties
 Key: IGNITE-5952
 URL: https://issues.apache.org/jira/browse/IGNITE-5952
 Project: Ignite
  Issue Type: Improvement
Reporter: Yakov Zhdanov
Priority: Minor


I would think of introducing enum each member of one should clearly define:
# name and envvar/sysprop name to set
# type
# default value
# additional methods for parsing and validation
# documentation, possibly, with links to code 

This should help to avoid situations like this:
org.apache.ignite.internal.IgniteKernal#PERIODIC_STARVATION_CHECK_FREQ and 
org.apache.ignite.IgniteSystemProperties#IGNITE_STARVATION_CHECK_INTERVAL. Here 
property and its default are defined with different properties and default is 
not stated in configuration.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5951) DDL: Support CREATE VIEW

[Vyacheslav Koptilin (JIRA)]

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

Vyacheslav Koptilin updated IGNITE-5951:

Description: 
Ignite should support sql VIEW.

The issue was mentioned on Stack Overflow:
https://stackoverflow.com/questions/45542016/unable-to-create-a-view-in-apache-ignite/45543134

  was:Ignite should support sql VIEW.


> DDL: Support CREATE VIEW
> 
>
> Key: IGNITE-5951
> URL: https://issues.apache.org/jira/browse/IGNITE-5951
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Vyacheslav Koptilin
>Priority: Minor
>
> Ignite should support sql VIEW.
> The issue was mentioned on Stack Overflow:
> https://stackoverflow.com/questions/45542016/unable-to-create-a-view-in-apache-ignite/45543134



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5951) DDL: Support CREATE VIEW

[Vyacheslav Koptilin (JIRA)]

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

Vyacheslav Koptilin updated IGNITE-5951:

Affects Version/s: (was: 2.1)

> DDL: Support CREATE VIEW
> 
>
> Key: IGNITE-5951
> URL: https://issues.apache.org/jira/browse/IGNITE-5951
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Vyacheslav Koptilin
>Priority: Minor
>
> Ignite should support sql VIEW.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5951) DDL: Support CREATE VIEW

[Vyacheslav Koptilin (JIRA)]

Vyacheslav Koptilin created IGNITE-5951:
---

 Summary: DDL: Support CREATE VIEW
 Key: IGNITE-5951
 URL: https://issues.apache.org/jira/browse/IGNITE-5951
 Project: Ignite
  Issue Type: Improvement
  Components: sql
Affects Versions: 2.1
Reporter: Vyacheslav Koptilin
Priority: Minor


Ignite should support sql VIEW.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5910) Method stopGrid(name) doesn't work in multiJvm mode

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur commented on IGNITE-5910:


[~dpavlov], 
I tested the PR-branch and the master-branch all weekends.
I found fails in the {{Ignite Basic}} build-plan which are absent in the 
master-branch.
At the same time {{Ignite Cache 2}} and {{Ignite Cache 3}} build-plans look 
better than in the master-branch.
I will investigate found issue more deeply. Moved the ticket to In-Progress.
Thanks!

> Method stopGrid(name) doesn't work in multiJvm mode
> ---
>
> Key: IGNITE-5910
> URL: https://issues.apache.org/jira/browse/IGNITE-5910
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
> Fix For: 2.2
>
>
> {code:title=Exception at call}
> java.lang.ClassCastException: 
> org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy cannot be 
> cast to org.apache.ignite.internal.IgniteKernal
> {code}
> {code:title=Reproducer snippet}
> /** {@inheritDoc} */
> @Override protected boolean isMultiJvm() {
> return true;
> }
> /**
>  * @throws Exception If failed.
>  */
> public void testGrid() throws Exception {
> try {
> startGrid(0);
> startGrid(1);
> }
> finally {
> stopGrid(1);
> stopGrid(0);
> }
> }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5912) [Redis] EXPIRE/PEXPIRE on keys

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-5912:
--

Hi [~anovikov],

I missed `KEY_REQUIRED_REQUESTS`. Thanks for pointing! How about it now?

> [Redis] EXPIRE/PEXPIRE on keys
> --
>
> Key: IGNITE-5912
> URL: https://issues.apache.org/jira/browse/IGNITE-5912
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> https://redis.io/commands/expire
> https://redis.io/commands/pexpire



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5918) Adding and searching objects in index tree produces a lot of garbage

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5918:
-

[~gvvinblade], looks good to me in general, but proposed improvement is not 
tested properly. We need to add much more tests to cover various string 
scenarios, including 1 byte chars (Latin), 2 byte chars (e.g. Cyrillic), and 
4-byte surrogate chars. 

> Adding and searching objects in index tree produces a lot of garbage
> 
>
> Key: IGNITE-5918
> URL: https://issues.apache.org/jira/browse/IGNITE-5918
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.1
>Reporter: Mikhail Cherkasov
>Assignee: Igor Seliverstov
>
> Adding and searching objects in index tree produces a lot of garbage and this 
> can lead to big GC pauses.
> Tests with data streaming of object with 5 string indexes show that ignite 
> server spends about 15-25% CPU time in GC.
> The problem is that ignite deserialize objects for comparing, while for the 
> primitive type and strings comparing can be implemented for bytes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-5950) Incorrect assertion for cache size

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5950:
---

 Summary: Incorrect assertion for cache size
 Key: IGNITE-5950
 URL: https://issues.apache.org/jira/browse/IGNITE-5950
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Affects Versions: 2.1
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
Priority: Critical
 Fix For: 2.2


*PagePartitionCountersIO::readCacheSizes* incorrectly asserts cache size:

{noformat}
public boolean readCacheSizes(long pageAddr, Map res) {
int cnt = getCount(pageAddr);

assert cnt >= 0 && cnt <= Short.MAX_VALUE : cnt;

if (cnt == 0)
return true;

int off = ITEMS_OFF;

for (int i = 0; i < cnt; i++) {
int cacheId = PageUtils.getInt(pageAddr, off);
off += 4;

assert cacheId != 0;

long cacheSize = PageUtils.getLong(pageAddr, off);
off += 8;

assert cacheSize > 0 : cacheSize; //WRONG assertion! cache of zero 
size if totally legal

Long old = res.put(cacheId, cacheSize);

assert old == null;
}

return getLastFlag(pageAddr);
}
{noformat}

Correct assertion is {{cacheSize >= 0}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5930) Long running transactions while load test with 1 or many memory policies, 14-30 caches and >=24 servers

[Ksenia Rybakova (JIRA)]

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

Ksenia Rybakova updated IGNITE-5930:

Summary: Long running transactions while load test with 1 or many memory 
policies, 14-30 caches and >=24 servers  (was: Long running transactions while 
load test with 1 memory policy, 14 caches and >=24 servers)

> Long running transactions while load test with 1 or many memory policies, 
> 14-30 caches and >=24 servers
> ---
>
> Key: IGNITE-5930
> URL: https://issues.apache.org/jira/browse/IGNITE-5930
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ksenia Rybakova
> Attachments: ignite-base-load-config.xml, run-load.properties, 
> run-load.xml
>
>
> 1) Load config:
> - CacheRandomOperation benchmark
> - Caches:
> atomic partitioned cache
> 2 tx partitioned caches
> 2 atomic partitioned onheap caches
> 2 atomic replicated onheap caches
> 2 tx partitioned onheap caches
> 2 tx replicated onheap caches
> 3 partitioned atomic indexed caches
> - 1 default memory policy is used
> - Preload amount: 500K-2.5M entries per cache
> - Key range: 1M
> - Persistent store is disabled
> - 24 server nodes or more (3 nodes per physical host), 16 client nodes
> Long running transactions occur after preloading and throughput dropps to 0. 
> Note, that with 16 server nodes transactions are ok.
> Complete configs are attached.
> 2) Another config that causes long running transactions:
> - CacheRandomOperation benchmark
> - 30 caches with different config
> - Separate memory policy is used for each cache
> - Preload amount: 500K-2.5M entries per cache
> - Key range: 1M
> - Persistent store is disabled
> - 24 server nodes or more (3 nodes per physical host), 16 client nodes
> Complete configs are attached.
> Note, that with 16 server nodes long running transactions are still there, 
> but throughput is much higher.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5930) Long running transactions while load test with 1 memory policy, 14 caches and >=24 servers

[Ksenia Rybakova (JIRA)]

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

Ksenia Rybakova updated IGNITE-5930:

Description: 
1) Load config:
- CacheRandomOperation benchmark
- Caches:
atomic partitioned cache
2 tx partitioned caches
2 atomic partitioned onheap caches
2 atomic replicated onheap caches
2 tx partitioned onheap caches
2 tx replicated onheap caches
3 partitioned atomic indexed caches
- 1 default memory policy is used
- Preload amount: 500K-2.5M entries per cache
- Key range: 1M
- Persistent store is disabled
- 24 server nodes or more (3 nodes per physical host), 16 client nodes

Long running transactions occur after preloading and throughput dropps to 0. 
Note, that with 16 server nodes transactions are ok.

Complete configs are attached.

2) Another config that causes long running transactions:
- CacheRandomOperation benchmark
- 30 caches with different config
- Separate memory policy is used for each cache
- Preload amount: 500K-2.5M entries per cache
- Key range: 1M
- Persistent store is disabled
- 24 server nodes or more (3 nodes per physical host), 16 client nodes

Complete configs are attached.
Note, that with 16 server nodes long running transactions are still there, but 
throughput is much higher.

  was:
Load config:
- CacheRandomOperation benchmark
- Caches:
atomic partitioned cache
2 tx partitioned caches
2 atomic partitioned onheap caches
2 atomic replicated onheap caches
2 tx partitioned onheap caches
2 tx replicated onheap caches
3 partitioned atomic indexed caches
- 1 default memory policy is used
- Preload amount: 500K-2.5M entries per cache
- Key range: 1M
- Persistent store is disabled
- 24 server nodes or more (3 nodes per physical host), 16 client nodes

Long running transactions occur after preloading and throughput dropps to 0. 
Note, that with 16 server nodes transactions are ok.

Complete configs are attached.


> Long running transactions while load test with 1 memory policy, 14 caches and 
> >=24 servers
> --
>
> Key: IGNITE-5930
> URL: https://issues.apache.org/jira/browse/IGNITE-5930
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ksenia Rybakova
> Attachments: ignite-base-load-config.xml, run-load.properties, 
> run-load.xml
>
>
> 1) Load config:
> - CacheRandomOperation benchmark
> - Caches:
> atomic partitioned cache
> 2 tx partitioned caches
> 2 atomic partitioned onheap caches
> 2 atomic replicated onheap caches
> 2 tx partitioned onheap caches
> 2 tx replicated onheap caches
> 3 partitioned atomic indexed caches
> - 1 default memory policy is used
> - Preload amount: 500K-2.5M entries per cache
> - Key range: 1M
> - Persistent store is disabled
> - 24 server nodes or more (3 nodes per physical host), 16 client nodes
> Long running transactions occur after preloading and throughput dropps to 0. 
> Note, that with 16 server nodes transactions are ok.
> Complete configs are attached.
> 2) Another config that causes long running transactions:
> - CacheRandomOperation benchmark
> - 30 caches with different config
> - Separate memory policy is used for each cache
> - Preload amount: 500K-2.5M entries per cache
> - Key range: 1M
> - Persistent store is disabled
> - 24 server nodes or more (3 nodes per physical host), 16 client nodes
> Complete configs are attached.
> Note, that with 16 server nodes long running transactions are still there, 
> but throughput is much higher.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5572) DDL: Support ALTER TABLE ADD COLUMN

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5572:

Fix Version/s: 2.2

> DDL: Support ALTER TABLE ADD COLUMN
> ---
>
> Key: IGNITE-5572
> URL: https://issues.apache.org/jira/browse/IGNITE-5572
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.2
>
>
> We should start gradual implementation of {{ALTER TABLE}} command. Let's 
> start with the most simple part - {{ADD COLUMN}}. Proposed design:
> 1) Send a message over a ring, similar to how we do that for create index
> 2) On local node: update relevant QueryEntity, update data strcutrues in 
> {{GridQueryProcessor}}, update {{IgniteH2Indexing}} data structures, execute 
> {{ALTER TABLE}} command on H2 database (global table lock must be acquired).
> 3) Make sure that update to {{QueryEntity}} is properly saved if persistence 
> is enabled.
> Feature should be covered with tests thoroughly:
> 1) Positive cases
> 2) Negative cases (no schema, no table, column already exists)
> 3) Test with concurrent SQL operations
> 4) Test with concurrent node restarts



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-5949) DDL: Support ALTER TABLE DROP COLUMN

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5949:

Fix Version/s: (was: 2.2)

> DDL: Support ALTER TABLE DROP COLUMN
> 
>
> Key: IGNITE-5949
> URL: https://issues.apache.org/jira/browse/IGNITE-5949
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Andrew Mashenkov
>
> Ignite should supports {{DROP COLUMN}} operation for {{ALTER TABLE}} command.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5794) BinaryMetadata is lost if all server nodes have been restarted

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov commented on IGNITE-5794:
-

More specific detail: after reconnect client still has binary metadata about 
custom type in BinaryContext::descByClass collection.
So to fix the root cause problem descriptors for custom types must be cleaned 
up from it, however it must be extensively tested to be sure that such a change 
won't break anything else.

> BinaryMetadata is lost if all server nodes have been restarted
> --
>
> Key: IGNITE-5794
> URL: https://issues.apache.org/jira/browse/IGNITE-5794
> Project: Ignite
>  Issue Type: Bug
>  Components: binary, general
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>
> Steps to reproduce are described here: 
> http://apache-ignite-users.70518.x6.nabble.com/Problem-with-Messages-after-client-reconnect-td15127.html#none
> This problem occurs because client has metadata in it's local metadata cache 
> and decides that server node should have it too. But server lost it after 
> restart.
> Possible fixes:
> - Make client nodes re-send all contents of local metadata cache after 
> reconnect.
> - If node doesn't have metadata to process incoming message, it should 
> request it from sender node.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)