[jira] [Commented] (IGNITE-12044) [IEP-35] JmxExporterSpi displays histogram values incorrectly

2019-09-19 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12044:


{panel:title=Branch: [pull/6882/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4614493buildTypeId=IgniteTests24Java8_RunAll]

> [IEP-35] JmxExporterSpi displays histogram values incorrectly
> -
>
> Key: IGNITE-12044
> URL: https://issues.apache.org/jira/browse/IGNITE-12044
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-35
> Fix For: 2.8
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> {{JmxExporterSpi}} exposes histogram values incorrectly. It looks like:
> {noformat}
> durationHistogramlong[5]
> {noformat}
> I think exporter should register attribute for each histogram bucket. 
> Something like this:
> {noformat}
> durationHistogram.10 0
> durationHistogram.50 0
> durationHistogram.1000
> durationHistogram.2500
> durationHistogram.5000
> {noformat}



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


[jira] [Created] (IGNITE-12202) Support system function ROWNUM()

2019-09-19 Thread YuJue Li (Jira)
YuJue Li created IGNITE-12202:
-

 Summary: Support system function ROWNUM()
 Key: IGNITE-12202
 URL: https://issues.apache.org/jira/browse/IGNITE-12202
 Project: Ignite
  Issue Type: New Feature
  Components: sql
Affects Versions: 2.7.5
Reporter: YuJue Li
 Fix For: 3.0


H2 database support system function ROWNUM(), which is very common, Ignite 
should support its distributed version.



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


[jira] [Commented] (IGNITE-11423) Multiple configurations to SpringCacheManager

2019-09-19 Thread Jinil Lee (Jira)


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

Jinil Lee commented on IGNITE-11423:


[~kcheng.mvp] I am still waiting for a review. Can I change the assignee?

> Multiple configurations to SpringCacheManager
> -
>
> Key: IGNITE-11423
> URL: https://issues.apache.org/jira/browse/IGNITE-11423
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, spring
>Reporter: Jinil Lee
>Priority: Minor
>  Labels: newbie, pull-request-available
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> I'm using SpringCacheManager for my project.
> I want to apply each cache-specific configuration (eg expiry policy),
> but only one configuration applies when I create the cachemanager.



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


[jira] [Assigned] (IGNITE-11927) [IEP-35] Add ability to enable\disable subset of metrics

2019-09-19 Thread Andrey Gura (Jira)


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

Andrey Gura reassigned IGNITE-11927:


Assignee: Andrey Gura  (was: Nikolay Izhikov)

> [IEP-35] Add ability to enable\disable subset of metrics
> 
>
> Key: IGNITE-11927
> URL: https://issues.apache.org/jira/browse/IGNITE-11927
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Nikolay Izhikov
>Assignee: Andrey Gura
>Priority: Major
>  Labels: IEP-35
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Ignite should be able to:
> * Enable or disable an arbitrary subset of the metrics. User should be able 
> to do it in runtime.



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


[jira] [Commented] (IGNITE-12088) Cache or template name should be validated before attempt to start

2019-09-19 Thread Pavel Kovalenko (Jira)


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

Pavel Kovalenko commented on IGNITE-12088:
--

[~kcheng.mvp] Thank you. I've left comments in your PR. To check your PR you 
need to run all tests suites on TeamCity and get a green visa from TeamCity 
bot. You can find your PR in https://mtcga.gridgain.com/prs.html page and run 
"Trigger build" for comfort.
Please adjust your changes according to Ignite code style - 
https://cwiki.apache.org/confluence/display/IGNITE/Coding+Guidelines
Information about team city bot - 
https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+Teamcity+Bot

> Cache or template name should be validated before attempt to start
> --
>
> Key: IGNITE-12088
> URL: https://issues.apache.org/jira/browse/IGNITE-12088
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Pavel Kovalenko
>Assignee: kcheng.mvp
>Priority: Critical
>  Labels: usability
> Fix For: 2.8
>
>
> If set too long cache name it can be a cause of impossibility to create work 
> directory for that cache:
> {noformat}
> [2019-08-20 
> 19:35:42,139][ERROR][exchange-worker-#172%node1%][IgniteTestResources] 
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, 
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Failed to 
> initialize cache working directory (failed to create, make sure the work 
> folder has correct permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0]]
> class org.apache.ignite.IgniteCheckedException: Failed to initialize cache 
> working directory (failed to create, make sure the work folder has correct 
> permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:769)
>   at 
> 

[jira] [Commented] (IGNITE-11817) org.apache.ignite.client.ClientCache#removeAll() and org.apache.ignite.client.ClientCache#clear missed Java Doc

2019-09-19 Thread kcheng.mvp (Jira)


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

kcheng.mvp commented on IGNITE-11817:
-

I have checked the code. somebody added the javadoc. so close it.

> org.apache.ignite.client.ClientCache#removeAll() and 
> org.apache.ignite.client.ClientCache#clear missed Java Doc
> ---
>
> Key: IGNITE-11817
> URL: https://issues.apache.org/jira/browse/IGNITE-11817
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation, thin client
>Affects Versions: 2.7
>Reporter: kcheng.mvp
>Assignee: kcheng.mvp
>Priority: Trivial
> Fix For: 2.8
>
>
> Use would be confused about the these api, need to address the difference in 
> the java doc.
> please see the mail list
> http://apache-ignite-users.70518.x6.nabble.com/What-s-the-difference-between-ClientCache-removeAll-and-ClientCache-clear-td28002.html



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


[jira] [Resolved] (IGNITE-11817) org.apache.ignite.client.ClientCache#removeAll() and org.apache.ignite.client.ClientCache#clear missed Java Doc

2019-09-19 Thread kcheng.mvp (Jira)


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

kcheng.mvp resolved IGNITE-11817.
-
Resolution: Fixed

> org.apache.ignite.client.ClientCache#removeAll() and 
> org.apache.ignite.client.ClientCache#clear missed Java Doc
> ---
>
> Key: IGNITE-11817
> URL: https://issues.apache.org/jira/browse/IGNITE-11817
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation, thin client
>Affects Versions: 2.7
>Reporter: kcheng.mvp
>Assignee: kcheng.mvp
>Priority: Trivial
> Fix For: 2.8
>
>
> Use would be confused about the these api, need to address the difference in 
> the java doc.
> please see the mail list
> http://apache-ignite-users.70518.x6.nabble.com/What-s-the-difference-between-ClientCache-removeAll-and-ClientCache-clear-td28002.html



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


[jira] [Updated] (IGNITE-12179) Test and javadoc fixes

2019-09-19 Thread Dmitriy Govorukhin (Jira)


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

Dmitriy Govorukhin updated IGNITE-12179:

Fix Version/s: 2.8

> Test and javadoc fixes
> --
>
> Key: IGNITE-12179
> URL: https://issues.apache.org/jira/browse/IGNITE-12179
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> *.testTtlNoTx flaky failed on TC
> TcpCommunicationSpiFreezingClientTest failed
> TcpCommunicationSpiFaultyClientSslTest.testNotAcceptedConnection failed
> testCacheIdleVerifyPrintLostPartitions failed



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


[jira] [Commented] (IGNITE-12088) Cache or template name should be validated before attempt to start

2019-09-19 Thread kcheng.mvp (Jira)


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

kcheng.mvp commented on IGNITE-12088:
-

TeamCity is green 
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_BuildApacheIgnite=buildTypeBranches

> Cache or template name should be validated before attempt to start
> --
>
> Key: IGNITE-12088
> URL: https://issues.apache.org/jira/browse/IGNITE-12088
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Pavel Kovalenko
>Assignee: kcheng.mvp
>Priority: Critical
>  Labels: usability
> Fix For: 2.8
>
>
> If set too long cache name it can be a cause of impossibility to create work 
> directory for that cache:
> {noformat}
> [2019-08-20 
> 19:35:42,139][ERROR][exchange-worker-#172%node1%][IgniteTestResources] 
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, 
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Failed to 
> initialize cache working directory (failed to create, make sure the work 
> folder has correct permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0]]
> class org.apache.ignite.IgniteCheckedException: Failed to initialize cache 
> working directory (failed to create, make sure the work folder has correct 
> permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:769)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:748)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.persistCacheConfigurations(CachesRegistry.java:289)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.registerAllCachesAndGroups(CachesRegistry.java:264)
>   at 
> 

[jira] [Commented] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH

2019-09-19 Thread kcheng.mvp (Jira)


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

kcheng.mvp commented on IGNITE-11008:
-

[~spilschikov] Raised a PR https://github.com/apache/ignite/pull/6885. 

> JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
> --
>
> Key: IGNITE-11008
> URL: https://issues.apache.org/jira/browse/IGNITE-11008
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: kcheng.mvp
>Priority: Minor
> Fix For: 2.8
>
>
> Found redundant spaces in 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns
> "IS_GENERATEDCOLUMN "
> "BUFFER_LENGTH "



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


[jira] [Commented] (IGNITE-12109) The distributed metastorage must support read/write operation on an inactive cluster.

2019-09-19 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12109:


