date:20200708

[jira] [Commented] (IGNITE-13229) GridClient instance leakage.

2020-07-08 Thread Stanilovsky Evgeny (Jira)



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

Stanilovsky Evgeny commented on IGNITE-13229:
-

looks like all ok, besides [1]but this is already existing problem, not mine.

[1] 
[https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PdsIndexing?branch==builds]

[~agoncharuk] can you check it please ?

> GridClient instance leakage.
> 
>
> Key: IGNITE-13229
> URL: https://issues.apache.org/jira/browse/IGNITE-13229
> Project: Ignite
>  Issue Type: Improvement
>  Components: thin client
>Affects Versions: 2.8.1
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Instances of GridClient - deprecated realization of thin client, still used 
> for example, in _control.sh_ can be leaked in some circumstances. Can bring 
> to OOM in some tests.



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

[jira] [Commented] (IGNITE-13229) GridClient instance leakage.

2020-07-08 Thread Ignite TC Bot (Jira)



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

Ignite TC Bot commented on IGNITE-13229:


{panel:title=Branch: [pull/8006/head] Base: [master] : Possible Blockers 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5450047]]

{panel}
{panel:title=Branch: [pull/8006/head] Base: [master] : New Tests 
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid{color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=1d3deeb7-c13d-4740-bc54-9ba5c8c1a4ee, topVer=0, 
nodeId8=6ef28d05, msg=, type=NODE_JOINED, tstamp=1594220236209], 
val2=AffinityTopologyVersion [topVer=7215358582909498952, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=1d3deeb7-c13d-4740-bc54-9ba5c8c1a4ee, topVer=0, 
nodeId8=6ef28d05, msg=, type=NODE_JOINED, tstamp=1594220236209], 
val2=AffinityTopologyVersion [topVer=7215358582909498952, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=5bd4eee2371-9569be51-7b3f-4180-9dd2-57341d8cd813, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=0a4002e9-1db2-4e32-9f20-c61157ef731c, topVer=0, nodeId8=0a4002e9, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594220236209]], 
val2=AffinityTopologyVersion [topVer=440979196143354, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=5bd4eee2371-9569be51-7b3f-4180-9dd2-57341d8cd813, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=0a4002e9-1db2-4e32-9f20-c61157ef731c, topVer=0, nodeId8=0a4002e9, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594220236209]], 
val2=AffinityTopologyVersion [topVer=440979196143354, minorTopVer=0]]] - 
PASSED{color}

{color:#8b}Service Grid (legacy mode){color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=0d0512d1-bed1-4a2f-b239-f76e31739329, topVer=0, 
nodeId8=2a4e0452, msg=, type=NODE_JOINED, tstamp=1594220520431], 
val2=AffinityTopologyVersion [topVer=-3810796796632234237, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=0d0512d1-bed1-4a2f-b239-f76e31739329, topVer=0, 
nodeId8=2a4e0452, msg=, type=NODE_JOINED, tstamp=1594220520431], 
val2=AffinityTopologyVersion [topVer=-3810796796632234237, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=3f3a2fe2371-aac23888-8aee-4812-a212-5e9c11adf721, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=543d7ad7-7861-4a68-9dbd-98a9c7a05b0b, topVer=0, nodeId8=543d7ad7, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594220520431]], 
val2=AffinityTopologyVersion [topVer=997360565232791116, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=3f3a2fe2371-aac23888-8aee-4812-a212-5e9c11adf721, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=543d7ad7-7861-4a68-9dbd-98a9c7a05b0b, topVer=0, nodeId8=543d7ad7, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594220520431]], 
val2=AffinityTopologyVersion [topVer=997360565232791116, minorTopVer=0]]] - 
PASSED{color}

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5449497buildTypeId=IgniteTests24Java8_RunAll]

> GridClient instance leakage.
> 
>
> Key: IGNITE-13229
> URL: https://issues.apache.org/jira/browse/IGNITE-13229
> Project: Ignite
>  Issue Type: Improvement
>  Components: thin client
>Affects Versions: 2.8.1
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Time Spent: 10m
>

[jira] [Commented] (IGNITE-12346) .NET: Platform error:System.NullReferenceException

2020-07-08 Thread Ignite TC Bot (Jira)



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

Ignite TC Bot commented on IGNITE-12346:


{panel:title=Branch: [pull/8007/head] Base: [master] : Possible Blockers 
(4)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}SPI{color} [[tests 0 TIMEOUT , Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5450468]]

