[jira] [Commented] (IGNITE-5241) Redis hash table support

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-5241:
--

Added HDEL and HEXISTS commands.

> Redis hash table support
> 
>
> Key: IGNITE-5241
> URL: https://issues.apache.org/jira/browse/IGNITE-5241
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>




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

[jira] [Comment Edited] (IGNITE-5369) Add possibility to generate alias for primary key in WebConsole

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko edited comment on IGNITE-5369 at 7/11/17 4:41 AM:


Added possibility to configure aliases for key field and value field. Configure 
"Key field name" and "Value Field Name" for specified aliases and use that 
aliases in queries in query page.


was (Author: vsisko):
Added possibility to configure aliases for key field and value field.

> Add possibility to generate alias for primary key in WebConsole
> ---
>
> Key: IGNITE-5369
> URL: https://issues.apache.org/jira/browse/IGNITE-5369
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Evgenii Zhuravlev
>Assignee: Pavel Konstantinov
> Fix For: 2.1
>
>
> Add field with alias name for primary key, that wiil be used in 
> QueryEntity.setKeyFieldName
> Automatically assign key field alias on import of model.



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

[jira] [Assigned] (IGNITE-5726) Duplicate dependencies in POM

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-5726:
-

Assignee: Andrey Novikov

> Duplicate dependencies in POM
> -
>
> Key: IGNITE-5726
> URL: https://issues.apache.org/jira/browse/IGNITE-5726
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Andrey Novikov
> Attachments: screenshot-1.png
>
>
> Import models from database
> Look at POM on Summary page



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

[jira] [Updated] (IGNITE-5351) Document K-means clustering algorithm

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5351:

Component/s: documentation

> Document K-means clustering algorithm
> -
>
> Key: IGNITE-5351
> URL: https://issues.apache.org/jira/browse/IGNITE-5351
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation, ml
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.1
>
>
> Someone should document K-means algorithm under the ML section on readme.io 
> pasting code snippets. I'll help to create new pages and rework the content 
> if needed.
> Plus, it makes sense to add an example to the source code and refer to it 
> from the readme.io documentation.



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

[jira] [Updated] (IGNITE-5350) Document ordinary least squares (OLS) linear regression

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5350:

Component/s: documentation

> Document ordinary least squares (OLS) linear regression
> ---
>
> Key: IGNITE-5350
> URL: https://issues.apache.org/jira/browse/IGNITE-5350
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation, ml
>Affects Versions: 2.1
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.1
>
>
> Someone should document OLS algorithm under the ML section on readme.io 
> pasting code snippets. I'll help to create new pages and rework the content 
> if needed.
> Plus, it makes sense to add an example to the source code and refer to it 
> from the readme.io documentation.



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

[jira] [Closed] (IGNITE-5710) Web console: H2 version in pom file depends from Ignite version

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-5710.
--

> Web console: H2 version in pom file depends from Ignite version
> ---
>
> Key: IGNITE-5710
> URL: https://issues.apache.org/jira/browse/IGNITE-5710
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.1
>
>
> 1.4.191 for 1.x version and 1.4.195 for 2.x version.



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

[jira] [Created] (IGNITE-5726) Duplicate dependencies in POM

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-5726:
--

 Summary: Duplicate dependencies in POM
 Key: IGNITE-5726
 URL: https://issues.apache.org/jira/browse/IGNITE-5726
 Project: Ignite
  Issue Type: Bug
Reporter: Pavel Konstantinov


Import models from database
Look at POM on Summary page




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

[jira] [Commented] (IGNITE-5726) Duplicate dependencies in POM

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-5726:


!screenshot-1.png!

> Duplicate dependencies in POM
> -
>
> Key: IGNITE-5726
> URL: https://issues.apache.org/jira/browse/IGNITE-5726
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
> Attachments: screenshot-1.png
>
>
> Import models from database
> Look at POM on Summary page



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

[jira] [Commented] (IGNITE-5710) Web console: H2 version in pom file depends from Ignite version

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-5710:


Tested.

> Web console: H2 version in pom file depends from Ignite version
> ---
>
> Key: IGNITE-5710
> URL: https://issues.apache.org/jira/browse/IGNITE-5710
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.1
>
>
> 1.4.191 for 1.x version and 1.4.195 for 2.x version.



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

[jira] [Assigned] (IGNITE-5351) Document K-means clustering algorithm

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-5351:
---

Assignee: Prachi Garg  (was: Denis Magda)

> Document K-means clustering algorithm
> -
>
> Key: IGNITE-5351
> URL: https://issues.apache.org/jira/browse/IGNITE-5351
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.1
>
>
> Someone should document K-means algorithm under the ML section on readme.io 
> pasting code snippets. I'll help to create new pages and rework the content 
> if needed.
> Plus, it makes sense to add an example to the source code and refer to it 
> from the readme.io documentation.



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

[jira] [Commented] (IGNITE-5351) Document K-means clustering algorithm

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5351:
-

Done from my side. Thanks, Artem!

[~pgarg], please do the final review and close the ticket:
https://apacheignite.readme.io/v2.1/docs/k-means-clustering

> Document K-means clustering algorithm
> -
>
> Key: IGNITE-5351
> URL: https://issues.apache.org/jira/browse/IGNITE-5351
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.1
>
>
> Someone should document K-means algorithm under the ML section on readme.io 
> pasting code snippets. I'll help to create new pages and rework the content 
> if needed.
> Plus, it makes sense to add an example to the source code and refer to it 
> from the readme.io documentation.



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

[jira] [Assigned] (IGNITE-5350) Document ordinary least squares (OLS) linear regression

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-5350:
---

Assignee: Prachi Garg  (was: Denis Magda)

> Document ordinary least squares (OLS) linear regression
> ---
>
> Key: IGNITE-5350
> URL: https://issues.apache.org/jira/browse/IGNITE-5350
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Affects Versions: 2.1
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.1
>
>
> Someone should document OLS algorithm under the ML section on readme.io 
> pasting code snippets. I'll help to create new pages and rework the content 
> if needed.
> Plus, it makes sense to add an example to the source code and refer to it 
> from the readme.io documentation.



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

[jira] [Commented] (IGNITE-5350) Document ordinary least squares (OLS) linear regression

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5350:
-

Reviewed and did minor cosmetic changes. [~pgarg], please do the final review 
and close the ticket:
https://apacheignite.readme.io/v2.1/docs/ols-multiple-linear-regression

> Document ordinary least squares (OLS) linear regression
> ---
>
> Key: IGNITE-5350
> URL: https://issues.apache.org/jira/browse/IGNITE-5350
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Affects Versions: 2.1
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.1
>
>
> Someone should document OLS algorithm under the ML section on readme.io 
> pasting code snippets. I'll help to create new pages and rework the content 
> if needed.
> Plus, it makes sense to add an example to the source code and refer to it 
> from the readme.io documentation.



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

[jira] [Assigned] (IGNITE-5352) Improve ML main page documentation

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-5352:
---

Assignee: Nikita Ivanov  (was: Yury Babak)

> Improve ML main page documentation
> --
>
> Key: IGNITE-5352
> URL: https://issues.apache.org/jira/browse/IGNITE-5352
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Nikita Ivanov
> Fix For: 2.1
>
>
> [~chief], please work with [~nivanov] to enhance the existing ML 
> documentation we have on the main page:
> https://apacheignite.readme.io/v2.1/docs/machine-learning
> Here is the following should be listed:
> * main goals of the lib.
> * how it's implemented and why it's better than others.
> * use cases.
> * etc.?



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

[jira] [Commented] (IGNITE-5157) Document Page Memory Defragmentation

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-5157:
-

Done. [~pgarg], please review and close the ticket:
https://apacheignite.readme.io/v2.1/docs/memory-defragmentation

> Document Page Memory Defragmentation
> 
>
> Key: IGNITE-5157
> URL: https://issues.apache.org/jira/browse/IGNITE-5157
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.1
>
>
> Document how the durable memory deals with memory fragmentation.



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

[jira] [Assigned] (IGNITE-5157) Document Page Memory Defragmentation

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-5157:
---

Assignee: Prachi Garg  (was: Denis Magda)

> Document Page Memory Defragmentation
> 
>
> Key: IGNITE-5157
> URL: https://issues.apache.org/jira/browse/IGNITE-5157
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.1
>
>
> Document how the durable memory deals with memory fragmentation.



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

[jira] [Assigned] (IGNITE-5607) HttpSessionBindingListener is not supported for clustered web session

[Yuci Gou (JIRA)]

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

Yuci Gou reassigned IGNITE-5607:


Assignee: Yuci Gou

> HttpSessionBindingListener is not supported for clustered web session
> -
>
> Key: IGNITE-5607
> URL: https://issues.apache.org/jira/browse/IGNITE-5607
> Project: Ignite
>  Issue Type: Bug
>  Components: websession
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: Yuci Gou
>
> Ignite's implementation of {{HttpSession}} ignores values implementing 
> {{HttpSessionBindingListener}}.
> {{WebSession#setAttribute}} and {{WebSession#removeAttribute}} should be 
> modified accordingly.



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

[jira] [Assigned] (IGNITE-5538) NPE (PersistentStoreExample)

[Pavel Kovalenko (JIRA)]

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

Pavel Kovalenko reassigned IGNITE-5538:
---

Assignee: Alexey Goncharuk  (was: Pavel Kovalenko)

> NPE (PersistentStoreExample)
> 
>
> Key: IGNITE-5538
> URL: https://issues.apache.org/jira/browse/IGNITE-5538
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Ilya Suntsov
>Assignee: Alexey Goncharuk
> Fix For: 2.1
>
> Attachments: PersistentStoreExampleNode.txt, 
> PersistentStoreExample.txt
>
>
> Steps to reproduce:
> 1. Start *PersistentStoreExampleNodeStartup*
> 2. Start *PersistentStoreExample* (UPLOAD=true)
> Result:
> 1. Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=7.1GB]
> 2. Started preloading
> 3. On ExampleNode got exception:
> {noformat}
> [2017-06-19 13:11:28,545][WARN 
> ][grid-nio-worker-tcp-comm-3-#20%null%][TcpCommunicationSpi] Failed to 
> process selector key (will close): GridSelectorNioSessionImpl 
> [worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=3, 
> bytesRcvd=2052, bytesSent=252, bytesRcvd0=228, bytesSent0=28, select=true, 
> super=GridWorker [name=grid-nio-worker-tcp-comm-3, igniteInstanceName=null, 
> finished=false, hashCode=1279096191, interrupted=false, 
> runner=grid-nio-worker-tcp-comm-3-#20%null%]]], 
> writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768], 
> readBuf=java.nio.DirectByteBuffer[pos=4 lim=186 cap=32768], 
> inRecovery=GridNioRecoveryDescriptor [acked=103, resendCnt=0, rcvCnt=104, 
> sentCnt=103, reserved=true, lastAck=96, nodeLeft=false, node=TcpDiscoveryNode 
> [id=be66eae2-3986-4772-b02b-bf2813370a15, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 172.25.4.115, 172.25.4.116, 2001:db8:85a3:0:0:8a2e:370:7334], 
> sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /172.25.4.115:0, 
> /172.25.4.116:0, /2001:db8:85a3:0:0:8a2e:370:7334:0], discPort=0, order=2, 
> intOrder=2, lastExchangeTime=1497867042970, loc=false, 
> ver=2.1.1#20170618-sha1:09ce29e0, isClient=true], connected=true, 
> connectCnt=1, queueLimit=4096, reserveCnt=35, pairedConnections=false], 
> outRecovery=GridNioRecoveryDescriptor [acked=103, resendCnt=0, rcvCnt=104, 
> sentCnt=103, reserved=true, lastAck=96, nodeLeft=false, node=TcpDiscoveryNode 
> [id=be66eae2-3986-4772-b02b-bf2813370a15, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 172.25.4.115, 172.25.4.116, 2001:db8:85a3:0:0:8a2e:370:7334], 
> sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /172.25.4.115:0, 
> /172.25.4.116:0, /2001:db8:85a3:0:0:8a2e:370:7334:0], discPort=0, order=2, 
> intOrder=2, lastExchangeTime=1497867042970, loc=false, 
> ver=2.1.1#20170618-sha1:09ce29e0, isClient=true], connected=true, 
> connectCnt=1, queueLimit=4096, reserveCnt=35, pairedConnections=false], 
> super=GridNioSessionImpl [locAddr=/0:0:0:0:0:0:0:1:47100, 
> rmtAddr=/0:0:0:0:0:0:0:1:60813, createTime=1497867087529, closeTime=0, 
> bytesSent=28, bytesRcvd=228, bytesSent0=28, bytesRcvd0=228, 
> sndSchedTime=1497867087529, lastSndTime=1497867087529, 
> lastRcvTime=1497867087541, readsPaused=false, 
> filterChain=FilterChain[filters=[GridNioCodecFilter 
> [parser=o.a.i.i.util.nio.GridDirectParser@7a94a8f6, directMode=true], 
> GridConnectionBytesVerifyFilter], accepted=true]]
> [2017-06-19 
> 13:11:28,545][ERROR][grid-nio-worker-tcp-comm-3-#20%null%][TcpCommunicationSpi]
>  Closing NIO session because of unhandled exception.
> class org.apache.ignite.internal.util.nio.GridNioException: null
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2199)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1968)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1669)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.managers.communication.GridIoMessageFactory.create(GridIoMessageFactory.java:879)
>   at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$9.create(TcpCommunicationSpi.java:2134)
>   at 
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1154)
>   at 
> org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:311)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:261)
>   at 
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:90)
>   at 
> 

[jira] [Commented] (IGNITE-5682) GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-5682:


Test fails on Stopping grid 3: stopGrid(3);
4 nodes, 3 single messages were sent to crd. 

{noformat}
init() from crd: 
[rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest0] 
remaining: nodes [
B43d9218-07d8-4028-bc69-4b582af2,
22687770-013b-4987-a4a5-80394891, 
86667a24-ea4d-4b74-a375-f783f7a4]

sendLocalPartitions(): from nodeid [ec705e77-fc89-4faa-a432-6aee56c0]; 
instance=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest2 
sent single map
MMM: GridDhtPartitionsSingleMessage [parts={1544803905=GridDhtPartitionMap 
[moving=0, top=AffinityTopologyVersion [topVer=10, minorTopVer=0], 
updateSeq=468, size=507], -2100569601=GridDhtPartitionMap [moving=0, 
top=AffinityTopologyVersion [topVer=10, minorTopVer=0], updateSeq=164, 
size=100]}, partCntrs={1544803905={}, -2100569601={}}, partHistCntrs=null, 
err=null, client=false, compress=true, super=GridDhtPartitionsAbstractMessage 
[exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=10, 
minorTopVer=0], nodeId=4196a84b, evt=NODE_LEFT], lastVer=GridCacheVersion 
[topVer=0, order=1499710025573, nodeOrder=0], flags=1, super=GridCacheMessage 
[msgId=237, depInfo=null, err=null, skipPrepare=false]]]