{panel:title=Branch: [pull/6873/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4605325buildTypeId=IgniteTests24Java8_RunAll]

> The distributed metastorage must support read/write operation on an inactive 
> cluster.
> -
>
> Key: IGNITE-12109
> URL: https://issues.apache.org/jira/browse/IGNITE-12109
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Ivan Bessonov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> The metastorage isn't able to propagate value on an inactive cluster.



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


[jira] [Commented] (IGNITE-9160) FindBugs: NPE and CCE on equals() methods

2019-09-19 Thread Maxim Muzafarov (Jira)


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

Maxim Muzafarov commented on IGNITE-9160:
-

[~zzzadruga]

Hello, is there any chance to complete this issue?

> FindBugs: NPE and CCE on equals() methods
> -
>
> Key: IGNITE-9160
> URL: https://issues.apache.org/jira/browse/IGNITE-9160
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
>
> Some classes have Incorrect equals() method:
> {code:java}
> // GridDhtPartitionMap.java
> @Override public boolean equals(Object o) {
> if (this == o)
> return true;
> GridDhtPartitionMap other = (GridDhtPartitionMap)o;
> return other.nodeId.equals(nodeId) && other.updateSeq == updateSeq;
> }{code}
> In this case, we can get CCE  
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(new Object());
> --
> Exception in thread "main" java.lang.ClassCastException: java.lang.Object 
> cannot be cast to 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:319)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
>  Or NPE 
> {code:java}
> GridDhtPartitionMap gridDhtPartMap = new GridDhtPartitionMap();
> gridDhtPartMap.equals(null);
> --
> Exception in thread "main" java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap.equals(GridDhtPartitionMap.java:321)
> at ru.zzzadruga.Ignite.main(Ignite.java:9){code}
>  The following code will prevent this
> {code:java}
> if (o == null || getClass() != o.getClass())
>     return false;{code}
> + List of classes with similar problems: +
>  * *GridTopic$T1-T8* - NPE
>  * *GridCachePreloadLifecycleAbstractTest -* NPE
>  * *GridDhtPartitionFullMap -* NPE and CCE
>  * *GridDhtPartitionMap -* NPE and CCE
>  * *OptimizedMarshallerSelfTest -* NPE and CCE
>  * *GatewayProtectedCacheProxy -* NPE and CCE
>  * *GridNearOptimisticTxPrepareFuture -* NPE and CCE
>  * *GridCacheDistributedQueryManager -* NPE and CCE
>  * *GridServiceMethodReflectKey -* NPE and CCE
>  *  *GridListSetSelfTest -* NPE and CCE
>  * *GridTestKey -* NPE and CCE
>  * *GridCacheMvccCandidate -* CCE
>  * *GridDhtPartitionExchangeId -* CCE
>  * *GridTuple6 -* CCE



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


[jira] [Assigned] (IGNITE-11008) JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH

2019-09-19 Thread kcheng.mvp (Jira)


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

kcheng.mvp reassigned IGNITE-11008:
---

Assignee: kcheng.mvp

> JDBC Metadata: redundant spaces IS_GENERATEDCOLUMN & BUFFER_LENGTH
> --
>
> Key: IGNITE-11008
> URL: https://issues.apache.org/jira/browse/IGNITE-11008
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc
>Affects Versions: 2.7
>Reporter: Stepan Pilschikov
>Assignee: kcheng.mvp
>Priority: Minor
> Fix For: 2.8
>
>
> Found redundant spaces in 
> org.apache.ignite.internal.jdbc.thin.JdbcThinDatabaseMetadata#getColumns
> "IS_GENERATEDCOLUMN "
> "BUFFER_LENGTH "



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


[jira] [Assigned] (IGNITE-11458) ClassCastException when reading objects in Collection and Map from ClientCache

2019-09-19 Thread kcheng.mvp (Jira)


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

kcheng.mvp reassigned IGNITE-11458:
---

Assignee: (was: kcheng.mvp)

> ClassCastException when reading objects in Collection and Map from ClientCache
> --
>
> Key: IGNITE-11458
> URL: https://issues.apache.org/jira/browse/IGNITE-11458
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
> Environment: ignite-core.2.8.0
>Reporter: Jinil Lee
>Priority: Major
>  Labels: newbie, patch, pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is a ClassCastException when reading objects in Collection or Map 
> stored in ClientCache while using thin client.
> When deserializing a BinaryObject, I think that the Object in the Collection 
> is not being processed.
> I made a patch and I think it works well with the my patch,
>  so please let me know if this is not a problem or if you have any other 
> solutions.
> Below is the test code.
> {code:java}
> //Case 0. Object
> ClientCache cache1 = igniteClient.getOrCreateCache("Object");
> cache1.put("key", val);
> //OK!!!
> System.out.println(cache1.get("key").getStreet());
> //---
> //Case 1. Collection
> //---
> ClientCache> cache2 = 
> igniteClient.getOrCreateCache("Collection");
> List list = new ArrayList<>();
> list.add(val);
> cache2.put("key", list);
> //ClassCastException!!!
> System.out.println(cache2.get("key").get(0).getStreet()); 
> //---
> //Case 2. Map
> //---
> ClientCache> cache3 = 
> igniteClient.getOrCreateCache("Map");
> Map map = new HashMap<>();
> map.put("key", val);
> cache3.getAndPut("key", map);
> //ClassCastException!!!
> System.out.println(cache3.get("key").get("key").getStreet());
> //---
> //Case 3. Colection + Map
> //---
> ClientCache>> cache4 = 
> igniteClient.getOrCreateCache("Collection_Map");
> List> mapList = new ArrayList<>();
> mapList.add(map);
> cache4.put("key", mapList);
> //ClassCastException!!!
> System.out.println(cache4.get("key").get(0).get("key").getStreet());
> {code}
>  
>  



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


[jira] [Assigned] (IGNITE-11458) ClassCastException when reading objects in Collection and Map from ClientCache

2019-09-19 Thread kcheng.mvp (Jira)


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

kcheng.mvp reassigned IGNITE-11458:
---

Assignee: kcheng.mvp

> ClassCastException when reading objects in Collection and Map from ClientCache
> --
>
> Key: IGNITE-11458
> URL: https://issues.apache.org/jira/browse/IGNITE-11458
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
> Environment: ignite-core.2.8.0
>Reporter: Jinil Lee
>Assignee: kcheng.mvp
>Priority: Major
>  Labels: newbie, patch, pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is a ClassCastException when reading objects in Collection or Map 
> stored in ClientCache while using thin client.
> When deserializing a BinaryObject, I think that the Object in the Collection 
> is not being processed.
> I made a patch and I think it works well with the my patch,
>  so please let me know if this is not a problem or if you have any other 
> solutions.
> Below is the test code.
> {code:java}
> //Case 0. Object
> ClientCache cache1 = igniteClient.getOrCreateCache("Object");
> cache1.put("key", val);
> //OK!!!
> System.out.println(cache1.get("key").getStreet());
> //---
> //Case 1. Collection
> //---
> ClientCache> cache2 = 
> igniteClient.getOrCreateCache("Collection");
> List list = new ArrayList<>();
> list.add(val);
> cache2.put("key", list);
> //ClassCastException!!!
> System.out.println(cache2.get("key").get(0).getStreet()); 
> //---
> //Case 2. Map
> //---
> ClientCache> cache3 = 
> igniteClient.getOrCreateCache("Map");
> Map map = new HashMap<>();
> map.put("key", val);
> cache3.getAndPut("key", map);
> //ClassCastException!!!
> System.out.println(cache3.get("key").get("key").getStreet());
> //---
> //Case 3. Colection + Map
> //---
> ClientCache>> cache4 = 
> igniteClient.getOrCreateCache("Collection_Map");
> List> mapList = new ArrayList<>();
> mapList.add(map);
> cache4.put("key", mapList);
> //ClassCastException!!!
> System.out.println(cache4.get("key").get(0).get("key").getStreet());
> {code}
>  
>  



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


[jira] [Assigned] (IGNITE-11723) IgniteSpark integration should support skipStore option for internal dataStreamer (IgniteRdd and Ignite DataFrame)

2019-09-19 Thread Aleksey Zinoviev (Jira)


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

Aleksey Zinoviev reassigned IGNITE-11723:
-

Assignee: Aleksey Zinoviev  (was: Andrey Aleksandrov)

> IgniteSpark integration should support skipStore option for internal 
> dataStreamer (IgniteRdd and Ignite DataFrame)
> --
>
> Key: IGNITE-11723
> URL: https://issues.apache.org/jira/browse/IGNITE-11723
> Project: Ignite
>  Issue Type: Improvement
>  Components: spark
>Affects Versions: 2.7
>Reporter: Andrey Aleksandrov
>Assignee: Aleksey Zinoviev
>Priority: Major
> Fix For: 2.8
>
>
> At the moment this option can't be set. But this integrations could be used 
> for initial data loading also for the caches with cache stores 
> implementation. 
> With skipStore option, we could avoid write-through behavior during this 
> initial data loading.



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


[jira] [Commented] (IGNITE-11721) IgniteJdbcDriver with streaming enabled doesn't use IgniteDataStreamer on executeBatch

2019-09-19 Thread kcheng.mvp (Jira)


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

kcheng.mvp commented on IGNITE-11721:
-

[~antkr] Can you supply a reproducer for this ticket? I would like to 
investigate this issue. thanks.

> IgniteJdbcDriver with streaming enabled doesn't use IgniteDataStreamer on 
> executeBatch
> --
>
> Key: IGNITE-11721
> URL: https://issues.apache.org/jira/browse/IGNITE-11721
> Project: Ignite
>  Issue Type: Bug
>  Components: jdbc, streaming
>Affects Versions: 2.7
>Reporter: Anton Kurbanov
>Priority: Minor
>




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