{color:#d04437}Cache 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5450499]]
* IgniteBinaryCacheTestSuite: 
GridCacheStopSelfTest.testStopImplicitMvccTransactionsReplicated - Test has low 
fail rate in base branch 0,0% and is not flaky

{color:#d04437}MVCC Cache 2{color} [[tests 
2|https://ci.ignite.apache.org/viewLog.html?buildId=5450535]]
* IgniteCacheMvccTestSuite2: 
CrossCacheTxRandomOperationsTest.testCrossCacheTxOperations - Test has low fail 
rate in base branch 0,0% and is not flaky
* IgniteCacheMvccTestSuite2: 
CrossCacheTxRandomOperationsTest.testCrossCacheTxOperationsReplicated - Test 
has low fail rate in base branch 0,0% and is not flaky

{panel}
{panel:title=Branch: [pull/8007/head] Base: [master] : New Tests 
(12)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET{color} [tests 2]
* {color:#013220}exe: 
CacheQueriesTest.TestScanQueryDisposedFromAnotherThreadThrowsObjectDisposedException
 - PASSED{color}
* {color:#013220}exe: 
CacheQueriesTest.TestScanQueryDisposedFromAnotherThreadThrowsObjectDisposedException
 - PASSED{color}

{color:#8b}Platform .NET (Core Linux){color} [tests 2]
* {color:#013220}dll: 
CacheQueriesTestSimpleName.TestScanQueryDisposedFromAnotherThreadThrowsObjectDisposedException
 - PASSED{color}
* {color:#013220}dll: 
CacheQueriesTest.TestScanQueryDisposedFromAnotherThreadThrowsObjectDisposedException
 - PASSED{color}

{color:#8b}Service Grid{color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=78ee32ce-5d24-48ef-9ed8-7c531334081b, topVer=0, 
nodeId8=1c41a3e1, msg=, type=NODE_JOINED, tstamp=1594251049991], 
val2=AffinityTopologyVersion [topVer=-560450980347361321, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=78ee32ce-5d24-48ef-9ed8-7c531334081b, topVer=0, 
nodeId8=1c41a3e1, msg=, type=NODE_JOINED, tstamp=1594251049991], 
val2=AffinityTopologyVersion [topVer=-560450980347361321, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=b456ec03371-0f5d1ae9-cb29-4f6b-a89d-017d7cce49bd, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=e4440a4e-77e9-476a-b58c-5d2da3791571, topVer=0, nodeId8=e4440a4e, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594251049991]], 
val2=AffinityTopologyVersion [topVer=-3219475227354924568, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=b456ec03371-0f5d1ae9-cb29-4f6b-a89d-017d7cce49bd, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=e4440a4e-77e9-476a-b58c-5d2da3791571, topVer=0, nodeId8=e4440a4e, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594251049991]], 
val2=AffinityTopologyVersion [topVer=-3219475227354924568, minorTopVer=0]]] - 
PASSED{color}

{color:#8b}Service Grid (legacy mode){color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=751f2c03371-621065d0-4217-4201-a23e-ed8aee3484a4, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=ea78b217-f79f-4f17-be2f-02a965137aef, topVer=0, nodeId8=ea78b217, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594250948947]], 
val2=AffinityTopologyVersion [topVer=6738094040448346092, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=c5c0aa22-84e0-447a-bb7b-ac1ab15064d5, topVer=0, 
nodeId8=6ba49f00, msg=, type=NODE_JOINED, tstamp=1594250948947], 
val2=AffinityTopologyVersion [topVer=-3723063100191673047, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=c5c0aa22-84e0-447a-bb7b-ac1ab15064d5, topVer=0,

[jira] [Commented] (IGNITE-13214) .NET different behavior when using TransactionScope and ITransactions.Start

2020-07-08 Thread Ignite TC Bot (Jira)



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

Ignite TC Bot commented on IGNITE-13214:


{panel:title=Branch: [pull/8004/head] Base: [master] : Possible Blockers 
(5)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS 4{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5450402]]
* IgnitePdsTestSuite4: 
RebalanceCancellationTest.testRebalanceNoneBltNodeFailedOnMixedCluster - Test 
has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Cache 2{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5450383]]
* IgniteCacheTestSuite2: 
GridCachePartitionedNearDisabledTxMultiThreadedSelfTest.testOptimisticSerializableCommitMultithreaded
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Cache 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5450382]]
* IgniteBinaryCacheTestSuite: 
GridCacheBalancingStoreSelfTest.testConcurrentLoad - Test has low fail rate in 
base branch 0,0% and is not flaky

{color:#d04437}Basic 1{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5450362]]
* IgniteBasicTestSuite: 
WALRecordSerializationTest.testAllWalRecordsSerializedCompressedAndThenDeserializedSuccessfully
 - Test has low fail rate in base branch 0,0% and is not flaky

{color:#d04437}Basic 2{color} [[tests 
1|https://ci.ignite.apache.org/viewLog.html?buildId=5450323]]
* IgniteComputeBasicConfigVariationsFullApiTestSuite: 
IgniteComputeConfigVariationsFullApiTest_17.testDeployExecuteByName - Test has 
low fail rate in base branch 0,0% and is not flaky

{panel}
{panel:title=Branch: [pull/8004/head] Base: [master] : New Tests 
(17)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Platform .NET (Long Running){color} [tests 3]
* {color:#013220}exe: 
CacheAbstractTransactionalTest.TestTransactionScopeWithSerializableIsolationLocksKeysOnRead
 - PASSED{color}
* {color:#013220}exe: 
CacheAbstractTransactionalTest.TestTransactionScopeWithSerializableIsolationLocksKeysOnRead
 - PASSED{color}
* {color:#013220}exe: 
CacheAbstractTransactionalTest.TestTransactionScopeWithSerializableIsolationLocksKeysOnRead
 - PASSED{color}

{color:#8b}Platform .NET{color} [tests 3]
* {color:#013220}exe: 
CacheAbstractTransactionalTest.TestTransactionScopeWithSerializableIsolationLocksKeysOnRead
 - PASSED{color}
* {color:#013220}exe: 
OptimisticTransactionTest.TestExplicitOptimisticTransactionThrowsOptimisticExceptionOnConflict
 - PASSED{color}
* {color:#013220}exe: 
OptimisticTransactionTest.TestAmbientOptimisticTransactionThrowsOptimisticExceptionOnConflict
 - PASSED{color}

{color:#8b}Platform .NET (Core Linux){color} [tests 3]
* {color:#013220}dll: 
CachePartitionedTest.TestTransactionScopeWithSerializableIsolationLocksKeysOnRead
 - PASSED{color}
* {color:#013220}dll: 
OptimisticTransactionTest.TestExplicitOptimisticTransactionThrowsOptimisticExceptionOnConflict
 - PASSED{color}
* {color:#013220}dll: 
OptimisticTransactionTest.TestAmbientOptimisticTransactionThrowsOptimisticExceptionOnConflict
 - PASSED{color}

{color:#8b}Service Grid{color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=d4f916bd-963e-4875-b0d9-b6cd769a32b4, topVer=0, 
nodeId8=08c81af0, msg=, type=NODE_JOINED, tstamp=1594248504235], 
val2=AffinityTopologyVersion [topVer=2876465466042446570, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=d4f916bd-963e-4875-b0d9-b6cd769a32b4, topVer=0, 
nodeId8=08c81af0, msg=, type=NODE_JOINED, tstamp=1594248504235], 
val2=AffinityTopologyVersion [topVer=2876465466042446570, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=fa3ad903371-ec906005-587a-4dd2-be8c-91ce64d48350, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=7ad4ae83-15c2-4a1f-93a5-fcb0acf73fbd, topVer=0, nodeId8=7ad4ae83, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594248504235]], 
val2=AffinityTopologyVersion [topVer=7244792805766858131, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=fa3ad903371-ec906005-587a-4dd2-be8c-91ce64d48350, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=7ad4ae83-15c2-4a1f-93a5-fcb0acf73fbd, topVer=0, nodeId8=7ad4ae83, 
msg=null,

[jira] [Commented] (IGNITE-13214) .NET different behavior when using TransactionScope and ITransactions.Start

2020-07-08 Thread Sergey Stronchinskiy (Jira)



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

Sergey Stronchinskiy commented on IGNITE-13214:
---

[~ptupitsyn] Looks great!

> .NET different behavior when using TransactionScope and  ITransactions.Start
> 
>
> Key: IGNITE-13214
> URL: https://issues.apache.org/jira/browse/IGNITE-13214
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Sergey Stronchinskiy
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .NET, transactions
> Fix For: 2.9
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Next code runs fine:
> {code:c#}
> var barier = new Barrier(2);
> var cache = Cache();
> cache.Put(1, 1);
> var task = Task.Factory.StartNew(() =>
> {
> var otherCache = Cache();
> barier.SignalAndWait();
> otherCache.Put(1, 10);
> barier.SignalAndWait();
> });
> using (var txscp = new 
> TransactionScope(TransactionScopeOption.Required, new 
> TransactionOptions{IsolationLevel = IsolationLevel.Serializable}))
> {
> var before = cache.Get(1);
> barier.SignalAndWait();
> barier.SignalAndWait();
> txscp.Complete();
> }
> Task.WaitAll(task);
> barier.Dispose();
> {code}
> When I switch to Ignite transactions I get exception:
> {code:c#}
> using (var tx = 
> Transactions.TxStart(TransactionConcurrency.Optimistic, 
> TransactionIsolation.Serializable))
> {
> var before = cache.Get(1);
> barier.SignalAndWait();
> barier.SignalAndWait();
> tx.Commit();
> }
> {code}
> {noformat}
> Apache.Ignite.Core.Transactions.TransactionOptimisticException : Failed to 
> prepare transaction (lock conflict): GridNearTxLocal 
> [mappings=IgniteTxMappingsImpl [], 
> {noformat}
> _Cache_ is _IIgnite.Cache()_  and _Transactions_ is 
> _IIgnite.GetTransactions()_



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

[jira] [Commented] (IGNITE-13214) .NET different behavior when using TransactionScope and ITransactions.Start

2020-07-08 Thread Pavel Tupitsyn (Jira)



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

Pavel Tupitsyn commented on IGNITE-13214:
-

[~GuruStron] please have a look again, I've addressed the comments. Added more 
tests and fixed error handling for ambient transactions.

> .NET different behavior when using TransactionScope and  ITransactions.Start
> 
>
> Key: IGNITE-13214
> URL: https://issues.apache.org/jira/browse/IGNITE-13214
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Sergey Stronchinskiy
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .NET, transactions
> Fix For: 2.9
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Next code runs fine:
> {code:c#}
> var barier = new Barrier(2);
> var cache = Cache();
> cache.Put(1, 1);
> var task = Task.Factory.StartNew(() =>
> {
> var otherCache = Cache();
> barier.SignalAndWait();
> otherCache.Put(1, 10);
> barier.SignalAndWait();
> });
> using (var txscp = new 
> TransactionScope(TransactionScopeOption.Required, new 
> TransactionOptions{IsolationLevel = IsolationLevel.Serializable}))
> {
> var before = cache.Get(1);
> barier.SignalAndWait();
> barier.SignalAndWait();
> txscp.Complete();
> }
> Task.WaitAll(task);
> barier.Dispose();
> {code}
> When I switch to Ignite transactions I get exception:
> {code:c#}
> using (var tx = 
> Transactions.TxStart(TransactionConcurrency.Optimistic, 
> TransactionIsolation.Serializable))
> {
> var before = cache.Get(1);
> barier.SignalAndWait();
> barier.SignalAndWait();
> tx.Commit();
> }
> {code}
> {noformat}
> Apache.Ignite.Core.Transactions.TransactionOptimisticException : Failed to 
> prepare transaction (lock conflict): GridNearTxLocal 
> [mappings=IgniteTxMappingsImpl [], 
> {noformat}
> _Cache_ is _IIgnite.Cache()_  and _Transactions_ is 
> _IIgnite.GetTransactions()_



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

[jira] [Commented] (IGNITE-13229) GridClient instance leakage.

2020-07-08 Thread Ignite TC Bot (Jira)



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

Ignite TC Bot commented on IGNITE-13229:


{panel:title=Branch: [pull/8006/head] Base: [master] : Possible Blockers 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5449922]]

{panel}
{panel:title=Branch: [pull/8006/head] Base: [master] : New Tests 
(8)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Service Grid{color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=1d3deeb7-c13d-4740-bc54-9ba5c8c1a4ee, topVer=0, 
nodeId8=6ef28d05, msg=, type=NODE_JOINED, tstamp=1594220236209], 
val2=AffinityTopologyVersion [topVer=7215358582909498952, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=1d3deeb7-c13d-4740-bc54-9ba5c8c1a4ee, topVer=0, 
nodeId8=6ef28d05, msg=, type=NODE_JOINED, tstamp=1594220236209], 
val2=AffinityTopologyVersion [topVer=7215358582909498952, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=5bd4eee2371-9569be51-7b3f-4180-9dd2-57341d8cd813, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=0a4002e9-1db2-4e32-9f20-c61157ef731c, topVer=0, nodeId8=0a4002e9, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594220236209]], 
val2=AffinityTopologyVersion [topVer=440979196143354, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=5bd4eee2371-9569be51-7b3f-4180-9dd2-57341d8cd813, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=0a4002e9-1db2-4e32-9f20-c61157ef731c, topVer=0, nodeId8=0a4002e9, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594220236209]], 
val2=AffinityTopologyVersion [topVer=440979196143354, minorTopVer=0]]] - 
PASSED{color}

{color:#8b}Service Grid (legacy mode){color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=0d0512d1-bed1-4a2f-b239-f76e31739329, topVer=0, 
nodeId8=2a4e0452, msg=, type=NODE_JOINED, tstamp=1594220520431], 
val2=AffinityTopologyVersion [topVer=-3810796796632234237, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=0d0512d1-bed1-4a2f-b239-f76e31739329, topVer=0, 
nodeId8=2a4e0452, msg=, type=NODE_JOINED, tstamp=1594220520431], 
val2=AffinityTopologyVersion [topVer=-3810796796632234237, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=3f3a2fe2371-aac23888-8aee-4812-a212-5e9c11adf721, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=543d7ad7-7861-4a68-9dbd-98a9c7a05b0b, topVer=0, nodeId8=543d7ad7, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594220520431]], 
val2=AffinityTopologyVersion [topVer=997360565232791116, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=3f3a2fe2371-aac23888-8aee-4812-a212-5e9c11adf721, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=543d7ad7-7861-4a68-9dbd-98a9c7a05b0b, topVer=0, nodeId8=543d7ad7, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594220520431]], 
val2=AffinityTopologyVersion [topVer=997360565232791116, minorTopVer=0]]] - 
PASSED{color}

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5449497buildTypeId=IgniteTests24Java8_RunAll]

> GridClient instance leakage.
> 
>
> Key: IGNITE-13229
> URL: https://issues.apache.org/jira/browse/IGNITE-13229
> Project: Ignite
>  Issue Type: Improvement
>  Components: thin client
>Affects Versions: 2.8.1
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
>  Time Spent: 10m
>

[jira] [Commented] (IGNITE-13146) OpenCensus example does not work from release build

2020-07-08 Thread Aleksey Plekhanov (Jira)



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

Aleksey Plekhanov commented on IGNITE-13146:


[~ilyak], thanks for the review!

> OpenCensus example does not work from release build
> ---
>
> Key: IGNITE-13146
> URL: https://issues.apache.org/jira/browse/IGNITE-13146
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: 2.9
>Reporter: Ilya Kasnacheev
>Assignee: Aleksey Plekhanov
>Priority: Blocker
> Fix For: 2.9
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> This happens in a binary distribution of 2.9:
> {code}
> /Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples% mvn clean install
> [INFO] 
> [INFO] -< org.apache.ignite:ignite-examples 
> >--
> [INFO] Building ignite-examples 2.9.0-SNAPSHOT
> [INFO] [ jar 
> ]-
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
> ignite-examples ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 255 source files to 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/target/classes
> ...
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[20,47]
>  package io.opencensus.exporter.stats.prometheus does not exist
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[21,37]
>  package io.prometheus.client.exporter does not exist
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[34,47]
>  package org.apache.ignite.spi.metric.opencensus does not exist
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[54,9]
>  cannot find symbol
>   symbol:   variable PrometheusStatsCollector
>   location: class 
> org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[57,9]
>  cannot find symbol
>   symbol:   class HTTPServer
>   location: class 
> org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[57,30]
>  cannot find symbol
>   symbol:   class HTTPServer
>   location: class 
> org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[62,9]
>  cannot find symbol
>   symbol:   class OpenCensusMetricExporterSpi
>   location: class 
> org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[62,71]
>  cannot find symbol
>   symbol:   class OpenCensusMetricExporterSpi
>   location: class 
> org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
> [INFO] 8 errors 
> [INFO] -
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> {code}
> This is because pom-standalone.xml and pom-standalone-lgpl.xml files needs to 
> be updated in accordance with examples/pom.xml changes. This is currently a 
> blocker for 2.9.



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

[jira] [Updated] (IGNITE-13227) AssertionError on getting cache size from the mbean on the inactive cluster

2020-07-08 Thread Amelchev Nikita (Jira)



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

Amelchev Nikita updated IGNITE-13227:
-
Fix Version/s: 2.9

> AssertionError on getting cache size from the mbean on the inactive cluster
> ---
>
> Key: IGNITE-13227
> URL: https://issues.apache.org/jira/browse/IGNITE-13227
> Project: Ignite
>  Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The reproducer for {{CacheMetricsManageTest}}:
> {noformat}
> /** @throws Exception If failed. */
> @Test
> public void testCacheSize() throws Exception {
> persistence = true;
> startGrid(0);
> CacheMetricsMXBean mxBean = mxBean(0, CACHE1, 
> CacheClusterMetricsMXBeanImpl.class);
> long size = mxBean.getCacheSize();
> assertEquals(0, size);
> }
> {noformat}
> AssertionError:
> {noformat}
> java.lang.AssertionError: AffinityTopologyVersion [topVer=-1, minorTopVer=0]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:794)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:771)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.primaryPartitions(GridAffinityAssignmentCache.java:697)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.cacheData(IgniteCacheOffheapManagerImpl.java:431)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.cacheEntriesCount(IgniteCacheOffheapManagerImpl.java:398)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedCacheAdapter.localSizeLong(GridDistributedCacheAdapter.java:284)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.localSize(GridCacheAdapter.java:4151)
>   at 
> org.apache.ignite.internal.processors.cache.CacheMetricsImpl.getEntriesStat(CacheMetricsImpl.java:1272)
>   at 
> org.apache.ignite.internal.processors.cache.CacheMetricsSnapshotV2.(CacheMetricsSnapshotV2.java:375)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.localMetrics(GridCacheAdapter.java:3546)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.clusterMetrics(GridCacheAdapter.java:3540)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.clusterMetrics(GridCacheAdapter.java:3522)
>   at 
> org.apache.ignite.internal.processors.cache.CacheClusterMetricsMXBeanImpl.getCacheSize(CacheClusterMetricsMXBeanImpl.java:119)
>   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 sun.reflect.misc.Trampoline.invoke(MethodUtil.java:71)
>   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 sun.reflect.misc.MethodUtil.invoke(MethodUtil.java:275)
>   at 
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:112)
>   at 
> com.sun.jmx.mbeanserver.StandardMBeanIntrospector.invokeM2(StandardMBeanIntrospector.java:46)
>   at 
> com.sun.jmx.mbeanserver.MBeanIntrospector.invokeM(MBeanIntrospector.java:237)
>   at 
> com.sun.jmx.mbeanserver.PerInterface.getAttribute(PerInterface.java:83)
>   at 
> com.sun.jmx.mbeanserver.MBeanSupport.getAttribute(MBeanSupport.java:206)
>   at javax.management.StandardMBean.getAttribute(StandardMBean.java:372)
>   at 
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647)
>   at 
> com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678)
>   at 
> javax.management.MBeanServerInvocationHandler.invoke(MBeanServerInvocationHandler.java:273)
>   at com.sun.proxy.$Proxy30.getCacheSize(Unknown Source)
>   at 
> org.apache.ignite.internal.processors.cache.CacheMetricsManageTest.testCacheSize(CacheMetricsManageTest.java:833)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>

[jira] [Commented] (IGNITE-13227) AssertionError on getting cache size from the mbean on the inactive cluster

2020-07-08 Thread Ignite TC Bot (Jira)



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

Ignite TC Bot commented on IGNITE-13227:


{panel:title=Branch: [pull/8005/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/8005/head] Base: [master] : New Tests 
(9)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Cache 7{color} [tests 1]
* {color:#013220}IgniteCacheTestSuite7: 
CacheMetricsManageTest.testCacheSizeOnInactiveCluster - PASSED{color}

{color:#8b}Service Grid{color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=d9f2e3f7-2300-4b4a-944a-9014df5ca796, topVer=0, 
nodeId8=d486eef9, msg=, type=NODE_JOINED, tstamp=1594193704470], 
val2=AffinityTopologyVersion [topVer=-8059358443962014770, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=d9f2e3f7-2300-4b4a-944a-9014df5ca796, topVer=0, 
nodeId8=d486eef9, msg=, type=NODE_JOINED, tstamp=1594193704470], 
val2=AffinityTopologyVersion [topVer=-8059358443962014770, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=36ab36d2371-f4f5e988-2d5d-4ff1-b9f8-b77dcbdd3524, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=b28f21b7-6bfe-4f1e-a19e-b457855da26a, topVer=0, nodeId8=b28f21b7, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594193704470]], 
val2=AffinityTopologyVersion [topVer=-8777312444905482645, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=36ab36d2371-f4f5e988-2d5d-4ff1-b9f8-b77dcbdd3524, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=b28f21b7-6bfe-4f1e-a19e-b457855da26a, topVer=0, nodeId8=b28f21b7, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594193704470]], 
val2=AffinityTopologyVersion [topVer=-8777312444905482645, minorTopVer=0]]] - 
PASSED{color}

{color:#8b}Service Grid (legacy mode){color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=5ca726d2371-d58f69b1-7e9b-46ce-9ed1-9aec5d662f9d, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=ab098635-5508-41d3-9fcf-e5a26cb784d7, topVer=0, nodeId8=ab098635, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594193639349]], 
val2=AffinityTopologyVersion [topVer=-6302947696903529487, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=5ca726d2371-d58f69b1-7e9b-46ce-9ed1-9aec5d662f9d, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=ab098635-5508-41d3-9fcf-e5a26cb784d7, topVer=0, nodeId8=ab098635, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594193639349]], 
val2=AffinityTopologyVersion [topVer=-6302947696903529487, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=9f5a8745-df8e-4548-9beb-6ca81e71e59e, topVer=0, 
nodeId8=bb53ce0c, msg=, type=NODE_JOINED, tstamp=1594193639349], 
val2=AffinityTopologyVersion [topVer=4832838139885376742, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=9f5a8745-df8e-4548-9beb-6ca81e71e59e, topVer=0, 
nodeId8=bb53ce0c, msg=, type=NODE_JOINED, tstamp=1594193639349], 
val2=AffinityTopologyVersion [topVer=4832838139885376742, minorTopVer=0]]] - 
PASSED{color}

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5448082buildTypeId=IgniteTests24Java8_RunAll]

> AssertionError on getting cache size from the mbean on the inactive cluster
> ---
>
> Key: IGNITE-13227
> URL: https://issues.apache.org/jira/browse/IGNITE-13227
> Project: Ignite
>  Issue Type: Bug
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>

[jira] [Commented] (IGNITE-13146) OpenCensus example does not work from release build

2020-07-08 Thread Ilya Kasnacheev (Jira)



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

Ilya Kasnacheev commented on IGNITE-13146:
--

Thank you for this fix, I have merged it to master and 2.9

> OpenCensus example does not work from release build
> ---
>
> Key: IGNITE-13146
> URL: https://issues.apache.org/jira/browse/IGNITE-13146
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: 2.9
>Reporter: Ilya Kasnacheev
>Assignee: Aleksey Plekhanov
>Priority: Blocker
> Fix For: 2.9
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> This happens in a binary distribution of 2.9:
> {code}
> /Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples% mvn clean install
> [INFO] 
> [INFO] -< org.apache.ignite:ignite-examples 
> >--
> [INFO] Building ignite-examples 2.9.0-SNAPSHOT
> [INFO] [ jar 
> ]-
> ...
> [INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @ 
> ignite-examples ---
> [INFO] Changes detected - recompiling the module!
> [INFO] Compiling 255 source files to 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/target/classes
> ...
> [INFO] -
> [ERROR] COMPILATION ERROR : 
> [INFO] -
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[20,47]
>  package io.opencensus.exporter.stats.prometheus does not exist
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[21,37]
>  package io.prometheus.client.exporter does not exist
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[34,47]
>  package org.apache.ignite.spi.metric.opencensus does not exist
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[54,9]
>  cannot find symbol
>   symbol:   variable PrometheusStatsCollector
>   location: class 
> org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[57,9]
>  cannot find symbol
>   symbol:   class HTTPServer
>   location: class 
> org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[57,30]
>  cannot find symbol
>   symbol:   class HTTPServer
>   location: class 
> org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[62,9]
>  cannot find symbol
>   symbol:   class OpenCensusMetricExporterSpi
>   location: class 
> org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
> [ERROR] 
> /home/gridgain/Downloads/apache-ignite-slim-2.9.0-SNAPSHOT-bin/examples/src/main/java/org/apache/ignite/examples/opencensus/OpenCensusMetricsExporterExample.java:[62,71]
>  cannot find symbol
>   symbol:   class OpenCensusMetricExporterSpi
>   location: class 
> org.apache.ignite.examples.opencensus.OpenCensusMetricsExporterExample
> [INFO] 8 errors 
> [INFO] -
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> {code}
> This is because pom-standalone.xml and pom-standalone-lgpl.xml files needs to 
> be updated in accordance with examples/pom.xml changes. This is currently a 
> blocker for 2.9.



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

[jira] [Commented] (IGNITE-13013) Thick client must not open server sockets when used by serverless functions

2020-07-08 Thread Denis A. Magda (Jira)



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

Denis A. Magda commented on IGNITE-13013:
-

Anton, agree, let’s do the way you’re suggesting!

> Thick client must not open server sockets when used by serverless functions
> ---
>
> Key: IGNITE-13013
> URL: https://issues.apache.org/jira/browse/IGNITE-13013
> Project: Ignite
>  Issue Type: Improvement
>  Components: networking
>Affects Versions: 2.8
>Reporter: Denis A. Magda
>Priority: Critical
> Fix For: 2.9
>
>
> A thick client fails to start if being used inside of a serverless function 
> such as AWS Lamda or Azure Functions. Cloud providers prohibit opening 
> network ports to accept connections on the function's end. In short, the 
> function can only connect to a remote address.
> To reproduce, you can follow this tutorial and swap the thin client (used in 
> the tutorial) with the thick one: 
> https://www.gridgain.com/docs/tutorials/serverless/azure_functions_tutorial
> The thick client needs to support a mode when the communication SPI doesn't 
> create a server socket if the client is used for serverless computing. This 
> improvement looks like an extra task of this initiative: 
> https://issues.apache.org/jira/browse/IGNITE-12438



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

[jira] [Commented] (IGNITE-13185) API to change Cluster Tag and notify about change of Cluster Tag

2020-07-08 Thread Sergey Chugunov (Jira)



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

Sergey Chugunov commented on IGNITE-13185:
--

[~alex_pl], 

Sure, I'll take a look right now.

> API to change Cluster Tag and notify about change of Cluster Tag
> 
>
> Key: IGNITE-13185
> URL: https://issues.apache.org/jira/browse/IGNITE-13185
> Project: Ignite
>  Issue Type: Improvement
>  Components: general, UI, visor
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> IGNITE-12111 introduced new feature to identify and distinguish different 
> clusters.
> To make the feature more usable we need new command in CLI interface to 
> change Cluster Tag and new event to subscribe for changes of Cluster Tag.



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

[jira] [Commented] (IGNITE-13185) API to change Cluster Tag and notify about change of Cluster Tag

2020-07-08 Thread Aleksey Plekhanov (Jira)



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

Aleksey Plekhanov commented on IGNITE-13185:


[~ilyak], [~sergey-chugunov], looks like master is broken after this fix, 
because control.sh utility was moved to a separate module earlier. Can you 
please have a look? 

> API to change Cluster Tag and notify about change of Cluster Tag
> 
>
> Key: IGNITE-13185
> URL: https://issues.apache.org/jira/browse/IGNITE-13185
> Project: Ignite
>  Issue Type: Improvement
>  Components: general, UI, visor
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> IGNITE-12111 introduced new feature to identify and distinguish different 
> clusters.
> To make the feature more usable we need new command in CLI interface to 
> change Cluster Tag and new event to subscribe for changes of Cluster Tag.



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

[jira] [Commented] (IGNITE-13013) Thick client must not open server sockets when used by serverless functions

2020-07-08 Thread Anton Kalashnikov (Jira)



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

Anton Kalashnikov commented on IGNITE-13013:


[~dmagda], I think I agree that client-to-client connectivity is not soo useful 
in ignite. So I have another solution which looks pretty easy for 
implementation. We can add the possibility to set a communication port to 
-1(this means server socket shouldn't be open). And when the user sets this 
port to -1 we also set forceClientToServer to true. Also, we can add validation 
on establishing communication connection, and if we see that it is the 
client-to-client connection but the remote client doesn't support such 
connection we notify the user about it( exception is thrown) - as I understand 
this scenario mostly corresponds to the compute.

In conclusion, expected changes:
* Setting communication port to -1 is allowed
* If the communication port set to -1, forceClientToServer will set to true
* If the client tries to establish a connection with another client which port 
equal to -1, the exception will be thrown.

> Thick client must not open server sockets when used by serverless functions
> ---
>
> Key: IGNITE-13013
> URL: https://issues.apache.org/jira/browse/IGNITE-13013
> Project: Ignite
>  Issue Type: Improvement
>  Components: networking
>Affects Versions: 2.8
>Reporter: Denis A. Magda
>Priority: Critical
> Fix For: 2.9
>
>
> A thick client fails to start if being used inside of a serverless function 
> such as AWS Lamda or Azure Functions. Cloud providers prohibit opening 
> network ports to accept connections on the function's end. In short, the 
> function can only connect to a remote address.
> To reproduce, you can follow this tutorial and swap the thin client (used in 
> the tutorial) with the thick one: 
> https://www.gridgain.com/docs/tutorials/serverless/azure_functions_tutorial
> The thick client needs to support a mode when the communication SPI doesn't 
> create a server socket if the client is used for serverless computing. This 
> improvement looks like an extra task of this initiative: 
> https://issues.apache.org/jira/browse/IGNITE-12438



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

[jira] [Commented] (IGNITE-13216) QuerySqlField annotation's "name" property is not used during validation of known fields names

2020-07-08 Thread Evgeniy Rudenko (Jira)



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

Evgeniy Rudenko commented on IGNITE-13216:
--

[~ilyak] Thank you.

> QuerySqlField annotation's "name" property is not used during validation of 
> known fields names
> --
>
> Key: IGNITE-13216
> URL: https://issues.apache.org/jira/browse/IGNITE-13216
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Evgeniy Rudenko
>Assignee: Evgeniy Rudenko
>Priority: Blocker
> Fix For: 2.9
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> If "name" parameter is set it should be used instead of actual field name. 
> Currently if 2 @QuerySqlField fields have same names we will receive error, 
> even if they have different "name" properties. 



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

[jira] [Commented] (IGNITE-13180) AuthenticationContext does not contain subject address when subject is IgniteClient

2020-07-08 Thread Ilya Kasnacheev (Jira)



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

Ilya Kasnacheev commented on IGNITE-13180:
--

LGTM. Please rebase it to Master so that I can merge it. Perhaps Travis will 
also re-run and become green [~RyzhovSV]

> AuthenticationContext does not contain subject address when subject is 
> IgniteClient
> ---
>
> Key: IGNITE-13180
> URL: https://issues.apache.org/jira/browse/IGNITE-13180
> Project: Ignite
>  Issue Type: Task
>  Components: thin client
>Reporter: Sergei Ryzhov
>Assignee: Sergei Ryzhov
>Priority: Minor
>
> AuthenticationContext does not contain subject address when subject is 
> IgniteClient



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

[jira] [Commented] (IGNITE-13013) Thick client must not open server sockets when used by serverless functions

2020-07-08 Thread Denis A. Magda (Jira)



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

Denis A. Magda commented on IGNITE-13013:
-

Anton,

In my experience, the client-to-client connectivity option is expected in the 
micro-services architectures. But usually high-level frameworks and protocols 
are used for inter-service communication. Certainly, there are usage scenarios 
of Ignite services and messaging APIs as well, however, those are not 
widespread and might be safely disregarded (especially in cloud environments 
that go with similar well-integrated APIs).

Personally, I would use the forceClientToServer for both things. It’s even 
better to create an Azure function and check that disabling of the 
communication server socket is the only thing we need. There might be something 
else hidden which can influence another configuration way/option.

> Thick client must not open server sockets when used by serverless functions
> ---
>
> Key: IGNITE-13013
> URL: https://issues.apache.org/jira/browse/IGNITE-13013
> Project: Ignite
>  Issue Type: Improvement
>  Components: networking
>Affects Versions: 2.8
>Reporter: Denis A. Magda
>Priority: Critical
> Fix For: 2.9
>
>
> A thick client fails to start if being used inside of a serverless function 
> such as AWS Lamda or Azure Functions. Cloud providers prohibit opening 
> network ports to accept connections on the function's end. In short, the 
> function can only connect to a remote address.
> To reproduce, you can follow this tutorial and swap the thin client (used in 
> the tutorial) with the thick one: 
> https://www.gridgain.com/docs/tutorials/serverless/azure_functions_tutorial
> The thick client needs to support a mode when the communication SPI doesn't 
> create a server socket if the client is used for serverless computing. This 
> improvement looks like an extra task of this initiative: 
> https://issues.apache.org/jira/browse/IGNITE-12438



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

[jira] [Updated] (IGNITE-13216) QuerySqlField annotation's "name" property is not used during validation of known fields names

2020-07-08 Thread Ilya Kasnacheev (Jira)



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

Ilya Kasnacheev updated IGNITE-13216:
-
Description: If "name" parameter is set it should be used instead of actual 
field name. Currently if 2 @QuerySqlField fields have same names we will 
receive error, even if they have different "name" properties.  

> QuerySqlField annotation's "name" property is not used during validation of 
> known fields names
> --
>
> Key: IGNITE-13216
> URL: https://issues.apache.org/jira/browse/IGNITE-13216
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Evgeniy Rudenko
>Assignee: Evgeniy Rudenko
>Priority: Blocker
> Fix For: 2.9
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> If "name" parameter is set it should be used instead of actual field name. 
> Currently if 2 @QuerySqlField fields have same names we will receive error, 
> even if they have different "name" properties. 



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

[jira] [Commented] (IGNITE-13216) QuerySqlField annotation's "name" property is not used during validation of known fields names

2020-07-08 Thread Ilya Kasnacheev (Jira)



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

Ilya Kasnacheev commented on IGNITE-13216:
--

[~erudenko] I have assumed that you have removed description by mistake, so I 
brought it back.

> QuerySqlField annotation's "name" property is not used during validation of 
> known fields names
> --
>
> Key: IGNITE-13216
> URL: https://issues.apache.org/jira/browse/IGNITE-13216
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Evgeniy Rudenko
>Assignee: Evgeniy Rudenko
>Priority: Blocker
> Fix For: 2.9
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> If "name" parameter is set it should be used instead of actual field name. 
> Currently if 2 @QuerySqlField fields have same names we will receive error, 
> even if they have different "name" properties. 



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

[jira] [Updated] (IGNITE-13185) API to change Cluster Tag and notify about change of Cluster Tag

2020-07-08 Thread Ilya Kasnacheev (Jira)



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

Ilya Kasnacheev updated IGNITE-13185:
-
Component/s: visor
 UI
 general

> API to change Cluster Tag and notify about change of Cluster Tag
> 
>
> Key: IGNITE-13185
> URL: https://issues.apache.org/jira/browse/IGNITE-13185
> Project: Ignite
>  Issue Type: Improvement
>  Components: general, UI, visor
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> IGNITE-12111 introduced new feature to identify and distinguish different 
> clusters.
> To make the feature more usable we need new command in CLI interface to 
> change Cluster Tag and new event to subscribe for changes of Cluster Tag.



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

[jira] [Commented] (IGNITE-13185) API to change Cluster Tag and notify about change of Cluster Tag

2020-07-08 Thread Ilya Kasnacheev (Jira)



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

Ilya Kasnacheev commented on IGNITE-13185:
--

Thank you for this contribution, [~sergey-chugunov], I have merged it to master.

Please provide release notes and documentation for this feature.

If you feel that this issue needs to be included to 2.9, please discuss it with 
[~alexpl] since it is his call.

> API to change Cluster Tag and notify about change of Cluster Tag
> 
>
> Key: IGNITE-13185
> URL: https://issues.apache.org/jira/browse/IGNITE-13185
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> IGNITE-12111 introduced new feature to identify and distinguish different 
> clusters.
> To make the feature more usable we need new command in CLI interface to 
> change Cluster Tag and new event to subscribe for changes of Cluster Tag.



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

[jira] [Commented] (IGNITE-11393) Create IgniteLinkTaglet.toString() implementation for Java9+

2020-07-08 Thread Aleksey Plekhanov (Jira)



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

Aleksey Plekhanov commented on IGNITE-11393:


[~amashenkov], thanks for the review! Yes, we still can't use JDK 11+ for 
release purposes (one more issue, on JDK 9+ we compiling with target 11, and 
class files generated with the wrong version and can't be used on JDK 8, but 
this issue can be easily fixed).

I've removed old PR and rebased the actual one. I will merge the fix today.

 

> Create IgniteLinkTaglet.toString() implementation for Java9+
> 
>
> Key: IGNITE-11393
> URL: https://issues.apache.org/jira/browse/IGNITE-11393
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitry Pavlov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> New implementation was added according to the new Java API for Javadoc.
> But the main method kept empty, need to implement toString() to process 
> IgniteLink annotation



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

[jira] [Commented] (IGNITE-13200) SQL create index on invalid data type

2020-07-08 Thread Ivan Bessonov (Jira)



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

Ivan Bessonov commented on IGNITE-13200:


Hi [~tledkov-gridgain],

fix looks good, but one particular change in BPlusTree looks excessive, can you 
please look at it? I left a comment in PR, thank you!

> SQL create index on invalid data type
> -
>
> Key: IGNITE-13200
> URL: https://issues.apache.org/jira/browse/IGNITE-13200
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.8.1
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> *Reproduce*
> - Create cache with value class
> {code}
> private static class Value {
> @QuerySqlField
> int val_int;
> java.util.Date val_date;
> }
> {code}
> - alter table with command
> {{ALTER TABLE TEST ADD COLUMN (VAL_DATE DATE)}}
> - try to create index with command
> {{CREATE INDEX TEST_VAL_DATE_IDX ON TEST(VAL_DATE)}}
> {{CorruptedTreeException}} is thrown, the node is stopped.
> {code}
> class org.apache.ignite.IgniteCheckedException: Runtime failure on row: 
> Row@6a2853cd[ key: 0, val: 
> org.apache.ignite.internal.processors.query.CreateIndexOnInvalidDataTypeTest$Value
>  [idHash=1693430008, hash=1583713321, val_int=0, val_date=Thu Jan 01 03:00:00 
> MSK 1970] ][ 0,  java.util.Date cannot be cast to java.sql.Date> ]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2438)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2388)
>   at 
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:434)
>   at 
> org.apache.ignite.internal.processors.query.h2.IndexBuildClosure.apply(IndexBuildClosure.java:52)
>   at 
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCachePartitionWorker$SchemaIndexCacheVisitorClosureWrapper.apply(SchemaIndexCachePartitionWorker.java:298)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.updateIndex(GridCacheMapEntry.java:4494)
>   at 
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCachePartitionWorker.processKey(SchemaIndexCachePartitionWorker.java:231)
>   at 
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCachePartitionWorker.processPartition(SchemaIndexCachePartitionWorker.java:188)
>   at 
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCachePartitionWorker.body(SchemaIndexCachePartitionWorker.java:127)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
> wrap object into H2 Value. java.util.Date cannot be cast to java.sql.Date
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.H2CacheRow.wrap(H2CacheRow.java:177)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.H2CacheRow.getValue0(H2CacheRow.java:109)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.H2CacheRow.getValue(H2CacheRow.java:91)
>   at 
> org.apache.ignite.internal.processors.query.h2.database.io.AbstractH2ExtrasLeafIO.storeByOffset(AbstractH2ExtrasLeafIO.java:115)
>   at 
> org.apache.ignite.internal.processors.query.h2.database.io.AbstractH2ExtrasLeafIO.storeByOffset(AbstractH2ExtrasLeafIO.java:37)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusIO.store(BPlusIO.java:185)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusIO.insert(BPlusIO.java:272)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insertSimple(BPlusTree.java:3685)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insert(BPlusTree.java:3667)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$1900(BPlusTree.java:3539)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:452)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:433)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5889)
>   at 
>