sendLocalPartitions(): from nodeid [ec705e77-fc89-4faa-a432-6aee56c0]; 
instance=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest1 
sent single map
MMM: GridDhtPartitionsSingleMessage [parts={1544803905=GridDhtPartitionMap 
[moving=0, top=AffinityTopologyVersion [topVer=10, minorTopVer=0], 
updateSeq=468, size=530], -2100569601=GridDhtPartitionMap [moving=0, 
top=AffinityTopologyVersion [topVer=10, minorTopVer=0], updateSeq=171, 
size=100]}, partCntrs={1544803905={}, -2100569601={}}, partHistCntrs=null, 
err=null, client=false, compress=true, super=GridDhtPartitionsAbstractMessage 
[exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=10, 
minorTopVer=0], nodeId=4196a84b, evt=NODE_LEFT], lastVer=GridCacheVersion 
[topVer=0, order=1499710023815, nodeOrder=0], flags=1, super=GridCacheMessage 
[msgId=238, depInfo=null, err=null, skipPrepare=false]]]

sendLocalPartitions(): from nodeid [ec705e77-fc89-4faa-a432-6aee56c0]; 
instance=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest4 
sent single map
MMM: GridDhtPartitionsSingleMessage [parts={1544803905=GridDhtPartitionMap 
[moving=0, top=AffinityTopologyVersion [topVer=10, minorTopVer=0], 
updateSeq=468, size=525], -2100569601=GridDhtPartitionMap [moving=0, 
top=AffinityTopologyVersion [topVer=10, minorTopVer=0], updateSeq=118, 
size=100]}, partCntrs={1544803905={}, -2100569601={}}, partHistCntrs=null, 
err=null, client=false, compress=true, super=GridDhtPartitionsAbstractMessage 
[exchId=GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=10, 
minorTopVer=0], nodeId=4196a84b, evt=NODE_LEFT], lastVer=GridCacheVersion 
[topVer=0, order=1499710051946, nodeOrder=0], flags=1, super=GridCacheMessage 
[msgId=239, depInfo=null, err=null, skipPrepare=false]]]


[2017-07-10 21:07:49,708][INFO 
][test-runner-#1%rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest%][root]
 Topology version mismatch 
[node=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest1, 
exchVer=AffinityTopologyVersion [topVer=9, minorTopVer=3], 
topVer=AffinityTopologyVersion [topVer=10, minorTopVer=0]]
 
MMM: GridDhtPartitionsFullMessage [parts={1544803905=GridDhtPartitionFullMap 
[nodeId=ec705e77-fc89-4faa-a432-6aee56c0, nodeOrder=1, updateSeq=117, 
size=4], -2100569601=GridDhtPartitionFullMap 
[nodeId=ec705e77-fc89-4faa-a432-6aee56c0, nodeOrder=1, updateSeq=108, 
size=4]}, partCntrs=null, partHistSuppliers=null, partsToReload=null, 
topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], errs=null, 
compress=true, partCnt=2, super=GridDhtPartitionsAbstractMessage [exchId=null, 
lastVer=null, flags=1, super=GridCacheMessage [msgId=272, depInfo=null, 
err=null, skipPrepare=false]]]
MMM: GridDhtPartitionsFullMessage [parts={1544803905=GridDhtPartitionFullMap 
[nodeId=ec705e77-fc89-4faa-a432-6aee56c0, nodeOrder=1, updateSeq=117, 
size=4], -2100569601=GridDhtPartitionFullMap 
[nodeId=ec705e77-fc89-4faa-a432-6aee56c0, nodeOrder=1, updateSeq=108, 
size=4]}, partCntrs=null, partHistSuppliers=null, partsToReload=null, 
topVer=AffinityTopologyVersion [topVer=-1, minorTopVer=0], errs=null, 
compress=true, partCnt=2, super=GridDhtPartitionsAbstractMessage [exchId=null, 
lastVer=null, flags=1, super=GridCacheMessage [msgId=272, depInfo=null, 
err=null, skipPrepare=false]]]
MMM: GridDhtPartitionsFullMessage [parts={1544803905=GridDhtPartitionFullMap 
[nodeId=ec705e77-fc89-4faa-a432-6aee56c0, nodeOrder=1, updateSeq=117, 
size=4], 

[jira] [Commented] (IGNITE-5567) Make benchmark Ignite.reentrantLock vs IgniteCache.lock

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov commented on IGNITE-5567:
-

[~avinogradov]
Fixed.

> Make benchmark Ignite.reentrantLock vs IgniteCache.lock
> ---
>
> Key: IGNITE-5567
> URL: https://issues.apache.org/jira/browse/IGNITE-5567
> Project: Ignite
>  Issue Type: Sub-task
>  Components: data structures
>Reporter: Alexander Menshikov
>Assignee: Alexander Menshikov
> Fix For: 2.3
>
>
> Ignite.reentrantLock slower than IgniteCache.lock. First of all, we must 
> create a benchmark for agreeing about use-case which we want to test.



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

[jira] [Updated] (IGNITE-5682) GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5682:
---
Attachment: ignite-5682.dump.txt

> GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails
> -
>
> Key: IGNITE-5682
> URL: https://issues.apache.org/jira/browse/IGNITE-5682
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
>  Labels: test-fail
> Fix For: 2.1
>
> Attachments: ignite-5682.dump.txt
>
>
> This appears to be a regression introduced during persistent store migration. 
> {code}
> class org.apache.ignite.IgniteException: Timeout of waiting for topology map 
> update 
> [igniteInstanceName=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest1,
>  cache=default, cacheId=1544803905, topVer=AffinityTopologyVersion 
> [topVer=10, minorTopVer=0], p=0, readVer=AffinityTopologyVersion [topVer=10, 
> minorTopVer=0], locNode=TcpDiscoveryNode 
> [id=c53cc66c-05ea-4441-825c-23d99ef1, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2, 
> lastExchangeTime=1499156862204, loc=true, ver=2.1.0#19700101-sha1:, 
> isClient=false]]
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:698)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:532)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:517)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.test(GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.java:154)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Commented] (IGNITE-5515) GridCacheReplicatedNodeRestartSelfTest hangs

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-5515:


Suite is locally passing, PR https://github.com/apache/ignite/pull/2276 was 
created to re-enable test

> GridCacheReplicatedNodeRestartSelfTest hangs
> 
>
> Key: IGNITE-5515
> URL: https://issues.apache.org/jira/browse/IGNITE-5515
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
>  Labels: test-fail
> Fix For: 2.2
>
>
> Sample log: 
> http://ci.ignite.apache.org/viewLog.html?buildId=06=buildResultsDiv=Ignite20Tests_IgniteDataGridRestarts
> Most probably this is the trigger:
> {code}
> [23:26:52]W:   [org.apache.ignite:ignite-core] [2017-06-15 
> 20:26:52,349][ERROR][sys-stripe-22-#191189%replicated.GridCacheReplicatedNodeRestartSelfTest3%][GridNearTxLocal]
>  Commit failed.
> [23:26:52]W:   [org.apache.ignite:ignite-core] class 
> org.apache.ignite.internal.transactions.IgniteTxHeuristicCheckedException: 
> Commit produced a runtime exception (all transaction entries will be 
> invalidated): 
> GridDhtTxRemote[id=e8aef6dac51--067f-cbd2--0002, 
> concurrency=PESSIMISTIC, isolation=REPEATABLE_READ, state=COMMITTING, 
> invalidate=false, rollbackOnly=false, 
> nodeId=64eba958-5741-4cee-ba4b-7ac75d81, duration=0]
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitIfLocked(GridDistributedTxRemoteAdapter.java:721)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.GridDistributedTxRemoteAdapter.commitRemoteTx(GridDistributedTxRemoteAdapter.java:790)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:1208)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processDhtTxFinishRequest(IgniteTxHandler.java:1116)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$600(IgniteTxHandler.java:95)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:177)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$7.apply(IgniteTxHandler.java:175)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1032)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:553)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:371)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:301)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:104)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:291)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1554)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1182)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:124)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1095)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:483)
> [23:26:52]W:   [org.apache.ignite:ignite-core]at 
> java.lang.Thread.run(Thread.java:745)
> [23:26:52]W:   

[jira] [Commented] (IGNITE-2190) ScanQuery without a filter triggers object's deserialization on the server side

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-2190:
--

[~NIzhikov], 

Looks good. See my minor comment at review.
BTW, did you check TC failures?

> ScanQuery without a filter triggers object's deserialization on the server 
> side
> ---
>
> Key: IGNITE-2190
> URL: https://issues.apache.org/jira/browse/IGNITE-2190
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4, 2.0
>Reporter: Denis Magda
>Assignee: Nikolay Izhikov
>Priority: Critical
>  Labels: newbie
> Fix For: 2.2
>
> Attachments: ScanQueryBug.java
>
>
> The issue is reproduced on version 1.4 where legacy PortableMarshaller is 
> used. However, I'm quiet sure that the issue happens when BinaryMarshaller is 
> used as well in 1.5.
> 1) Start a server using ignite.sh/bat
> 2) Create a simple app, that uses binary or portable marshaller, creates a 
> cache dynamically and executes a ScanQuery like below
> {{int size=employees1.query(new ScanQuery()).getAll().size();}}
> 3) As you see the query doesn't use any filters. However on the server side 
> some filter is still being checked 
> {{org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$5.checkPredicate(GridCacheQueryManager.java:963)}}
>  which makes the server to deserialize a value.
> According to the stack trace there is some internal filter that triggered 
> checkPredicate function - 
> filter=o.a.i.i.processors.cache.IgniteCacheProxy$1@3224ff7b.
> {noformat}
> [11:05:22,725][SEVERE][ignite-#25%sys-null%][GridCacheDistributedQueryManager]
>   Failed to run query [qry=GridCacheQueryInfo [loc=false, 
> trans=null, rdc=null, qry=GridCacheQueryAdapter [type=SCAN, clsName=null, 
> clause=null, filter=o.a.i.i.processors.cache.IgniteCacheProxy$1@3224ff7b, 
> part=null, incMeta=false, metrics=null, pageSize=1024, timeout=0, 
> keepAll=false, incBackups=false, dedup=false, prj=null, keepPortable=false, 
> subjId=c6aeb542-1693-4b5f-89db-96db50e3435f, taskHash=0], locFut=null, 
> sndId=c6aeb542-1693-4b5f-89db-96db50e3435f, reqId=14, incMeta=false, 
> all=false], node=209c237a-9e33-4d05-abe4-bbc14f93c439]
> class org.apache.ignite.IgniteCheckedException: 
> **.SubMessageB
> at org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:6979)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$CachedResult.iterator(GridCacheQueryManager.java:2784)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.runQuery(GridCacheQueryManager.java:1376)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryRequest(GridCacheDistributedQueryManager.java:226)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$2.apply(GridCacheDistributedQueryManager.java:105)
> at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$2.apply(GridCacheDistributedQueryManager.java:103)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:580)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:280)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:198)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:77)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:160)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: 
> **.SubMessageB
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at 

[jira] [Commented] (IGNITE-5662) Primary index name should contain type ID or name

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev commented on IGNITE-5662:
---

https://github.com/apache/ignite/pull/2275 - patch.

> Primary index name should contain type ID or name
> -
>
> Key: IGNITE-5662
> URL: https://issues.apache.org/jira/browse/IGNITE-5662
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 2.1
>
> Attachments: IgnitePersistentStoreQueryTest.java
>
>
> Currently, the primary index name contains neither type ID nor type name. 
> Since metadata storage allocates tree root based on the index name, two 
> different indexes will be using the same index tree.
> Attached test reproduces this issue.
> A correct fix would be to include type ID or type name (depends on the 
> current SQL internals) to the index name.



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

[jira] [Commented] (IGNITE-5662) Primary index name should contain type ID or name

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev commented on IGNITE-5662:
---

As I found, the issue was that we don't set typeId for description. After this 
was fixed reproducer passed.

http://ci.ignite.apache.org/viewQueued.html?itemId=716528 - CI.

> Primary index name should contain type ID or name
> -
>
> Key: IGNITE-5662
> URL: https://issues.apache.org/jira/browse/IGNITE-5662
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Eduard Shangareev
> Fix For: 2.1
>
> Attachments: IgnitePersistentStoreQueryTest.java
>
>
> Currently, the primary index name contains neither type ID nor type name. 
> Since metadata storage allocates tree root based on the index name, two 
> different indexes will be using the same index tree.
> Attached test reproduces this issue.
> A correct fix would be to include type ID or type name (depends on the 
> current SQL internals) to the index name.



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

[jira] [Commented] (IGNITE-5686) Endless partition eviction during node shutdown

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-5686:
--

Actually both methods return another {{RDD}} with its own {{compute}} method. 
I've put this logic there as well.

> Endless partition eviction during node shutdown
> ---
>
> Key: IGNITE-5686
> URL: https://issues.apache.org/jira/browse/IGNITE-5686
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Igor Seliverstov
> Fix For: 2.2
>
> Attachments: dump.txt
>
>
> Observed the following behavior on TC:
> A node cannot stop because system threads are continuously trying to clean 
> partitions.
> http://ci.ignite.apache.org/viewLog.html?buildId=702633=Ignite20Tests_IgniteRdd=buildResultsDiv
> Attached is a thread dump from the test



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

[jira] [Commented] (IGNITE-5467) Exception in communication SPI can stall the cluster

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev commented on IGNITE-5467:
---

tc looks good, [~agura], please review this PR