[jira] [Assigned] (IGNITE-11724) IgniteSpark integration forget to close the IgniteContext and stops the client node in case if error during PairFunction logic

2019-09-19 Thread Aleksey Zinoviev (Jira)


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

Aleksey Zinoviev reassigned IGNITE-11724:
-

Assignee: Aleksey Zinoviev

> IgniteSpark integration forget to close the IgniteContext and stops the 
> client node in case if error during PairFunction logic 
> ---
>
> Key: IGNITE-11724
> URL: https://issues.apache.org/jira/browse/IGNITE-11724
> Project: Ignite
>  Issue Type: Bug
>  Components: spark
>Affects Versions: 2.7
>Reporter: Andrey Aleksandrov
>Assignee: Aleksey Zinoviev
>Priority: Major
> Fix For: 2.8
>
>
> Next code could hang in case if PairFunction logic will throw the exception:
> JavaPairRDD rdd_records = records.mapToPair(new MapFunction());
> JavaIgniteContext igniteContext = new 
> JavaIgniteContext<>(sparkCtx, configUrl);
> JavaIgniteRDD igniteRdd = igniteContext. Value>fromCache(cacheName);
> igniteRdd.savePairs(rdd_records);
> Looks like next internal code (saveValues method)should also close the 
> IgniteContext in case of an unexpected exception, not only data streamer:
>  try {
>     it.foreach(value ⇒ {
>          val key = affinityKeyFunc(value, node.orNull)
>           streamer.addData(key, value)
>        })
>     }
>     finally {
>         streamer.close()
>     }
>  })
> }



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


[jira] [Assigned] (IGNITE-12141) Ignite Spark Integration Support Schema on Table Write

2019-09-19 Thread Aleksey Zinoviev (Jira)


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

Aleksey Zinoviev reassigned IGNITE-12141:
-

Assignee: Aleksey Zinoviev

> Ignite Spark Integration Support Schema on Table Write
> --
>
> Key: IGNITE-12141
> URL: https://issues.apache.org/jira/browse/IGNITE-12141
> Project: Ignite
>  Issue Type: Improvement
>  Components: spark
>Affects Versions: 2.7.5
>Reporter: Manoj G T
>Assignee: Aleksey Zinoviev
>Priority: Critical
> Fix For: 2.8
>
>   Original Estimate: 4h
>  Remaining Estimate: 4h
>
> Ignite 2.6 doesn't allow to create table on any schema other than Public 
> Schema and this is the reason for not supporting "OPTION_SCHEMA" during 
> Overwrite mode. Now that Ignite supports to create the table in any given 
> schema it will be great if we can incorporate the changes to support 
> "OPTION_SCHEMA" during Overwrite mode and make it available as part of next 
> Ignite release.
>  
> +Related Issue:+
> [https://stackoverflow.com/questions/57782033/apache-ignite-spark-integration-not-working-with-schema-name]



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


[jira] [Assigned] (IGNITE-12159) Ignite spark doesn't support Alter Column syntax

2019-09-19 Thread Aleksey Zinoviev (Jira)


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

Aleksey Zinoviev reassigned IGNITE-12159:
-

Assignee: Aleksey Zinoviev

> Ignite spark doesn't support Alter Column syntax
> 
>
> Key: IGNITE-12159
> URL: https://issues.apache.org/jira/browse/IGNITE-12159
> Project: Ignite
>  Issue Type: Bug
>  Components: spark
>Affects Versions: 2.7.5
>Reporter: Andrey Aleksandrov
>Assignee: Aleksey Zinoviev
>Priority: Critical
> Fix For: 2.8
>
>
> Steps:
> 1)Start the server
>  2)Run next SQL commands
> CREATE TABLE person (id LONG, name VARCHAR(64), age LONG, city_id DOUBLE, 
> zip_code LONG, PRIMARY KEY (name)) WITH "backups=1"
>  ALTER TABLE person ADD COLUMN (first_name VARCHAR(64), last_name VARCHAR(64))
> 3)After that run next spark code:
>        String configPath = "client.xml";
>        
>     SparkConf sparkConf = new SparkConf()
>     .setMaster("local")
>     .setAppName("Example"); 
>       IgniteSparkSession.builder()
>     .appName("Spark Ignite catalog example")
>     .master("local")
>     .config("ignite.disableSparkSQLOptimization", true)
>     .igniteConfig(configPath)
>     .getOrCreate();
>   
>        Dataset df2 = igniteSession.sql("select * from person");   
>        df2.show();
> The result will contain only 5 columns from CREATE TABLE call.
> [http://apache-ignite-users.70518.x6.nabble.com/Altered-sql-table-adding-new-columns-does-not-reflect-in-Spark-shell-td29265.html]



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


[jira] [Commented] (IGNITE-12088) Cache or template name should be validated before attempt to start

2019-09-19 Thread kcheng.mvp (Jira)


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

kcheng.mvp commented on IGNITE-12088:
-

[~Jokser] PR is read : https://github.com/apache/ignite/pull/6884. Can you help 
me do a code review?

> Cache or template name should be validated before attempt to start
> --
>
> Key: IGNITE-12088
> URL: https://issues.apache.org/jira/browse/IGNITE-12088
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Pavel Kovalenko
>Assignee: kcheng.mvp
>Priority: Critical
>  Labels: usability
> Fix For: 2.8
>
>
> If set too long cache name it can be a cause of impossibility to create work 
> directory for that cache:
> {noformat}
> [2019-08-20 
> 19:35:42,139][ERROR][exchange-worker-#172%node1%][IgniteTestResources] 
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED, 
> SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Failed to 
> initialize cache working directory (failed to create, make sure the work 
> folder has correct permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0]]
> class org.apache.ignite.IgniteCheckedException: Failed to initialize cache 
> working directory (failed to create, make sure the work folder has correct 
> permissions): 
> /home/gridgain/projects/incubator-ignite/work/db/node1/cache-CacheConfiguration
>  [name=ccfg3staticTemplate*, grpName=null, memPlcName=null, 
> storeConcurrentLoadAllThreshold=5, rebalancePoolSize=1, 
> rebalanceTimeout=1, evictPlc=null, evictPlcFactory=null, 
> onheapCache=false, sqlOnheapCache=false, sqlOnheapCacheMaxSize=0, 
> evictFilter=null, eagerTtl=true, dfltLockTimeout=0, nearCfg=null, 
> writeSync=null, storeFactory=null, storeKeepBinary=false, loadPrevVal=false, 
> aff=null, cacheMode=PARTITIONED, atomicityMode=null, backups=6, 
> invalidate=false, tmLookupClsName=null, rebalanceMode=ASYNC, 
> rebalanceOrder=0, rebalanceBatchSize=524288, rebalanceBatchesPrefetchCnt=2, 
> maxConcurrentAsyncOps=500, sqlIdxMaxInlineSize=-1, writeBehindEnabled=false, 
> writeBehindFlushSize=10240, writeBehindFlushFreq=5000, 
> writeBehindFlushThreadCnt=1, writeBehindBatchSize=512, 
> writeBehindCoalescing=true, maxQryIterCnt=1024, affMapper=null, 
> rebalanceDelay=0, rebalanceThrottle=0, interceptor=null, 
> longQryWarnTimeout=3000, qryDetailMetricsSz=0, readFromBackup=true, 
> nodeFilter=null, sqlSchema=null, sqlEscapeAll=false, cpOnRead=true, 
> topValidator=null, partLossPlc=IGNORE, qryParallelism=1, evtsDisabled=false, 
> encryptionEnabled=false, diskPageCompression=null, 
> diskPageCompressionLevel=null]0
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:769)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.checkAndInitCacheWorkDir(FilePageStoreManager.java:748)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.persistCacheConfigurations(CachesRegistry.java:289)
>   at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.registerAllCachesAndGroups(CachesRegistry.java:264)
>   at 
> 

[jira] [Closed] (IGNITE-11737) Apache Ignite 2.7.5 Linux packages version update

2019-09-19 Thread Peter Ivanov (Jira)


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

Peter Ivanov closed IGNITE-11737.
-

> Apache Ignite 2.7.5 Linux packages version update
> -
>
> Key: IGNITE-11737
> URL: https://issues.apache.org/jira/browse/IGNITE-11737
> Project: Ignite
>  Issue Type: Task
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.7.5
>
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> Update DEB and RPM packages' versions in Apache Ignite for the next version 
> (2.7.5)



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


[jira] [Updated] (IGNITE-12201) distributed sql join not working as mentioned in documentation

2019-09-19 Thread shivakumar (Jira)


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

shivakumar updated IGNITE-12201:

Attachment: distributed_sql_error.txt