[jira] [Created] (IGNITE-13229) GridClient instance leakage.

2020-07-08 Thread Stanilovsky Evgeny (Jira)

Stanilovsky Evgeny created IGNITE-13229:
---

 Summary: GridClient instance leakage.
 Key: IGNITE-13229
 URL: https://issues.apache.org/jira/browse/IGNITE-13229
 Project: Ignite
  Issue Type: Improvement
  Components: thin client
Affects Versions: 2.8.1
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny


Instances of GridClient - deprecated realization of thin client, still used for 
example, in _control.sh_ can be leaked in some circumstances. Can bring to OOM 
in some tests.



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

[jira] [Updated] (IGNITE-13123) Move control.sh to a separate module

2020-07-08 Thread Alexey Goncharuk (Jira)



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

Alexey Goncharuk updated IGNITE-13123:
--
Release Note: Moved control utility command classes to a separate module

> Move control.sh to a separate module
> 
>
> Key: IGNITE-13123
> URL: https://issues.apache.org/jira/browse/IGNITE-13123
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Move [1] and its associated classes to a separate "ignite-control-utility" 
> module.
> [1] - org.apache.ignite.internal.commandline.CommandHandler



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

[jira] [Commented] (IGNITE-13123) Move control.sh to a separate module

2020-07-08 Thread Alexey Goncharuk (Jira)



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