> Exception in communication SPI can stall the cluster
> 
>
> Key: IGNITE-5467
> URL: https://issues.apache.org/jira/browse/IGNITE-5467
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: Evgenii Zhuravlev
> Fix For: 2.2
>
> Attachments: MessageSendExceptionTest.java
>
>
> Test attached.
> If there is an exception in {{CommunicationSpi#sendMessage}} while sending 
> response for a cache operation, it can stall whole cluster forever (operation 
> doesn't complete, new nodes can't join, etc.).



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

[jira] [Comment Edited] (IGNITE-3562) Dependency to outdated Lucene 3.5.0

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov edited comment on IGNITE-3562 at 7/10/17 3:13 PM:
---

Conflicts has been resolved.
Waiting for TC tests.


was (Author: amashenkov):
Conflicts resolved.
Waiting for TC tests.

> Dependency to outdated Lucene 3.5.0
> ---
>
> Key: IGNITE-3562
> URL: https://issues.apache.org/jira/browse/IGNITE-3562
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
>Reporter: Alexander Veit
>Assignee: Andrew Mashenkov
>  Labels: important
> Fix For: 2.1
>
>
> Ignite 1.6.0 comes with Lucene 3.5.0 core as dependency, which dates back to 
> the year 2011.
> This makes it difficult to integrate with newer software.



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

[jira] [Updated] (IGNITE-5712) Context switching for optimistic transactions

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-5712:
-
Description: 
Implement context switching between threads for optimistic transactions

http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests_Ignite20Tests=pull%2F2257%2Fhead

  was:Implement context switching between threads for optimistic transactions


> Context switching for optimistic transactions
> -
>
> Key: IGNITE-5712
> URL: https://issues.apache.org/jira/browse/IGNITE-5712
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> Implement context switching between threads for optimistic transactions
> http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests_Ignite20Tests=pull%2F2257%2Fhead



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

[jira] [Commented] (IGNITE-425) Introduce transformers for continuous queries

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-425:
-

[~NIzhikov], 

1) Reuse if possible.
2) We have to keep compatibility.
3) Second case is preferable.

> Introduce transformers for continuous queries
> -
>
> Key: IGNITE-425
> URL: https://issues.apache.org/jira/browse/IGNITE-425
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Izhikov
>
> Currently if updated entry passes the filter, it is sent to node initiated 
> the query entirely. It would be good to provide user with the ability to 
> transform entry and, for example, select only fields that are important. This 
> may bring huge economy to traffic and lower GC pressure as well.
> Possible signatures will be:
> {noformat}
> public final class ContinuousQuery {..} // T is a type transformer 
> transforms to
> public ContinuousQuery setLocalListener(Listener locLsnr) {..} // 
> Probably, we will have to introduce new listener type, since user may want to 
> wipe out key as well.
> /* new method to add */
> public ContinuousQuery setRemoteTransformerFactory(Factory ContinuousQueryTransformer> factory) { ..}
> {noformat}



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

[jira] [Commented] (IGNITE-5567) Make benchmark Ignite.reentrantLock vs IgniteCache.lock

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-5567:
--

[~sharpler], 

I've checked yardstick benchmark and it looks like you changed testing strategy.
See my comments at review.

> Make benchmark Ignite.reentrantLock vs IgniteCache.lock
> ---
>
> Key: IGNITE-5567
> URL: https://issues.apache.org/jira/browse/IGNITE-5567
> Project: Ignite
>  Issue Type: Sub-task
>  Components: data structures
>Reporter: Alexander Menshikov
>Assignee: Alexander Menshikov
> Fix For: 2.3
>
>
> Ignite.reentrantLock slower than IgniteCache.lock. First of all, we must 
> create a benchmark for agreeing about use-case which we want to test.



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

[jira] [Issue Comment Deleted] (IGNITE-5712) Context switching for optimistic transactions

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-5712:
-
Comment: was deleted

(was: 
http://ci.ignite.apache.org/viewLog.html?buildId=713131=buildResultsDiv=Ignite20Tests_RunAll)

> Context switching for optimistic transactions
> -
>
> Key: IGNITE-5712
> URL: https://issues.apache.org/jira/browse/IGNITE-5712
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Reporter: Alexey Kuznetsov
>Assignee: Alexey Kuznetsov
>
> Implement context switching between threads for optimistic transactions



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

[jira] [Commented] (IGNITE-5538) NPE (PersistentStoreExample)

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov commented on IGNITE-5538:
--

I've re-checked this issue and got another exception on 
*PersistentStoreExampleNodeStartup*
{noformat}
2017-07-10 
18:03:21,143][ERROR][grid-nio-worker-tcp-comm-2-#19%null%][GridDirectParser] 
Failed to read message [msg=GridIoMessage [plc=0, topic=null, topicOrd=-1, 
ordered=false, timeout=0, skipOnTimeout=false, msg=null], 
buf=java.nio.DirectByteBuffer[pos=4 lim=186 cap=32768], 
reader=DirectMessageReader [state=DirectMessageState [pos=0, stack=[StateItem 
[stream=DirectByteBufferStreamImplV2 [baseOff=140442328149504, arrOff=-1, 
tmpArrOff=0, tmpArrBytes=0, msgTypeDone=false, msg=null, mapIt=null, it=null, 
arrPos=-1, keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0, 
uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true], 
state=0], null, null, null, null, null, null, null, null, null]], 
lastRead=false], ses=GridSelectorNioSessionImpl [worker=DirectNioClientWorker 
[super=AbstractNioClientWorker [idx=2, bytesRcvd=9078, bytesSent=1092, 
bytesRcvd0=228, bytesSent0=28, select=true, super=GridWorker 
[name=grid-nio-worker-tcp-comm-2, igniteInstanceName=null, finished=false, 
hashCode=1625090318, interrupted=false, 
runner=grid-nio-worker-tcp-comm-2-#19%null%]]], 
writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768], 
readBuf=java.nio.DirectByteBuffer[pos=4 lim=186 cap=32768], 
inRecovery=GridNioRecoveryDescriptor [acked=102, resendCnt=0, rcvCnt=103, 
sentCnt=102, reserved=true, lastAck=96, nodeLeft=false, node=TcpDiscoveryNode 
[id=c7daa293-fa04-46e2-9bac-00bc74fea454, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
192.168.1.143, 2001:db8:85a3:0:0:8a2e:370:7334], sockAddrs=[/0:0:0:0:0:0:0:1:0, 
/127.0.0.1:0, /2001:db8:85a3:0:0:8a2e:370:7334:0, mpb/192.168.1.143:0], 
discPort=0, order=2, intOrder=2, lastExchangeTime=1499698832629, loc=false, 
ver=2.1.2#20170707-sha1:17904cb1, isClient=true], connected=true, connectCnt=1, 
queueLimit=4096, reserveCnt=158, pairedConnections=false], 
outRecovery=GridNioRecoveryDescriptor [acked=102, resendCnt=0, rcvCnt=103, 
sentCnt=102, reserved=true, lastAck=96, nodeLeft=false, node=TcpDiscoveryNode 
[id=c7daa293-fa04-46e2-9bac-00bc74fea454, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
192.168.1.143, 2001:db8:85a3:0:0:8a2e:370:7334], sockAddrs=[/0:0:0:0:0:0:0:1:0, 
/127.0.0.1:0, /2001:db8:85a3:0:0:8a2e:370:7334:0, mpb/192.168.1.143:0], 
discPort=0, order=2, intOrder=2, lastExchangeTime=1499698832629, loc=false, 
ver=2.1.2#20170707-sha1:17904cb1, isClient=true], connected=true, connectCnt=1, 
queueLimit=4096, reserveCnt=158, pairedConnections=false], 
super=GridNioSessionImpl [locAddr=/0:0:0:0:0:0:0:1:47100, 
rmtAddr=/0:0:0:0:0:0:0:1:50726, createTime=1499699001135, closeTime=0, 
bytesSent=28, bytesRcvd=228, bytesSent0=28, bytesRcvd0=228, 
sndSchedTime=1499699001135, lastSndTime=1499699001135, 
lastRcvTime=1499699001135, readsPaused=false, 
filterChain=FilterChain[filters=[GridNioCodecFilter 
[parser=o.a.i.i.util.nio.GridDirectParser@6df9f203, directMode=true], 
GridConnectionBytesVerifyFilter], accepted=true]]]
java.lang.NullPointerException
at 
org.apache.ignite.internal.managers.communication.GridIoMessageFactory.create(GridIoMessageFactory.java:879)
at 
org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$9.create(TcpCommunicationSpi.java:2140)
at 
org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1154)
at 
org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:311)
at 
org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:261)
at 
org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:90)
at 
org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at 
org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:133)
at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at 
org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3222)
at 
org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
at 
org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1213)
at 
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2180)
at 

[jira] [Commented] (IGNITE-5686) Endless partition eviction during node shutdown

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-5686:
--

[~gvvinblade],
Got it. I'm ok with a fix.

What about IgniteSqlRDD.sql and IgniteSqlRDD.objectSql method?
Looks like they have same issues and return cursors that will never been 
closed. 
So, we have to create ticket for this, aren't we?

> Endless partition eviction during node shutdown
> ---
>
> Key: IGNITE-5686
> URL: https://issues.apache.org/jira/browse/IGNITE-5686
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Igor Seliverstov
> Fix For: 2.2
>
> Attachments: dump.txt
>
>
> Observed the following behavior on TC:
> A node cannot stop because system threads are continuously trying to clean 
> partitions.
> http://ci.ignite.apache.org/viewLog.html?buildId=702633=Ignite20Tests_IgniteRdd=buildResultsDiv
> Attached is a thread dump from the test



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

[jira] [Commented] (IGNITE-5686) Endless partition eviction during node shutdown

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-5686:
--

Internally {{Iterator}} closes on {{QueryCursor}} close, so, it's enough to 
close cursor only.

> Endless partition eviction during node shutdown
> ---
>
> Key: IGNITE-5686
> URL: https://issues.apache.org/jira/browse/IGNITE-5686
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Igor Seliverstov
> Fix For: 2.2
>
> Attachments: dump.txt
>
>
> Observed the following behavior on TC:
> A node cannot stop because system threads are continuously trying to clean 
> partitions.
> http://ci.ignite.apache.org/viewLog.html?buildId=702633=Ignite20Tests_IgniteRdd=buildResultsDiv
> Attached is a thread dump from the test



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

[jira] [Commented] (IGNITE-5686) Endless partition eviction during node shutdown

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-5686:
--

{{IgniteQueryIterator}} implements {{scala.Iterator}} and is used inside Spark. 
Spark doesn't expect {{AutoClosable}} iterator and isn't responsible for 
closing it. Compute operation happens only on terminal action ant it's 
guaranteed that {{TaskContext}} will be available, so, we can register a 
callback to clean resources after operation finishes.

> Endless partition eviction during node shutdown
> ---
>
> Key: IGNITE-5686
> URL: https://issues.apache.org/jira/browse/IGNITE-5686
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Igor Seliverstov
> Fix For: 2.2
>
> Attachments: dump.txt
>
>
> Observed the following behavior on TC:
> A node cannot stop because system threads are continuously trying to clean 
> partitions.
> http://ci.ignite.apache.org/viewLog.html?buildId=702633=Ignite20Tests_IgniteRdd=buildResultsDiv
> Attached is a thread dump from the test



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

[jira] [Comment Edited] (IGNITE-425) Introduce transformers for continuous queries

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov edited comment on IGNITE-425 at 7/10/17 2:41 PM:
-

# Other parts of Ignite \[1] use IgniteClosure \[2] as transformer. I think we 
can reuse interface. Thoughts?
# Do we need to provide backward compatibility for a ContinuousQuery as it a 
public API?
We will broke all client code that using ContinuousQuery if simply add one more 
generic parameter(ContinuousQuery)
# Which way of implementation is preferable?
## First way to implement feature is create GenericContinuousQuery. 
Internal code will use new GenericContinuousQuery but all client code that 
using ContinuousQuery still be valid(see first code example)
## Second way ContinuousQueryWIthTransformer extends ContinuousQuery.
Internal code has to check which instance it has when execute some logic(see 
second code example)

{code:java}
public final class GenericContinuousQuery extends Query> {
/* new method to add */
public GenericContinuousQuery 
setRemoteTransformerFactory(Factory> factory) { ..}

//other new methods
}

public final class ContinuousQuery extends GenericContinuousQuery {
public ContinuousQuery() {
setRemoteTransformerFactory(new Factory> {
public IgniteClosure create() {
return new IgniteClosure {
public V apply(V e) { return e; }
}
}
});
}
}
{code}

{code:java}
public final class ContinuousQueryWithTransformer extends 
ContinuousQuery {
/* new method to add */
public GenericContinuousQuery 
setRemoteTransformerFactory(Factory> factory) { ..}

//other new methods
}
{code}

\[1] 
https://www.gridgain.com/sdk/pe/latest/javadoc/org/apache/ignite/IgniteCache.html#query(org.apache.ignite.cache.query.Query,%20org.apache.ignite.lang.IgniteClosure)
\[2] 
https://www.gridgain.com/sdk/pe/latest/javadoc/org/apache/ignite/lang/IgniteClosure.html


was (Author: nizhikov):
# Other parts of Ignite \[1] use IgniteClosure \[2] as transformer. I think we 
can reuse interface. Thoughts?
# Do we need to provide backward compatibility for a ContinuousQuery as it a 
public API?
We will broke all client code that using ContinuousQuery if simply add one more 
generic parameter(ContinuousQuery)
# Which way of implementation is preferable?
## First way to implement feature is create GenericContinuousQuery. 
Internal code will use new GenericContinuousQuery but all client code that 
using ContinuousQuery still be valid(see first code example)
## Second way ContinuousQueryWIthTransformer extends ContinuousQuery.
Internal code has to check which instance it has when execute some logic

{code:java}
public final class GenericContinuousQuery extends Query> {
/* new method to add */
public GenericContinuousQuery 
setRemoteTransformerFactory(Factory> factory) { ..}

//other new methods
}

public final class ContinuousQuery extends GenericContinuousQuery {
public ContinuousQuery() {
setRemoteTransformerFactory(new Factory> {
public IgniteClosure create() {
return new IgniteClosure {
public V apply(V e) { return e; }
}
}
});
}
}
{code}

{code:java}
public final class ContinuousQueryWithTransformer extends 
ContinuousQuery {
/* new method to add */
public GenericContinuousQuery 
setRemoteTransformerFactory(Factory> factory) { ..}

//other new methods
}
{code}

\[1] 
https://www.gridgain.com/sdk/pe/latest/javadoc/org/apache/ignite/IgniteCache.html#query(org.apache.ignite.cache.query.Query,%20org.apache.ignite.lang.IgniteClosure)
\[2] 
https://www.gridgain.com/sdk/pe/latest/javadoc/org/apache/ignite/lang/IgniteClosure.html

> Introduce transformers for continuous queries
> -
>
> Key: IGNITE-425
> URL: https://issues.apache.org/jira/browse/IGNITE-425
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Izhikov
>
> Currently if updated entry passes the filter, it is sent to node initiated 
> the query entirely. It would be good to provide user with the ability to 
> transform entry and, for example, select only fields that are important. This 
> may bring huge economy to traffic and lower GC pressure as well.
> Possible signatures will be:
> {noformat}
> public final class ContinuousQuery {..} // T is a type transformer 
> transforms to
> public ContinuousQuery 