> distributed sql join not working as mentioned in documentation
> --
>
> Key: IGNITE-12201
> URL: https://issues.apache.org/jira/browse/IGNITE-12201
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.7
> Environment: Kubernetes on RHEL 7.6
>Reporter: shivakumar
>Priority: Major
> Attachments: distributed_sql_error.txt
>
>
> I am trying to do a simple cross join on two tables with non-collocated data 
> (without affinity key), 
> This non-collocated distributed join always fails with the error message:
>  
> *"java.sql.SQLException: javax.cache.CacheException: Failed to prepare 
> distributed join query: join condition does not use index "*
>  
> If I create one of the tables in replicated mode and another one in 
> partitioned mode this Join operation works but documentation mentions that 
> Ignite supports non-collocated joins without any condition.
> And we tried with 3 tables and 1 in replicated and other 2 in partitioned 
> then we observed that it failed.
> we are running the Join operations with *distributedJoins=true.*
> *We observed that if there are N tables in Join operation then (N-1) should 
> be in replicated mode, is our understanding right?*
> *If our understanding is correct then to do Join operation the dimensioning 
> of cluster increases by many folds which can't be used in a production 
> environment.*
> *To reproduce:*
> *Ignite with 4 node cluster with native persistence enabled.*
> *create the following tables*
> {quote} {{CREATE TABLE City (}}{quote}
> {quote} {{  id LONG PRIMARY KEY, name VARCHAR)}}{quote}
> {quote} {{  WITH "backup=1";}}{quote}
> {quote} {{}}{quote}
> {quote} {{CREATE TABLE Person (}}
>  {{  id LONG, name VARCHAR, city_id LONG, PRIMARY KEY (id, city_id))}}
>  {{  WITH "backups=1";}}
>  {{}}
>  {{CREATE INDEX idx_city_name ON City (name);}}
>  {{}}
>  {{CREATE INDEX idx_person_name ON Person (name);}}
>  
>  {{INSERT INTO City (id, name) VALUES (1, 'Forest Hill');}}
>  {{INSERT INTO City (id, name) VALUES (2, 'Denver');}}
>  {{INSERT INTO City (id, name) VALUES (3, 'St. Petersburg');}}
>  {{}}
>  {{INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3);}}
>  {{INSERT INTO Person (id, name, city_id) VALUES (2, 'Jane Roe', 2);}}
>  {{INSERT INTO Person (id, name, city_id) VALUES (3, 'Mary Major', 1);}}
>  {{INSERT INTO Person (id, name, city_id) VALUES (4, 'Richard Miles', 2);}} {{
> }}{quote}
> Query to be run:
> {quote}select * from City c, Person p;{color:#66}
> {color}{quote}
> {quote}or 
> {color:#80}*SELECT*{color} * *{color:#80}FROM{color}* City 
> *{color:#80}AS{color}* c *{color:#80}CROSS{color}* 
> *{color:#80}join{color}* Person *{color:#80}AS{color}* p;{quote}



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


[jira] [Created] (IGNITE-12201) distributed sql join not working as mentioned in documentation

2019-09-19 Thread shivakumar (Jira)
shivakumar created IGNITE-12201:
---

 Summary: distributed sql join not working as mentioned in 
documentation
 Key: IGNITE-12201
 URL: https://issues.apache.org/jira/browse/IGNITE-12201
 Project: Ignite
  Issue Type: Bug
  Components: sql
Affects Versions: 2.7
 Environment: Kubernetes on RHEL 7.6
Reporter: shivakumar
 Attachments: distributed_sql_error.txt

I am trying to do a simple cross join on two tables with non-collocated data 
(without affinity key), 
This non-collocated distributed join always fails with the error message:
 
*"java.sql.SQLException: javax.cache.CacheException: Failed to prepare 
distributed join query: join condition does not use index "*
 
If I create one of the tables in replicated mode and another one in partitioned 
mode this Join operation works but documentation mentions that Ignite supports 
non-collocated joins without any condition.
And we tried with 3 tables and 1 in replicated and other 2 in partitioned then 
we observed that it failed.
we are running the Join operations with *distributedJoins=true.*
*We observed that if there are N tables in Join operation then (N-1) should be 
in replicated mode, is our understanding right?*
*If our understanding is correct then to do Join operation the dimensioning of 
cluster increases by many folds which can't be used in a production 
environment.*
*To reproduce:*
*Ignite with 4 node cluster with native persistence enabled.*
*create the following tables*
{quote} {{CREATE TABLE City (}}{quote}
{quote} {{  id LONG PRIMARY KEY, name VARCHAR)}}{quote}
{quote} {{  WITH "backup=1";}}{quote}
{quote} {{}}{quote}
{quote} {{CREATE TABLE Person (}}
 {{  id LONG, name VARCHAR, city_id LONG, PRIMARY KEY (id, city_id))}}
 {{  WITH "backups=1";}}
 {{}}
 {{CREATE INDEX idx_city_name ON City (name);}}
 {{}}
 {{CREATE INDEX idx_person_name ON Person (name);}}
 
 {{INSERT INTO City (id, name) VALUES (1, 'Forest Hill');}}
 {{INSERT INTO City (id, name) VALUES (2, 'Denver');}}
 {{INSERT INTO City (id, name) VALUES (3, 'St. Petersburg');}}
 {{}}
 {{INSERT INTO Person (id, name, city_id) VALUES (1, 'John Doe', 3);}}
 {{INSERT INTO Person (id, name, city_id) VALUES (2, 'Jane Roe', 2);}}
 {{INSERT INTO Person (id, name, city_id) VALUES (3, 'Mary Major', 1);}}
 {{INSERT INTO Person (id, name, city_id) VALUES (4, 'Richard Miles', 2);}} {{
}}{quote}
Query to be run:
{quote}select * from City c, Person p;{color:#66}
{color}{quote}
{quote}or 
{color:#80}*SELECT*{color} * *{color:#80}FROM{color}* City 
*{color:#80}AS{color}* c *{color:#80}CROSS{color}* 
*{color:#80}join{color}* Person *{color:#80}AS{color}* p;{quote}



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


[jira] [Commented] (IGNITE-12044) [IEP-35] JmxExporterSpi displays histogram values incorrectly

2019-09-19 Thread Amelchev Nikita (Jira)


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

Amelchev Nikita commented on IGNITE-12044:
--

[~NIzhikov], LGTM

> [IEP-35] JmxExporterSpi displays histogram values incorrectly
> -
>
> Key: IGNITE-12044
> URL: https://issues.apache.org/jira/browse/IGNITE-12044
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-35
> Fix For: 2.8
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> {{JmxExporterSpi}} exposes histogram values incorrectly. It looks like:
> {noformat}
> durationHistogramlong[5]
> {noformat}
> I think exporter should register attribute for each histogram bucket. 
> Something like this:
> {noformat}
> durationHistogram.10 0
> durationHistogram.50 0
> durationHistogram.1000
> durationHistogram.2500
> durationHistogram.5000
> {noformat}



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


[jira] [Updated] (IGNITE-12200) More informative assertion message at constructor of CachedDeploymentInfo (GridCacheDeploymentManager class)

2019-09-19 Thread Dmitriy Sorokin (Jira)


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

Dmitriy Sorokin updated IGNITE-12200:
-
Description: 
{code:java}
/**
 * @param sndId Sender.
 * @param ldrId Loader ID.
 * @param userVer User version.
 * @param depMode Deployment mode.
 * @param participants Participants.
 */
private CachedDeploymentInfo(UUID sndId, IgniteUuid ldrId, String userVer, 
DeploymentMode depMode,
Map participants) {
assert sndId.equals(ldrId.globalId()) || participants != null;

this.sndId = sndId;
this.ldrId = ldrId;
this.userVer = userVer;
this.depMode = depMode;
this.participants = participants == null || participants.isEmpty() ? null :
new ConcurrentLinkedHashMap<>(participants);
}
{code}
The code above may produce the following stacktrace, where AssertionError 
should contain more informative message for better root cause analysis:
{noformat}
2019-09-17 
18:29:29.890[ERROR][query-#1577440%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
 Failed to process message [senderId=4c071d12-325a-4bb1-a68d-cc910f636562, 
msg=GridCacheQueryRequest [id=4922, 
cacheName=com.sbt.limits.data.entity.LimitTemplateV1Entity_DPL_union-module, 
type=SCAN, fields=false, clause=null, clsName=null, keyValFilter=null, 
rdc=null, trans=null, pageSize=1024, incBackups=false, cancel=false, 
incMeta=false, all=false, keepBinary=true, 
subjId=4c071d12-325a-4bb1-a68d-cc910f636562, taskHash=0, part=-1, 
topVer=AffinityTopologyVersion [topVer=191, minorTopVer=0], 
super=GridCacheIdMessage [cacheId=-724666788]]]2019-09-17 
18:29:29.890[ERROR][query-#1577440%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
 Failed to process message [senderId=4c071d12-325a-4bb1-a68d-cc910f636562, 
msg=GridCacheQueryRequest [id=4922, 
cacheName=com.sbt.limits.data.entity.LimitTemplateV1Entity_DPL_union-module, 
type=SCAN, fields=false, clause=null, clsName=null, keyValFilter=null, 
rdc=null, trans=null, pageSize=1024, incBackups=false, cancel=false, 
incMeta=false, all=false, keepBinary=true, 
subjId=4c071d12-325a-4bb1-a68d-cc910f636562, taskHash=0, part=-1, 
topVer=AffinityTopologyVersion [topVer=191, minorTopVer=0], 
super=GridCacheIdMessage [cacheId=-724666788]]]
java.lang.AssertionError: null
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:918)
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:889)
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.p2pContext(GridCacheDeploymentManager.java:422)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1547)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:582)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:386)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:312)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:102)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:301)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
 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)
2019-09-17 
18:29:29.912[ERROR][query-#1577440%DPL_GRID%DplGridNodeName%][org.apache.ignite.Ignite]
 Critical system error detected. Will be handled accordingly to configured 
handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], 
failureCtx=FailureContext [type=CRITICAL_ERROR, err=java.lang.AssertionError]]
java.lang.AssertionError: null
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:918)
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:889)
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.p2pContext(GridCacheDeploymentManager.java:422)
 at 