Alexey Goncharuk commented on IGNITE-13123:
---

Verified that {{control.sh}} works after building the release from sources. 
Also, checked the commands working on nodes without the new module in the 
classpath.
[~ktkale...@gridgain.com] thanks for the change, merged to master!

> Move control.sh to a separate module
> 
>
> Key: IGNITE-13123
> URL: https://issues.apache.org/jira/browse/IGNITE-13123
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Move [1] and its associated classes to a separate "ignite-control-utility" 
> module.
> [1] - org.apache.ignite.internal.commandline.CommandHandler



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

[jira] [Updated] (IGNITE-13123) Move control.sh to a separate module

2020-07-08 Thread Alexey Goncharuk (Jira)



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

Alexey Goncharuk updated IGNITE-13123:
--
Fix Version/s: 2.9

> Move control.sh to a separate module
> 
>
> Key: IGNITE-13123
> URL: https://issues.apache.org/jira/browse/IGNITE-13123
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Kirill Tkalenko
>Assignee: Kirill Tkalenko
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Move [1] and its associated classes to a separate "ignite-control-utility" 
> module.
> [1] - org.apache.ignite.internal.commandline.CommandHandler



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

[jira] [Commented] (IGNITE-13185) API to change Cluster Tag and notify about change of Cluster Tag