[jira] [Issue Comment Deleted] (IGNITE-5688) Fix SparseDistributedMatrixTest::testCacheBehaviour crash

[Artem Malykh (JIRA)]

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

Artem Malykh updated IGNITE-5688:
-
Comment: was deleted

(was: 
http://ci.ignite.apache.org/viewLog.html?buildTypeId=Ignite20Tests_IgniteMl=716191_Ignite20Tests_IgniteMl=pull/2272/head
 -- Green TC run.)

> Fix SparseDistributedMatrixTest::testCacheBehaviour crash
> -
>
> Key: IGNITE-5688
> URL: https://issues.apache.org/jira/browse/IGNITE-5688
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.0
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>  Labels: test-fail
> Fix For: 2.1
>
>
> SparseDistributedMatrixTest::testCacheBehaviour crashed because of wrong 
> checks of cache behaviour.



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

[jira] [Commented] (IGNITE-425) Introduce transformers for continuous queries

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-425:


# Other parts of Ignite \[1] use IgniteClosure \[2] as transformer. I think we 
can reuse interface. Thoughts?
# Do we need to provide backward compatibility for a ContinuousQuery as it a 
public API?
We will broke all client code that using ContinuousQuery if simply add one more 
generic parameter(ContinuousQuery)
# Which way of implementation is preferable?
## First way to implement feature is create GenericContinuousQuery. 
Internal code will use new GenericContinuousQuery but all client code that 
using ContinuousQuery still be valid(see first code example)
## Second way ContinuousQueryWIthTransformer extends ContinuousQuery.
Internal code has to check which instance it has when execute some logic

{code:java}
public final class GenericContinuousQuery extends Query> {
/* new method to add */
public GenericContinuousQuery 
setRemoteTransformerFactory(Factory> factory) { ..}

//other new methods
}

public final class ContinuousQuery extends GenericContinuousQuery {
public ContinuousQuery() {
setRemoteTransformerFactory(new Factory> {
public IgniteClosure create() {
return new IgniteClosure {
public V apply(V e) { return e; }
}
}
});
}
}
{code}

{code:java}
public final class ContinuousQueryWithTransformer extends 
ContinuousQuery {
/* new method to add */
public GenericContinuousQuery 
setRemoteTransformerFactory(Factory> factory) { ..}

//other new methods
}
{code}

\[1] 
https://www.gridgain.com/sdk/pe/latest/javadoc/org/apache/ignite/IgniteCache.html#query(org.apache.ignite.cache.query.Query,%20org.apache.ignite.lang.IgniteClosure)
\[2] 
https://www.gridgain.com/sdk/pe/latest/javadoc/org/apache/ignite/lang/IgniteClosure.html

> Introduce transformers for continuous queries
> -
>
> Key: IGNITE-425
> URL: https://issues.apache.org/jira/browse/IGNITE-425
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Izhikov
>
> Currently if updated entry passes the filter, it is sent to node initiated 
> the query entirely. It would be good to provide user with the ability to 
> transform entry and, for example, select only fields that are important. This 
> may bring huge economy to traffic and lower GC pressure as well.
> Possible signatures will be:
> {noformat}
> public final class ContinuousQuery {..} // T is a type transformer 
> transforms to
> public ContinuousQuery setLocalListener(Listener locLsnr) {..} // 
> Probably, we will have to introduce new listener type, since user may want to 
> wipe out key as well.
> /* new method to add */
> public ContinuousQuery setRemoteTransformerFactory(Factory ContinuousQueryTransformer> factory) { ..}
> {noformat}



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

[jira] [Commented] (IGNITE-5688) Fix SparseDistributedMatrixTest::testCacheBehaviour crash

[Artem Malykh (JIRA)]

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

Artem Malykh commented on IGNITE-5688:
--

http://ci.ignite.apache.org/viewLog.html?buildTypeId=Ignite20Tests_IgniteMl=716191_Ignite20Tests_IgniteMl=pull/2272/head
 -- Green TC run.

> Fix SparseDistributedMatrixTest::testCacheBehaviour crash
> -
>
> Key: IGNITE-5688
> URL: https://issues.apache.org/jira/browse/IGNITE-5688
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.0
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>  Labels: test-fail
> Fix For: 2.1
>
>
> SparseDistributedMatrixTest::testCacheBehaviour crashed because of wrong 
> checks of cache behaviour.



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

[jira] [Commented] (IGNITE-5479) PersistentStoreConfiguration improvements

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5479:


What is the point of {{DFLT_CHECKPOINTING_PAGE_BUFFER_SIZE}} then? The actual 
value is never used, we just use a reference comparison?

Let's change both setter and getter to {{Long}}, default to null, and state in 
the Javadoc that {{null}} means "automatic buffer size".

> PersistentStoreConfiguration improvements
> -
>
> Key: IGNITE-5479
> URL: https://issues.apache.org/jira/browse/IGNITE-5479
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.1
>
>
> Improve {{PersistentStoreConfiguration}} to be consistent with other 
> configuration classes:
> * {{LockWaitTime}} - should be {{long}} and in milliseconds
> * {{getCheckpointingPageBufferSize}} should return {{long}} instead of 
> {{Long}}
> * {{WalFlushFrequency}} - should be {{long}} and in milliseconds
> * {{WalFsyncDelay}}  - should be {{long}} and in milliseconds. Add javadoc.



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

[jira] [Commented] (IGNITE-5725) Adopt TracerTest for TC builds.

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-5725:


one option to consider is to establish a dedicated Maven profile for execution 
at TeamCity (per my brief check there is no such profile yet) and after that 
configure surefire plugin to skip these tests when TC profile is activated as 
described eg here: [How to Split JUnit Tests in a Continuous Integration 
Environment|https://semaphoreci.com/community/tutorials/how-to-split-junit-tests-in-a-continuous-integration-environment]

> Adopt TracerTest for TC builds.
> ---
>
> Key: IGNITE-5725
> URL: https://issues.apache.org/jira/browse/IGNITE-5725
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Reporter: Yury Babak
>
> Currently TracerTest runs browser but we don`t have even X11 on TC. So we 
> need to decide - run add possibility to run browser on TC, change tests and 
> don`t call "Desktop.getDesktop().browse" during TC build or just ignore this 
> test for TC build.



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

[jira] [Comment Edited] (IGNITE-5725) Adopt TracerTest for TC builds.

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko edited comment on IGNITE-5725 at 7/10/17 2:21 PM:
-

one option to consider is to establish a dedicated Maven profile for execution 
at TeamCity (per my brief check there is no such profile yet) and after that 
configure surefire plugin to skip these tests when TC profile is activated as 
described eg here: [How to Split JUnit Tests in a Continuous Integration 
Environment|https://semaphoreci.com/community/tutorials/how-to-split-junit-tests-in-a-continuous-integration-environment].
 It looks less desirable compared to making it just possible to normally run 
these tests at TC though, because skipping tests is less safe than letting them 
run.


was (Author: oignatenko):
one option to consider is to establish a dedicated Maven profile for execution 
at TeamCity (per my brief check there is no such profile yet) and after that 
configure surefire plugin to skip these tests when TC profile is activated as 
described eg here: [How to Split JUnit Tests in a Continuous Integration 
Environment|https://semaphoreci.com/community/tutorials/how-to-split-junit-tests-in-a-continuous-integration-environment]

> Adopt TracerTest for TC builds.
> ---
>
> Key: IGNITE-5725
> URL: https://issues.apache.org/jira/browse/IGNITE-5725
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Reporter: Yury Babak
>
> Currently TracerTest runs browser but we don`t have even X11 on TC. So we 
> need to decide - run add possibility to run browser on TC, change tests and 
> don`t call "Desktop.getDesktop().browse" during TC build or just ignore this 
> test for TC build.



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

[jira] [Commented] (IGNITE-5688) Fix SparseDistributedMatrixTest::testCacheBehaviour crash

[Yury Babak (JIRA)]

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

Yury Babak commented on IGNITE-5688:


[~amalykh] looks ok for me.

> Fix SparseDistributedMatrixTest::testCacheBehaviour crash
> -
>
> Key: IGNITE-5688
> URL: https://issues.apache.org/jira/browse/IGNITE-5688
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.0
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>  Labels: test-fail
> Fix For: 2.1
>
>
> SparseDistributedMatrixTest::testCacheBehaviour crashed because of wrong 
> checks of cache behaviour.



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

[jira] [Closed] (IGNITE-4751) JVM crash while accessing Offheap entry.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov closed IGNITE-4751.


> JVM crash while accessing Offheap entry.
> 
>
> Key: IGNITE-4751
> URL: https://issues.apache.org/jira/browse/IGNITE-4751
> Project: Ignite
>  Issue Type: Bug
>  Components: general, swap
>Affects Versions: 1.7, 1.8
>Reporter: Andrew Mashenkov
>Priority: Critical
> Attachments: mm-rbp-server-err-pid8466.log
>
>
> JVM crashed with SIGSEGV error while iterating over offheap entries on stable 
> topology.
> PFA logs attached.
> Partitioned OffHeap-Tiered  cache with swap enabled has been configured.



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

[jira] [Resolved] (IGNITE-4788) JVM crash while accessing offheap rows of SQL query result.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov resolved IGNITE-4788.
--
   Resolution: Cannot Reproduce
Fix Version/s: (was: 2.2)

> JVM crash while accessing offheap rows of SQL query result.
> ---
>
> Key: IGNITE-4788
> URL: https://issues.apache.org/jira/browse/IGNITE-4788
> Project: Ignite
>  Issue Type: Bug
>  Components: sql, swap
>Affects Versions: 1.8
>Reporter: Andrew Mashenkov
> Attachments: hs_err_pid18543.log.txt, log.txt
>
>
> JVM crashed with SIGSEGV error while iterating over SQL query offheap rows.



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

[jira] [Commented] (IGNITE-2313) Need to add a mode to fail atomic operations within a transaction

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-2313:
--

[~SomeFire],

I've checked fixes, looks good. 
Let's investigate MultiJvm issues with jcache() method.

> Need to add a mode to fail atomic operations within a transaction
> -
>
> Key: IGNITE-2313
> URL: https://issues.apache.org/jira/browse/IGNITE-2313
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Dmitriy Setrakyan
>Assignee: Ryabov Dmitrii
> Fix For: 2.2
>
>
> Currently atomic operations within a transaction succeed without alarming a 
> user that no transaction really occurs. We should add a mode to fail such 
> operations (such mode should be turned off by default).
> New transaction configuration flag (default is {{false}}):
> {code}TransactionConfiguration.isAllowAtomicUpdatesInTransaction(){code}
> If the flag is violated, we should throw an exception with the following 
> error message: {{Transaction spans operations on atomic cache (consider 
> setting TransactionConfiguration.isAllowAttomicUpdatesInTransaction() flag to 
> true)}}



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

[jira] [Commented] (IGNITE-5479) PersistentStoreConfiguration improvements

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-5479:
--

This does not work: we need Long to distinguish between the following two cases:
{code}
new PersistentStoreConfiguration(); // Ignite will automatically adjust 
checkpoint buffer size
{code}
and
{code}
   new PersistentStoreConfiguration().setCheckpointPageBufferSize(someValue); 
// Ignite will NOT adjust the checkpoint buffer size even if someValue == 
DEFAULT_VALUE
{code}

This can be solved by adding a flag isDefaultPageBufferSize on 
PersistentStoreConfiguration, but the approach with Long looks more clear to 
me. What do you think?

> PersistentStoreConfiguration improvements
> -
>
> Key: IGNITE-5479
> URL: https://issues.apache.org/jira/browse/IGNITE-5479
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.1
>
>
> Improve {{PersistentStoreConfiguration}} to be consistent with other 
> configuration classes:
> * {{LockWaitTime}} - should be {{long}} and in milliseconds
> * {{getCheckpointingPageBufferSize}} should return {{long}} instead of 
> {{Long}}
> * {{WalFlushFrequency}} - should be {{long}} and in milliseconds
> * {{WalFsyncDelay}}  - should be {{long}} and in milliseconds. Add javadoc.



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

[jira] [Commented] (IGNITE-5686) Endless partition eviction during node shutdown

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-5686:
--

[~gvvinblade],

I've looked at a code and have a question.
Why IgniteQueryIterator doesn't implements java.lang.AutoCloseable (or 
Closeable)?

AFAIK in SQL module we have a cursors that implement those interfaces and have 
no problems with iterators closing.
Would it be workable solution if we'll close cursor together with iterator 
instead of using a listeners?

> Endless partition eviction during node shutdown
> ---
>
> Key: IGNITE-5686
> URL: https://issues.apache.org/jira/browse/IGNITE-5686
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Igor Seliverstov
> Fix For: 2.2
>
> Attachments: dump.txt
>
>
> Observed the following behavior on TC:
> A node cannot stop because system threads are continuously trying to clean 
> partitions.
> http://ci.ignite.apache.org/viewLog.html?buildId=702633=Ignite20Tests_IgniteRdd=buildResultsDiv
> Attached is a thread dump from the test



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

[jira] [Resolved] (IGNITE-4751) JVM crash while accessing Offheap entry.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov resolved IGNITE-4751.
--
   Resolution: Cannot Reproduce
Fix Version/s: (was: 2.2)

> JVM crash while accessing Offheap entry.
> 
>
> Key: IGNITE-4751
> URL: https://issues.apache.org/jira/browse/IGNITE-4751
> Project: Ignite
>  Issue Type: Bug
>  Components: general, swap
>Affects Versions: 1.7, 1.8
>Reporter: Andrew Mashenkov
>Priority: Critical
> Attachments: mm-rbp-server-err-pid8466.log
>
>
> JVM crashed with SIGSEGV error while iterating over offheap entries on stable 
> topology.
> PFA logs attached.
> Partitioned OffHeap-Tiered  cache with swap enabled has been configured.



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

[jira] [Closed] (IGNITE-4788) JVM crash while accessing offheap rows of SQL query result.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov closed IGNITE-4788.


> JVM crash while accessing offheap rows of SQL query result.
> ---
>
> Key: IGNITE-4788
> URL: https://issues.apache.org/jira/browse/IGNITE-4788
> Project: Ignite
>  Issue Type: Bug
>  Components: sql, swap
>Affects Versions: 1.8
>Reporter: Andrew Mashenkov
> Attachments: hs_err_pid18543.log.txt, log.txt
>
>
> JVM crashed with SIGSEGV error while iterating over SQL query offheap rows.



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

[jira] [Assigned] (IGNITE-5662) Primary index name should contain type ID or name

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev reassigned IGNITE-5662:
-

Assignee: Eduard Shangareev  (was: Alexey Goncharuk)

> Primary index name should contain type ID or name
> -
>
> Key: IGNITE-5662
> URL: https://issues.apache.org/jira/browse/IGNITE-5662
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Eduard Shangareev
> Fix For: 2.1
>
> Attachments: IgnitePersistentStoreQueryTest.java
>
>
> Currently, the primary index name contains neither type ID nor type name. 
> Since metadata storage allocates tree root based on the index name, two 
> different indexes will be using the same index tree.
> Attached test reproduces this issue.
> A correct fix would be to include type ID or type name (depends on the 
> current SQL internals) to the index name.



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

[jira] [Assigned] (IGNITE-5103) TcpDiscoverySpi ignores maxMissedClientHeartbeats property

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev reassigned IGNITE-5103:
---

Assignee: Dmitry Karachentsev  (was: Alexei Kaigorodov)

> TcpDiscoverySpi ignores maxMissedClientHeartbeats property
> --
>
> Key: IGNITE-5103
> URL: https://issues.apache.org/jira/browse/IGNITE-5103
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.9
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
> Fix For: 2.2
>
> Attachments: TcpDiscoveryClientSuspensionSelfTest.java
>
>
> Test scenario is the following:
> * Start one or more servers.
> * Start a client node.
> * Suspend client process using {{-SIGSTOP}} signal.
> * Wait for {{maxMissedClientHeartbeats*heartbeatFrequency}}.
> * Client node is expected to be removed from topology, but server nodes don't 
> do that.
> Attached is the unit test reproducing the same by stopping the heartbeat 
> sender thread on the client.



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

[jira] [Assigned] (IGNITE-5538) NPE (PersistentStoreExample)

[Pavel Kovalenko (JIRA)]

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

Pavel Kovalenko reassigned IGNITE-5538:
---

Assignee: Pavel Kovalenko  (was: Alexey Goncharuk)

> NPE (PersistentStoreExample)
> 
>
> Key: IGNITE-5538
> URL: https://issues.apache.org/jira/browse/IGNITE-5538
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Ilya Suntsov
>Assignee: Pavel Kovalenko
> Fix For: 2.1
>
> Attachments: PersistentStoreExampleNode.txt, 
> PersistentStoreExample.txt
>
>
> Steps to reproduce:
> 1. Start *PersistentStoreExampleNodeStartup*
> 2. Start *PersistentStoreExample* (UPLOAD=true)
> Result:
> 1. Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=7.1GB]
> 2. Started preloading
> 3. On ExampleNode got exception:
> {noformat}
> [2017-06-19 13:11:28,545][WARN 
> ][grid-nio-worker-tcp-comm-3-#20%null%][TcpCommunicationSpi] Failed to 
> process selector key (will close): GridSelectorNioSessionImpl 
> [worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=3, 
> bytesRcvd=2052, bytesSent=252, bytesRcvd0=228, bytesSent0=28, select=true, 
> super=GridWorker [name=grid-nio-worker-tcp-comm-3, igniteInstanceName=null, 
> finished=false, hashCode=1279096191, interrupted=false, 
> runner=grid-nio-worker-tcp-comm-3-#20%null%]]], 
> writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768], 
> readBuf=java.nio.DirectByteBuffer[pos=4 lim=186 cap=32768], 
> inRecovery=GridNioRecoveryDescriptor [acked=103, resendCnt=0, rcvCnt=104, 
> sentCnt=103, reserved=true, lastAck=96, nodeLeft=false, node=TcpDiscoveryNode 
> [id=be66eae2-3986-4772-b02b-bf2813370a15, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 172.25.4.115, 172.25.4.116, 2001:db8:85a3:0:0:8a2e:370:7334], 
> sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /172.25.4.115:0, 
> /172.25.4.116:0, /2001:db8:85a3:0:0:8a2e:370:7334:0], discPort=0, order=2, 
> intOrder=2, lastExchangeTime=1497867042970, loc=false, 
> ver=2.1.1#20170618-sha1:09ce29e0, isClient=true], connected=true, 
> connectCnt=1, queueLimit=4096, reserveCnt=35, pairedConnections=false], 
> outRecovery=GridNioRecoveryDescriptor [acked=103, resendCnt=0, rcvCnt=104, 
> sentCnt=103, reserved=true, lastAck=96, nodeLeft=false, node=TcpDiscoveryNode 
> [id=be66eae2-3986-4772-b02b-bf2813370a15, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 172.25.4.115, 172.25.4.116, 2001:db8:85a3:0:0:8a2e:370:7334], 
> sockAddrs=[/0:0:0:0:0:0:0:1:0, /127.0.0.1:0, /172.25.4.115:0, 
> /172.25.4.116:0, /2001:db8:85a3:0:0:8a2e:370:7334:0], discPort=0, order=2, 
> intOrder=2, lastExchangeTime=1497867042970, loc=false, 
> ver=2.1.1#20170618-sha1:09ce29e0, isClient=true], connected=true, 
> connectCnt=1, queueLimit=4096, reserveCnt=35, pairedConnections=false], 
> super=GridNioSessionImpl [locAddr=/0:0:0:0:0:0:0:1:47100, 
> rmtAddr=/0:0:0:0:0:0:0:1:60813, createTime=1497867087529, closeTime=0, 
> bytesSent=28, bytesRcvd=228, bytesSent0=28, bytesRcvd0=228, 
> sndSchedTime=1497867087529, lastSndTime=1497867087529, 
> lastRcvTime=1497867087541, readsPaused=false, 
> filterChain=FilterChain[filters=[GridNioCodecFilter 
> [parser=o.a.i.i.util.nio.GridDirectParser@7a94a8f6, directMode=true], 
> GridConnectionBytesVerifyFilter], accepted=true]]
> [2017-06-19 
> 13:11:28,545][ERROR][grid-nio-worker-tcp-comm-3-#20%null%][TcpCommunicationSpi]
>  Closing NIO session because of unhandled exception.
> class org.apache.ignite.internal.util.nio.GridNioException: null
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2199)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1968)
>   at 
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1669)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.managers.communication.GridIoMessageFactory.create(GridIoMessageFactory.java:879)
>   at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi$9.create(TcpCommunicationSpi.java:2134)
>   at 
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1154)
>   at 
> org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:311)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:261)
>   at 
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:90)
>   at 
> 