[jira] [Updated] (IGNITE-12200) More informative assertion message at constructor of CachedDeploymentInfo (GridCacheDeploymentManager class)

2019-09-19 Thread Dmitriy Sorokin (Jira)


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

Dmitriy Sorokin updated IGNITE-12200:
-
Description: 
{code:java}
/**
 * @param sndId Sender.
 * @param ldrId Loader ID.
 * @param userVer User version.
 * @param depMode Deployment mode.
 * @param participants Participants.
 */
private CachedDeploymentInfo(UUID sndId, IgniteUuid ldrId, String userVer, 
DeploymentMode depMode,
Map participants) {
assert sndId.equals(ldrId.globalId()) || participants != null;

this.sndId = sndId;
this.ldrId = ldrId;
this.userVer = userVer;
this.depMode = depMode;
this.participants = participants == null || participants.isEmpty() ? null :
new ConcurrentLinkedHashMap<>(participants);
}
{code}
The code above may produce the following stacktrace, where AssertionError 
should contain more informative message for better root cause analysis:
{noformat}
2019-09-17 
18:29:29.890[ERROR][query-#1577440%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
 Failed to process message [senderId=4c071d12-325a-4bb1-a68d-cc910f636562, 
msg=GridCacheQueryRequest [id=4922, 
cacheName=com.sbt.limits.data.entity.LimitTemplateV1Entity_DPL_union-module, 
type=SCAN, fields=false, clause=null, clsName=null, keyValFilter=null, 
rdc=null, trans=null, pageSize=1024, incBackups=false, cancel=false, 
incMeta=false, all=false, keepBinary=true, 
subjId=4c071d12-325a-4bb1-a68d-cc910f636562, taskHash=0, part=-1, 
topVer=AffinityTopologyVersion [topVer=191, minorTopVer=0], 
super=GridCacheIdMessage [cacheId=-724666788]]]2019-09-17 
18:29:29.890[ERROR][query-#1577440%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
 Failed to process message [senderId=4c071d12-325a-4bb1-a68d-cc910f636562, 
msg=GridCacheQueryRequest [id=4922, 
cacheName=com.sbt.limits.data.entity.LimitTemplateV1Entity_DPL_union-module, 
type=SCAN, fields=false, clause=null, clsName=null, keyValFilter=null, 
rdc=null, trans=null, pageSize=1024, incBackups=false, cancel=false, 
incMeta=false, all=false, keepBinary=true, 
subjId=4c071d12-325a-4bb1-a68d-cc910f636562, taskHash=0, part=-1, 
topVer=AffinityTopologyVersion [topVer=191, minorTopVer=0], 
super=GridCacheIdMessage [cacheId=-724666788]]]java.lang.AssertionError: null
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:918)
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:889)
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.p2pContext(GridCacheDeploymentManager.java:422)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1547)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:582)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:386)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:312)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:102)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:301)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
 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)
2019-09-17 
18:29:29.912[ERROR][query-#1577440%DPL_GRID%DplGridNodeName%][org.apache.ignite.Ignite]
 Critical system error detected. Will be handled accordingly to configured 
handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], 
failureCtx=FailureContext [type=CRITICAL_ERROR, 
err=java.lang.AssertionError]]java.lang.AssertionError: null
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:918)
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:889)
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.p2pContext(GridCacheDeploymentManager.java:422)
 at 

[jira] [Updated] (IGNITE-12188) Metric CacheGroupMetrics.IndexBuildCountPartitionsLeft doesn't work correctly if there is more then one cache in cache group

2019-09-19 Thread Maxim Muzafarov (Jira)


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

Maxim Muzafarov updated IGNITE-12188:
-
Labels: IEP-35  (was: )

> Metric CacheGroupMetrics.IndexBuildCountPartitionsLeft doesn't work correctly 
> if there is more then one cache in cache group
> 
>
> Key: IGNITE-12188
> URL: https://issues.apache.org/jira/browse/IGNITE-12188
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.8
>Reporter: Aleksey Plekhanov
>Priority: Major
>  Labels: IEP-35
>
> Initial partitions counter is set to a total number of partitions for cache 
> group but decremented each time partition processed for each cache.
> Reproducer:
> {code:java}
> @Test
> public void testIndexRebuildMetrics() throws Exception {
> IgniteEx ignite = startGrid(new IgniteConfiguration()
> .setConsistentId("ignite")
> .setDataStorageConfiguration(new DataStorageConfiguration()
> .setDefaultDataRegionConfiguration(new 
> DataRegionConfiguration().setPersistenceEnabled(true)))
> .setCacheConfiguration(
> new CacheConfiguration Integer>("c1").setGroupName("grp").setIndexedTypes(Integer.class, 
> Integer.class),
> new CacheConfiguration Integer>("c2").setGroupName("grp").setIndexedTypes(Integer.class, 
> Integer.class)
> ));
> ignite.cluster().active(true);
> for (int i = 0; i < 10_000; i++)
> ignite.cache("c1").put(i, i);
> ignite.cluster().active(false);
> File dir = U.resolveWorkDirectory(U.defaultWorkDirectory(), 
> DFLT_STORE_DIR, false);
> U.delete(new File(dir, "ignite/cacheGroup-grp/index.bin"));
> ignite.cluster().active(true);
> doSleep(1_000L);
> 
> assertTrue(ignite.context().cache().cache("c1").context().group().metrics().getIndexBuildCountPartitionsLeft()
>  >= 0);
> }
> {code}



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


[jira] [Created] (IGNITE-12200) More informative assertion message at constructor of CachedDeploymentInfo (GridCacheDeploymentManager class)

2019-09-19 Thread Dmitriy Sorokin (Jira)
Dmitriy Sorokin created IGNITE-12200:


 Summary: More informative assertion message at constructor of 
CachedDeploymentInfo (GridCacheDeploymentManager class)
 Key: IGNITE-12200
 URL: https://issues.apache.org/jira/browse/IGNITE-12200
 Project: Ignite
  Issue Type: Improvement
Affects Versions: 2.7.5, 2.5
Reporter: Dmitriy Sorokin
Assignee: Dmitriy Sorokin


{code:java}
/**
 * @param sndId Sender.
 * @param ldrId Loader ID.
 * @param userVer User version.
 * @param depMode Deployment mode.
 * @param participants Participants.
 */
private CachedDeploymentInfo(UUID sndId, IgniteUuid ldrId, String userVer, 
DeploymentMode depMode,
Map participants) {
assert sndId.equals(ldrId.globalId()) || participants != null;

this.sndId = sndId;
this.ldrId = ldrId;
this.userVer = userVer;
this.depMode = depMode;
this.participants = participants == null || participants.isEmpty() ? null :
new ConcurrentLinkedHashMap<>(participants);
}
{code}
The code above may produce the following stacktrace, where AssertionError 
should contain more informative message for better root cause analysis:
{noformat}
2019-09-17 
18:29:29.890[ERROR][query-#1577440%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
 Failed to process message [senderId=4c071d12-325a-4bb1-a68d-cc910f636562, 
msg=GridCacheQueryRequest [id=4922, 
cacheName=com.sbt.limits.data.entity.LimitTemplateV1Entity_DPL_union-module, 
type=SCAN, fields=false, clause=null, clsName=null, keyValFilter=null, 
rdc=null, trans=null, pageSize=1024, incBackups=false, cancel=false, 
incMeta=false, all=false, keepBinary=true, 
subjId=4c071d12-325a-4bb1-a68d-cc910f636562, taskHash=0, part=-1, 
topVer=AffinityTopologyVersion [topVer=191, minorTopVer=0], 
super=GridCacheIdMessage [cacheId=-724666788]]]2019-09-17 
18:29:29.890[ERROR][query-#1577440%DPL_GRID%DplGridNodeName%][o.a.i.i.p.cache.GridCacheIoManager]
 Failed to process message [senderId=4c071d12-325a-4bb1-a68d-cc910f636562, 
msg=GridCacheQueryRequest [id=4922, 
cacheName=com.sbt.limits.data.entity.LimitTemplateV1Entity_DPL_union-module, 
type=SCAN, fields=false, clause=null, clsName=null, keyValFilter=null, 
rdc=null, trans=null, pageSize=1024, incBackups=false, cancel=false, 
incMeta=false, all=false, keepBinary=true, 
subjId=4c071d12-325a-4bb1-a68d-cc910f636562, taskHash=0, part=-1, 
topVer=AffinityTopologyVersion [topVer=191, minorTopVer=0], 
super=GridCacheIdMessage [cacheId=-724666788]]]java.lang.AssertionError: null 
at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:918)
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:889)
 at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.p2pContext(GridCacheDeploymentManager.java:422)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.unmarshall(GridCacheIoManager.java:1547)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:582)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:386)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:312)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:102)
 at 
org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:301)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
 at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
 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)2019-09-17 