2020-07-08 Thread Sergey Chugunov (Jira)



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

Sergey Chugunov commented on IGNITE-13185:
--

[~ilyak],

I addressed your comments in the PR and got another green visa - could you take 
another look at the change?

Thanks!

> API to change Cluster Tag and notify about change of Cluster Tag
> 
>
> Key: IGNITE-13185
> URL: https://issues.apache.org/jira/browse/IGNITE-13185
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> IGNITE-12111 introduced new feature to identify and distinguish different 
> clusters.
> To make the feature more usable we need new command in CLI interface to 
> change Cluster Tag and new event to subscribe for changes of Cluster Tag.



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

[jira] [Commented] (IGNITE-13185) API to change Cluster Tag and notify about change of Cluster Tag

2020-07-08 Thread Ignite TC Bot (Jira)



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

Ignite TC Bot commented on IGNITE-13185:


{panel:title=Branch: [pull/7964/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
{panel:title=Branch: [pull/7964/head] Base: [master] : New Tests 
(14)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}ZooKeeper (Discovery) 2{color} [tests 1]
* {color:#013220}ZookeeperDiscoverySpiTestSuite2: 
GridCommandHandlerTest.testClusterChangeTag - PASSED{color}

{color:#8b}Basic 3{color} [tests 5]
* {color:#013220}IgniteBasicWithPersistenceTestSuite: 
IgniteClusterIdTagTest.testTagChangedEvent - PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite: 
IgniteClusterIdTagTest.testChangeTagExceptions - PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite: 
IgniteClusterIdTagTest.testTagChangedEventMultinodeWithRemoteFilter - 
PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite: 
GridCommandHandlerWithSSLTest.testClusterChangeTag - PASSED{color}
* {color:#013220}IgniteBasicWithPersistenceTestSuite: 
GridCommandHandlerTest.testClusterChangeTag - PASSED{color}

{color:#8b}Service Grid{color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=81b9c70a-66c6-40a1-a42b-9adcf98689a2, topVer=0, 
nodeId8=f492af84, msg=, type=NODE_JOINED, tstamp=1594140404418], 
val2=AffinityTopologyVersion [topVer=1603531752557536031, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=504763a2371-627cdcf5-6732-4614-bf82-6f1b2935b10e, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=0eaf3a62-1a20-4020-b091-2f23ca8dcebc, topVer=0, nodeId8=0eaf3a62, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594140404418]], 
val2=AffinityTopologyVersion [topVer=8992486467505103191, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=504763a2371-627cdcf5-6732-4614-bf82-6f1b2935b10e, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=0eaf3a62-1a20-4020-b091-2f23ca8dcebc, topVer=0, nodeId8=0eaf3a62, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594140404418]], 
val2=AffinityTopologyVersion [topVer=8992486467505103191, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=81b9c70a-66c6-40a1-a42b-9adcf98689a2, topVer=0, 
nodeId8=f492af84, msg=, type=NODE_JOINED, tstamp=1594140404418], 
val2=AffinityTopologyVersion [topVer=1603531752557536031, minorTopVer=0]]] - 
PASSED{color}

{color:#8b}Service Grid (legacy mode){color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=52c9cd13-bdcf-43e8-888f-092f6e7648af, topVer=0, 
nodeId8=b47077f5, msg=, type=NODE_JOINED, tstamp=1594140341796], 
val2=AffinityTopologyVersion [topVer=7632917585497587426, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=52c9cd13-bdcf-43e8-888f-092f6e7648af, topVer=0, 
nodeId8=b47077f5, msg=, type=NODE_JOINED, tstamp=1594140341796], 
val2=AffinityTopologyVersion [topVer=7632917585497587426, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=8263b2a2371-8bf97cb3-627c-4ddd-a48a-b7c064bc6249, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=95c9650d-48f5-4426-aaeb-b932c36d0a69, topVer=0, nodeId8=95c9650d, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594140341796]], 
val2=AffinityTopologyVersion [topVer=-4059230009518180750, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=8263b2a2371-8bf97cb3-627c-4ddd-a48a-b7c064bc6249, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=95c9650d-48f5-4426-aaeb-b932c36d0a69, topVer=0, nodeId8=95c9650d, 
msg=null, type=DISCOVERY_CUSTOM_EVT,

[jira] [Commented] (IGNITE-13200) SQL create index on invalid data type

2020-07-08 Thread Ignite TC Bot (Jira)



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

Ignite TC Bot commented on IGNITE-13200:


{panel:title=Branch: [pull/7982/head] Base: [master] : Possible Blockers 
(1)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}PDS (Indexing){color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=5448357]]

{panel}
{panel:title=Branch: [pull/7982/head] Base: [master] : New Tests 
(10)|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}
{color:#8b}Queries 2{color} [tests 2]
* {color:#013220}IgniteBinaryCacheQueryTestSuite2: 
CreateIndexOnInvalidDataTypeTest.testAddInvalidDataToIndex - PASSED{color}
* {color:#013220}IgniteBinaryCacheQueryTestSuite2: 
CreateIndexOnInvalidDataTypeTest.testCreateIndexOnInvalidData - PASSED{color}

{color:#8b}Service Grid{color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=987239a2371-79390b11-3632-4d85-9e95-a7e1376d8b8e, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=a2d0036f-5db7-47db-b473-ca3e4ae0a2e6, topVer=0, nodeId8=a2d0036f, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594147153797]], 
val2=AffinityTopologyVersion [topVer=7601406044098132898, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=987239a2371-79390b11-3632-4d85-9e95-a7e1376d8b8e, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=a2d0036f-5db7-47db-b473-ca3e4ae0a2e6, topVer=0, nodeId8=a2d0036f, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594147153797]], 
val2=AffinityTopologyVersion [topVer=7601406044098132898, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=4b15f9e7-19e4-4d4a-bb0f-1b2a62060f2b, topVer=0, 
nodeId8=a3f3937f, msg=, type=NODE_JOINED, tstamp=1594147153797], 
val2=AffinityTopologyVersion [topVer=-2262562060701615165, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=4b15f9e7-19e4-4d4a-bb0f-1b2a62060f2b, topVer=0, 
nodeId8=a3f3937f, msg=, type=NODE_JOINED, tstamp=1594147153797], 
val2=AffinityTopologyVersion [topVer=-2262562060701615165, minorTopVer=0]]] - 
PASSED{color}

{color:#8b}Service Grid (legacy mode){color} [tests 4]
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=7eb6990e-ed38-42dd-b1ae-f4cb8f33956e, topVer=0, 
nodeId8=7904b65e, msg=, type=NODE_JOINED, tstamp=1594127065232], 
val2=AffinityTopologyVersion [topVer=-590633232614788648, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryEvent [evtNode=7eb6990e-ed38-42dd-b1ae-f4cb8f33956e, topVer=0, 
nodeId8=7904b65e, msg=, type=NODE_JOINED, tstamp=1594127065232], 
val2=AffinityTopologyVersion [topVer=-590633232614788648, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.topologyVersion[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=1b48a692371-20368e63-1380-47f7-a15e-81c80f14d2d7, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=6b04be02-f370-4c26-b3c0-934a046489b6, topVer=0, nodeId8=6b04be02, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594127065232]], 
val2=AffinityTopologyVersion [topVer=8130921099951580873, minorTopVer=0]]] - 
PASSED{color}
* {color:#013220}IgniteServiceGridTestSuite: 
ServiceDeploymentProcessIdSelfTest.requestId[Test event=IgniteBiTuple 
[val1=DiscoveryCustomEvent [customMsg=ServiceChangeBatchRequest 
[id=1b48a692371-20368e63-1380-47f7-a15e-81c80f14d2d7, reqs=SingletonList 
[ServiceUndeploymentRequest []]], affTopVer=null, super=DiscoveryEvent 
[evtNode=6b04be02-f370-4c26-b3c0-934a046489b6, topVer=0, nodeId8=6b04be02, 
msg=null, type=DISCOVERY_CUSTOM_EVT, tstamp=1594127065232]], 
val2=AffinityTopologyVersion [topVer=8130921099951580873, minorTopVer=0]]] - 
PASSED{color}

{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=5446157buildTypeId=IgniteTests24Java8_RunAll]

> SQL create index on invalid data type
> -
>
> Key: IGNITE-13200
> URL:

[jira] [Commented] (IGNITE-13200) SQL create index on invalid data type

2020-07-08 Thread Taras Ledkov (Jira)



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

Taras Ledkov commented on IGNITE-13200:
---

[~korlov], [~ibessonov], please review the patch.

> SQL create index on invalid data type
> -
>
> Key: IGNITE-13200
> URL: https://issues.apache.org/jira/browse/IGNITE-13200
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.8.1
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
> Fix For: 2.9
>
>
> *Reproduce*
> - Create cache with value class
> {code}
> private static class Value {
> @QuerySqlField
> int val_int;
> java.util.Date val_date;
> }
> {code}
> - alter table with command
> {{ALTER TABLE TEST ADD COLUMN (VAL_DATE DATE)}}
> - try to create index with command
> {{CREATE INDEX TEST_VAL_DATE_IDX ON TEST(VAL_DATE)}}
> {{CorruptedTreeException}} is thrown, the node is stopped.
> {code}
> class org.apache.ignite.IgniteCheckedException: Runtime failure on row: 
> Row@6a2853cd[ key: 0, val: 
> org.apache.ignite.internal.processors.query.CreateIndexOnInvalidDataTypeTest$Value
>  [idHash=1693430008, hash=1583713321, val_int=0, val_date=Thu Jan 01 03:00:00 
> MSK 1970] ][ 0,  java.util.Date cannot be cast to java.sql.Date> ]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doPut(BPlusTree.java:2438)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.putx(BPlusTree.java:2388)
>   at 
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.putx(H2TreeIndex.java:434)
>   at 
> org.apache.ignite.internal.processors.query.h2.IndexBuildClosure.apply(IndexBuildClosure.java:52)
>   at 
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCachePartitionWorker$SchemaIndexCacheVisitorClosureWrapper.apply(SchemaIndexCachePartitionWorker.java:298)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.updateIndex(GridCacheMapEntry.java:4494)
>   at 
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCachePartitionWorker.processKey(SchemaIndexCachePartitionWorker.java:231)
>   at 
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCachePartitionWorker.processPartition(SchemaIndexCachePartitionWorker.java:188)
>   at 
> org.apache.ignite.internal.processors.query.schema.SchemaIndexCachePartitionWorker.body(SchemaIndexCachePartitionWorker.java:127)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: class 
> org.apache.ignite.internal.processors.query.IgniteSQLException: Failed to 
> wrap object into H2 Value. java.util.Date cannot be cast to java.sql.Date
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.H2CacheRow.wrap(H2CacheRow.java:177)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.H2CacheRow.getValue0(H2CacheRow.java:109)
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.H2CacheRow.getValue(H2CacheRow.java:91)
>   at 
> org.apache.ignite.internal.processors.query.h2.database.io.AbstractH2ExtrasLeafIO.storeByOffset(AbstractH2ExtrasLeafIO.java:115)
>   at 
> org.apache.ignite.internal.processors.query.h2.database.io.AbstractH2ExtrasLeafIO.storeByOffset(AbstractH2ExtrasLeafIO.java:37)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusIO.store(BPlusIO.java:185)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.BPlusIO.insert(BPlusIO.java:272)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insertSimple(BPlusTree.java:3685)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.insert(BPlusTree.java:3667)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Put.access$1900(BPlusTree.java:3539)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:452)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Insert.run0(BPlusTree.java:433)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5889)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$GetPageHandler.run(BPlusTree.java:5875)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writePage(PageHandler.java:360)
>   at