[jira] [Commented] (IGNITE-5538) NPE (PersistentStoreExample)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5538:


GitHub user Jokser opened a pull request:

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

IGNITE-5538 Double check for PersistenceStore message factory existence.



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

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

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

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

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

This closes #2273


commit ab5267134966b466a2d4bfba15d0c7e3ebe91139
Author: sboikov 
Date:   2017-07-07T10:14:18Z

2.1 More simple tx cancel on node stop

commit 85d8c6572d78c7d6796906d92b566e2fa5b116be
Author: Dmitriy Govorukhin 
Date:   2017-07-07T10:13:55Z

IGNITE-5520 - Fixed IgniteChangeGlobalStateFailoverTest

commit f589628f4846f14efc8e702b61856cc90a3d0dc7
Author: sboikov 
Date:   2017-07-07T10:52:38Z

Rename ActionData -> CacheActionData.

commit 30922ed8ac518749a2559aff51fe183a890041bb
Author: Alexey Kuznetsov 
Date:   2017-07-07T11:03:18Z

ignite-2.1 Added map with previous snapshots.

commit 99fd75dd7766318af88a38b5640a648bba3ccdf1
Author: Sergey Kalashnikov 
Date:   2017-07-07T11:38:36Z

IGNITE-5483: Added limited support for Java8 LocalDateTime. This closes 
#2248.

commit 4fc8124d9538625cb0a95c918634b43ec1319bee
Author: sboikov 
Date:   2017-07-07T11:43:28Z

Fixed formatting.

commit 984ab5bd3c08b2af9222964451acc281b92814b8
Author: sboikov 
Date:   2017-07-07T11:43:50Z

Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2

commit 7adb11109bab5d83ed4f376b0cad42b026dd0a71
Author: sboikov 
Date:   2017-07-07T11:49:13Z

Fixed formatting.

commit 2a5390b1c083819f059e449b34a5979ec35b7755
Author: Alexander Paschenko 
Date:   2017-07-07T12:01:43Z

IGNITE-5159: DDL example. This closes #2227.

commit d232648711c882ed304eae89ae19f151067649fd
Author: devozerov 
Date:   2017-07-07T12:02:29Z

Merge remote-tracking branch 'upstream/ignite-2.1.2' into ignite-2.1.2

commit a9387adef490086406b05fe961ff0f3151045caa
Author: Pavel Tupitsyn 
Date:   2017-07-07T12:21:20Z

IGNITE-5717 .NET: Reduce MemoryPolicyConfiguration.MaxSize for persistence 
tests as a workaround for OOM on default settings

commit 13399d530f3458c3bf59634857cb05f801e8cc34
Author: sboikov 
Date:   2017-07-07T12:24:09Z

2.1 Fixed assert (cacheName can be null here).

commit ea4420e6aad509c4ae58d6d0880918c98fd1959a
Author: sboikov 
Date:   2017-07-07T12:24:26Z

Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2

commit 0d6fb1ad73e8ed448dabe7c0cc631222835b52c4
Author: Sergey Kalashnikov 
Date:   2017-07-07T12:54:52Z

IGNITE-5204: Fixed NPE on certain data with index inlining. This closes 
#2115.

commit a1cac1b7cc1c3afdcc12afb08bf1ecdcb6f28828
Author: sboikov 
Date:   2017-07-07T12:55:18Z

Removed unused method GridDhtPartitionTopology.checkEvictions().

commit 55a5ca019db7d06aab2fb567dbc0da1f133d0fb7
Author: sboikov 
Date:   2017-07-07T12:55:38Z

Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2

commit 99713feea764fc8c3e5b247a24698a2c04d3bcf4
Author: Sergey Kalashnikov 
Date:   2017-07-07T13:30:37Z

IGNITE-5204: SQL: fixed incorrect partition calculation in case of unicast 
optimization, when WHERE clause argument type was different from key or 
affinity key type. This close #2107.

commit 3c887378eb64d2d236073410070082e5699e8334
Author: Igor Sapego 
Date:   2017-07-07T13:52:31Z

IGNITE-5582: Implemented Compute::Broadcast for C++

(cherry picked from commit fa974286e8f066a8d6aa57519edf5ec7761be095)

commit 3314a4513c816c027dad80258ded1fe5a4c2b700
Author: sboikov 
Date:   2017-07-07T14:28:47Z

Fixed cache plugin validation.

commit 517a23d252078e62a8addca55ca78497e5226b5b
Author: mcherkasov 
Date:   2017-06-30T17:23:55Z

IGNITE-5554 ServiceProcessor may process failed reassignments in timeout 
thread

commit 993f7fbe1d49a524e2dee626aef72e16fd5d3cda
Author: Ilya Lantukh 
Date:   2017-07-07T15:55:27Z

IGNITE-5701 - Some nodes have partitionUpdateCounter equal to 0 after 
rebalancing

commit 

[jira] [Commented] (IGNITE-5479) PersistentStoreConfiguration improvements

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5479:


Agree on fsync delay.

Do not agree on page buffer size. Internally we may maintain a nullable value, 
but user-facing method must be {{long}} (otherwise it is inconsistent and 
confusing; setter and getter should be of same type).

Can we do this?
{code}
public long getCheckpointingPageBufferSize() {
return checkpointingPageBufSize == null ? 
DFLT_CHECKPOINTING_PAGE_BUFFER_SIZE : checkpointingPageBufSize;
}
{code}

> PersistentStoreConfiguration improvements
> -
>
> Key: IGNITE-5479
> URL: https://issues.apache.org/jira/browse/IGNITE-5479
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.1
>
>
> Improve {{PersistentStoreConfiguration}} to be consistent with other 
> configuration classes:
> * {{LockWaitTime}} - should be {{long}} and in milliseconds
> * {{getCheckpointingPageBufferSize}} should return {{long}} instead of 
> {{Long}}
> * {{WalFlushFrequency}} - should be {{long}} and in milliseconds
> * {{WalFsyncDelay}}  - should be {{long}} and in milliseconds. Add javadoc.



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

[jira] [Commented] (IGNITE-5479) PersistentStoreConfiguration improvements

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-5479:
--

Agree on all but:
 - getCheckpointPageBufferSize - this unique long is used to determine the 
default setting override.
 - fsync delay should be fine-grained enough to wait less than a millisecond 
because fsync latency itself may be 0.5 ms. Will rename this method to 
getWalFsyncDelayNanos to emphasize the different time unit

> PersistentStoreConfiguration improvements
> -
>
> Key: IGNITE-5479
> URL: https://issues.apache.org/jira/browse/IGNITE-5479
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.1
>
>
> Improve {{PersistentStoreConfiguration}} to be consistent with other 
> configuration classes:
> * {{LockWaitTime}} - should be {{long}} and in milliseconds
> * {{getCheckpointingPageBufferSize}} should return {{long}} instead of 
> {{Long}}
> * {{WalFlushFrequency}} - should be {{long}} and in milliseconds
> * {{WalFsyncDelay}}  - should be {{long}} and in milliseconds. Add javadoc.



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

[jira] [Commented] (IGNITE-5688) Fix SparseDistributedMatrixTest::testCacheBehaviour crash

[Artem Malykh (JIRA)]

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

Artem Malykh commented on IGNITE-5688:
--

[~chief] Please, look into the pull request.

> Fix SparseDistributedMatrixTest::testCacheBehaviour crash
> -
>
> Key: IGNITE-5688
> URL: https://issues.apache.org/jira/browse/IGNITE-5688
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.0
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>  Labels: test-fail
> Fix For: 2.1
>
>
> SparseDistributedMatrixTest::testCacheBehaviour crashed because of wrong 
> checks of cache behaviour.



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

[jira] [Commented] (IGNITE-5688) Fix SparseDistributedMatrixTest::testCacheBehaviour crash

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5688:


GitHub user artemmalykh opened a pull request:

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

IGNITE-5688 Fix SparseDistributedMatrixTest::testCacheBehaviour crash

Fixed tests of cache behaviour for sparse distributed matrix.
Also code style fixes are done for various ml-module file.

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

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

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

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

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

This closes #2272


commit ce323a7550ee2b3e0b242abce0842ebcebb09b83
Author: artemmalykh 
Date:   2017-07-10T12:50:10Z