18:29:29.912[ERROR][query-#1577440%DPL_GRID%DplGridNodeName%][org.apache.ignite.Ignite]
 Critical system error detected. Will be handled accordingly to configured 
handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], 
failureCtx=FailureContext [type=CRITICAL_ERROR, 
err=java.lang.AssertionError]]java.lang.AssertionError: null at 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager$CachedDeploymentInfo.(GridCacheDeploymentManager.java:918)
 at 

[jira] [Commented] (IGNITE-11094) Add SSL support for ignite zookeeper SPI

2019-09-19 Thread Pavel Kovalenko (Jira)


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

Pavel Kovalenko commented on IGNITE-11094:
--

[~SomeFire] Thank you for your work on the issue. Now changes are ready to 
merge. Please re-run Zookeeper suites to ensure that everything works well.

> Add SSL support for ignite zookeeper SPI
> 
>
> Key: IGNITE-11094
> URL: https://issues.apache.org/jira/browse/IGNITE-11094
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Ryabov Dmitrii
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 6.5h
>  Remaining Estimate: 0h
>
> ZK 3.5.4-beta is already supporting SSL [1]. We should add SSL support to ZK 
> server connections  if Zookeeper SPI used.
> 1. 
> https://cwiki.apache.org/confluence/display/ZOOKEEPER/ZooKeeper+SSL+User+Guide



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


[jira] [Commented] (IGNITE-12110) Bugs & tests fixes

2019-09-19 Thread Sergey Chugunov (Jira)


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

Sergey Chugunov commented on IGNITE-12110:
--

[~DmitriyGovorukhin],

I finished working on minor code improvements, it seems they don't break any 
existing tests. Could you please take a look at the change?

>  Bugs & tests fixes
> ---
>
> Key: IGNITE-12110
> URL: https://issues.apache.org/jira/browse/IGNITE-12110
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Fixed test:
> - *.testMassiveServersShutdown2
> - Fixed isStopped flag was't set during disconnect
> - Don't allow "NodeStoppingException" to fail checkpoint thread on stopping
> Test improvements:
> - Add page lock tracker and failure handler for all BPlustTree tests



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


[jira] [Updated] (IGNITE-12110) Bugs & tests fixes

2019-09-19 Thread Sergey Chugunov (Jira)


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

Sergey Chugunov updated IGNITE-12110:
-
Ignite Flags:   (was: Docs Required)

>  Bugs & tests fixes
> ---
>
> Key: IGNITE-12110
> URL: https://issues.apache.org/jira/browse/IGNITE-12110
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Fixed test:
> - *.testMassiveServersShutdown2
> - Fixed isStopped flag was't set during disconnect
> - Don't allow "NodeStoppingException" to fail checkpoint thread on stopping
> Test improvements:
> - Add page lock tracker and failure handler for all BPlustTree tests



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


[jira] [Commented] (IGNITE-12110) Bugs & tests fixes

2019-09-19 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12110:


{panel:title=Branch: [pull/6815/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4608200buildTypeId=IgniteTests24Java8_RunAll]

>  Bugs & tests fixes
> ---
>
> Key: IGNITE-12110
> URL: https://issues.apache.org/jira/browse/IGNITE-12110
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Govorukhin
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> Fixed test:
> - *.testMassiveServersShutdown2
> - Fixed isStopped flag was't set during disconnect
> - Don't allow "NodeStoppingException" to fail checkpoint thread on stopping
> Test improvements:
> - Add page lock tracker and failure handler for all BPlustTree tests



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


[jira] [Commented] (IGNITE-12179) Test and javadoc fixes

2019-09-19 Thread Ignite TC Bot (Jira)


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

Ignite TC Bot commented on IGNITE-12179:


{panel:title=Branch: [pull/6878/head] Base: [master] : No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *-- Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4608084buildTypeId=IgniteTests24Java8_RunAll]

> Test and javadoc fixes
> --
>
> Key: IGNITE-12179
> URL: https://issues.apache.org/jira/browse/IGNITE-12179
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Kalashnikov
>Assignee: Anton Kalashnikov
>Priority: Major
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> *.testTtlNoTx flaky failed on TC
> TcpCommunicationSpiFreezingClientTest failed
> TcpCommunicationSpiFaultyClientSslTest.testNotAcceptedConnection failed
> testCacheIdleVerifyPrintLostPartitions failed



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


[jira] [Comment Edited] (IGNITE-12014) Getting affinity for topology version earlier than affinity is calculated for system cache

2019-09-19 Thread PetrovMikhail (Jira)


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

PetrovMikhail edited comment on IGNITE-12014 at 9/19/19 11:19 AM:
--

[~ilyak], my attached to the ticket test is still fails on current master.  Can 
you take a look at it, please. 


was (Author: petrovmikhail):
[~ilyak], my attaches to the ticket test is still fails on current master.  Can 
you take a look at it, please. 

>  Getting affinity for topology version earlier than affinity is calculated 
> for system cache
> ---
>
> Key: IGNITE-12014
> URL: https://issues.apache.org/jira/browse/IGNITE-12014
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7.5
>Reporter: PetrovMikhail
>Priority: Major
> Attachments: JcacheExchangeAwaitTest.java
>
>
> The following exception was being caught occasionally on a big cluster (128 
> nodes) after it's activation and concurrent Ignite#reentrantLock() method 
> call from different nodes. (On 16 nodes cluster this exception was never 
> detected with no code change).
> It's attached a presumptive reproducer of that problem which stable fails 
> with the specified exception.
> {code:java}
> java.lang.IllegalStateException: Getting affinity for topology version 
> earlier than affinity is calculated [locNode=TcpDiscoveryNode 
> [id=cf397493-7528-46dc-bc5a-444f9d51, consistentId=127.0.0.1:47501, 
> addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47501], 
> discPort=47501, order=2, intOrder=2, lastExchangeTime=1564050248387, 
> loc=true, ver=2.8.0#20190725-sha1:, isClient=false], 
> grp=default-volatile-ds-group, topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=1], lastAffChangeTopVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=1], head=AffinityTopologyVersion [topVer=2, minorTopVer=2], 
> history=[AffinityTopologyVersion [topVer=2, minorTopVer=2]]]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:802)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:749)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.nodes(GridAffinityAssignmentCache.java:657)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.nodesByPartition(GridCacheAffinityManager.java:227)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByPartition(GridCacheAffinityManager.java:273)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:264)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:288)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.entryExx(GridDhtColocatedCache.java:161)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.entryEx(GridNearTxLocal.java:4470)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.enlistRead(GridNearTxLocal.java:2709)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.getAllAsync(GridNearTxLocal.java:2188)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache$4.op(GridDhtColocatedCache.java:204)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$AsyncOp.op(GridCacheAdapter.java:5644)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4561)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:202)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4842)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.repairableGet(GridCacheAdapter.java:4808)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1480)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:396)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:561)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:556)
>   at 
> 

[jira] [Reopened] (IGNITE-12014) Getting affinity for topology version earlier than affinity is calculated for system cache

2019-09-19 Thread PetrovMikhail (Jira)


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

PetrovMikhail reopened IGNITE-12014:


>  Getting affinity for topology version earlier than affinity is calculated 
> for system cache
> ---
>
> Key: IGNITE-12014
> URL: https://issues.apache.org/jira/browse/IGNITE-12014
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7.5
>Reporter: PetrovMikhail
>Priority: Major
> Attachments: JcacheExchangeAwaitTest.java
>
>
> The following exception was being caught occasionally on a big cluster (128 
> nodes) after it's activation and concurrent Ignite#reentrantLock() method 
> call from different nodes. (On 16 nodes cluster this exception was never 
> detected with no code change).
> It's attached a presumptive reproducer of that problem which stable fails 
> with the specified exception.
> {code:java}
> java.lang.IllegalStateException: Getting affinity for topology version 
> earlier than affinity is calculated [locNode=TcpDiscoveryNode 
> [id=cf397493-7528-46dc-bc5a-444f9d51, consistentId=127.0.0.1:47501, 
> addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47501], 
> discPort=47501, order=2, intOrder=2, lastExchangeTime=1564050248387, 
> loc=true, ver=2.8.0#20190725-sha1:, isClient=false], 
> grp=default-volatile-ds-group, topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=1], lastAffChangeTopVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=1], head=AffinityTopologyVersion [topVer=2, minorTopVer=2], 
> history=[AffinityTopologyVersion [topVer=2, minorTopVer=2]]]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:802)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:749)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.nodes(GridAffinityAssignmentCache.java:657)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.nodesByPartition(GridCacheAffinityManager.java:227)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByPartition(GridCacheAffinityManager.java:273)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:264)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:288)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.entryExx(GridDhtColocatedCache.java:161)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.entryEx(GridNearTxLocal.java:4470)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.enlistRead(GridNearTxLocal.java:2709)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.getAllAsync(GridNearTxLocal.java:2188)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache$4.op(GridDhtColocatedCache.java:204)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$AsyncOp.op(GridCacheAdapter.java:5644)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4561)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:202)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4842)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.repairableGet(GridCacheAdapter.java:4808)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1480)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:396)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:561)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:556)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1664)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.getAtomic(DataStructuresProcessor.java:556)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.reentrantLock(DataStructuresProcessor.java:1361)
>   at 
> 

[jira] [Assigned] (IGNITE-12044) [IEP-35] JmxExporterSpi displays histogram values incorrectly

2019-09-19 Thread Nikolay Izhikov (Jira)


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