[jira] [Commented] (IGNITE-13126) Refactor of Continuous Query buffers to reduce heap usage

2020-07-08 Thread Maxim Muzafarov (Jira)



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

Maxim Muzafarov commented on IGNITE-13126:
--

{code:title=CacheContinuousQueryEventBuffer.java}
if (batch == null || cntr < batch.startCntr)
{code}

We can skip backupQ.add() if we already have acked counter more then current 
counter.



> Refactor of Continuous Query buffers to reduce heap usage
> -
>
> Key: IGNITE-13126
> URL: https://issues.apache.org/jira/browse/IGNITE-13126
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Major
> Fix For: 2.9
>
>
> There are several unnecessary changes needs to be done to reduce continuous 
> query buffer usage:
> - CacheContinuousQueryEventBuffer.part is unnecessary;
> - CacheContinuousQueryEventBuffer.backupQ must be changed to 
> ConcurrentLinkedDeque;
> - Use lambda instead for partition counter resolving instead on anonymous 
> class creation for CacheContinuousQueryEventBuffer;
> - Batch local variables may be {{short}} type;
> etc.



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

[jira] [Created] (IGNITE-13228) Remote filter of IgniteEvents has to run with appropriate SecurityContext.

2020-07-08 Thread Denis Garus (Jira)

Denis Garus created IGNITE-13228:


 Summary: Remote filter of IgniteEvents has to run with appropriate 
SecurityContext.
 Key: IGNITE-13228
 URL: https://issues.apache.org/jira/browse/IGNITE-13228
 Project: Ignite
  Issue Type: Improvement
  Components: security
Affects Versions: 2.8.1
Reporter: Denis Garus
Assignee: Denis Garus
 Fix For: 2.9


The remote filter of IgniteEvents has to run on a remote node with the 
SecurityContext of the initiator node.



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

[jira] [Commented] (IGNITE-11393) Create IgniteLinkTaglet.toString() implementation for Java9+

2020-07-08 Thread Andrey Mashenkov (Jira)



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

Andrey Mashenkov commented on IGNITE-11393:
---

[~alex_pl], I've noticed you created a new PR and closed the old one.
Please, remove a link to the outdated PR and fix merge conflicts for the new 
one.

> Create IgniteLinkTaglet.toString() implementation for Java9+
> 
>
> Key: IGNITE-11393
> URL: https://issues.apache.org/jira/browse/IGNITE-11393
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitry Pavlov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> New implementation was added according to the new Java API for Javadoc.
> But the main method kept empty, need to implement toString() to process 
> IgniteLink annotation



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

[jira] [Commented] (IGNITE-11393) Create IgniteLinkTaglet.toString() implementation for Java9+

2020-07-08 Thread Andrey Mashenkov (Jira)



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

Andrey Mashenkov commented on IGNITE-11393:
---