IGNITE-5688 Fix SparseDistributedMatrixTest::testCacheBehaviour crash




> Fix SparseDistributedMatrixTest::testCacheBehaviour crash
> -
>
> Key: IGNITE-5688
> URL: https://issues.apache.org/jira/browse/IGNITE-5688
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.0
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>  Labels: test-fail
> Fix For: 2.1
>
>
> SparseDistributedMatrixTest::testCacheBehaviour crashed because of wrong 
> checks of cache behaviour.



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

[jira] [Commented] (IGNITE-5681) IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover fails

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh commented on IGNITE-5681:
--

Duplicate of https://issues.apache.org/jira/browse/IGNITE-5694

> IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover 
> fails
> -
>
> Key: IGNITE-5681
> URL: https://issues.apache.org/jira/browse/IGNITE-5681
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
>  Labels: test-fail
> Fix For: 2.1
>
>
> This is a regression introduced during persistent store migration.
> {code}
> [2017-07-04 11:20:46,993][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteException: Failed to update keys (retry update 
> if possible).: [GridCacheQueueHeaderKey [name=q-3]]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
>   at org.apache.ignite.internal.IgniteKernal.queue(IgniteKernal.java:3648)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:164)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testFailoverWithClient(IgniteAtomicLongChangingTopologySelfTest.java:221)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover(IgniteAtomicLongChangingTopologySelfTest.java:155)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [GridCacheQueueHeaderKey 
> [name=q-3]]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:398)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onNodeLeft(GridNearAtomicSingleUpdateFuture.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$4.onEvent(GridCacheMvccManager.java:266)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager$LocalListenerWrapper.onEvent(GridEventStorageManager.java:1353)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:895)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record0(GridEventStorageManager.java:344)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:311)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2401)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2598)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2430)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   ... 1 more
>   Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> update keys on primary node.
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.UpdateErrors.addFailedKeys(UpdateErrors.java:124)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:342)
>   at 
> 

[jira] [Created] (IGNITE-5724) Remove all autoboxing staff from the component.

[Yury Babak (JIRA)]

Yury Babak created IGNITE-5724:
--

 Summary: Remove all autoboxing staff from the component.
 Key: IGNITE-5724
 URL: https://issues.apache.org/jira/browse/IGNITE-5724
 Project: Ignite
  Issue Type: Improvement
  Components: ml
Reporter: Yury Babak


Find and remove all boxing/unboxing code from vectors and matrices.



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

[jira] [Updated] (IGNITE-5723) Improve code quality for existing code.

[Yury Babak (JIRA)]

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

Yury Babak updated IGNITE-5723:
---
Description: 
(?) check code style for all sources.
(?) check code coverage.

> Improve code quality for existing code.
> ---
>
> Key: IGNITE-5723
> URL: https://issues.apache.org/jira/browse/IGNITE-5723
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Reporter: Yury Babak
>
> (?) check code style for all sources.
> (?) check code coverage.



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

[jira] [Assigned] (IGNITE-5682) GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov reassigned IGNITE-5682:
--

Assignee: Dmitriy Pavlov  (was: Sergey Chugunov)

> GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails
> -
>
> Key: IGNITE-5682
> URL: https://issues.apache.org/jira/browse/IGNITE-5682
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
>  Labels: test-fail
> Fix For: 2.1
>
>
> This appears to be a regression introduced during persistent store migration. 
> {code}
> class org.apache.ignite.IgniteException: Timeout of waiting for topology map 
> update 
> [igniteInstanceName=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest1,
>  cache=default, cacheId=1544803905, topVer=AffinityTopologyVersion 
> [topVer=10, minorTopVer=0], p=0, readVer=AffinityTopologyVersion [topVer=10, 
> minorTopVer=0], locNode=TcpDiscoveryNode 
> [id=c53cc66c-05ea-4441-825c-23d99ef1, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2, 
> lastExchangeTime=1499156862204, loc=true, ver=2.1.0#19700101-sha1:, 
> isClient=false]]
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:698)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:532)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:517)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.test(GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.java:154)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Updated] (IGNITE-5723) Improve code quality for existing code.

[Yury Babak (JIRA)]

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

Yury Babak updated IGNITE-5723:
---
Environment: (was: (?) check code style for all sources.
(?) check code coverage.)

> Improve code quality for existing code.
> ---
>
> Key: IGNITE-5723
> URL: https://issues.apache.org/jira/browse/IGNITE-5723
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Reporter: Yury Babak
>




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

[jira] [Created] (IGNITE-5723) Improve code quality for existing code.

[Yury Babak (JIRA)]

Yury Babak created IGNITE-5723:
--

 Summary: Improve code quality for existing code.
 Key: IGNITE-5723
 URL: https://issues.apache.org/jira/browse/IGNITE-5723
 Project: Ignite
  Issue Type: Improvement
  Components: ml
 Environment: (?) check code style for all sources.
(?) check code coverage.
Reporter: Yury Babak






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

[jira] [Resolved] (IGNITE-5681) IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover fails

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh resolved IGNITE-5681.
--
Resolution: Duplicate

> IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover 
> fails
> -
>
> Key: IGNITE-5681
> URL: https://issues.apache.org/jira/browse/IGNITE-5681
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
>  Labels: test-fail
> Fix For: 2.1
>
>
> This is a regression introduced during persistent store migration.
> {code}
> [2017-07-04 11:20:46,993][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteException: Failed to update keys (retry update 
> if possible).: [GridCacheQueueHeaderKey [name=q-3]]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
>   at org.apache.ignite.internal.IgniteKernal.queue(IgniteKernal.java:3648)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:164)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testFailoverWithClient(IgniteAtomicLongChangingTopologySelfTest.java:221)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover(IgniteAtomicLongChangingTopologySelfTest.java:155)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [GridCacheQueueHeaderKey 
> [name=q-3]]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:398)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onNodeLeft(GridNearAtomicSingleUpdateFuture.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$4.onEvent(GridCacheMvccManager.java:266)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager$LocalListenerWrapper.onEvent(GridEventStorageManager.java:1353)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:895)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record0(GridEventStorageManager.java:344)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:311)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2401)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2598)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2430)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   ... 1 more
>   Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> update keys on primary node.
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.UpdateErrors.addFailedKeys(UpdateErrors.java:124)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:342)
>   at 
> 

[jira] [Created] (IGNITE-5722) Cache entries stay in onheap after scan query execution for OFFHEAP_TIRED cache with expiry policy

[Andrey Gura (JIRA)]

Andrey Gura created IGNITE-5722:
---

 Summary: Cache entries stay in onheap after scan query execution 
for OFFHEAP_TIRED cache with expiry policy
 Key: IGNITE-5722
 URL: https://issues.apache.org/jira/browse/IGNITE-5722
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 1.0
Reporter: Andrey Gura
Assignee: Andrey Gura
 Fix For: 2.1




Cache entries stay in onheap after scan query execution for OFFHEAP_TIRED cache 
with expiry policy.

In PeekValueExpiryAwareIterator.value() method the entry should be touched 
after unswap.





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

[jira] [Commented] (IGNITE-5681) IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-5681:


[~ilantukh], thank you!

> IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover 
> fails
> -
>
> Key: IGNITE-5681
> URL: https://issues.apache.org/jira/browse/IGNITE-5681
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
>  Labels: test-fail
> Fix For: 2.1
>
>
> This is a regression introduced during persistent store migration.
> {code}
> [2017-07-04 11:20:46,993][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteException: Failed to update keys (retry update 
> if possible).: [GridCacheQueueHeaderKey [name=q-3]]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
>   at org.apache.ignite.internal.IgniteKernal.queue(IgniteKernal.java:3648)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:164)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testFailoverWithClient(IgniteAtomicLongChangingTopologySelfTest.java:221)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover(IgniteAtomicLongChangingTopologySelfTest.java:155)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [GridCacheQueueHeaderKey 
> [name=q-3]]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:398)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onNodeLeft(GridNearAtomicSingleUpdateFuture.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$4.onEvent(GridCacheMvccManager.java:266)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager$LocalListenerWrapper.onEvent(GridEventStorageManager.java:1353)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:895)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record0(GridEventStorageManager.java:344)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:311)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2401)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2598)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2430)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   ... 1 more
>   Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> update keys on primary node.
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.UpdateErrors.addFailedKeys(UpdateErrors.java:124)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateResponse.addFailedKeys(GridNearAtomicUpdateResponse.java:342)
>   at 
> 

[jira] [Commented] (IGNITE-5686) Endless partition eviction during node shutdown

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-5686:
--

[~agoncharuk], could you look at the changes?

> Endless partition eviction during node shutdown
> ---
>
> Key: IGNITE-5686
> URL: https://issues.apache.org/jira/browse/IGNITE-5686
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Igor Seliverstov
> Fix For: 2.2
>
> Attachments: dump.txt
>
>
> Observed the following behavior on TC:
> A node cannot stop because system threads are continuously trying to clean 
> partitions.
> http://ci.ignite.apache.org/viewLog.html?buildId=702633=Ignite20Tests_IgniteRdd=buildResultsDiv
> Attached is a thread dump from the test



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

[jira] [Updated] (IGNITE-5688) Fix SparseDistributedMatrixTest::testCacheBehaviour crash

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5688:
---
Component/s: ml

> Fix SparseDistributedMatrixTest::testCacheBehaviour crash
> -
>
> Key: IGNITE-5688
> URL: https://issues.apache.org/jira/browse/IGNITE-5688
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.0
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>  Labels: test-fail
> Fix For: 2.1
>
>
> SparseDistributedMatrixTest::testCacheBehaviour crashed because of wrong 
> checks of cache behaviour.



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

[jira] [Updated] (IGNITE-5688) Fix SparseDistributedMatrixTest::testCacheBehaviour crash

[Artem Malykh (JIRA)]

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

Artem Malykh updated IGNITE-5688:
-
Description: SparseDistributedMatrixTest::testCacheBehaviour crashed 
because of wrong checks of cache behaviour.

> Fix SparseDistributedMatrixTest::testCacheBehaviour crash
> -
>
> Key: IGNITE-5688
> URL: https://issues.apache.org/jira/browse/IGNITE-5688
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>  Labels: test-fail
> Fix For: 2.1
>
>
> SparseDistributedMatrixTest::testCacheBehaviour crashed because of wrong 
> checks of cache behaviour.



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

[jira] [Issue Comment Deleted] (IGNITE-5688) Fix SparseDistributedMatrixTest::testCacheBehaviour crash

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-5688:
---
Comment: was deleted

(was: https://github.com/gridgain/apache-ignite/pull/77 -- patch)

> Fix SparseDistributedMatrixTest::testCacheBehaviour crash
> -
>
> Key: IGNITE-5688
> URL: https://issues.apache.org/jira/browse/IGNITE-5688
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.0
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>  Labels: test-fail
> Fix For: 2.1
>
>
> SparseDistributedMatrixTest::testCacheBehaviour crashed because of wrong 
> checks of cache behaviour.



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

[jira] [Assigned] (IGNITE-5551) Optimize service deployment assignments object

[Alexey Kukushkin (JIRA)]

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

Alexey Kukushkin reassigned IGNITE-5551:


Assignee: Alexey Kukushkin

> Optimize service deployment assignments object
> --
>
> Key: IGNITE-5551
> URL: https://issues.apache.org/jira/browse/IGNITE-5551
> Project: Ignite
>  Issue Type: Improvement
>  Components: managed services
>Affects Versions: 1.7
>Reporter: Alexey Goncharuk
>Assignee: Alexey Kukushkin
>Priority: Critical
> Fix For: 2.2
>
>
> 1) The deployment assignment is stored using a map [node ID -> number of 
> assigned services]. However, this assignment is not very effective for cases 
> when service configuration is (maxPerCluster = 0, maxPerNode > 0), because in 
> this case, we can avoid assignment recalculation at all. The assignment for 
> this case may look like (eachNode=N). In this case, the assignment does not 
> change and we can effectively skip it during the reassign loop.
> 2) We store zero assignment counters, which does not make sense at all - if 
> there are no service deployments for a node, there should be no corresponding 
> entry in the map at all. The size of assignments for (maxPerCluster > 0) 
> configurations is O(number of nodes in the cluster), but it should be 
> O(maxPerCluster).
> 3) If an assignment did not change, we should not commit the assignment 
> transaction - this is redundant
> 4) Perhaps, it also makes sense to calculate several assignments at once and 
> do a putAll commit instead of single puts - this should also decrease the 
> assignment calculation latency



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

[jira] [Commented] (IGNITE-5491) .NET: PersistentStoreMetrics

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5491:


Merged to ignite-2.1: {{b085fa0db67f8cda01e6927715241b10ac43c0f2}}

> .NET: PersistentStoreMetrics
> 
>
> Key: IGNITE-5491
> URL: https://issues.apache.org/jira/browse/IGNITE-5491
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> * {{PersistentStoreConfiguration.EnableMetrics}}, {{RateTimeInterval}}, 
> {{SubIntervals}} properties
> * {{PersistenceMetrics}} class
> * {{IIgnite.GetPersistenceMetrics()}} method



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

[jira] [Resolved] (IGNITE-5491) .NET: PersistentStoreMetrics

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-5491.

Resolution: Fixed

> .NET: PersistentStoreMetrics
> 
>
> Key: IGNITE-5491
> URL: https://issues.apache.org/jira/browse/IGNITE-5491
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> * {{PersistentStoreConfiguration.EnableMetrics}}, {{RateTimeInterval}}, 
> {{SubIntervals}} properties
> * {{PersistenceMetrics}} class
> * {{IIgnite.GetPersistenceMetrics()}} method



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

[jira] [Commented] (IGNITE-5688) Fix SparseDistributedMatrixTest::testCacheBehaviour crash

[Artem Malykh (JIRA)]

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

Artem Malykh commented on IGNITE-5688:
--

https://github.com/gridgain/apache-ignite/pull/77 -- patch

> Fix SparseDistributedMatrixTest::testCacheBehaviour crash
> -
>
> Key: IGNITE-5688
> URL: https://issues.apache.org/jira/browse/IGNITE-5688
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>  Labels: test-fail
> Fix For: 2.1
>
>




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

[jira] [Updated] (IGNITE-5505) @AffinityKeyMapped annotation is ignored if class names are configured on BinaryConfiguration

[Alexey Kukushkin (JIRA)]

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

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