Nikolay Izhikov reassigned IGNITE-12044:


Assignee: Nikolay Izhikov

> [IEP-35] JmxExporterSpi displays histogram values incorrectly
> -
>
> Key: IGNITE-12044
> URL: https://issues.apache.org/jira/browse/IGNITE-12044
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-35
> Fix For: 2.8
>
>
> {{JmxExporterSpi}} exposes histogram values incorrectly. It looks like:
> {noformat}
> durationHistogramlong[5]
> {noformat}
> I think exporter should register attribute for each histogram bucket. 
> Something like this:
> {noformat}
> durationHistogram.10 0
> durationHistogram.50 0
> durationHistogram.1000
> durationHistogram.2500
> durationHistogram.5000
> {noformat}



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


[jira] [Assigned] (IGNITE-12199) WAL record with data entries doesn't flushes on backups for transactional cache

2019-09-19 Thread Andrey Kuznetsov (Jira)


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

Andrey Kuznetsov reassigned IGNITE-12199:
-

Assignee: Andrey Gura  (was: Andrey Kuznetsov)

> WAL record with data entries doesn't flushes on backups for transactional 
> cache
> ---
>
> Key: IGNITE-12199
> URL: https://issues.apache.org/jira/browse/IGNITE-12199
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> WAL record with data entries doesn't flushes on backups for transactional 
> cache.
> This issue can be reproduced for example by 
> {{TxPartitionCounterStateConsistencyTest.testSingleThreadedUpdateOrder}} test 
> with disabled MMAP mode.
> Problem place in code is {{GridDistributedTxRemoteAdapter#commitIfLocked}} 
> where {{wal.log()}} doesn't assign returned file pointer to the {{ptr}} 
> variable.



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


[jira] [Assigned] (IGNITE-12199) WAL record with data entries doesn't flushes on backups for transactional cache

2019-09-19 Thread Andrey Kuznetsov (Jira)


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

Andrey Kuznetsov reassigned IGNITE-12199:
-

Assignee: Andrey Kuznetsov  (was: Andrey Gura)

> WAL record with data entries doesn't flushes on backups for transactional 
> cache
> ---
>
> Key: IGNITE-12199
> URL: https://issues.apache.org/jira/browse/IGNITE-12199
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> WAL record with data entries doesn't flushes on backups for transactional 
> cache.
> This issue can be reproduced for example by 
> {{TxPartitionCounterStateConsistencyTest.testSingleThreadedUpdateOrder}} test 
> with disabled MMAP mode.
> Problem place in code is {{GridDistributedTxRemoteAdapter#commitIfLocked}} 
> where {{wal.log()}} doesn't assign returned file pointer to the {{ptr}} 
> variable.



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


[jira] [Comment Edited] (IGNITE-12014) Getting affinity for topology version earlier than affinity is calculated for system cache

2019-09-19 Thread PetrovMikhail (Jira)


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

PetrovMikhail edited comment on IGNITE-12014 at 9/19/19 11:08 AM:
--

[~ilyak], my attaches to the ticket test is still fails on current master.  Can 
you take a look at it, please. 


was (Author: petrovmikhail):
[~ilyak], my test is still fails on current master.  Can you take a look at it, 
please. 

>  Getting affinity for topology version earlier than affinity is calculated 
> for system cache
> ---
>
> Key: IGNITE-12014
> URL: https://issues.apache.org/jira/browse/IGNITE-12014
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7.5
>Reporter: PetrovMikhail
>Priority: Major
> Attachments: JcacheExchangeAwaitTest.java
>
>
> The following exception was being caught occasionally on a big cluster (128 
> nodes) after it's activation and concurrent Ignite#reentrantLock() method 
> call from different nodes. (On 16 nodes cluster this exception was never 
> detected with no code change).
> It's attached a presumptive reproducer of that problem which stable fails 
> with the specified exception.
> {code:java}
> java.lang.IllegalStateException: Getting affinity for topology version 
> earlier than affinity is calculated [locNode=TcpDiscoveryNode 
> [id=cf397493-7528-46dc-bc5a-444f9d51, consistentId=127.0.0.1:47501, 
> addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47501], 
> discPort=47501, order=2, intOrder=2, lastExchangeTime=1564050248387, 
> loc=true, ver=2.8.0#20190725-sha1:, isClient=false], 
> grp=default-volatile-ds-group, topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=1], lastAffChangeTopVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=1], head=AffinityTopologyVersion [topVer=2, minorTopVer=2], 
> history=[AffinityTopologyVersion [topVer=2, minorTopVer=2]]]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:802)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:749)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.nodes(GridAffinityAssignmentCache.java:657)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.nodesByPartition(GridCacheAffinityManager.java:227)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByPartition(GridCacheAffinityManager.java:273)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:264)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:288)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.entryExx(GridDhtColocatedCache.java:161)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.entryEx(GridNearTxLocal.java:4470)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.enlistRead(GridNearTxLocal.java:2709)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.getAllAsync(GridNearTxLocal.java:2188)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache$4.op(GridDhtColocatedCache.java:204)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$AsyncOp.op(GridCacheAdapter.java:5644)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4561)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:202)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4842)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.repairableGet(GridCacheAdapter.java:4808)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1480)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:396)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:561)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:556)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1664)
>   at 

[jira] [Commented] (IGNITE-12014) Getting affinity for topology version earlier than affinity is calculated for system cache

2019-09-19 Thread PetrovMikhail (Jira)


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

PetrovMikhail commented on IGNITE-12014:


[~ilyak], my test is still fails on current master.  Can you take a look at it, 
please. 

>  Getting affinity for topology version earlier than affinity is calculated 
> for system cache
> ---
>
> Key: IGNITE-12014
> URL: https://issues.apache.org/jira/browse/IGNITE-12014
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.7.5
>Reporter: PetrovMikhail
>Priority: Major
> Attachments: JcacheExchangeAwaitTest.java
>
>
> The following exception was being caught occasionally on a big cluster (128 
> nodes) after it's activation and concurrent Ignite#reentrantLock() method 
> call from different nodes. (On 16 nodes cluster this exception was never 
> detected with no code change).
> It's attached a presumptive reproducer of that problem which stable fails 
> with the specified exception.
> {code:java}
> java.lang.IllegalStateException: Getting affinity for topology version 
> earlier than affinity is calculated [locNode=TcpDiscoveryNode 
> [id=cf397493-7528-46dc-bc5a-444f9d51, consistentId=127.0.0.1:47501, 
> addrs=ArrayList [127.0.0.1], sockAddrs=HashSet [/127.0.0.1:47501], 
> discPort=47501, order=2, intOrder=2, lastExchangeTime=1564050248387, 
> loc=true, ver=2.8.0#20190725-sha1:, isClient=false], 
> grp=default-volatile-ds-group, topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=1], lastAffChangeTopVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=1], head=AffinityTopologyVersion [topVer=2, minorTopVer=2], 
> history=[AffinityTopologyVersion [topVer=2, minorTopVer=2]]]
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:802)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.cachedAffinity(GridAffinityAssignmentCache.java:749)
>   at 
> org.apache.ignite.internal.processors.affinity.GridAffinityAssignmentCache.nodes(GridAffinityAssignmentCache.java:657)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.nodesByPartition(GridCacheAffinityManager.java:227)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByPartition(GridCacheAffinityManager.java:273)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:264)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAffinityManager.primaryByKey(GridCacheAffinityManager.java:288)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.entryExx(GridDhtColocatedCache.java:161)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.entryEx(GridNearTxLocal.java:4470)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.enlistRead(GridNearTxLocal.java:2709)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTxLocal.getAllAsync(GridNearTxLocal.java:2188)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache$4.op(GridDhtColocatedCache.java:204)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$AsyncOp.op(GridCacheAdapter.java:5644)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.asyncOp(GridCacheAdapter.java:4561)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.colocated.GridDhtColocatedCache.getAsync(GridDhtColocatedCache.java:202)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4842)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.repairableGet(GridCacheAdapter.java:4808)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1480)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.get(GridCacheProxyImpl.java:396)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:561)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor$4.applyx(DataStructuresProcessor.java:556)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.retryTopologySafe(DataStructuresProcessor.java:1664)
>   at 
> org.apache.ignite.internal.processors.datastructures.DataStructuresProcessor.getAtomic(DataStructuresProcessor.java:556)
>   at 
> 

[jira] [Updated] (IGNITE-12197) Incorrect way for getting value of persistent enabled in CacheGroupMetricsImpl

2019-09-19 Thread Andrey Gura (Jira)


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

Andrey Gura updated IGNITE-12197:
-
Labels: IEP-35  (was: )

> Incorrect way for getting value of persistent enabled in CacheGroupMetricsImpl
> --
>
> Key: IGNITE-12197
> URL: https://issues.apache.org/jira/browse/IGNITE-12197
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Andrey Gura
>Assignee: Andrey Gura
>Priority: Major
>  Labels: IEP-35
> Fix For: 2.8
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> IGNITE-12027 introduces possible bug  due to incorrect way for getting value 
> of persistent enabled property in {{CacheGroupMetricsImpl}}



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


[jira] [Created] (IGNITE-12199) WAL record with data entries doesn't flushes on backups for transactional cache

2019-09-19 Thread Andrey Gura (Jira)
Andrey Gura created IGNITE-12199:


 Summary: WAL record with data entries doesn't flushes on backups 