[~alex_pl], fix look good.
{noformat}
But there still some issues with Javadoc on JDK 11+ (see IGNITE-13202){noformat}
Do you mean, Apache Ignite can now be successfully build from sources on JDK 
11+, 
but we still can't use JDK 11+ for release purposes as javadocs are still 
broken?

> Create IgniteLinkTaglet.toString() implementation for Java9+
> 
>
> Key: IGNITE-11393
> URL: https://issues.apache.org/jira/browse/IGNITE-11393
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitry Pavlov
>Assignee: Aleksey Plekhanov
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> New implementation was added according to the new Java API for Javadoc.
> But the main method kept empty, need to implement toString() to process 
> IgniteLink annotation



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

[jira] [Commented] (IGNITE-8728) "IllegalStateException: Duplicate Key" on node join

2020-07-08 Thread Abhay (Jira)



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

Abhay commented on IGNITE-8728:
---

Moreover I saw that if we use a create table command and use primary key 
against any column name then idxname is __KEY _PK and is this not duplicate 
KEY_ 

> "IllegalStateException: Duplicate Key" on node join
> ---
>
> Key: IGNITE-8728
> URL: https://issues.apache.org/jira/browse/IGNITE-8728
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.7
>Reporter: Mahesh Renduchintala
>Priority: Critical
> Fix For: 2.10
>
> Attachments: NS1_ignite-9676df15.0.log, NS2_ignite-7cfc8008.0.log, 
> ignite.txt, node-config.xml
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> I have two nodes on which we have 3 tables which are partitioned.  Index are 
> also built on these tables. 
> For 24 hours caches work fine.  The tables are definitely distributed across 
> both the nodes
> Node 2 reboots due to some issue - goes out of the baseline - comes back and 
> joins the baseline.  Other baseline nodes crash and in the logs we see 
> duplicate Key error
> [10:38:35,437][INFO][tcp-disco-srvr-#2|#2][TcpDiscoverySpi] TCP discovery 
> accepted incoming connection [rmtAddr=/192.168.1.7, rmtPort=45102]
>  [10:38:35,437][INFO][tcp-disco-srvr-#2|#2][TcpDiscoverySpi] TCP discovery 
> spawning a new thread for connection [rmtAddr=/192.168.1.7, rmtPort=45102]
>  [10:38:35,437][INFO][tcp-disco-sock-reader-#12|#12][TcpDiscoverySpi] Started 
> serving remote node connection [rmtAddr=/192.168.1.7:45102, rmtPort=45102]
>  [10:38:35,451][INFO][tcp-disco-sock-reader-#12|#12][TcpDiscoverySpi] 
> Finished serving remote node connection [rmtAddr=/192.168.1.7:45102, 
> rmtPort=45102
>  [10:38:35,457][SEVERE][tcp-disco-msg-worker-#3|#3][TcpDiscoverySpi] 
> TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node 
> in order to prevent cluster wide instability.
>  *java.lang.IllegalStateException: Duplicate key*
> at org.apache.ignite.cache.QueryEntity.checkIndexes(QueryEntity.java:223)
> at org.apache.ignite.cache.QueryEntity.makePatch(QueryEntity.java:174)
> at 
> org.apache.ignite.internal.processors.query.QuerySchema.makePatch(QuerySchema.java:114)
> at 
> org.apache.ignite.internal.processors.cache.DynamicCacheDescriptor.makeSchemaPatch(DynamicCacheDescriptor.java:360)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.validateNode(GridCacheProcessor.java:2536)
> at 
> org.apache.ignite.internal.managers.GridManagerAdapter$1.validateNode(GridManagerAdapter.java:566)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3629)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2736)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2621)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
>  [10:38:35,459][SEVERE][tcp-disco-msg-worker-#3|#3][] Critical system error 
> detected. Will be handled accordingly to configured handler [hnd=class 
> o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext 
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: 
> Duplicate key]]
> java.lang.IllegalStateException: Duplicate key
> at org.apache.ignite.cache.QueryEntity.checkIndexes(QueryEntity.java:223)
> at org.apache.ignite.cache.QueryEntity.makePatch(QueryEntity.java:174)
> at 
> org.apache.ignite.internal.processors.query.QuerySchema.makePatch(QuerySchema.java:114)
> at 
> org.apache.ignite.internal.processors.cache.DynamicCacheDescriptor.makeSchemaPatch(DynamicCacheDescriptor.java:360)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.validateNode(GridCacheProcessor.java:2536)
> at 
> org.apache.ignite.internal.managers.GridManagerAdapter$1.validateNode(GridManagerAdapter.java:566)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3629)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2736)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2621)
> at

[jira] [Commented] (IGNITE-8728) "IllegalStateException: Duplicate Key" on node join

2020-07-08 Thread Abhay (Jira)



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

Abhay commented on IGNITE-8728:
---

I have a test server where I have only one node on version 2.8.1 and it still 
crashes with same Duplicate key error and the only option that remains is to 
remove the work folder and create the complete tables again . 

The logs are attached [^ignite.txt]

> "IllegalStateException: Duplicate Key" on node join
> ---
>
> Key: IGNITE-8728
> URL: https://issues.apache.org/jira/browse/IGNITE-8728
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.7
>Reporter: Mahesh Renduchintala
>Priority: Critical
> Fix For: 2.10
>
> Attachments: NS1_ignite-9676df15.0.log, NS2_ignite-7cfc8008.0.log, 
> ignite.txt, node-config.xml
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> I have two nodes on which we have 3 tables which are partitioned.  Index are 
> also built on these tables. 
> For 24 hours caches work fine.  The tables are definitely distributed across 
> both the nodes
> Node 2 reboots due to some issue - goes out of the baseline - comes back and 
> joins the baseline.  Other baseline nodes crash and in the logs we see 
> duplicate Key error
> [10:38:35,437][INFO][tcp-disco-srvr-#2|#2][TcpDiscoverySpi] TCP discovery 
> accepted incoming connection [rmtAddr=/192.168.1.7, rmtPort=45102]
>  [10:38:35,437][INFO][tcp-disco-srvr-#2|#2][TcpDiscoverySpi] TCP discovery 
> spawning a new thread for connection [rmtAddr=/192.168.1.7, rmtPort=45102]
>  [10:38:35,437][INFO][tcp-disco-sock-reader-#12|#12][TcpDiscoverySpi] Started 
> serving remote node connection [rmtAddr=/192.168.1.7:45102, rmtPort=45102]
>  [10:38:35,451][INFO][tcp-disco-sock-reader-#12|#12][TcpDiscoverySpi] 
> Finished serving remote node connection [rmtAddr=/192.168.1.7:45102, 
> rmtPort=45102
>  [10:38:35,457][SEVERE][tcp-disco-msg-worker-#3|#3][TcpDiscoverySpi] 
> TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node 
> in order to prevent cluster wide instability.
>  *java.lang.IllegalStateException: Duplicate key*
> at org.apache.ignite.cache.QueryEntity.checkIndexes(QueryEntity.java:223)
> at org.apache.ignite.cache.QueryEntity.makePatch(QueryEntity.java:174)
> at 
> org.apache.ignite.internal.processors.query.QuerySchema.makePatch(QuerySchema.java:114)
> at 
> org.apache.ignite.internal.processors.cache.DynamicCacheDescriptor.makeSchemaPatch(DynamicCacheDescriptor.java:360)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.validateNode(GridCacheProcessor.java:2536)
> at 
> org.apache.ignite.internal.managers.GridManagerAdapter$1.validateNode(GridManagerAdapter.java:566)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3629)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2736)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2621)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
>  [10:38:35,459][SEVERE][tcp-disco-msg-worker-#3|#3][] Critical system error 
> detected. Will be handled accordingly to configured handler [hnd=class 
> o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext 
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: 
> Duplicate key]]
> java.lang.IllegalStateException: Duplicate key
> at org.apache.ignite.cache.QueryEntity.checkIndexes(QueryEntity.java:223)
> at org.apache.ignite.cache.QueryEntity.makePatch(QueryEntity.java:174)
> at 
> org.apache.ignite.internal.processors.query.QuerySchema.makePatch(QuerySchema.java:114)
> at 
> org.apache.ignite.internal.processors.cache.DynamicCacheDescriptor.makeSchemaPatch(DynamicCacheDescriptor.java:360)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.validateNode(GridCacheProcessor.java:2536)
> at 
> org.apache.ignite.internal.managers.GridManagerAdapter$1.validateNode(GridManagerAdapter.java:566)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3629)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2736)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775)
> at 
>

[jira] [Updated] (IGNITE-8728) "IllegalStateException: Duplicate Key" on node join

2020-07-08 Thread Abhay (Jira)



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

Abhay updated IGNITE-8728:
--
Attachment: ignite.txt