> @AffinityKeyMapped annotation is ignored if class names are configured on 
> BinaryConfiguration
> -
>
> Key: IGNITE-5505
> URL: https://issues.apache.org/jira/browse/IGNITE-5505
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Alexey Kukushkin
> Fix For: 2.2
>
>
> {{@AffinityKeyMapped}} annotation on key class field is ignored in case when 
> class names passed to {{inaryConfiguration}} via {{setClassNames()}} method.
> The problem is that Ignite uses {{IgniteConfiguration.cacheKeyCfg}} during 
> {{BinaryContext.configure()}} execution and doesn't check class fileds on 
> {{@AffinityKeyMapped}} annotation.
> Possible solution: check class fields on {{@AffinityKeyMapped}} annotation if 
> there is no any mapping for cache key type.



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

[jira] [Commented] (IGNITE-4901) Decrease logging level for DataStremer retry

[Alexey Kukushkin (JIRA)]

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

Alexey Kukushkin commented on IGNITE-4901:
--

Fix was approved, waiting for merge to master

> Decrease logging level for DataStremer retry 
> -
>
> Key: IGNITE-4901
> URL: https://issues.apache.org/jira/browse/IGNITE-4901
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.9
>Reporter: Nikolay Tikhonov
>Assignee: Alexey Kukushkin
>Priority: Trivial
>
> When topology are changed DataStreame log the following error message which 
> confused users. Need to decrease logging level for this case.
> {noformat}
> ERROR  Failed to execute compound future reducer: GridCompoundFuture [...] 
> class org.apache.ignite.IgniteCheckedException: DataStreamer request failed 
> [node=9d405934-eb78-4452-a3a8-fc44c3c61e76] 
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$Buffer.onResponse(DataStreamerImpl.java:1777)
>  
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$3.onMessage(DataStreamerImpl.java:335)
>  
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1080)
>  
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:708)
>  
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:101)
>  
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:671)
>  
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  
>   at java.lang.Thread.run(Thread.java:745) 
> Caused by: class org.apache.ignite.IgniteCheckedException: DataStreamer will 
> retry data transfer at stable topology [...] 
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.localUpdate(DataStreamProcessor.java:337)
>  
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:297)
>  
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:56)
>  
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:86)
>  
>   ... 7 more 
> {noformat}



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

[jira] [Updated] (IGNITE-5721) Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge allocation of org.apache.ignite.internal.binary.BinaryReaderExImpl instances

[Alexandr Fedotov (JIRA)]

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

Alexandr Fedotov updated IGNITE-5721:
-
Description: 
Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances 
in org.apache.ignite.internal.binary.BinaryUtils#doReadObject method.
Optimizing this point should reduce memory pressure.

An example of memory allocation in a read only scenario



  was:
Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances 
in org.apache.ignite.internal.binary.BinaryUtils#doReadObject method.
Optimizing this point should reduce memory pressure.




> Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
> allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances
> ---
>
> Key: IGNITE-5721
> URL: https://issues.apache.org/jira/browse/IGNITE-5721
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Alexandr Fedotov
>  Labels: 2.0
> Fix For: 2.2
>
>
> Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
> allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances 
> in org.apache.ignite.internal.binary.BinaryUtils#doReadObject method.
> Optimizing this point should reduce memory pressure.
> An example of memory allocation in a read only scenario



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

[jira] [Assigned] (IGNITE-5680) IgniteCacheP2pUnmarshallingTxErrorTest#testResponseMessageOnUnmarshallingFailed fails

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5680:
---

Assignee: Sergey Chugunov  (was: Dmitriy Govorukhin)

> IgniteCacheP2pUnmarshallingTxErrorTest#testResponseMessageOnUnmarshallingFailed
>  fails
> -
>
> Key: IGNITE-5680
> URL: https://issues.apache.org/jira/browse/IGNITE-5680
> Project: Ignite
>  Issue Type: Task
>  Components: cache, general
>Reporter: Vladimir Ozerov
>Assignee: Sergey Chugunov
>  Labels: test-fail
> Fix For: 2.1
>
>
> This is a regression introduced during persistent store migration.
> {code}
> class org.apache.ignite.IgniteException: Timeout of waiting for topology map 
> update [igniteInstanceName=cache.IgniteCacheP2pUnmarshallingTxErrorTest1, 
> cache=default, cacheId=1544803905, topVer=AffinityTopologyVersion [topVer=3, 
> minorTopVer=0], p=0, readVer=AffinityTopologyVersion [topVer=3, 
> minorTopVer=0], locNode=TcpDiscoveryNode 
> [id=14c9b23b-eb1c-48bb-a8c1-18b7c861, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47502], discPort=47502, order=3, intOrder=3, 
> lastExchangeTime=1499155944028, loc=true, ver=2.1.0#19700101-sha1:, 
> isClient=false]]
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:698)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:532)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:517)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:507)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:494)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheAbstractTest.startGrids(IgniteCacheAbstractTest.java:76)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheAbstractTest.beforeTestsStarted(IgniteCacheAbstractTest.java:65)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.setUp(GridAbstractTest.java:598)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.setUp(GridCommonAbstractTest.java:482)
>   at junit.framework.TestCase.runBare(TestCase.java:139)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
>   at 
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:117)
>   at 
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:262)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:84)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> {code}



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

[jira] [Reopened] (IGNITE-5688) Fix SparseDistributedMatrixTest::testCacheBehaviour crash

[Artem Malykh (JIRA)]

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

Artem Malykh reopened IGNITE-5688:
--

> Fix SparseDistributedMatrixTest::testCacheBehaviour crash
> -
>
> Key: IGNITE-5688
> URL: https://issues.apache.org/jira/browse/IGNITE-5688
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>  Labels: test-fail
> Fix For: 2.1
>
>




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

[jira] [Updated] (IGNITE-5721) Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge allocation of org.apache.ignite.internal.binary.BinaryReaderExImpl instances

[Alexandr Fedotov (JIRA)]

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

Alexandr Fedotov updated IGNITE-5721:
-
Description: 
Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances 
in org.apache.ignite.internal.binary.BinaryUtils#doReadObject method.
Optimizing this point should reduce memory pressure.

An example of memory allocation in a read only scenario
!mem-allocation1.png!



  was:
Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances 
in org.apache.ignite.internal.binary.BinaryUtils#doReadObject method.
Optimizing this point should reduce memory pressure.

An example of memory allocation in a read only scenario




> Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
> allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances
> ---
>
> Key: IGNITE-5721
> URL: https://issues.apache.org/jira/browse/IGNITE-5721
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Alexandr Fedotov
>  Labels: 2.0
> Fix For: 2.2
>
> Attachments: mem-allocation1.png
>
>
> Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
> allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances 
> in org.apache.ignite.internal.binary.BinaryUtils#doReadObject method.
> Optimizing this point should reduce memory pressure.
> An example of memory allocation in a read only scenario
> !mem-allocation1.png!



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

[jira] [Updated] (IGNITE-5721) Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge allocation of org.apache.ignite.internal.binary.BinaryReaderExImpl instances

[Alexandr Fedotov (JIRA)]

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

Alexandr Fedotov updated IGNITE-5721:
-
Description: 
Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances 
in org.apache.ignite.internal.binary.BinaryUtils#doReadObject method.
Optimizing this point should reduce memory pressure.

An example of memory allocation in a read-only scenario:

!mem-allocation1.png!



  was:
Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances 
in org.apache.ignite.internal.binary.BinaryUtils#doReadObject method.
Optimizing this point should reduce memory pressure.

An example of memory allocation in a read only scenario
!mem-allocation1.png!




> Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
> allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances
> ---
>
> Key: IGNITE-5721
> URL: https://issues.apache.org/jira/browse/IGNITE-5721
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Alexandr Fedotov
>  Labels: 2.0
> Fix For: 2.2
>
> Attachments: mem-allocation1.png
>
>
> Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
> allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances 
> in org.apache.ignite.internal.binary.BinaryUtils#doReadObject method.
> Optimizing this point should reduce memory pressure.
> An example of memory allocation in a read-only scenario:
> !mem-allocation1.png!



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

[jira] [Updated] (IGNITE-5721) Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge allocation of org.apache.ignite.internal.binary.BinaryReaderExImpl instances

[Alexandr Fedotov (JIRA)]

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

Alexandr Fedotov updated IGNITE-5721:
-
Attachment: mem-allocation1.png

> Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
> allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances
> ---
>
> Key: IGNITE-5721
> URL: https://issues.apache.org/jira/browse/IGNITE-5721
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Alexandr Fedotov
>  Labels: 2.0
> Fix For: 2.2
>
> Attachments: mem-allocation1.png
>
>
> Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
> allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances 
> in org.apache.ignite.internal.binary.BinaryUtils#doReadObject method.
> Optimizing this point should reduce memory pressure.
> An example of memory allocation in a read only scenario



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

[jira] [Created] (IGNITE-5721) Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge allocation of org.apache.ignite.internal.binary.BinaryReaderExImpl instances

[Alexandr Fedotov (JIRA)]

Alexandr Fedotov created IGNITE-5721:


 Summary: Calls to org.apache.ignite.IgniteCache#localPeek under 
high load lead to huge allocation of  
org.apache.ignite.internal.binary.BinaryReaderExImpl instances
 Key: IGNITE-5721
 URL: https://issues.apache.org/jira/browse/IGNITE-5721
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.0
Reporter: Alexandr Fedotov
 Fix For: 2.2


Calls to org.apache.ignite.IgniteCache#localPeek under high load lead to huge 
allocation of  org.apache.ignite.internal.binary.BinaryReaderExImpl instances 
in org.apache.ignite.internal.binary.BinaryUtils#doReadObject method.
Optimizing this point should reduce memory pressure.





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

[jira] [Assigned] (IGNITE-5682) GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5682:
---

Assignee: Sergey Chugunov  (was: Dmitriy Govorukhin)

> GridCacheRabalancingDelayedPartitionMapExchangeSelfTest fails
> -
>
> Key: IGNITE-5682
> URL: https://issues.apache.org/jira/browse/IGNITE-5682
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Sergey Chugunov
>  Labels: test-fail
> Fix For: 2.1
>
>
> This appears to be a regression introduced during persistent store migration. 
> {code}
> class org.apache.ignite.IgniteException: Timeout of waiting for topology map 
> update 
> [igniteInstanceName=rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest1,
>  cache=default, cacheId=1544803905, topVer=AffinityTopologyVersion 
> [topVer=10, minorTopVer=0], p=0, readVer=AffinityTopologyVersion [topVer=10, 
> minorTopVer=0], locNode=TcpDiscoveryNode 
> [id=c53cc66c-05ea-4441-825c-23d99ef1, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47501], discPort=47501, order=2, intOrder=2, 
> lastExchangeTime=1499156862204, loc=true, ver=2.1.0#19700101-sha1:, 
> isClient=false]]
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:698)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:532)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:517)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.rebalancing.GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.test(GridCacheRabalancingDelayedPartitionMapExchangeSelfTest.java:154)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Updated] (IGNITE-5280) SparseDistributedMatrix refactorig

[Yury Babak (JIRA)]

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

Yury Babak updated IGNITE-5280:
---
Fix Version/s: (was: 2.1)
   2.2

> SparseDistributedMatrix refactorig
> --
>
> Key: IGNITE-5280
> URL: https://issues.apache.org/jira/browse/IGNITE-5280
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.2
>
>
> We must refactor SparseDistributedMatrix for decrease communication during 
> computations.



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

[jira] [Commented] (IGNITE-5422) CREATE TABLE command should support all-key fields case

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-5422:
-

Too risky for {{2.1}}. Moving to {{2.2}}.

> CREATE TABLE command should support all-key fields case
> ---
>
> Key: IGNITE-5422
> URL: https://issues.apache.org/jira/browse/IGNITE-5422
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.2
>
>
> Currently it is impossible to create a table containing only {{PRIMARY KEY}} 
> columns:
> {code}
> CREATE TABLE PersonProject {
> person_id BIGINT,
> project_id BIGINT,
> PRIMARY KEY (person_id, project_id);
> };
> {code}
> The reason for this limitation is that we have nothing to be saved as cache 
> value and {{null}} values are restricted because they are indistinguishable 
> from removal.
> We should allow this case somehow. Possible solutions:
> 1) Save empty object of table type: 
> {{IgniteBinary.builder("PersonProject").build()}}
> 2) Save {{false}} as it is done in Java in Map-to-Set conversion
> Note that DML processing should be adjusted accordingly.



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

[jira] [Updated] (IGNITE-5422) CREATE TABLE command should support all-key fields case

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5422:

Fix Version/s: (was: 2.1)
   2.2

> CREATE TABLE command should support all-key fields case
> ---
>
> Key: IGNITE-5422
> URL: https://issues.apache.org/jira/browse/IGNITE-5422
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
> Fix For: 2.2
>
>
> Currently it is impossible to create a table containing only {{PRIMARY KEY}} 
> columns:
> {code}
> CREATE TABLE PersonProject {
> person_id BIGINT,
> project_id BIGINT,
> PRIMARY KEY (person_id, project_id);
> };
> {code}
> The reason for this limitation is that we have nothing to be saved as cache 
> value and {{null}} values are restricted because they are indistinguishable 
> from removal.
> We should allow this case somehow. Possible solutions:
> 1) Save empty object of table type: 
> {{IgniteBinary.builder("PersonProject").build()}}
> 2) Save {{false}} as it is done in Java in Map-to-Set conversion
> Note that DML processing should be adjusted accordingly.



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

[jira] [Commented] (IGNITE-5684) IgniteClientCacheStartFailoverTest.testClientStartLastServerFails* fails

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5684:


GitHub user Jokser opened a pull request:

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

IGNITE-5684 Remove FullMap stale updates check



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

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

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

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

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

This closes #2271


commit ab5267134966b466a2d4bfba15d0c7e3ebe91139
Author: sboikov 
Date:   2017-07-07T10:14:18Z

2.1 More simple tx cancel on node stop

commit 85d8c6572d78c7d6796906d92b566e2fa5b116be
Author: Dmitriy Govorukhin 
Date:   2017-07-07T10:13:55Z

IGNITE-5520 - Fixed IgniteChangeGlobalStateFailoverTest

commit f589628f4846f14efc8e702b61856cc90a3d0dc7
Author: sboikov 
Date:   2017-07-07T10:52:38Z

Rename ActionData -> CacheActionData.

commit 30922ed8ac518749a2559aff51fe183a890041bb
Author: Alexey Kuznetsov 
Date:   2017-07-07T11:03:18Z

ignite-2.1 Added map with previous snapshots.

commit 99fd75dd7766318af88a38b5640a648bba3ccdf1
Author: Sergey Kalashnikov 
Date:   2017-07-07T11:38:36Z