for transactional cache
 Key: IGNITE-12199
 URL: https://issues.apache.org/jira/browse/IGNITE-12199
 Project: Ignite
  Issue Type: Improvement
Reporter: Andrey Gura
Assignee: Andrey Gura
 Fix For: 2.8


WAL record with data entries doesn't flushes on backups for transactional cache.

This issue can be reproduced for example by 
{{TxPartitionCounterStateConsistencyTest.testSingleThreadedUpdateOrder}} test 
with disabled MMAP mode.

Problem place in code is {{GridDistributedTxRemoteAdapter#commitIfLocked}} 
where {{wal.log()}} doesn't assign returned file pointer to the {{ptr}} 
variable.




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


[jira] [Updated] (IGNITE-12165) Negative time in Transaction time dump

2019-09-19 Thread Denis Chudov (Jira)


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

Denis Chudov updated IGNITE-12165:
--
Ignite Flags:   (was: Docs Required,Release Notes Required)

> Negative time in Transaction time dump
> --
>
> Key: IGNITE-12165
> URL: https://issues.apache.org/jira/browse/IGNITE-12165
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Fix For: 2.8
>
>
> After implementing ticket IGNITE-12063 we have transaction dumps in the logs.
>  there are some issues with information in these dumps:
> {code:java}
> [11:53:36,154][INFO][snapshot-scheduler-restats-#69][GridNearTxLocal] 
> Transaction time dump [startTime=11:53:36.081, totalTime=65, systemTime=3, 
> userTime=62, cacheOperationsTime=-41943785508, rollbackTime=41943785512, 
> tx=GridNearTxLocal [mappings=IgniteTxMappingsImpl [], 
> nearLocallyMapped=false, colocatedLocallyMapped=false, needCheckBackup=null, 
> hasRemoteLocks=true, trackTimeout=false, systemTime=3953576, 
> systemStartTime=0, prepareStartTime=0, prepareTime=0, 
> commitOrRollbackStartTime=0, commitOrRollbackTime=41943785512318555, 
> txDumpsThrottling=org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$TxDumpsThrottling@760d8025,
>  lb=null, thread=snapshot-scheduler-restats-#69, 
> mappings=IgniteTxMappingsImpl [], super=GridDhtTxLocalAdapter 
> [nearOnOriginatingNode=false, nearNodes=KeySetView [], dhtNodes=KeySetView 
> [], explicitLock=false, super=IgniteTxLocalAdapter [completedBase=null, 
> sndTransformedVals=false, depEnabled=false, txState=IgniteTxStateImpl 
> [activeCacheIds=[-2100569601], recovery=false, txMap=HashSet [IgniteTxEntry 
> [key=KeyCacheObjectImpl [part=2, val=SnapshotScheduleKey [id=_SCHEDULES_], 
> hasValBytes=true], cacheId=-2100569601, txKey=IgniteTxKey 
> [key=KeyCacheObjectImpl [part=2, val=SnapshotScheduleKey [id=_SCHEDULES_], 
> hasValBytes=true], cacheId=-2100569601], val=[op=READ, val=null], 
> prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=null, filtersPassed=false, 
> filtersSet=true, entry=GridCacheMapEntry [key=KeyCacheObjectImpl [part=2, 
> val=SnapshotScheduleKey [id=_SCHEDULES_], hasValBytes=true], val=null, 
> ver=GridCacheVersion [topVer=0, order=0, nodeOrder=0], hash=886348002, 
> extras=null, flags=0]GridDistributedCacheEntry 
> [super=]GridDhtDetachedCacheEntry [super=], prepared=0, locked=true, 
> nodeId=1adbae78-40fe-480d-803d-4d498919ae63, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null, 
> xidVer=GridCacheVersion [topVer=179672005, order=1568192005565, 
> nodeOrder=1, super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=179672005, order=1568192005565, nodeOrder=1], writeVer=null, 
> implicit=false, loc=true, threadId=125, startTime=1568192016081, 
> nodeId=9e00ae45-4084-4f29-949f-c19c933f4299, startVer=GridCacheVersion 
> [topVer=179672005, order=1568192005565, nodeOrder=1], endVer=null, 
> isolation=REPEATABLE_READ, concurrency=PESSIMISTIC, timeout=0, 
> sysInvalidate=false, sys=true, plc=5, commitVer=null, finalizing=NONE, 
> invalidParts=null, state=ROLLED_BACK, timedOut=false, 
> topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1], duration=60ms, 
> onePhaseCommit=false], size=1
> {code}
> For example:
>  # Negative time: cacheOperationsTime=-41943785508,
>  # Huge times: rollbackTime=41943785512



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


[jira] [Updated] (IGNITE-12165) Negative time in Transaction time dump

2019-09-19 Thread Denis Chudov (Jira)


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

Denis Chudov updated IGNITE-12165:
--
Fix Version/s: 2.8

> Negative time in Transaction time dump
> --
>
> Key: IGNITE-12165
> URL: https://issues.apache.org/jira/browse/IGNITE-12165
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Chudov
>Assignee: Denis Chudov
>Priority: Major
> Fix For: 2.8
>
>
> After implementing ticket IGNITE-12063 we have transaction dumps in the logs.
>  there are some issues with information in these dumps:
> {code:java}
> [11:53:36,154][INFO][snapshot-scheduler-restats-#69][GridNearTxLocal] 
> Transaction time dump [startTime=11:53:36.081, totalTime=65, systemTime=3, 
> userTime=62, cacheOperationsTime=-41943785508, rollbackTime=41943785512, 
> tx=GridNearTxLocal [mappings=IgniteTxMappingsImpl [], 
> nearLocallyMapped=false, colocatedLocallyMapped=false, needCheckBackup=null, 
> hasRemoteLocks=true, trackTimeout=false, systemTime=3953576, 
> systemStartTime=0, prepareStartTime=0, prepareTime=0, 
> commitOrRollbackStartTime=0, commitOrRollbackTime=41943785512318555, 
> txDumpsThrottling=org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$TxDumpsThrottling@760d8025,
>  lb=null, thread=snapshot-scheduler-restats-#69, 
> mappings=IgniteTxMappingsImpl [], super=GridDhtTxLocalAdapter 
> [nearOnOriginatingNode=false, nearNodes=KeySetView [], dhtNodes=KeySetView 
> [], explicitLock=false, super=IgniteTxLocalAdapter [completedBase=null, 
> sndTransformedVals=false, depEnabled=false, txState=IgniteTxStateImpl 
> [activeCacheIds=[-2100569601], recovery=false, txMap=HashSet [IgniteTxEntry 
> [key=KeyCacheObjectImpl [part=2, val=SnapshotScheduleKey [id=_SCHEDULES_], 
> hasValBytes=true], cacheId=-2100569601, txKey=IgniteTxKey 
> [key=KeyCacheObjectImpl [part=2, val=SnapshotScheduleKey [id=_SCHEDULES_], 
> hasValBytes=true], cacheId=-2100569601], val=[op=READ, val=null], 
> prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=null, filtersPassed=false, 
> filtersSet=true, entry=GridCacheMapEntry [key=KeyCacheObjectImpl [part=2, 
> val=SnapshotScheduleKey [id=_SCHEDULES_], hasValBytes=true], val=null, 
> ver=GridCacheVersion [topVer=0, order=0, nodeOrder=0], hash=886348002, 
> extras=null, flags=0]GridDistributedCacheEntry 
> [super=]GridDhtDetachedCacheEntry [super=], prepared=0, locked=true, 
> nodeId=1adbae78-40fe-480d-803d-4d498919ae63, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null, 
> xidVer=GridCacheVersion [topVer=179672005, order=1568192005565, 
> nodeOrder=1, super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=179672005, order=1568192005565, nodeOrder=1], writeVer=null, 
> implicit=false, loc=true, threadId=125, startTime=1568192016081, 
> nodeId=9e00ae45-4084-4f29-949f-c19c933f4299, startVer=GridCacheVersion 
> [topVer=179672005, order=1568192005565, nodeOrder=1], endVer=null, 
> isolation=REPEATABLE_READ, concurrency=PESSIMISTIC, timeout=0, 
> sysInvalidate=false, sys=true, plc=5, commitVer=null, finalizing=NONE, 
> invalidParts=null, state=ROLLED_BACK, timedOut=false, 
> topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1], duration=60ms, 
> onePhaseCommit=false], size=1
> {code}
> For example:
>  # Negative time: cacheOperationsTime=-41943785508,
>  # Huge times: rollbackTime=41943785512



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


[jira] [Assigned] (IGNITE-12193) [Phase-1] Rebalancing cache group keys metric counters

2019-09-19 Thread Surkov Aleksandr (Jira)


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

Surkov Aleksandr reassigned IGNITE-12193:
-

Assignee: Surkov Aleksandr

> [Phase-1] Rebalancing cache group keys metric counters
> --
>
> Key: IGNITE-12193
> URL: https://issues.apache.org/jira/browse/IGNITE-12193
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Maxim Muzafarov
>Assignee: Surkov Aleksandr
>Priority: Major
>
> Implement metrics counters related to the cache group:
> * rebalancingPartitionsLeft long metric
> * rebalancingReceivedKeys long metric
> * rebalancingReceivedBytes long metric
> * rebalancingStartTime long metric
> * rebalancingFinishTime long metric



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