> "IllegalStateException: Duplicate Key" on node join
> ---
>
> Key: IGNITE-8728
> URL: https://issues.apache.org/jira/browse/IGNITE-8728
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.7
>Reporter: Mahesh Renduchintala
>Priority: Critical
> Fix For: 2.10
>
> Attachments: NS1_ignite-9676df15.0.log, NS2_ignite-7cfc8008.0.log, 
> ignite.txt, node-config.xml
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> I have two nodes on which we have 3 tables which are partitioned.  Index are 
> also built on these tables. 
> For 24 hours caches work fine.  The tables are definitely distributed across 
> both the nodes
> Node 2 reboots due to some issue - goes out of the baseline - comes back and 
> joins the baseline.  Other baseline nodes crash and in the logs we see 
> duplicate Key error
> [10:38:35,437][INFO][tcp-disco-srvr-#2|#2][TcpDiscoverySpi] TCP discovery 
> accepted incoming connection [rmtAddr=/192.168.1.7, rmtPort=45102]
>  [10:38:35,437][INFO][tcp-disco-srvr-#2|#2][TcpDiscoverySpi] TCP discovery 
> spawning a new thread for connection [rmtAddr=/192.168.1.7, rmtPort=45102]
>  [10:38:35,437][INFO][tcp-disco-sock-reader-#12|#12][TcpDiscoverySpi] Started 
> serving remote node connection [rmtAddr=/192.168.1.7:45102, rmtPort=45102]
>  [10:38:35,451][INFO][tcp-disco-sock-reader-#12|#12][TcpDiscoverySpi] 
> Finished serving remote node connection [rmtAddr=/192.168.1.7:45102, 
> rmtPort=45102
>  [10:38:35,457][SEVERE][tcp-disco-msg-worker-#3|#3][TcpDiscoverySpi] 
> TcpDiscoverSpi's message worker thread failed abnormally. Stopping the node 
> in order to prevent cluster wide instability.
>  *java.lang.IllegalStateException: Duplicate key*
> at org.apache.ignite.cache.QueryEntity.checkIndexes(QueryEntity.java:223)
> at org.apache.ignite.cache.QueryEntity.makePatch(QueryEntity.java:174)
> at 
> org.apache.ignite.internal.processors.query.QuerySchema.makePatch(QuerySchema.java:114)
> at 
> org.apache.ignite.internal.processors.cache.DynamicCacheDescriptor.makeSchemaPatch(DynamicCacheDescriptor.java:360)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.validateNode(GridCacheProcessor.java:2536)
> at 
> org.apache.ignite.internal.managers.GridManagerAdapter$1.validateNode(GridManagerAdapter.java:566)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3629)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2736)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2621)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
>  [10:38:35,459][SEVERE][tcp-disco-msg-worker-#3|#3][] Critical system error 
> detected. Will be handled accordingly to configured handler [hnd=class 
> o.a.i.failure.StopNodeOrHaltFailureHandler, failureCtx=FailureContext 
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.IllegalStateException: 
> Duplicate key]]
> java.lang.IllegalStateException: Duplicate key
> at org.apache.ignite.cache.QueryEntity.checkIndexes(QueryEntity.java:223)
> at org.apache.ignite.cache.QueryEntity.makePatch(QueryEntity.java:174)
> at 
> org.apache.ignite.internal.processors.query.QuerySchema.makePatch(QuerySchema.java:114)
> at 
> org.apache.ignite.internal.processors.cache.DynamicCacheDescriptor.makeSchemaPatch(DynamicCacheDescriptor.java:360)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.validateNode(GridCacheProcessor.java:2536)
> at 
> org.apache.ignite.internal.managers.GridManagerAdapter$1.validateNode(GridManagerAdapter.java:566)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processJoinRequestMessage(ServerImpl.java:3629)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2736)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2536)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6775)
> at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2621)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
>  [10:38:35,460][SEVERE][tcp-disco-msg-worker-#3|#3][] JVM will be halted 
> immediately due to the failure: [failureCtx=FailureContext 
>

[jira] [Commented] (IGNITE-13180) AuthenticationContext does not contain subject address when subject is IgniteClient

2020-07-08 Thread Sergei Ryzhov (Jira)



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

Sergei Ryzhov commented on IGNITE-13180:


[~ilyak] Please check the changes.

> AuthenticationContext does not contain subject address when subject is 
> IgniteClient
> ---
>
> Key: IGNITE-13180
> URL: https://issues.apache.org/jira/browse/IGNITE-13180
> Project: Ignite
>  Issue Type: Task
>  Components: thin client
>Reporter: Sergei Ryzhov
>Assignee: Sergei Ryzhov
>Priority: Minor
>
> AuthenticationContext does not contain subject address when subject is 
> IgniteClient



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

[jira] [Commented] (IGNITE-13013) Thick client must not open server sockets when used by serverless functions

2020-07-08 Thread Anton Kalashnikov (Jira)



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

Anton Kalashnikov commented on IGNITE-13013:


As I understand, If we forbid to create a server socket on the client-side, 
client-to-client connection would be impossible. So I have several corresponded 
questions:
* Does it need to support client-to-client connection along with prohibiting a 
server socket? Or if the server socket is forbidden, the client-to-client 
connection can be unsupported?
* Should a server socket ban and forceClientToServerConnection(IGNITE-12438) be 
merged into one feature or it should be two different features(one depends on 
other)? (ex. when forceClientToServerConnection set to true, only client able 
to connect to the server and at the same time client doesn't open the server 
socket).
* If we still need client-to-client connection(I believe we do), is it ok to 
use one of the server nodes as a proxy for such connection? It means the client 
doesn't establish a direct connection to other client but it establishes a 
connection to the server node(I believe the router node is best in this case) 
then this server node establishes a connection to the second client. 

My personal answers are the following:
* client-to-client connection should be supported because of its looks useful 
in several scenarios and some internal features also use it(deployment).
* It should be two different features but when the server socket isn't open, 
forceClientToServerConnection should be set to true automatically.
* Server node as the proxy is not a bad idea but it can lead to some problem in 
the failure scenarios and it leads to performance drop(It should be 
investigated how frequently and in which scenarios the ignite use 
client-to-client connection for understanding how big drop could be).

[~dmagda] can you share your view about this problem?

> Thick client must not open server sockets when used by serverless functions
> ---
>
> Key: IGNITE-13013
> URL: https://issues.apache.org/jira/browse/IGNITE-13013
> Project: Ignite
>  Issue Type: Improvement
>  Components: networking
>Affects Versions: 2.8
>Reporter: Denis A. Magda
>Priority: Critical
> Fix For: 2.9
>
>
> A thick client fails to start if being used inside of a serverless function 
> such as AWS Lamda or Azure Functions. Cloud providers prohibit opening 
> network ports to accept connections on the function's end. In short, the 
> function can only connect to a remote address.
> To reproduce, you can follow this tutorial and swap the thin client (used in 
> the tutorial) with the thick one: 
> https://www.gridgain.com/docs/tutorials/serverless/azure_functions_tutorial
> The thick client needs to support a mode when the communication SPI doesn't 
> create a server socket if the client is used for serverless computing. This 
> improvement looks like an extra task of this initiative: 
> https://issues.apache.org/jira/browse/IGNITE-12438



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

[jira] [Commented] (IGNITE-13219) Slf4jLogger does not implement the LoggerNodeIdAware interface.

2020-07-08 Thread YuJue Li (Jira)



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

YuJue Li commented on IGNITE-13219:
---

Both Log4JLogger and Log4J2Logger have implemented the LoggerNodeIdAware 
interface.

Slf4jLogger as a bridge library, if do not implement this interface and assign 
a value to the nodeId system property, the default configuration will not run 
normally, because the configuration of config/ignite-log4j2.xml is as follows:


 
 
 
 
 
 
 
 
 
 
 
 

> Slf4jLogger does not implement the LoggerNodeIdAware interface.
> ---
>
> Key: IGNITE-13219
> URL: https://issues.apache.org/jira/browse/IGNITE-13219
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.8.1
>Reporter: YuJue Li
>Assignee: YuJue Li
>Priority: Minor
> Fix For: 2.9
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> In the scenario of ignite + slf4j + log4j2, the generated log file is named 
> ignite-${sys:nodeId}.log, The reason for this problem is that Slf4jLogger 
> does not implement the
> LoggerNodeIdAware interface.



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

[jira] [Commented] (IGNITE-13226) .NET: Thin Client Compute leaks ClientNotificationHandler instances

2020-07-08 Thread Pavel Tupitsyn (Jira)



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

Pavel Tupitsyn commented on IGNITE-13226:
-

Merged to master: 69c5b516686924834876d3f52d349ac1880b20f3
Cherry-picked to ignite-2.9: bffe714072c3b9d45cad1bc6cd2a2fcf100b0795

> .NET: Thin Client Compute leaks ClientNotificationHandler instances
> ---
>
> Key: IGNITE-13226
> URL: https://issues.apache.org/jira/browse/IGNITE-13226
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.9
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .NET
> Fix For: 2.9
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> In multithreaded thin client compute scenarios there is a possibility for 
> ClientNotificationHandler leak: handlers remain in 
> ClientSocket._notificationListeners even after corresponding tasks have 
> completed.
> To reproduce, add the following code at the end of 
> ComputeClientTests.TestExecuteJavaTaskAsyncMultithreaded:
> {code}
> var failoverSocket = 
> TestUtils.GetPrivateField(client, "_socket");
> var socket = 
> TestUtils.GetPrivateField(failoverSocket, "_socket");
> var listeners = TestUtils.GetPrivateField(socket, 
> "_notificationListeners");
> Assert.IsEmpty(listeners);
> {code}



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

[jira] [Updated] (IGNITE-13216) QuerySqlField annotation's "name" property is not used during validation of known fields names

2020-07-08 Thread Evgeniy Rudenko (Jira)



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

Evgeniy Rudenko updated IGNITE-13216:
-
Description: (was: If "name" parameter is set it should be used instead 
of actual field name. Currently if 2 @QuerySqlField fields have same names we 
will receive error, even if they have different "name" properties.)

> QuerySqlField annotation's "name" property is not used during validation of 
> known fields names
> --
>
> Key: IGNITE-13216
> URL: https://issues.apache.org/jira/browse/IGNITE-13216
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Evgeniy Rudenko
>Assignee: Evgeniy Rudenko
>Priority: Blocker
> Fix For: 2.9
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>




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

[jira] [Updated] (IGNITE-12561) SQL: Fix incorrect check for conflict of field names in key and value.

2020-07-08 Thread Evgeniy Rudenko (Jira)



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

Evgeniy Rudenko updated IGNITE-12561:
-
Release Note: Added validation of the uniqueness of field's name annotated 
with @QuerySqlEntity. Previously cache could be started without errors, but the 
key's field would not be queryable:

> SQL: Fix incorrect check for conflict of field names in key and value.
> --
>
> Key: IGNITE-12561
> URL: https://issues.apache.org/jira/browse/IGNITE-12561
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Evgeniy Rudenko
>Assignee: Evgeniy Rudenko
>Priority: Major
> Fix For: 2.9
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> If key and value types of an SQL-enabled cache have the same fields annotated 
> with `@QuerySqlEntity` the cache will start without errors but the key's 
> field will not be queryable:
> {noformat}
> // here, you can't query Key.a via SQL
> class Key {
>@QuerySqlField int a; 
>@QuerySqlField int b; 
> }
> class Value { 
>@QuerySqlField int a;
>@QuerySqlField int c;
> }
> {noformat}
>  
> To workaround that, one needs to specify a different name for one of the `a` 
> fields: 
> {noformat}
> class Key {
>@QuerySqlField(name = "key_a") int a;
>@QuerySqlField int b; 
> }
> class Value {
>@QuerySqlField int a; 
>@QuerySqlField int c;
> }
> {noformat}
> The first configuration is obviously incorrect - one can't use the `Key.a` in 
> SQL but annotates it as queryable. We need to issue an error or at least a 
> warning for starting a configuration like this.



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

[jira] [Assigned] (IGNITE-13223) empty Batch throw an Exception

2020-07-08 Thread Jira



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

底限 reassigned IGNITE-13223:
---

Assignee: 底限

> empty Batch throw an Exception 
> ---
>
> Key: IGNITE-13223
> URL: https://issues.apache.org/jira/browse/IGNITE-13223
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.7.6
>Reporter: 底限
>Assignee: 底限
>Priority: Major
>




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

46 matches

Mail list logo