IGNITE-5483: Added limited support for Java8 LocalDateTime. This closes 
#2248.

commit 4fc8124d9538625cb0a95c918634b43ec1319bee
Author: sboikov 
Date:   2017-07-07T11:43:28Z

Fixed formatting.

commit 984ab5bd3c08b2af9222964451acc281b92814b8
Author: sboikov 
Date:   2017-07-07T11:43:50Z

Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2

commit 7adb11109bab5d83ed4f376b0cad42b026dd0a71
Author: sboikov 
Date:   2017-07-07T11:49:13Z

Fixed formatting.

commit 2a5390b1c083819f059e449b34a5979ec35b7755
Author: Alexander Paschenko 
Date:   2017-07-07T12:01:43Z

IGNITE-5159: DDL example. This closes #2227.

commit d232648711c882ed304eae89ae19f151067649fd
Author: devozerov 
Date:   2017-07-07T12:02:29Z

Merge remote-tracking branch 'upstream/ignite-2.1.2' into ignite-2.1.2

commit a9387adef490086406b05fe961ff0f3151045caa
Author: Pavel Tupitsyn 
Date:   2017-07-07T12:21:20Z

IGNITE-5717 .NET: Reduce MemoryPolicyConfiguration.MaxSize for persistence 
tests as a workaround for OOM on default settings

commit 13399d530f3458c3bf59634857cb05f801e8cc34
Author: sboikov 
Date:   2017-07-07T12:24:09Z

2.1 Fixed assert (cacheName can be null here).

commit ea4420e6aad509c4ae58d6d0880918c98fd1959a
Author: sboikov 
Date:   2017-07-07T12:24:26Z

Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2

commit 0d6fb1ad73e8ed448dabe7c0cc631222835b52c4
Author: Sergey Kalashnikov 
Date:   2017-07-07T12:54:52Z

IGNITE-5204: Fixed NPE on certain data with index inlining. This closes 
#2115.

commit a1cac1b7cc1c3afdcc12afb08bf1ecdcb6f28828
Author: sboikov 
Date:   2017-07-07T12:55:18Z

Removed unused method GridDhtPartitionTopology.checkEvictions().

commit 55a5ca019db7d06aab2fb567dbc0da1f133d0fb7
Author: sboikov 
Date:   2017-07-07T12:55:38Z

Merge remote-tracking branch 'community/ignite-2.1.2' into ignite-2.1.2

commit 99713feea764fc8c3e5b247a24698a2c04d3bcf4
Author: Sergey Kalashnikov 
Date:   2017-07-07T13:30:37Z

IGNITE-5204: SQL: fixed incorrect partition calculation in case of unicast 
optimization, when WHERE clause argument type was different from key or 
affinity key type. This close #2107.

commit 3c887378eb64d2d236073410070082e5699e8334
Author: Igor Sapego 
Date:   2017-07-07T13:52:31Z

IGNITE-5582: Implemented Compute::Broadcast for C++

(cherry picked from commit fa974286e8f066a8d6aa57519edf5ec7761be095)

commit 3314a4513c816c027dad80258ded1fe5a4c2b700
Author: sboikov 
Date:   2017-07-07T14:28:47Z

Fixed cache plugin validation.

commit 517a23d252078e62a8addca55ca78497e5226b5b
Author: mcherkasov 
Date:   2017-06-30T17:23:55Z

IGNITE-5554 ServiceProcessor may process failed reassignments in timeout 
thread

commit 993f7fbe1d49a524e2dee626aef72e16fd5d3cda
Author: Ilya Lantukh 
Date:   2017-07-07T15:55:27Z

IGNITE-5701 - Some nodes have partitionUpdateCounter equal to 0 after 
rebalancing

commit 

[jira] [Commented] (IGNITE-5087) Enum comparison fails after marshal-unmarshal with BinaryMarshaller.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-5087:
--

Great! 
TC tests looks fine. Can be merged.

[~NSAmelchev], thanks for contribution.

> Enum comparison fails after marshal-unmarshal with BinaryMarshaller.
> 
>
> Key: IGNITE-5087
> URL: https://issues.apache.org/jira/browse/IGNITE-5087
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Assignee: Amelchev Nikita
> Fix For: 2.2
>
> Attachments: EnumBinaryMarshallerBug.java
>
>
> PFA repro.
> It fails on 1.9 and on 2.0-snapshot as well.



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

[jira] [Commented] (IGNITE-5505) @AffinityKeyMapped annotation is ignored if class names are configured on BinaryConfiguration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5505:


GitHub user kukushal opened a pull request:

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

IGNITE-5505 @AffinityKeyMapped annotation is ignored if class names are 
configured on BinaryConfiguration



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

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

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

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

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

This closes #2270


commit c0a0e1340d3576b9880eaf9c9ad431cde85e5429
Author: Alexey Kukushkin 
Date:   2017-07-07T15:54:39Z

test for IGNITE-5505

commit 67e1457d4fd62bbd5004a60a8d3e1799b4125c9a
Author: Alexey Kukushkin 
Date:   2017-07-07T16:49:23Z

Fix code style

commit 5023ff50fb461d37fb2b05a7c8a01fc6091028ba
Author: Alexey Kukushkin 
Date:   2017-07-10T10:44:49Z

Solution for IGNITE-5505




> @AffinityKeyMapped annotation is ignored if class names are configured on 
> BinaryConfiguration
> -
>
> Key: IGNITE-5505
> URL: https://issues.apache.org/jira/browse/IGNITE-5505
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Alexey Kukushkin
>
> {{@AffinityKeyMapped}} annotation on key class field is ignored in case when 
> class names passed to {{inaryConfiguration}} via {{setClassNames()}} method.
> The problem is that Ignite uses {{IgniteConfiguration.cacheKeyCfg}} during 
> {{BinaryContext.configure()}} execution and doesn't check class fileds on 
> {{@AffinityKeyMapped}} annotation.
> Possible solution: check class fields on {{@AffinityKeyMapped}} annotation if 
> there is no any mapping for cache key type.



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

[jira] [Assigned] (IGNITE-5592) Remove IgniteCache#localEvict method

[Aleksandr Meterko (JIRA)]

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

Aleksandr Meterko reassigned IGNITE-5592:
-

Assignee: (was: Aleksandr Meterko)

> Remove IgniteCache#localEvict method
> 
>
> Key: IGNITE-5592
> URL: https://issues.apache.org/jira/browse/IGNITE-5592
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
> Fix For: 2.2
>
>
> The method doesn't make much sense in 2.0. Before 2.0 it could be used to 
> evict from on-heap memory to off-heap or swap. Currently off-heap always has 
> the data and there is no swap, so the method should be removed to avoid 
> confusion.



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

[jira] [Commented] (IGNITE-5681) IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover fails

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-5681:


This test seems to be passing for 2.1.2 now
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-7561430903306738928=testDetails_Ignite20Tests=pull%2F2251%2Fhead

Locally passed 18+ times

> IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover 
> fails
> -
>
> Key: IGNITE-5681
> URL: https://issues.apache.org/jira/browse/IGNITE-5681
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Pavlov
>  Labels: test-fail
> Fix For: 2.1
>
>
> This is a regression introduced during persistent store migration.
> {code}
> [2017-07-04 11:20:46,993][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteException: Failed to update keys (retry update 
> if possible).: [GridCacheQueueHeaderKey [name=q-3]]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:957)
>   at org.apache.ignite.internal.IgniteKernal.queue(IgniteKernal.java:3648)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:164)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest$2.apply(IgniteAtomicLongChangingTopologySelfTest.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testFailoverWithClient(IgniteAtomicLongChangingTopologySelfTest.java:221)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.IgniteAtomicLongChangingTopologySelfTest.testClientQueueCreateCloseFailover(IgniteAtomicLongChangingTopologySelfTest.java:155)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.processors.cache.CachePartialUpdateCheckedException:
>  Failed to update keys (retry update if possible).: [GridCacheQueueHeaderKey 
> [name=q-3]]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicAbstractUpdateFuture.onPrimaryError(GridNearAtomicAbstractUpdateFuture.java:398)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicSingleUpdateFuture.onNodeLeft(GridNearAtomicSingleUpdateFuture.java:155)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMvccManager$4.onEvent(GridCacheMvccManager.java:266)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager$LocalListenerWrapper.onEvent(GridEventStorageManager.java:1353)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.notifyListeners(GridEventStorageManager.java:895)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record0(GridEventStorageManager.java:344)
>   at 
> org.apache.ignite.internal.managers.eventstorage.GridEventStorageManager.record(GridEventStorageManager.java:311)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.recordEvent(GridDiscoveryManager.java:2401)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body0(GridDiscoveryManager.java:2598)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryWorker.body(GridDiscoveryManager.java:2430)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   ... 1 more
>   Suppressed: class org.apache.ignite.IgniteCheckedException: Failed to 
> update keys on primary node.
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.UpdateErrors.addFailedKeys(UpdateErrors.java:124)
>   at 
> 

[jira] [Assigned] (IGNITE-425) Introduce transformers for continuous queries

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov reassigned IGNITE-425:
--

Assignee: Nikolay Izhikov

> Introduce transformers for continuous queries
> -
>
> Key: IGNITE-425
> URL: https://issues.apache.org/jira/browse/IGNITE-425
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Izhikov
>
> Currently if updated entry passes the filter, it is sent to node initiated 
> the query entirely. It would be good to provide user with the ability to 
> transform entry and, for example, select only fields that are important. This 
> may bring huge economy to traffic and lower GC pressure as well.
> Possible signatures will be:
> {noformat}
> public final class ContinuousQuery {..} // T is a type transformer 
> transforms to
> public ContinuousQuery setLocalListener(Listener locLsnr) {..} // 
> Probably, we will have to introduce new listener type, since user may want to 
> wipe out key as well.
> /* new method to add */
> public ContinuousQuery setRemoteTransformerFactory(Factory ContinuousQueryTransformer> factory) { ..}
> {noformat}



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

[jira] [Assigned] (IGNITE-5680) IgniteCacheP2pUnmarshallingTxErrorTest#testResponseMessageOnUnmarshallingFailed fails

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5680:
---

Assignee: Dmitriy Govorukhin  (was: Alexey Goncharuk)

> IgniteCacheP2pUnmarshallingTxErrorTest#testResponseMessageOnUnmarshallingFailed
>  fails
> -
>
> Key: IGNITE-5680
> URL: https://issues.apache.org/jira/browse/IGNITE-5680
> Project: Ignite
>  Issue Type: Task
>  Components: cache, general
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Govorukhin
>  Labels: test-fail
> Fix For: 2.1
>
>
> This is a regression introduced during persistent store migration.
> {code}
> class org.apache.ignite.IgniteException: Timeout of waiting for topology map 
> update [igniteInstanceName=cache.IgniteCacheP2pUnmarshallingTxErrorTest1, 
> cache=default, cacheId=1544803905, topVer=AffinityTopologyVersion [topVer=3, 
> minorTopVer=0], p=0, readVer=AffinityTopologyVersion [topVer=3, 
> minorTopVer=0], locNode=TcpDiscoveryNode 
> [id=14c9b23b-eb1c-48bb-a8c1-18b7c861, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47502], discPort=47502, order=3, intOrder=3, 
> lastExchangeTime=1499155944028, loc=true, ver=2.1.0#19700101-sha1:, 
> isClient=false]]
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:698)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:532)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.awaitPartitionMapExchange(GridCommonAbstractTest.java:517)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:507)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.startGridsMultiThreaded(GridCommonAbstractTest.java:494)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheAbstractTest.startGrids(IgniteCacheAbstractTest.java:76)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheAbstractTest.beforeTestsStarted(IgniteCacheAbstractTest.java:65)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.setUp(GridAbstractTest.java:598)
>   at 
> org.apache.ignite.testframework.junits.common.GridCommonAbstractTest.setUp(GridCommonAbstractTest.java:482)
>   at junit.framework.TestCase.runBare(TestCase.java:139)
>   at junit.framework.TestResult$1.protect(TestResult.java:122)
>   at junit.framework.TestResult.runProtected(TestResult.java:142)
>   at junit.framework.TestResult.run(TestResult.java:125)
>   at junit.framework.TestCase.run(TestCase.java:129)
>   at junit.framework.TestSuite.runTest(TestSuite.java:255)
>   at junit.framework.TestSuite.run(TestSuite.java:250)
>   at 
> org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
>   at org.junit.runner.JUnitCore.run(JUnitCore.java:160)
>   at 
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:117)
>   at 
> com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:42)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:262)
>   at 
> com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:84)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:497)
>   at com.intellij.rt.execution.application.AppMain.main(AppMain.java:147)
> {code}



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

[jira] [Updated] (IGNITE-5432) Test IgniteMarshallerCacheClassNameConflictTest failed

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5432:

Fix Version/s: (was: 2.1)
   2.2

>  Test IgniteMarshallerCacheClassNameConflictTest failed
> ---
>
> Key: IGNITE-5432
> URL: https://issues.apache.org/jira/browse/IGNITE-5432
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Alexey Ivanov
>Assignee: Alexey Ivanov
> Fix For: 2.2
>
>
> Test suit:
> IgniteBinarySimpleNameMapperBasicTestSuite
> Test:
> IgniteMarshallerCacheClassNameConflictTest



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

[jira] [Updated] (IGNITE-5432) Test IgniteMarshallerCacheClassNameConflictTest failed

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5432:

Fix Version/s: (was: 2.1)
   2.2

>  Test IgniteMarshallerCacheClassNameConflictTest failed
> ---
>
> Key: IGNITE-5432
> URL: https://issues.apache.org/jira/browse/IGNITE-5432
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Alexey Ivanov
>Assignee: Alexey Ivanov
> Fix For: 2.2
>
>
> Test suit:
> IgniteBinarySimpleNameMapperBasicTestSuite
> Test:
> IgniteMarshallerCacheClassNameConflictTest



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

[jira] [Updated] (IGNITE-5432) Test IgniteMarshallerCacheClassNameConflictTest failed

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5432:

Fix Version/s: (was: 2.2)
   2.1

>  Test IgniteMarshallerCacheClassNameConflictTest failed
> ---
>
> Key: IGNITE-5432
> URL: https://issues.apache.org/jira/browse/IGNITE-5432
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
>Reporter: Alexey Ivanov
>Assignee: Alexey Ivanov
> Fix For: 2.1
>
>
> Test suit:
> IgniteBinarySimpleNameMapperBasicTestSuite
> Test:
> IgniteMarshallerCacheClassNameConflictTest



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

[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5097:


.NET part looks good to me.

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important, performance
> Fix For: 2.2
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



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