[jira] [Commented] (IGNITE-6333) Improve cache transaction metrics to better understand transactions efficiency.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6333:


GitHub user xtern reopened a pull request:

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

IGNITE-6333 Improve cache transaction metrics to better understand 
transactions efficiency.



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

$ git pull https://github.com/xtern/ignite IGNITE-6333

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

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


commit 78b312d73c947cd62af787838ce42fecf96f87d3
Author: Pereslegin Pavel 
Date:   2017-11-20T18:31:10Z

IGNITE-6333 Added rollbacks due to deadlock/timeout tx metrics.

commit 0dd91820e5bf017d408ff364cd3906d69b76df30
Author: Pereslegin Pavel 
Date:   2017-12-11T20:48:26Z

IGNITE-6333 Removed unrelated changes, fixed test code style.

commit 3c0c2153bbc753eac88bc99f6dde00108397c219
Author: Pavel Pereslegin <30606288+xt...@users.noreply.github.com>
Date:   2017-12-12T07:56:29Z

IGNITE-6333 Wrong Jira issue.




> Improve cache transaction metrics to better understand transactions 
> efficiency.
> ---
>
> Key: IGNITE-6333
> URL: https://issues.apache.org/jira/browse/IGNITE-6333
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Alexei Scherbakov
>Assignee: Pavel Pereslegin
>  Labels: cache, newbie
>
> I suggest to add:
> 1. Count of rollbacks due to transaction timeout. Depends on IGNITE-6181
> 2. Count of rollbacks due to deadlocks.



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

[jira] [Commented] (IGNITE-6333) Improve cache transaction metrics to better understand transactions efficiency.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6333:


Github user xtern closed the pull request at:

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


> Improve cache transaction metrics to better understand transactions 
> efficiency.
> ---
>
> Key: IGNITE-6333
> URL: https://issues.apache.org/jira/browse/IGNITE-6333
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Alexei Scherbakov
>Assignee: Pavel Pereslegin
>  Labels: cache, newbie
>
> I suggest to add:
> 1. Count of rollbacks due to transaction timeout. Depends on IGNITE-6181
> 2. Count of rollbacks due to deadlocks.



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

[jira] [Created] (IGNITE-7179) Create events for cluster activation/deactivation

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-7179:
---

 Summary: Create events for cluster activation/deactivation
 Key: IGNITE-7179
 URL: https://issues.apache.org/jira/browse/IGNITE-7179
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 2.3
Reporter: Valentin Kulichenko






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

[jira] [Updated] (IGNITE-7179) Create events for cluster activation/deactivation

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko updated IGNITE-7179:

Description: It would be great to have a distributed system event (similar 
to discovery vents) fired when cluster is activated or deactivated.

> Create events for cluster activation/deactivation
> -
>
> Key: IGNITE-7179
> URL: https://issues.apache.org/jira/browse/IGNITE-7179
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.3
>Reporter: Valentin Kulichenko
>
> It would be great to have a distributed system event (similar to discovery 
> vents) fired when cluster is activated or deactivated.



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

[jira] [Assigned] (IGNITE-7172) Web console: Add example to queries page

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-7172:


Assignee: Andrey Novikov  (was: Ilya Borisov)

[~anovikov] I've fixed the CSS issues, please review.

> Web console: Add example to queries page
> 
>
> Key: IGNITE-7172
> URL: https://issues.apache.org/jira/browse/IGNITE-7172
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
> Attachments: screenshot-1.png
>
>




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

[jira] [Comment Edited] (IGNITE-7172) Web console: Add example to queries page

[Ilya Borisov (JIRA)]

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

Ilya Borisov edited comment on IGNITE-7172 at 12/13/17 4:20 AM:


I've attached a screenshot of what the example block should look like. There 
are other minor CSS issues too:
1. -"Example" label lacks background and is positioned slightly off vertically.-
2. -Bottom of the example block does not clips child content (border-radiuses 
don't match).-


was (Author: klaster_1):
I've attached a screenshot of what the example block should look like. There 
are other minor CSS issues too:
1. "Example" label lacks background and is positioned slightly off vertically.
2. Bottom of the example block does not clips child content (border-radiuses 
don't match).

> Web console: Add example to queries page
> 
>
> Key: IGNITE-7172
> URL: https://issues.apache.org/jira/browse/IGNITE-7172
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
> Attachments: screenshot-1.png
>
>




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

[jira] [Commented] (IGNITE-7172) Web console: Add example to queries page

[Ilya Borisov (JIRA)]

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

Ilya Borisov commented on IGNITE-7172:
--

I've attached a screenshot of what the example block should look like. There 
are other minor CSS issues too:
1. "Example" label lacks background and is positioned slightly off vertically.
2. Bottom of the example block does not clips child content (border-radiuses 
don't match).

> Web console: Add example to queries page
> 
>
> Key: IGNITE-7172
> URL: https://issues.apache.org/jira/browse/IGNITE-7172
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitriy Shabalin
>Assignee: Ilya Borisov
> Attachments: screenshot-1.png
>
>




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

[jira] [Commented] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6976:


Date format wasn't be recognized. I tried d/m/yyy and dd/mm/  with and w\o 
time.


> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




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

[jira] [Assigned] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-6976:
--

Assignee: Vasiliy Sisko  (was: Pavel Konstantinov)

> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>




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

[jira] [Updated] (IGNITE-7172) Web console: Add example to queries page

[Ilya Borisov (JIRA)]

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

Ilya Borisov updated IGNITE-7172:
-
Attachment: screenshot-1.png

> Web console: Add example to queries page
> 
>
> Key: IGNITE-7172
> URL: https://issues.apache.org/jira/browse/IGNITE-7172
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitriy Shabalin
>Assignee: Ilya Borisov
> Attachments: screenshot-1.png
>
>




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

[jira] [Assigned] (IGNITE-7172) Web console: Add example to queries page

[Andrey Novikov (JIRA)]

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

Andrey Novikov reassigned IGNITE-7172:
--

Assignee: Ilya Borisov  (was: Andrey Novikov)

> Web console: Add example to queries page
> 
>
> Key: IGNITE-7172
> URL: https://issues.apache.org/jira/browse/IGNITE-7172
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitriy Shabalin
>Assignee: Ilya Borisov
>




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

[jira] [Commented] (IGNITE-7172) Web console: Add example to queries page

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-7172:


Reviewed. Please fix following notes and then merge: 
# Remove blue color from information icon
# Use solid border style

> Web console: Add example to queries page
> 
>
> Key: IGNITE-7172
> URL: https://issues.apache.org/jira/browse/IGNITE-7172
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
>




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

[jira] [Commented] (IGNITE-3084) Spark Data Frames Support in Apache Ignite

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-3084:
-

[~NIzhikov], I'm doing the review and have several questions/comments (probably 
more to come, but wanted to keep you updated).
# {{IgniteRelationProvider}} looks a bit overcomplicated. I think we should 
leave only {{IGNITE}}, {{CONFIG_FILE}}, {{TABLE}} options and also add 
{{CONFIG}} to allow providing {{IgniteConfiguration}} object. {{GRID}}, 
{{TCP_IP_ADDRESSES}} and {{PEER_CLASS_LOADING}} should be removed. Others are 
related to non-SQL use case which I'm not sure about, let's discuss it 
separately.
# {{IgniteRelationProvider}} always created {{IgniteContext}} in embedded mode 
({{standalone=false}}). Let's set this flag to {{true}} instead, embedded mode 
will be deprecated in 2.4 anyway.
# What is the purpose of implementing {{onApplicationEnd}}? When exactly is it 
invoked? If it's needed, should it be on {{IgniteContext}} level instead?
# {{IgniteSQLRelation}} lines 74-76 are not used, can they be removed?
# {{IgniteSQLRelation#sqlCacheName}} looks incorrect as it assumes that cache 
is created via DDL. This is not always the case.
# What is the purpose of {{IgniteSQLRelation#calcPartitions}} method? Can you 
please explain what it does and how it works?
# Why {{*Relation}}, {{IgniteRelationProvider}} and {{package.scala}} are in 
public package? It seems that user never accesses them directly; if that's the 
case, let's move them to {{impl}} package.
# I'm not sure I understand the value of custom catalog implementation. Can you 
please elaborate what exactly it provides to a user?
# {{IgniteCacheRelation}} is questionable. Main problem is that it works with 
classes which are not always available. Also what if schema is dynamic, how are 
we going to support it? I think it's better to support data frames only via 
Ignite SQL, unless we come up with a cleaner solution. Let me know what you 
think.

> Spark Data Frames Support in Apache Ignite
> --
>
> Key: IGNITE-3084
> URL: https://issues.apache.org/jira/browse/IGNITE-3084
> Project: Ignite
>  Issue Type: Task
>  Components: spark
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Izhikov
>Priority: Critical
>  Labels: bigdata, important
> Fix For: 2.4
>
>
> Apache Spark already benefits from integration with Apache Ignite. The latter 
> provides shared RDDs, an implementation of Spark RDD, that help Spark to 
> share a state between Spark workers and execute SQL queries much faster. The 
> next logical step is to enable support for modern Spark Data Frames API in a 
> similar way.
> As a contributor, you will be fully in charge of the integration of Spark 
> Data Frame API and Apache Ignite.



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

[jira] [Closed] (IGNITE-7178) Ignite fails to start on non x86/64 architectures

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-7178.
---

> Ignite fails to start on non x86/64 architectures
> -
>
> Key: IGNITE-7178
> URL: https://issues.apache.org/jira/browse/IGNITE-7178
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Denis Magda
>Assignee: Yakov Zhdanov
>Priority: Blocker
> Fix For: 2.4
>
>
> Ignite fails with the exception below on AIX and Solar Spark. Most likely 
> because of the bug that pops up on big-endian and non x86/64 CPU 
> architectures:
> {code}
> ERROR 2017-11-02 11:59:01.331 [grid-nio-worker-tcp-comm-1-#22]
> org.apache.ignite.internal.util.nio.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=16841 lim=16844 cap=32768],
> reader=DirectMessageReader [state=DirectMessageState [pos=0,
> stack=[StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
> msgTypeDone=true, msg=GridDhtPartitionsFullMessage [parts=null,
> partCntrs=null, partCntrs2=null, partHistSuppliers=null, partsToReload=null,
> topVer=null, errs=null, compress=false, resTopVer=null, partCnt=0,
> super=GridDhtPartitionsAbstractMessage [exchId=GridDhtPartitionExchangeId
> [topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0], discoEvt=null,
> nodeId=e3ac3f40, evt=NODE_JOINED], lastVer=GridCacheVersion [topVer=0,
> order=1509612963224, nodeOrder=0], super=GridCacheMessage [msgId=369,
> depInfo=null, err=null, skipPrepare=false]]], 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], StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
> msgTypeDone=true, msg=CacheGroupAffinityMessage [], mapIt=null, it=null,
> arrPos=-1, keyDone=true, readSize=7, readItems=2, prim=0, primShift=0,
> uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true],
> state=0], StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
> msgTypeDone=true, msg=GridLongList [idx=0, arr=[]], mapIt=null, it=null,
> arrPos=-1, keyDone=false, readSize=512, readItems=47, prim=0, primShift=0,
> uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true],
> state=0], StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=1100144027456, arrOff=-1, tmpArrOff=40, tmpArrBytes=40,
> 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]], lastRead=true], ses=GridSelectorNioSessionImpl
> [worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=1,
> bytesRcvd=404253, bytesSent=1989, bytesRcvd0=16886, bytesSent0=28,
> select=true, super=GridWorker [name=grid-nio-worker-tcp-comm-1,
> igniteInstanceName=null, finished=false, hashCode=-2134841549,
> interrupted=false, runner=grid-nio-worker-tcp-comm-1-#22]]],
> writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
> readBuf=java.nio.DirectByteBuffer[pos=16841 lim=16844 cap=32768],
> inRecovery=GridNioRecoveryDescriptor [acked=6, resendCnt=0, rcvCnt=0,
> sentCnt=6, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
> [id=7683662b-16c9-42b7-aa0d-8328a60fc58e, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:6250], discPort=6250, order=1, intOrder=1,
> lastExchangeTime=1509612963744, loc=false, ver=2.3.0#20171028-sha1:8add7fd5,
> isClient=false], connected=true, connectCnt=11, queueLimit=131072,
> reserveCnt=175, pairedConnections=false],
> outRecovery=GridNioRecoveryDescriptor [acked=6, resendCnt=0, rcvCnt=0,
> sentCnt=6, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
> [id=7683662b-16c9-42b7-aa0d-8328a60fc58e, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:6250], discPort=6250, order=1, intOrder=1,
> lastExchangeTime=1509612963744, loc=false, ver=2.3.0#20171028-sha1:8add7fd5,
> isClient=false], connected=true, connectCnt=11, queueLimit=131072,
> reserveCnt=175, pairedConnections=false], super=GridNioSessionImpl
> [locAddr=/127.0.0.1:6284, rmtAddr=/127.0.0.1:61790,
> createTime=1509613141318, closeTime=0, bytesSent=28, bytesRcvd=16886,
> bytesSent0=28, bytesRcvd0=16886, sndSchedTime=1509613141318,
> lastSndTime=1509613141318, lastRcvTime=1509613141318, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioCodecFilter
> [parser=o.a.i.i.util.nio.GridDirectParser@8e66d834, directMode=true],
> 

[jira] [Updated] (IGNITE-6952) Ignite fails to start on non x86/64 architectures

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-6952:

Summary: Ignite fails to start on non x86/64 architectures  (was: 
Deserialization failures on AIX )

> Ignite fails to start on non x86/64 architectures
> -
>
> Key: IGNITE-6952
> URL: https://issues.apache.org/jira/browse/IGNITE-6952
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Denis Magda
>Priority: Blocker
> Fix For: 2.4
>
>
> Ignite fails on AIX with the following stack trace:
> {code}
> GridConnectionBytesVerifyFilter], accepted=true]]]
> java.lang.IllegalArgumentException: null
>   at java.nio.Buffer.position(Buffer.java:255) ~[?:1.8.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readArrayLE(DirectByteBufferStreamImplV2.java:1587)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readArrayLE(DirectByteBufferStreamImplV2.java:1542)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readLongArray(DirectByteBufferStreamImplV2.java:1013)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readLongArray(DirectMessageReader.java:212)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.GridLongList.readFrom(GridLongList.java:558)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1165)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.read(DirectByteBufferStreamImplV2.java:1785)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readCollection(DirectByteBufferStreamImplV2.java:1244)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readCollection(DirectMessageReader.java:333)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.CacheGroupAffinityMessage.readFrom(CacheGroupAffinityMessage.java:292)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1165)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.read(DirectByteBufferStreamImplV2.java:1785)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMap(DirectByteBufferStreamImplV2.java:1294)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readMap(DirectMessageReader.java:345)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.readFrom(GridDhtPartitionsFullMessage.java:645)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1165)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:311)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:262)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:90)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:133)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3388)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> 

[jira] [Assigned] (IGNITE-6952) Ignite fails to start on non x86/64 architectures

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-6952:
---

Assignee: Yakov Zhdanov

> Ignite fails to start on non x86/64 architectures
> -
>
> Key: IGNITE-6952
> URL: https://issues.apache.org/jira/browse/IGNITE-6952
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Denis Magda
>Assignee: Yakov Zhdanov
>Priority: Blocker
> Fix For: 2.4
>
>
> Ignite fails on AIX with the following stack trace:
> {code}
> GridConnectionBytesVerifyFilter], accepted=true]]]
> java.lang.IllegalArgumentException: null
>   at java.nio.Buffer.position(Buffer.java:255) ~[?:1.8.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readArrayLE(DirectByteBufferStreamImplV2.java:1587)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readArrayLE(DirectByteBufferStreamImplV2.java:1542)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readLongArray(DirectByteBufferStreamImplV2.java:1013)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readLongArray(DirectMessageReader.java:212)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.GridLongList.readFrom(GridLongList.java:558)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1165)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.read(DirectByteBufferStreamImplV2.java:1785)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readCollection(DirectByteBufferStreamImplV2.java:1244)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readCollection(DirectMessageReader.java:333)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.CacheGroupAffinityMessage.readFrom(CacheGroupAffinityMessage.java:292)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1165)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.read(DirectByteBufferStreamImplV2.java:1785)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMap(DirectByteBufferStreamImplV2.java:1294)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readMap(DirectMessageReader.java:345)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.readFrom(GridDhtPartitionsFullMessage.java:645)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1165)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:311)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:262)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:90)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:133)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3388)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1261)
> 

[jira] [Resolved] (IGNITE-7178) Ignite fails to start on non x86/64 architectures

[Denis Magda (JIRA)]

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

Denis Magda resolved IGNITE-7178.
-
Resolution: Duplicate

> Ignite fails to start on non x86/64 architectures
> -
>
> Key: IGNITE-7178
> URL: https://issues.apache.org/jira/browse/IGNITE-7178
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Denis Magda
>Assignee: Yakov Zhdanov
>Priority: Blocker
> Fix For: 2.4
>
>
> Ignite fails with the exception below on AIX and Solar Spark. Most likely 
> because of the bug that pops up on big-endian and non x86/64 CPU 
> architectures:
> {code}
> ERROR 2017-11-02 11:59:01.331 [grid-nio-worker-tcp-comm-1-#22]
> org.apache.ignite.internal.util.nio.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=16841 lim=16844 cap=32768],
> reader=DirectMessageReader [state=DirectMessageState [pos=0,
> stack=[StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
> msgTypeDone=true, msg=GridDhtPartitionsFullMessage [parts=null,
> partCntrs=null, partCntrs2=null, partHistSuppliers=null, partsToReload=null,
> topVer=null, errs=null, compress=false, resTopVer=null, partCnt=0,
> super=GridDhtPartitionsAbstractMessage [exchId=GridDhtPartitionExchangeId
> [topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0], discoEvt=null,
> nodeId=e3ac3f40, evt=NODE_JOINED], lastVer=GridCacheVersion [topVer=0,
> order=1509612963224, nodeOrder=0], super=GridCacheMessage [msgId=369,
> depInfo=null, err=null, skipPrepare=false]]], 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], StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
> msgTypeDone=true, msg=CacheGroupAffinityMessage [], mapIt=null, it=null,
> arrPos=-1, keyDone=true, readSize=7, readItems=2, prim=0, primShift=0,
> uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true],
> state=0], StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
> msgTypeDone=true, msg=GridLongList [idx=0, arr=[]], mapIt=null, it=null,
> arrPos=-1, keyDone=false, readSize=512, readItems=47, prim=0, primShift=0,
> uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true],
> state=0], StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=1100144027456, arrOff=-1, tmpArrOff=40, tmpArrBytes=40,
> 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]], lastRead=true], ses=GridSelectorNioSessionImpl
> [worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=1,
> bytesRcvd=404253, bytesSent=1989, bytesRcvd0=16886, bytesSent0=28,
> select=true, super=GridWorker [name=grid-nio-worker-tcp-comm-1,
> igniteInstanceName=null, finished=false, hashCode=-2134841549,
> interrupted=false, runner=grid-nio-worker-tcp-comm-1-#22]]],
> writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
> readBuf=java.nio.DirectByteBuffer[pos=16841 lim=16844 cap=32768],
> inRecovery=GridNioRecoveryDescriptor [acked=6, resendCnt=0, rcvCnt=0,
> sentCnt=6, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
> [id=7683662b-16c9-42b7-aa0d-8328a60fc58e, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:6250], discPort=6250, order=1, intOrder=1,
> lastExchangeTime=1509612963744, loc=false, ver=2.3.0#20171028-sha1:8add7fd5,
> isClient=false], connected=true, connectCnt=11, queueLimit=131072,
> reserveCnt=175, pairedConnections=false],
> outRecovery=GridNioRecoveryDescriptor [acked=6, resendCnt=0, rcvCnt=0,
> sentCnt=6, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
> [id=7683662b-16c9-42b7-aa0d-8328a60fc58e, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:6250], discPort=6250, order=1, intOrder=1,
> lastExchangeTime=1509612963744, loc=false, ver=2.3.0#20171028-sha1:8add7fd5,
> isClient=false], connected=true, connectCnt=11, queueLimit=131072,
> reserveCnt=175, pairedConnections=false], super=GridNioSessionImpl
> [locAddr=/127.0.0.1:6284, rmtAddr=/127.0.0.1:61790,
> createTime=1509613141318, closeTime=0, bytesSent=28, bytesRcvd=16886,
> bytesSent0=28, bytesRcvd0=16886, sndSchedTime=1509613141318,
> lastSndTime=1509613141318, lastRcvTime=1509613141318, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioCodecFilter
> [parser=o.a.i.i.util.nio.GridDirectParser@8e66d834, 

[jira] [Updated] (IGNITE-6952) Deserialization failures on AIX

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-6952:

Priority: Blocker  (was: Critical)

> Deserialization failures on AIX 
> 
>
> Key: IGNITE-6952
> URL: https://issues.apache.org/jira/browse/IGNITE-6952
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Denis Magda
>Priority: Blocker
> Fix For: 2.4
>
>
> Ignite fails on AIX with the following stack trace:
> {code}
> GridConnectionBytesVerifyFilter], accepted=true]]]
> java.lang.IllegalArgumentException: null
>   at java.nio.Buffer.position(Buffer.java:255) ~[?:1.8.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readArrayLE(DirectByteBufferStreamImplV2.java:1587)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readArrayLE(DirectByteBufferStreamImplV2.java:1542)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readLongArray(DirectByteBufferStreamImplV2.java:1013)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readLongArray(DirectMessageReader.java:212)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.GridLongList.readFrom(GridLongList.java:558)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1165)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.read(DirectByteBufferStreamImplV2.java:1785)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readCollection(DirectByteBufferStreamImplV2.java:1244)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readCollection(DirectMessageReader.java:333)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.CacheGroupAffinityMessage.readFrom(CacheGroupAffinityMessage.java:292)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1165)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.read(DirectByteBufferStreamImplV2.java:1785)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMap(DirectByteBufferStreamImplV2.java:1294)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readMap(DirectMessageReader.java:345)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.readFrom(GridDhtPartitionsFullMessage.java:645)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1165)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:311)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:262)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:90)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:133)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3388)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1261)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> 

[jira] [Assigned] (IGNITE-7178) Ignite fails to start on non x86/64 architectures

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-7178:
---

Assignee: Yakov Zhdanov

> Ignite fails to start on non x86/64 architectures
> -
>
> Key: IGNITE-7178
> URL: https://issues.apache.org/jira/browse/IGNITE-7178
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Denis Magda
>Assignee: Yakov Zhdanov
>Priority: Blocker
> Fix For: 2.4
>
>
> Ignite fails with the exception below on AIX and Solar Spark. Most likely 
> because of the bug that pops up on big-endian and non x86/64 CPU 
> architectures:
> {code}
> ERROR 2017-11-02 11:59:01.331 [grid-nio-worker-tcp-comm-1-#22]
> org.apache.ignite.internal.util.nio.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=16841 lim=16844 cap=32768],
> reader=DirectMessageReader [state=DirectMessageState [pos=0,
> stack=[StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
> msgTypeDone=true, msg=GridDhtPartitionsFullMessage [parts=null,
> partCntrs=null, partCntrs2=null, partHistSuppliers=null, partsToReload=null,
> topVer=null, errs=null, compress=false, resTopVer=null, partCnt=0,
> super=GridDhtPartitionsAbstractMessage [exchId=GridDhtPartitionExchangeId
> [topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0], discoEvt=null,
> nodeId=e3ac3f40, evt=NODE_JOINED], lastVer=GridCacheVersion [topVer=0,
> order=1509612963224, nodeOrder=0], super=GridCacheMessage [msgId=369,
> depInfo=null, err=null, skipPrepare=false]]], 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], StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
> msgTypeDone=true, msg=CacheGroupAffinityMessage [], mapIt=null, it=null,
> arrPos=-1, keyDone=true, readSize=7, readItems=2, prim=0, primShift=0,
> uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true],
> state=0], StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
> msgTypeDone=true, msg=GridLongList [idx=0, arr=[]], mapIt=null, it=null,
> arrPos=-1, keyDone=false, readSize=512, readItems=47, prim=0, primShift=0,
> uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true],
> state=0], StateItem [stream=DirectByteBufferStreamImplV2
> [baseOff=1100144027456, arrOff=-1, tmpArrOff=40, tmpArrBytes=40,
> 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]], lastRead=true], ses=GridSelectorNioSessionImpl
> [worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=1,
> bytesRcvd=404253, bytesSent=1989, bytesRcvd0=16886, bytesSent0=28,
> select=true, super=GridWorker [name=grid-nio-worker-tcp-comm-1,
> igniteInstanceName=null, finished=false, hashCode=-2134841549,
> interrupted=false, runner=grid-nio-worker-tcp-comm-1-#22]]],
> writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
> readBuf=java.nio.DirectByteBuffer[pos=16841 lim=16844 cap=32768],
> inRecovery=GridNioRecoveryDescriptor [acked=6, resendCnt=0, rcvCnt=0,
> sentCnt=6, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
> [id=7683662b-16c9-42b7-aa0d-8328a60fc58e, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:6250], discPort=6250, order=1, intOrder=1,
> lastExchangeTime=1509612963744, loc=false, ver=2.3.0#20171028-sha1:8add7fd5,
> isClient=false], connected=true, connectCnt=11, queueLimit=131072,
> reserveCnt=175, pairedConnections=false],
> outRecovery=GridNioRecoveryDescriptor [acked=6, resendCnt=0, rcvCnt=0,
> sentCnt=6, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
> [id=7683662b-16c9-42b7-aa0d-8328a60fc58e, addrs=[127.0.0.1],
> sockAddrs=[/127.0.0.1:6250], discPort=6250, order=1, intOrder=1,
> lastExchangeTime=1509612963744, loc=false, ver=2.3.0#20171028-sha1:8add7fd5,
> isClient=false], connected=true, connectCnt=11, queueLimit=131072,
> reserveCnt=175, pairedConnections=false], super=GridNioSessionImpl
> [locAddr=/127.0.0.1:6284, rmtAddr=/127.0.0.1:61790,
> createTime=1509613141318, closeTime=0, bytesSent=28, bytesRcvd=16886,
> bytesSent0=28, bytesRcvd0=16886, sndSchedTime=1509613141318,
> lastSndTime=1509613141318, lastRcvTime=1509613141318, readsPaused=false,
> filterChain=FilterChain[filters=[GridNioCodecFilter
> [parser=o.a.i.i.util.nio.GridDirectParser@8e66d834, 

[jira] [Created] (IGNITE-7178) Ignite fails to start on non x86/64 architectures

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7178:
---

 Summary: Ignite fails to start on non x86/64 architectures
 Key: IGNITE-7178
 URL: https://issues.apache.org/jira/browse/IGNITE-7178
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Denis Magda
Priority: Blocker
 Fix For: 2.4


Ignite fails with the exception below on AIX and Solar Spark. Most likely 
because of the bug that pops up on big-endian and non x86/64 CPU architectures:

{code}
ERROR 2017-11-02 11:59:01.331 [grid-nio-worker-tcp-comm-1-#22]
org.apache.ignite.internal.util.nio.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=16841 lim=16844 cap=32768],
reader=DirectMessageReader [state=DirectMessageState [pos=0,
stack=[StateItem [stream=DirectByteBufferStreamImplV2
[baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
msgTypeDone=true, msg=GridDhtPartitionsFullMessage [parts=null,
partCntrs=null, partCntrs2=null, partHistSuppliers=null, partsToReload=null,
topVer=null, errs=null, compress=false, resTopVer=null, partCnt=0,
super=GridDhtPartitionsAbstractMessage [exchId=GridDhtPartitionExchangeId
[topVer=AffinityTopologyVersion [topVer=5, minorTopVer=0], discoEvt=null,
nodeId=e3ac3f40, evt=NODE_JOINED], lastVer=GridCacheVersion [topVer=0,
order=1509612963224, nodeOrder=0], super=GridCacheMessage [msgId=369,
depInfo=null, err=null, skipPrepare=false]]], 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], StateItem [stream=DirectByteBufferStreamImplV2
[baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
msgTypeDone=true, msg=CacheGroupAffinityMessage [], mapIt=null, it=null,
arrPos=-1, keyDone=true, readSize=7, readItems=2, prim=0, primShift=0,
uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true],
state=0], StateItem [stream=DirectByteBufferStreamImplV2
[baseOff=1100144027456, arrOff=-1, tmpArrOff=0, tmpArrBytes=0,
msgTypeDone=true, msg=GridLongList [idx=0, arr=[]], mapIt=null, it=null,
arrPos=-1, keyDone=false, readSize=512, readItems=47, prim=0, primShift=0,
uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true],
state=0], StateItem [stream=DirectByteBufferStreamImplV2
[baseOff=1100144027456, arrOff=-1, tmpArrOff=40, tmpArrBytes=40,
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]], lastRead=true], ses=GridSelectorNioSessionImpl
[worker=DirectNioClientWorker [super=AbstractNioClientWorker [idx=1,
bytesRcvd=404253, bytesSent=1989, bytesRcvd0=16886, bytesSent0=28,
select=true, super=GridWorker [name=grid-nio-worker-tcp-comm-1,
igniteInstanceName=null, finished=false, hashCode=-2134841549,
interrupted=false, runner=grid-nio-worker-tcp-comm-1-#22]]],
writeBuf=java.nio.DirectByteBuffer[pos=0 lim=32768 cap=32768],
readBuf=java.nio.DirectByteBuffer[pos=16841 lim=16844 cap=32768],
inRecovery=GridNioRecoveryDescriptor [acked=6, resendCnt=0, rcvCnt=0,
sentCnt=6, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
[id=7683662b-16c9-42b7-aa0d-8328a60fc58e, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:6250], discPort=6250, order=1, intOrder=1,
lastExchangeTime=1509612963744, loc=false, ver=2.3.0#20171028-sha1:8add7fd5,
isClient=false], connected=true, connectCnt=11, queueLimit=131072,
reserveCnt=175, pairedConnections=false],
outRecovery=GridNioRecoveryDescriptor [acked=6, resendCnt=0, rcvCnt=0,
sentCnt=6, reserved=true, lastAck=0, nodeLeft=false, node=TcpDiscoveryNode
[id=7683662b-16c9-42b7-aa0d-8328a60fc58e, addrs=[127.0.0.1],
sockAddrs=[/127.0.0.1:6250], discPort=6250, order=1, intOrder=1,
lastExchangeTime=1509612963744, loc=false, ver=2.3.0#20171028-sha1:8add7fd5,
isClient=false], connected=true, connectCnt=11, queueLimit=131072,
reserveCnt=175, pairedConnections=false], super=GridNioSessionImpl
[locAddr=/127.0.0.1:6284, rmtAddr=/127.0.0.1:61790,
createTime=1509613141318, closeTime=0, bytesSent=28, bytesRcvd=16886,
bytesSent0=28, bytesRcvd0=16886, sndSchedTime=1509613141318,
lastSndTime=1509613141318, lastRcvTime=1509613141318, readsPaused=false,
filterChain=FilterChain[filters=[GridNioCodecFilter
[parser=o.a.i.i.util.nio.GridDirectParser@8e66d834, directMode=true],
GridConnectionBytesVerifyFilter], accepted=true]]]
java.lang.IllegalArgumentException: null
at java.nio.Buffer.position(Buffer.java:255) ~[?:1.8.0]
at
org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readArrayLE(DirectByteBufferStreamImplV2.java:1587)
~[ignite-core-2.3.0.jar:2.3.0]
at

[jira] [Commented] (IGNITE-7166) SQL join with partition and replicated caches fails if number of partitions is too low.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7166:


Github user devozerov closed the pull request at:

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


> SQL join with partition and replicated caches fails if number of partitions 
> is too low.
> ---
>
> Key: IGNITE-7166
> URL: https://issues.apache.org/jira/browse/IGNITE-7166
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.3
>Reporter: Alexei Scherbakov
>Assignee: Vladimir Ozerov
> Fix For: 2.4
>
>
> If not all nodes receive primary partition, we fail to validate nodes 
> predicate:
> {code}
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor#stableDataNodes
> ...
> else if (!isReplicatedOnly && extraCctx.isReplicated()) {
> if (!extraNodes.containsAll(nodes))
> {code}
> Solution: remove from validation nodes containing no primary partitions for 
> replicated cache.
> Reproducer:
> {noformat}
> /*
>  * Licensed to the Apache Software Foundation (ASF) under one or more
>  * contributor license agreements.  See the NOTICE file distributed with
>  * this work for additional information regarding copyright ownership.
>  * The ASF licenses this file to You under the Apache License, Version 2.0
>  * (the "License"); you may not use this file except in compliance with
>  * the License.  You may obtain a copy of the License at
>  *
>  *  http://www.apache.org/licenses/LICENSE-2.0
>  *
>  * Unless required by applicable law or agreed to in writing, software
>  * distributed under the License is distributed on an "AS IS" BASIS,
>  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>  * See the License for the specific language governing permissions and
>  * limitations under the License.
>  */
> package org.apache.ignite.internal.processors.cache.distributed.replicated;
> import java.util.List;
> import org.apache.ignite.Ignite;
> import org.apache.ignite.cache.affinity.rendezvous.RendezvousAffinityFunction;
> import org.apache.ignite.cache.query.FieldsQueryCursor;
> import org.apache.ignite.cache.query.SqlFieldsQuery;
> import org.apache.ignite.cache.query.annotations.QuerySqlField;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import static org.apache.ignite.cache.CacheAtomicityMode.TRANSACTIONAL;
> import static org.apache.ignite.cache.CacheMode.PARTITIONED;
> import static org.apache.ignite.cache.CacheMode.REPLICATED;
> import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
> /**
>  * Tests non collocated join with replicated cache.
>  */
> public class IgniteCacheReplicatedJoinSelfTest extends GridCommonAbstractTest 
> {
> /** */
> public static final String REP_CACHE_NAME = "repCache";
> /** */
> public static final String PART_CACHE_NAME = "partCache";
> /** */
> public static final int REP_CNT = 3;
> /** */
> public static final int PART_CNT = 10_000;
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> final IgniteConfiguration cfg = 
> super.getConfiguration(igniteInstanceName);
> cfg.setClientMode("client".equals(igniteInstanceName));
> final CacheConfiguration ccfg1 = new 
> CacheConfiguration(PART_CACHE_NAME);
> ccfg1.setCacheMode(PARTITIONED);
> ccfg1.setAtomicityMode(TRANSACTIONAL);
> ccfg1.setWriteSynchronizationMode(FULL_SYNC);
> ccfg1.setIndexedTypes(Integer.class, PartValue.class);
> final CacheConfiguration ccfg2 = new 
> CacheConfiguration(REP_CACHE_NAME);
> ccfg2.setAffinity(new RendezvousAffinityFunction(false, REP_CNT));
> ccfg2.setCacheMode(REPLICATED);
> ccfg2.setAtomicityMode(TRANSACTIONAL);
> ccfg2.setWriteSynchronizationMode(FULL_SYNC);
> ccfg2.setIndexedTypes(Integer.class, RepValue.class);
> cfg.setCacheConfiguration(ccfg1, ccfg2);
> return cfg;
> }
> /**
>  *
>  * @throws Exception
>  */
> public void testJoinNonCollocated() throws Exception {
> startGridsMultiThreaded(3);
> final Ignite client = startGrid("client");
> for (int i = 0; i < REP_CNT; i++)
> client.cache(REP_CACHE_NAME).put(i, new RepValue(i, "rep" + i));
> for (int i = 0; i < PART_CNT; i++)
> client.cache(PART_CACHE_NAME).put(i, new PartValue(i, "part" + i, 
> ((i + 1) % REP_CNT)));
> final 

[jira] [Commented] (IGNITE-6495) performance measurement of decision trees algorithms

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6495:


GitHub user oignatenko opened a pull request:

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

IGNITE-6495 performance measurement of decision trees algorithms

- benchmark drafted a while ago integrated with recent changes in master
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results

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

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

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

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


commit f6782229ed97e848ff4770d5c8f49c5d97a4f2fb
Author: Oleg Ignatenko 
Date:   2017-12-12T16:24:41Z

IGNITE-6495 performance measurement of decision trees algorithms
- benchmark drafted a while ago integrated with recent changes in master
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results




> performance measurement of decision trees algorithms
> 
>
> Key: IGNITE-6495
> URL: https://issues.apache.org/jira/browse/IGNITE-6495
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Attachments: IGNITE-6495-draft.zip
>
>
> We want to start tracking our performance to avoid performance degradation. 
> Also we need some performance comparison with other ml libs.
> This task is "extracted" from IGNITE-6123 because implementation of decision 
> trees is not yet integrated into master (IGNITE-5218).



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

[jira] [Assigned] (IGNITE-7177) Custom discovery messages from plugins are handled incorrectly

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk reassigned IGNITE-7177:


Assignee: Alexey Goncharuk

> Custom discovery messages from plugins are handled incorrectly
> --
>
> Key: IGNITE-7177
> URL: https://issues.apache.org/jira/browse/IGNITE-7177
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 2.4
>
>
> We call onServerNodeJoin for custom messages which do not change affinity



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

[jira] [Created] (IGNITE-7177) Custom discovery messages from plugins are handled incorrectly

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-7177:


 Summary: Custom discovery messages from plugins are handled 
incorrectly
 Key: IGNITE-7177
 URL: https://issues.apache.org/jira/browse/IGNITE-7177
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.1
Reporter: Alexey Goncharuk
 Fix For: 2.4


We call onServerNodeJoin for custom messages which do not change affinity



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

[jira] [Commented] (IGNITE-6343) Index is not used properly if changing sort order.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6343:


GitHub user dolphin1414 opened a pull request:

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

IGNITE-6343: Index is not used properly if changing sort order.

Index is not used properly if changing sort order.

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

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

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

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


commit bcaac3a76af07f63a023d4e21916278906be4ac8
Author: rkondakov 
Date:   2017-12-11T07:51:37Z

IGNITE-6343: Workaround - reversed index creation for each user index.




> Index is not used properly if changing sort order.
> --
>
> Key: IGNITE-6343
> URL: https://issues.apache.org/jira/browse/IGNITE-6343
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.0
>Reporter: Alexei Scherbakov
>Assignee: Roman Kondakov
>  Labels: performance
>
> Unit test reproducer:
> {noformat}
> /*
>  * Licensed to the Apache Software Foundation (ASF) under one or more
>  * contributor license agreements.  See the NOTICE file distributed with
>  * this work for additional information regarding copyright ownership.
>  * The ASF licenses this file to You under the Apache License, Version 2.0
>  * (the "License"); you may not use this file except in compliance with
>  * the License.  You may obtain a copy of the License at
>  *
>  *  http://www.apache.org/licenses/LICENSE-2.0
>  *
>  * Unless required by applicable law or agreed to in writing, software
>  * distributed under the License is distributed on an "AS IS" BASIS,
>  * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
>  * See the License for the specific language governing permissions and
>  * limitations under the License.
>  */
> package org.apache.ignite.internal.processors.cache;
> import java.util.Calendar;
> import java.util.Collections;
> import java.util.Date;
> import java.util.LinkedHashMap;
> import java.util.List;
> import org.apache.ignite.IgniteCache;
> import org.apache.ignite.cache.CacheMode;
> import org.apache.ignite.cache.QueryEntity;
> import org.apache.ignite.cache.QueryIndex;
> import org.apache.ignite.cache.QueryIndexType;
> import org.apache.ignite.cache.query.SqlFieldsQuery;
> import org.apache.ignite.configuration.CacheConfiguration;
> import org.apache.ignite.configuration.IgniteConfiguration;
> import org.apache.ignite.configuration.MemoryConfiguration;
> import org.apache.ignite.configuration.MemoryPolicyConfiguration;
> import org.apache.ignite.internal.util.typedef.internal.U;
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.TcpDiscoveryIpFinder;
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> import static org.apache.ignite.cache.CacheMode.PARTITIONED;
> import static org.apache.ignite.cache.CacheWriteSynchronizationMode.FULL_SYNC;
> import static java.util.Calendar.*;
> /**
>  * Tests for cache query results serialization.
>  */
> public class GridCacheQueryIndexUsageSelfTest extends GridCommonAbstractTest {
> /** */
> private static final int GRID_CNT = 1;
> /** */
> private static final String CACHE_NAME = "A";
> /** */
> private static final CacheMode CACHE_MODE = PARTITIONED;
> /** */
> private static TcpDiscoveryIpFinder ipFinder = new 
> TcpDiscoveryVmIpFinder(true);
> /** {@inheritDoc} */
> @Override protected void beforeTest() throws Exception {
> startGridsMultiThreaded(GRID_CNT);
> }
> /** {@inheritDoc} */
> @Override protected void afterTest() throws Exception {
> stopAllGrids();
> }
> /** {@inheritDoc} */
> @Override protected IgniteConfiguration getConfiguration(String 
> igniteInstanceName) throws Exception {
> IgniteConfiguration cfg = super.getConfiguration(igniteInstanceName);
> MemoryPolicyConfiguration mpcfg = new MemoryPolicyConfiguration();
> //mpcfg.setMaxSize(2 * 1024 * 1024 * 1024L);
> mpcfg.setName("def");
> MemoryConfiguration mcfg = new MemoryConfiguration();
> mcfg.setDefaultMemoryPolicyName("def");
> mcfg.setMemoryPolicies(mpcfg);
> cfg.setMemoryConfiguration(mcfg);
> 

[jira] [Commented] (IGNITE-7118) performance measurement for distributed k-means clustering

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7118:


Github user oignatenko closed the pull request at:

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


> performance measurement for distributed k-means clustering
> --
>
> Key: IGNITE-7118
> URL: https://issues.apache.org/jira/browse/IGNITE-7118
> Project: Ignite
>  Issue Type: Bug
>  Components: ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> We want to start tracking our performance to avoid performance degradation. 
> Also we need some performance comparison with other ml libs.
> Initial draft for this benchmark was made per IGNITE-6123 (class 
> {{IgniteKMeansDistributedClustererBenchmark}}) but it currently fails because 
> of the implementation issues reported in IGNITE-6849 so it is excluded.
> Enable this benchmark and re-test it using codebase that has has corrected 
> implementation.



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

[jira] [Updated] (IGNITE-7176) SqlQuery does not always find matching entries

[Markus Kinzler (JIRA)]

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

Markus Kinzler updated IGNITE-7176:
---
Attachment: sqlbug.zip

> SqlQuery does not always find matching entries
> --
>
> Key: IGNITE-7176
> URL: https://issues.apache.org/jira/browse/IGNITE-7176
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Markus Kinzler
> Attachments: sqlbug.zip
>
>
> When the @QuerySqlField annotation is put on a custom class, the sql query 
> sometimes does not find the entry.
> With an cache of 100'000 entries, the problem occurs in about 50% of the test 
> runs for 1 - 2 entries.
> When the entry is not found, no log statement is written and no exception is 
> thrown, but the result is missing, despite beeing accessible via 
> cache.get(key).
> Note that i could not reproduce the Issue when i rename the class 
> LegaldocAcceptPk to TestEntityPk.
> A reproducible unit test is attached.



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

[jira] [Created] (IGNITE-7176) SqlQuery does not always find matching entries

[Markus Kinzler (JIRA)]

Markus Kinzler created IGNITE-7176:
--

 Summary: SqlQuery does not always find matching entries
 Key: IGNITE-7176
 URL: https://issues.apache.org/jira/browse/IGNITE-7176
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.3
Reporter: Markus Kinzler


When the @QuerySqlField annotation is put on a custom class, the sql query 
sometimes does not find the entry.
With an cache of 100'000 entries, the problem occurs in about 50% of the test 
runs for 1 - 2 entries.

When the entry is not found, no log statement is written and no exception is 
thrown, but the result is missing, despite beeing accessible via cache.get(key).

Note that i could not reproduce the Issue when i rename the class 
LegaldocAcceptPk to TestEntityPk.

A reproducible unit test is attached.




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

[jira] [Commented] (IGNITE-7118) performance measurement for distributed k-means clustering

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7118:


GitHub user oignatenko opened a pull request:

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

IGNITE-7118 performance measurement for distributed k-means clustering



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

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

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

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


commit a782ee3f944d556686e8d0a68acb3f534e3ecb13
Author: Oleg Ignatenko 
Date:   2017-12-12T13:30:11Z

IGNITE-7118 performance measurement for distributed k-means clustering
- enabled benchmark after integration of necessary fix from master
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results

commit 125b3d1fe182dbaeba3ba99476e92a48f6daf9aa
Author: Oleg Ignatenko 
Date:   2017-12-12T14:04:42Z

IGNITE-7118 performance measurement for distributed k-means clustering
- enabled benchmark after integration of necessary fix from master
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results




> performance measurement for distributed k-means clustering
> --
>
> Key: IGNITE-7118
> URL: https://issues.apache.org/jira/browse/IGNITE-7118
> Project: Ignite
>  Issue Type: Bug
>  Components: ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> We want to start tracking our performance to avoid performance degradation. 
> Also we need some performance comparison with other ml libs.
> Initial draft for this benchmark was made per IGNITE-6123 (class 
> {{IgniteKMeansDistributedClustererBenchmark}}) but it currently fails because 
> of the implementation issues reported in IGNITE-6849 so it is excluded.
> Enable this benchmark and re-test it using codebase that has has corrected 
> implementation.



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

[jira] [Assigned] (IGNITE-6731) Java 9: remove sun.misc.PerfCounter usages

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov reassigned IGNITE-6731:


Assignee: Andrey Kuznetsov

> Java 9: remove sun.misc.PerfCounter usages
> --
>
> Key: IGNITE-6731
> URL: https://issues.apache.org/jira/browse/IGNITE-6731
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> This class is used in Hadoop module only:
> 1) {{HadoopClassLoader}}
> 2) {{HadoopTestClassLoader}}
> Need to understand whether it is safe to simply remove this calls. Most 
> probably - yes.



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

[jira] [Commented] (IGNITE-7118) performance measurement for distributed k-means clustering

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7118:


Github user asfgit closed the pull request at:

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


> performance measurement for distributed k-means clustering
> --
>
> Key: IGNITE-7118
> URL: https://issues.apache.org/jira/browse/IGNITE-7118
> Project: Ignite
>  Issue Type: Bug
>  Components: ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> We want to start tracking our performance to avoid performance degradation. 
> Also we need some performance comparison with other ml libs.
> Initial draft for this benchmark was made per IGNITE-6123 (class 
> {{IgniteKMeansDistributedClustererBenchmark}}) but it currently fails because 
> of the implementation issues reported in IGNITE-6849 so it is excluded.
> Enable this benchmark and re-test it using codebase that has has corrected 
> implementation.



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

[jira] [Comment Edited] (IGNITE-6123) First performance measurement of implemented ml algorithms

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko edited comment on IGNITE-6123 at 12/12/17 1:55 PM:
--

Note after this is completed and merged need to create a ticket to accommodate 
Teamcity builds for ML benchmarks (in 
[build|https://issues.apache.org/jira/browse/IGNITE/component/12324403] 
component).

*Update* per discussion with Oleg Ostanin currently there are no TC tasks 
related to benchmarks, meaning there is nothing to accommodate.


was (Author: oignatenko):
note after this is completed and merged need to create a ticket to accommodate 
Teamcity builds for ML benchmarks (in 
[build|https://issues.apache.org/jira/browse/IGNITE/component/12324403] 
component)

> First performance measurement of implemented ml algorithms
> --
>
> Key: IGNITE-6123
> URL: https://issues.apache.org/jira/browse/IGNITE-6123
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml, yardstick
>Reporter: Yury Babak
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> We want to start tracking our performance to avoid performance degradation. 
> Also we need some performance comparison with other ml libs.



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

[jira] [Commented] (IGNITE-7169) Missed javadoc for IgniteToDoubleFunction

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7169:


Github user asfgit closed the pull request at:

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


> Missed javadoc for IgniteToDoubleFunction
> -
>
> Key: IGNITE-7169
> URL: https://issues.apache.org/jira/browse/IGNITE-7169
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.4
>
>
> Missed javadoc for IgniteToDoubleFunction



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

[jira] [Updated] (IGNITE-4192) SQL TX: JDBC driver support

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4192:

Component/s: sql

> SQL TX: JDBC driver support
> ---
>
> Key: IGNITE-4192
> URL: https://issues.apache.org/jira/browse/IGNITE-4192
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc, sql
>Reporter: Denis Magda
>Assignee: Alexander Paschenko
>  Labels: iep-3
> Fix For: 2.4
>
>
> To support execution of DML and SELECT statements inside of a transaction 
> started from JDBC driver side.



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

[jira] [Updated] (IGNITE-4192) SQL TX: JDBC driver support

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4192:

Labels: iep-3  (was: iep-3 sql)

> SQL TX: JDBC driver support
> ---
>
> Key: IGNITE-4192
> URL: https://issues.apache.org/jira/browse/IGNITE-4192
> Project: Ignite
>  Issue Type: Task
>  Components: jdbc, sql
>Reporter: Denis Magda
>Assignee: Alexander Paschenko
>  Labels: iep-3
> Fix For: 2.4
>
>
> To support execution of DML and SELECT statements inside of a transaction 
> started from JDBC driver side.



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

[jira] [Commented] (IGNITE-6952) Deserialization failures on AIX

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov commented on IGNITE-6952:
---

The problem can be reproduced with a spark machine too:

https://ci.ignite.apache.org/downloadBuildLog.html?buildId=984942=true

> Deserialization failures on AIX 
> 
>
> Key: IGNITE-6952
> URL: https://issues.apache.org/jira/browse/IGNITE-6952
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Denis Magda
>Priority: Critical
> Fix For: 2.4
>
>
> Ignite fails on AIX with the following stack trace:
> {code}
> GridConnectionBytesVerifyFilter], accepted=true]]]
> java.lang.IllegalArgumentException: null
>   at java.nio.Buffer.position(Buffer.java:255) ~[?:1.8.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readArrayLE(DirectByteBufferStreamImplV2.java:1587)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readArrayLE(DirectByteBufferStreamImplV2.java:1542)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readLongArray(DirectByteBufferStreamImplV2.java:1013)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readLongArray(DirectMessageReader.java:212)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.GridLongList.readFrom(GridLongList.java:558)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1165)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.read(DirectByteBufferStreamImplV2.java:1785)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readCollection(DirectByteBufferStreamImplV2.java:1244)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readCollection(DirectMessageReader.java:333)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.CacheGroupAffinityMessage.readFrom(CacheGroupAffinityMessage.java:292)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1165)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.read(DirectByteBufferStreamImplV2.java:1785)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMap(DirectByteBufferStreamImplV2.java:1294)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readMap(DirectMessageReader.java:345)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsFullMessage.readFrom(GridDhtPartitionsFullMessage.java:645)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.stream.v2.DirectByteBufferStreamImplV2.readMessage(DirectByteBufferStreamImplV2.java:1165)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.direct.DirectMessageReader.readMessage(DirectMessageReader.java:311)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.managers.communication.GridIoMessage.readFrom(GridIoMessage.java:262)
> ~[ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridDirectParser.decode(GridDirectParser.java:90)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:114)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridConnectionBytesVerifyFilter.onMessageReceived(GridConnectionBytesVerifyFilter.java:133)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3388)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:175)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> 

[jira] [Commented] (IGNITE-7118) performance measurement for distributed k-means clustering

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7118:


GitHub user oignatenko opened a pull request:

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

IGNITE-7118 performance measurement for distributed k-means clustering

- enabled benchmark after integration of necessary fix from master
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results

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

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

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

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


commit a782ee3f944d556686e8d0a68acb3f534e3ecb13
Author: Oleg Ignatenko 
Date:   2017-12-12T13:30:11Z

IGNITE-7118 performance measurement for distributed k-means clustering
- enabled benchmark after integration of necessary fix from master
-- verified with diffs overview, clean rebuild, trial execution of the 
benchmarks and studying results




> performance measurement for distributed k-means clustering
> --
>
> Key: IGNITE-7118
> URL: https://issues.apache.org/jira/browse/IGNITE-7118
> Project: Ignite
>  Issue Type: Bug
>  Components: ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>
> We want to start tracking our performance to avoid performance degradation. 
> Also we need some performance comparison with other ml libs.
> Initial draft for this benchmark was made per IGNITE-6123 (class 
> {{IgniteKMeansDistributedClustererBenchmark}}) but it currently fails because 
> of the implementation issues reported in IGNITE-6849 so it is excluded.
> Enable this benchmark and re-test it using codebase that has has corrected 
> implementation.



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

[jira] [Commented] (IGNITE-7175) Throttling is not applied to page allocation

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7175:


GitHub user dspavlov opened a pull request:

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

IGNITE-7175: Throttling is not applied to page allocation



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

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

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

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


commit c4b794f4d6d2efe50b75094d06196d174b821b55
Author: dpavlov 
Date:   2017-12-12T13:24:59Z

IGNITE-7175: Throttling is not applied to page allocation




> Throttling is not applied to page allocation
> 
>
> Key: IGNITE-7175
> URL: https://issues.apache.org/jira/browse/IGNITE-7175
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.3
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
> Fix For: 2.4
>
>
> Found during IGNITE-6341 testing, throttling check is not done for newly 
> allocated pages.
> Allocated page already has dirty flag, but Throttling parkNanos is applied 
> only for intially not dirty page.
> For initial load case it is required to do Throttling check for mostly new 
> pages



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

[jira] [Assigned] (IGNITE-6945) SQL: optionally do not copy offheap rows for local SqlQuery

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-6945:
---

Assignee: (was: Taras Ledkov)

> SQL: optionally do not copy offheap rows for local SqlQuery
> ---
>
> Key: IGNITE-6945
> URL: https://issues.apache.org/jira/browse/IGNITE-6945
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>
> Currently when iterating over rows we eagerly materialize them [1]. If key or 
> value are large enough, we could loose a lot of time on offheap-heap copying. 
> To partially mitigate this, we can do the following:
> 1) Add new flag {{SqlQuery.localNoCopy}} which is applicable only for local 
> queries.
> 2) When enabled we will not copy final {{_KEY}} and {{_VAL}} columns to heap. 
> but rather wrap them into {{BinaryOffheapObjectImpl}}
> 3) These rows must be released when query iterator switches to the next row.
> [1] {{H2RowFactory.getRow}}



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

[jira] [Updated] (IGNITE-6945) SQL: optionally do not copy offheap rows for local SqlQuery

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6945:

Fix Version/s: (was: 2.4)

> SQL: optionally do not copy offheap rows for local SqlQuery
> ---
>
> Key: IGNITE-6945
> URL: https://issues.apache.org/jira/browse/IGNITE-6945
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>
> Currently when iterating over rows we eagerly materialize them [1]. If key or 
> value are large enough, we could loose a lot of time on offheap-heap copying. 
> To partially mitigate this, we can do the following:
> 1) Add new flag {{SqlQuery.localNoCopy}} which is applicable only for local 
> queries.
> 2) When enabled we will not copy final {{_KEY}} and {{_VAL}} columns to heap. 
> but rather wrap them into {{BinaryOffheapObjectImpl}}
> 3) These rows must be released when query iterator switches to the next row.
> [1] {{H2RowFactory.getRow}}



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

[jira] [Closed] (IGNITE-6945) SQL: optionally do not copy offheap rows for local SqlQuery

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-6945.
---

> SQL: optionally do not copy offheap rows for local SqlQuery
> ---
>
> Key: IGNITE-6945
> URL: https://issues.apache.org/jira/browse/IGNITE-6945
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>
> Currently when iterating over rows we eagerly materialize them [1]. If key or 
> value are large enough, we could loose a lot of time on offheap-heap copying. 
> To partially mitigate this, we can do the following:
> 1) Add new flag {{SqlQuery.localNoCopy}} which is applicable only for local 
> queries.
> 2) When enabled we will not copy final {{_KEY}} and {{_VAL}} columns to heap. 
> but rather wrap them into {{BinaryOffheapObjectImpl}}
> 3) These rows must be released when query iterator switches to the next row.
> [1] {{H2RowFactory.getRow}}



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

[jira] [Assigned] (IGNITE-3464) Possible race between partition exchange and prepare/finish requests

[Vitaliy Biryukov (JIRA)]

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

Vitaliy Biryukov reassigned IGNITE-3464:


Assignee: Vitaliy Biryukov

> Possible race between partition exchange and prepare/finish requests
> 
>
> Key: IGNITE-3464
> URL: https://issues.apache.org/jira/browse/IGNITE-3464
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Alexey Goncharuk
>Assignee: Vitaliy Biryukov
>
> Consider the following scenario:
> Two nodes A (coordinator), B. Node C is joining the grid. Current topology 
> version is 2.
>  - Node A starts a transaction on version 2 and sends a prepare request to 
> node B
>  - Discovery event happens on node A. Exchange future is created, captures 
> the transaction and waits for this transaction to finish.
>  - Discovery event happens on node B. Exchange future is created, but since 
> there is no transaction on this node (the request has not been processed 
> yet), partition release future is completed and exchange waits for an ACK 
> from coordinator.
>  - Prepare request is processed on node B
>  - Node A commits the transaction locally, partition release future is 
> completed. Both finish request and exchange message are sent to the node B.
>  - Node B processes the exchange message first and completes exchange.
>  - Node C starts rebalancing from node B and acquires stale value of the key 
> which was supposed to be updated in the transaction.
>  - Node B processes finish request and commits the transaction.
> As a result, node B and C have different values stored in the cache.



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

[jira] [Comment Edited] (IGNITE-6945) SQL: optionally do not copy offheap rows for local SqlQuery

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov edited comment on IGNITE-6945 at 12/12/17 1:23 PM:
---

It appears that the patch may produce improvement in certain cases (e.g. big 
objects with numeric fields or huge arrays), but decrease performance in others 
(e.g. lots of strings). Another prospective approach is row cache (IGNITE-7173).


was (Author: vozerov):
It appears that the patch may produce improvement in certain cases (e.g. big 
objects with numeric fields or huge arrays), but decrease performance in others 
(e.g. lots of strings). 

> SQL: optionally do not copy offheap rows for local SqlQuery
> ---
>
> Key: IGNITE-6945
> URL: https://issues.apache.org/jira/browse/IGNITE-6945
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.4
>
>
> Currently when iterating over rows we eagerly materialize them [1]. If key or 
> value are large enough, we could loose a lot of time on offheap-heap copying. 
> To partially mitigate this, we can do the following:
> 1) Add new flag {{SqlQuery.localNoCopy}} which is applicable only for local 
> queries.
> 2) When enabled we will not copy final {{_KEY}} and {{_VAL}} columns to heap. 
> but rather wrap them into {{BinaryOffheapObjectImpl}}
> 3) These rows must be released when query iterator switches to the next row.
> [1] {{H2RowFactory.getRow}}



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

[jira] [Commented] (IGNITE-7169) Missed javadoc for IgniteToDoubleFunction

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7169:


GitHub user ybabak opened a pull request:

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

IGNITE-7169: Missed javadoc for IgniteToDoubleFunction

fixed

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

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

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

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


commit 9bab0d8cca9873cfb0ee1ee87442025bf9d658f6
Author: YuriBabak 
Date:   2017-12-12T13:17:58Z

IGNITE-7169: Missed javadoc for IgniteToDoubleFunction

fixed




> Missed javadoc for IgniteToDoubleFunction
> -
>
> Key: IGNITE-7169
> URL: https://issues.apache.org/jira/browse/IGNITE-7169
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.4
>
>
> Missed javadoc for IgniteToDoubleFunction



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

[jira] [Reopened] (IGNITE-7169) Missed javadoc for IgniteToDoubleFunction

[Yury Babak (JIRA)]

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

Yury Babak reopened IGNITE-7169:


javadoc is empty

> Missed javadoc for IgniteToDoubleFunction
> -
>
> Key: IGNITE-7169
> URL: https://issues.apache.org/jira/browse/IGNITE-7169
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.4
>
>
> Missed javadoc for IgniteToDoubleFunction



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

[jira] [Created] (IGNITE-7175) Throttling is not applied to page allocation

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-7175:
--

 Summary: Throttling is not applied to page allocation
 Key: IGNITE-7175
 URL: https://issues.apache.org/jira/browse/IGNITE-7175
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Affects Versions: 2.3
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
 Fix For: 2.4


Found during IGNITE-6341 testing, throttling check is not done for newly 
allocated pages.

Allocated page already has dirty flag, but Throttling parkNanos is applied only 
for intially not dirty page.

For initial load case it is required to do Throttling check for mostly new pages



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

[jira] [Commented] (IGNITE-6743) Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6743:


GitHub user andrey-kuznetsov opened a pull request:

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

IGNITE-6743: Cleaning direct buffer through reflection.



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

$ git pull https://github.com/andrey-kuznetsov/ignite ignite-6743

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

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


commit b37392cbbdd3fd04d7e4640563a12af9e5a6f09d
Author: Andrey Kuznetsov 
Date:   2017-12-12T13:11:17Z

IGNITE-6743: Cleaning direct buffer through reflection.




> Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer
> 
>
> Key: IGNITE-6743
> URL: https://issues.apache.org/jira/browse/IGNITE-6743
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> When session is closed we clean allocated {{DirectByteBuffer}}-s using 
> {{sun.misc.Cleaner}}. Need to rework this piece to reflection-based approach 
> which will work for supported Java versions.



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

[jira] [Commented] (IGNITE-7143) CPP: Can not insert zero decimal value with the ODBC driver.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7143:


GitHub user isapego opened a pull request:

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

IGNITE-7143: Fixed Decimal serialization issue



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

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

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

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


commit f0dfad560ce7b6013346454bff2700282de4ca65
Author: Igor Sapego 
Date:   2017-12-12T13:08:35Z

IGNITE-7143: Fixed Decimal serialization issue




> CPP: Can not insert zero decimal value with the ODBC driver.
> 
>
> Key: IGNITE-7143
> URL: https://issues.apache.org/jira/browse/IGNITE-7143
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Affects Versions: 2.1
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Blocker
> Fix For: 2.4
>
>
> Create the following table:
> {code}
> CREATE TABLE IF NOT EXISTS TestTable (RecId varchar PRIMARY KEY, RecValue 
> DECIMAL(4,2))
> WITH "template=replicated, cache_name=TestTable_Cache";
> {code}
> Then do an ODBC insert using the OdbcParameter with the OdbcCommand object:
> {code}
> INSERT INTO TestTable (RecId, RecValue) VALUES ('1', ?)
> {code}
> The Odbc error is "The connection has been disabled." however the JVM is
> throwing this error:
> {noformat}
> [SEVERE][client-connector-#47][ClientListenerNioListener] Failed to parse
> client request.
> java.lang.ArrayIndexOutOfBoundsException: 0
>  at org.apache.ignite.internal.binary.BinaryUtils.doReadDecimal
> {noformat}
> Everything works out ok until the actual value set on the parameter is 0.
> Null works fine, values other than 0 work fine. Precision and
> Scale are set appropriately. 



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

[jira] [Updated] (IGNITE-7095) JdbcConnection hard linked in IgniteH2Indexing preventing old connections from closing

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7095:

Fix Version/s: (was: 2.5)

> JdbcConnection hard linked in IgniteH2Indexing preventing old connections 
> from closing
> --
>
> Key: IGNITE-7095
> URL: https://issues.apache.org/jira/browse/IGNITE-7095
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.3
>Reporter: Alexandr Kuramshin
>Assignee: Taras Ledkov
> Fix For: 2.4
>
> Attachments: IndexClientTest.java, IndexTest.java
>
>
> Every time a new thread performs {{SqlFieldsQuery}} the new 
> {{org.h2.jdbc.JdbcConnection}} will be created and added to the 
> {{org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing#conns}}.
> Such hard link prevents from the {{org.h2.util.CloseWatcher}} to be enqueued 
> and old connections will remain in heap even after the thread exits.
> After some number of SQL queries the {{java.lang.OutOfMemoryError}} will 
> occur.



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

[jira] [Commented] (IGNITE-7122) Page lock status is not checked in BPlusTree.treePrinter methods

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7122:


Github user asfgit closed the pull request at:

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


> Page lock status is not checked in BPlusTree.treePrinter methods
> 
>
> Key: IGNITE-7122
> URL: https://issues.apache.org/jira/browse/IGNITE-7122
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.4
>Reporter: Kirill Shirokov
>Assignee: Kirill Shirokov
> Fix For: 2.4
>
>
> The result of readLock(), which can be 0 is not checked in 
> BPlusTree.treePrinter getChildren() and formatTreeNode() calls:
> {noformat}
> java.lang.AssertionError: 0
> at 
> org.apache.ignite.internal.pagemem.PageUtils.getLong(PageUtils.java:117)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.PageIO.getPageId(PageIO.java:279)
> at 
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.checkPageId(BPlusTreeSelfTest.java:2307)
> at 
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest$TestTree.onReadUnlock(BPlusTreeSelfTest.java:2445)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readUnlock(PageHandler.java:203)
> at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.readUnlock(DataStructure.java:186)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$400(BPlusTree.java:82)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$1.getChildren(BPlusTree.java:163)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$1.getChildren(BPlusTree.java:120)
> at 
> org.apache.ignite.internal.util.lang.GridTreePrinter.printTree(GridTreePrinter.java:60)
> at 
> org.apache.ignite.internal.util.lang.GridTreePrinter.printTree(GridTreePrinter.java:67)
> at 
> org.apache.ignite.internal.util.lang.GridTreePrinter.print(GridTreePrinter.java:32)
> at 
> org.apache.ignite.internal.util.lang.GridTreePrinter.print(GridTreePrinter.java:43)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.printTree(BPlusTree.java:1188)
> at 
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest$19.call(BPlusTreeSelfTest.java:1777)
> at 
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest$19.call(BPlusTreeSelfTest.java:1771)
> at 
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {noformat}
> ...which causes intermittent failures in the BPlusTree unit tests:
> BPlusTreePageMemoryImplTest.testPutRmvSizeSinglePageContention
> BPlusTreeReuseListPageMemoryImplTest.testPutRmvSizeSinglePageContention 



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

[jira] [Updated] (IGNITE-7122) Page lock status is not checked in BPlusTree.treePrinter methods

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-7122:

Fix Version/s: 2.4

> Page lock status is not checked in BPlusTree.treePrinter methods
> 
>
> Key: IGNITE-7122
> URL: https://issues.apache.org/jira/browse/IGNITE-7122
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.4
>Reporter: Kirill Shirokov
>Assignee: Kirill Shirokov
> Fix For: 2.4
>
>
> The result of readLock(), which can be 0 is not checked in 
> BPlusTree.treePrinter getChildren() and formatTreeNode() calls:
> {noformat}
> java.lang.AssertionError: 0
> at 
> org.apache.ignite.internal.pagemem.PageUtils.getLong(PageUtils.java:117)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.PageIO.getPageId(PageIO.java:279)
> at 
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest.checkPageId(BPlusTreeSelfTest.java:2307)
> at 
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest$TestTree.onReadUnlock(BPlusTreeSelfTest.java:2445)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.readUnlock(PageHandler.java:203)
> at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.readUnlock(DataStructure.java:186)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.access$400(BPlusTree.java:82)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$1.getChildren(BPlusTree.java:163)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$1.getChildren(BPlusTree.java:120)
> at 
> org.apache.ignite.internal.util.lang.GridTreePrinter.printTree(GridTreePrinter.java:60)
> at 
> org.apache.ignite.internal.util.lang.GridTreePrinter.printTree(GridTreePrinter.java:67)
> at 
> org.apache.ignite.internal.util.lang.GridTreePrinter.print(GridTreePrinter.java:32)
> at 
> org.apache.ignite.internal.util.lang.GridTreePrinter.print(GridTreePrinter.java:43)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.printTree(BPlusTree.java:1188)
> at 
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest$19.call(BPlusTreeSelfTest.java:1777)
> at 
> org.apache.ignite.internal.processors.database.BPlusTreeSelfTest$19.call(BPlusTreeSelfTest.java:1771)
> at 
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> {noformat}
> ...which causes intermittent failures in the BPlusTree unit tests:
> BPlusTreePageMemoryImplTest.testPutRmvSizeSinglePageContention
> BPlusTreeReuseListPageMemoryImplTest.testPutRmvSizeSinglePageContention 



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

[jira] [Updated] (IGNITE-6882) Introduction of computation graph

[Yury Babak (JIRA)]

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

Yury Babak updated IGNITE-6882:
---
Fix Version/s: (was: 2.4)

> Introduction of computation graph
> -
>
> Key: IGNITE-6882
> URL: https://issues.apache.org/jira/browse/IGNITE-6882
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
>
> We want to implement a computation graph for NNs because this should helps us 
> achieve for neural networks not only data parallelism but model parallelism 
> too.



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

[jira] [Created] (IGNITE-7174) Local MLP

[Yury Babak (JIRA)]

Yury Babak created IGNITE-7174:
--

 Summary: Local MLP
 Key: IGNITE-7174
 URL: https://issues.apache.org/jira/browse/IGNITE-7174
 Project: Ignite
  Issue Type: Sub-task
  Components: ml
Reporter: Yury Babak
 Fix For: 2.4


local version of MLP



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

[jira] [Commented] (IGNITE-6663) SQL: optimize primary key equality lookup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6663:


Github user asfgit closed the pull request at:

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


> SQL: optimize primary key equality lookup
> -
>
> Key: IGNITE-6663
> URL: https://issues.apache.org/jira/browse/IGNITE-6663
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Kirill Shirokov
>  Labels: performance
> Fix For: 2.4
>
>
> H2 perform every index search through {{BaseIndex.find}} method. It contains 
> both {{first}} and {{last}} rows. If condition looks like {{attr = ?}}, then 
> both bounds are the same. When this call is propagated to our {{BPlusTree}}, 
> then two index lookups occur:
> - Lower bound: {{BPlusTree#findInsertionPoint}}
> - Upper bound: {{BPlusTree.ForwardCursor#findUpperBound}}
> This is done for a reason because we do not know in advance how many elements 
> are in between the bounds, so one lookup + scan is not an option in general 
> case. But in case of PK lookup with equality condition, when we know in 
> advance that only one row will be returned, this leads to additional 
> unnecessary comparisons. 
> Suggested fix:
> 1) Make sure that all rows in {{GridH2PlainRowFactory}} has correct 
> {{equals}} implementation.
> 2) Inside {{H2TreeIndex#find}}: if this is PK index (see constructor args) 
> and {{lower.equals(upper)}}, then use {{BPlusTree.findOne}} instead of 
> {{BPlusTree.find}}.



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

[jira] [Updated] (IGNITE-7129) Implement Multilayer Perceptron

[Yury Babak (JIRA)]

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

Yury Babak updated IGNITE-7129:
---
Labels: important  (was: )

> Implement Multilayer Perceptron
> ---
>
> Key: IGNITE-7129
> URL: https://issues.apache.org/jira/browse/IGNITE-7129
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>  Labels: important
>




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

[jira] [Updated] (IGNITE-7129) Implement Multilayer Perceptron

[Yury Babak (JIRA)]

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

Yury Babak updated IGNITE-7129:
---
Component/s: ml

> Implement Multilayer Perceptron
> ---
>
> Key: IGNITE-7129
> URL: https://issues.apache.org/jira/browse/IGNITE-7129
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>




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

[jira] [Resolved] (IGNITE-7150) Gradient boosting for lin regression

[Yury Babak (JIRA)]

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

Yury Babak resolved IGNITE-7150.

Resolution: Invalid

Wrong task

> Gradient boosting for lin regression
> 
>
> Key: IGNITE-7150
> URL: https://issues.apache.org/jira/browse/IGNITE-7150
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>
> Currently for linreg we have only the analytical trainer (via QR 
> decomposition). We want to add new trainer(implementation of Trainer 
> interface) based on gradient boosting.



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

[jira] [Created] (IGNITE-7173) SQL: implement optional row cache

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-7173:
---

 Summary: SQL: implement optional row cache
 Key: IGNITE-7173
 URL: https://issues.apache.org/jira/browse/IGNITE-7173
 Project: Ignite
  Issue Type: Bug
  Components: sql
Reporter: Vladimir Ozerov
Assignee: Vladimir Ozerov
 Fix For: 2.4






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

[jira] [Assigned] (IGNITE-6743) Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov reassigned IGNITE-6743:


Assignee: Andrey Kuznetsov

> Java 9: rework DirectBuffer.cleaner().clean() usage in GridNioServer
> 
>
> Key: IGNITE-6743
> URL: https://issues.apache.org/jira/browse/IGNITE-6743
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Andrey Kuznetsov
> Fix For: 2.4
>
>
> When session is closed we clean allocated {{DirectByteBuffer}}-s using 
> {{sun.misc.Cleaner}}. Need to rework this piece to reflection-based approach 
> which will work for supported Java versions.



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

[jira] [Commented] (IGNITE-7170) Fix javadoc MemoryConfiguration (20% instead of 80%)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7170:


Github user asfgit closed the pull request at:

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


> Fix javadoc MemoryConfiguration (20% instead of 80%)
> 
>
> Key: IGNITE-7170
> URL: https://issues.apache.org/jira/browse/IGNITE-7170
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Trivial
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> org.apache.ignite.configuration.MemoryConfiguration#setDefaultMemoryPolicySize
>  - has wrong javadoc - there is info about 80%.
> It should be 20% 



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

[jira] [Commented] (IGNITE-7170) Fix javadoc MemoryConfiguration (20% instead of 80%)

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov commented on IGNITE-7170:
--

[~alexey.tank2],
Thank for your contribution! I've merged the changes to master.

> Fix javadoc MemoryConfiguration (20% instead of 80%)
> 
>
> Key: IGNITE-7170
> URL: https://issues.apache.org/jira/browse/IGNITE-7170
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Trivial
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> org.apache.ignite.configuration.MemoryConfiguration#setDefaultMemoryPolicySize
>  - has wrong javadoc - there is info about 80%.
> It should be 20% 



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

[jira] [Resolved] (IGNITE-7170) Fix javadoc MemoryConfiguration (20% instead of 80%)

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov resolved IGNITE-7170.
--
Resolution: Fixed

> Fix javadoc MemoryConfiguration (20% instead of 80%)
> 
>
> Key: IGNITE-7170
> URL: https://issues.apache.org/jira/browse/IGNITE-7170
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Trivial
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> org.apache.ignite.configuration.MemoryConfiguration#setDefaultMemoryPolicySize
>  - has wrong javadoc - there is info about 80%.
> It should be 20% 



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

[jira] [Assigned] (IGNITE-7172) Web console: Add example to queries page

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin reassigned IGNITE-7172:


Assignee: Andrey Novikov  (was: Alexey Kuznetsov)

> Web console: Add example to queries page
> 
>
> Key: IGNITE-7172
> URL: https://issues.apache.org/jira/browse/IGNITE-7172
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitriy Shabalin
>Assignee: Andrey Novikov
>




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

[jira] [Commented] (IGNITE-4447) Remove "Ignite 150 Clients" suite.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4447:


GitHub user SomeFire opened a pull request:

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

IGNITE-4447: Remove "Ignite 150 Clients" suite.

Picked from 
https://github.com/apache/ignite/pull/1952/commits/f9d64f1e58b794caee47e584aa32ec18246fe434
 by vadopolski.

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

$ git pull https://github.com/SomeFire/ignite ignite-4447

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

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


commit 146c785326b9091f0fa07308677a7dc4ce630fe2
Author: Dmitrii Ryabov 
Date:   2017-12-12T11:19:37Z

IGNITE-4447: Remove "Ignite 150 Clients" suite.




> Remove "Ignite 150 Clients" suite.
> --
>
> Key: IGNITE-4447
> URL: https://issues.apache.org/jira/browse/IGNITE-4447
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Ryabov Dmitrii
>Priority: Minor
>
> It has only 1 tests. It runs for ~1m, but takes ~6m including build phase. 
> Let's just embed it into one of cache suites.



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

[jira] [Assigned] (IGNITE-4447) Remove "Ignite 150 Clients" suite.

[Ryabov Dmitrii (JIRA)]

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

Ryabov Dmitrii reassigned IGNITE-4447:
--

Assignee: Ryabov Dmitrii  (was: Vadim Opolski)

> Remove "Ignite 150 Clients" suite.
> --
>
> Key: IGNITE-4447
> URL: https://issues.apache.org/jira/browse/IGNITE-4447
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Ryabov Dmitrii
>Priority: Minor
>
> It has only 1 tests. It runs for ~1m, but takes ~6m including build phase. 
> Let's just embed it into one of cache suites.



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

[jira] [Assigned] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-6976:
-

Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>




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

[jira] [Commented] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-6976:
---

1-3 fixed.
To test: 
# Execution of base Visor console commands.
# Checks in disconnected and inactive state.
# -k and -v arguments of modify command.

> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>




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

[jira] [Assigned] (IGNITE-7172) Web console: Add example to queries page

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin reassigned IGNITE-7172:


Assignee: Alexey Kuznetsov  (was: Dmitriy Shabalin)

[~kuaw26] added example, pls review it

> Web console: Add example to queries page
> 
>
> Key: IGNITE-7172
> URL: https://issues.apache.org/jira/browse/IGNITE-7172
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitriy Shabalin
>Assignee: Alexey Kuznetsov
>




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

[jira] [Created] (IGNITE-7172) Web console: Add example to queries page

[Dmitriy Shabalin (JIRA)]

Dmitriy Shabalin created IGNITE-7172:


 Summary: Web console: Add example to queries page
 Key: IGNITE-7172
 URL: https://issues.apache.org/jira/browse/IGNITE-7172
 Project: Ignite
  Issue Type: Improvement
Reporter: Dmitriy Shabalin
Assignee: Dmitriy Shabalin






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

[jira] [Updated] (IGNITE-7171) .NET: Support additional Data Region metrics

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov updated IGNITE-7171:
-
Description: 
Issue [1] adds some new Data Region metrics. They should be added to .NET as 
well:
* totalAllocatedSize
* physicalMemorySize
* checkpointBufferSize

[1] https://issues.apache.org/jira/browse/IGNITE-6902

  was:
Issue [1] adds two new Data Region metrics. Both should be added to .NET as 
well.

[1] https://issues.apache.org/jira/browse/IGNITE-6902


> .NET: Support additional Data Region metrics
> 
>
> Key: IGNITE-7171
> URL: https://issues.apache.org/jira/browse/IGNITE-7171
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Andrey Kuznetsov
>  Labels: iep-6
> Fix For: 2.4
>
>
> Issue [1] adds some new Data Region metrics. They should be added to .NET as 
> well:
> * totalAllocatedSize
> * physicalMemorySize
> * checkpointBufferSize
> [1] https://issues.apache.org/jira/browse/IGNITE-6902



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

[jira] [Commented] (IGNITE-6902) Implement new JMX metrics for Memory Regions

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov commented on IGNITE-6902:
--

[~ptupitsyn], thanks, I've created separate ticket for .NET counterpart, [1]

[1] https://issues.apache.org/jira/browse/IGNITE-7171

> Implement new JMX metrics for Memory Regions
> 
>
> Key: IGNITE-6902
> URL: https://issues.apache.org/jira/browse/IGNITE-6902
> Project: Ignite
>  Issue Type: New Feature
>Reporter: Anton Vinogradov
>Assignee: Andrey Kuznetsov
>Priority: Blocker
>  Labels: iep-6, important
> Fix For: 2.4
>
>
> These additional metrics and methods should be implemented:
> - Bytes used per data region.
> - Size of checkpointing buffer.



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

[jira] [Created] (IGNITE-7171) .NET: Support additional Data Region metrics

[Andrey Kuznetsov (JIRA)]

Andrey Kuznetsov created IGNITE-7171:


 Summary: .NET: Support additional Data Region metrics
 Key: IGNITE-7171
 URL: https://issues.apache.org/jira/browse/IGNITE-7171
 Project: Ignite
  Issue Type: New Feature
Reporter: Andrey Kuznetsov
 Fix For: 2.4


Issue [1] adds two new Data Region metrics. Both should be added to .NET as 
well.

[1] https://issues.apache.org/jira/browse/IGNITE-6902



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

[jira] [Comment Edited] (IGNITE-4750) SQL: Support GROUP_CONCAT function

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-4750 at 12/12/17 10:49 AM:
-

[~al.psc], you right {{sql}} member is used as argument for {{CAST}} and 
{{TABLE}} functions. Fixed.
[~vozerov], please take a look.


was (Author: tledkov-gridgain):
[~al.psc], you right {{sql}} member is used as argument for {{CAST}} and 
{{TABLE}} functions. Fixed.

> SQL: Support GROUP_CONCAT function
> --
>
> Key: IGNITE-4750
> URL: https://issues.apache.org/jira/browse/IGNITE-4750
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
> Fix For: 2.4
>
>
> GROUP_CONCAT function is not supported at the moment. Makes sense to fill 
> this gap:
> http://apache-ignite-users.70518.x6.nabble.com/GROUP-CONCAT-function-is-unsupported-td10757.html
> Presently the function doc is hidden:
> https://apacheignite-sql.readme.io/docs/group_concat
> Open it up once the ticket is released.



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

[jira] [Commented] (IGNITE-4750) SQL: Support GROUP_CONCAT function

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-4750:
--

[~al.psc], you right {{sql}} member is used as argument for {{CAST}} and 
{{TABLE}} functions. Fixed.

> SQL: Support GROUP_CONCAT function
> --
>
> Key: IGNITE-4750
> URL: https://issues.apache.org/jira/browse/IGNITE-4750
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
> Fix For: 2.4
>
>
> GROUP_CONCAT function is not supported at the moment. Makes sense to fill 
> this gap:
> http://apache-ignite-users.70518.x6.nabble.com/GROUP-CONCAT-function-is-unsupported-td10757.html
> Presently the function doc is hidden:
> https://apacheignite-sql.readme.io/docs/group_concat
> Open it up once the ticket is released.



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

[jira] [Updated] (IGNITE-6433) We need to cancel eviction instead of waiting it when we should own a partition because we had lost it

[Alexandr Kuramshin (JIRA)]

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

Alexandr Kuramshin updated IGNITE-6433:
---
Priority: Critical  (was: Major)

> We need to cancel eviction instead of waiting it when we should own a 
> partition because we had lost it
> --
>
> Key: IGNITE-6433
> URL: https://issues.apache.org/jira/browse/IGNITE-6433
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Priority: Critical
>
> If PartitionLossPolicy.IGNORE is used and we have lost some partition which 
> would belong to us because of affinity assignment and its state was RENTING 
> then we would wait for its eviction completing what would hang cluster (the 
> time of exchange would significantly increase).
> Instead of waiting we should cancel eviction and it's all.



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

[jira] [Commented] (IGNITE-6433) We need to cancel eviction instead of waiting it when we should own a partition because we had lost it

[Alexandr Kuramshin (JIRA)]

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

Alexandr Kuramshin commented on IGNITE-6433:


The following thread deadlock occurs frequently on node stop causing the whole 
test suite timeout

{noformat}
sys-#1524465%dht.GridCachePartitionedNearDisabledOptimisticTxNodeRestartTest0%
prio=10 tid=0x7f082002a800 nid=0x6c13 waiting on condition 
[0x7f0793ebc000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x000748e6d530> (a 
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireShared(AbstractQueuedSynchronizer.java:964)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireShared(AbstractQueuedSynchronizer.java:1282)
at 
java.util.concurrent.locks.ReentrantReadWriteLock$ReadLock.lock(ReentrantReadWriteLock.java:731)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.partitionMap(GridDhtPartitionTopologyImpl.java:1162)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.createPartitionsFullMessage(GridCachePartitionExchangeManager.java:1045)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.sendAllPartitions(GridCachePartitionExchangeManager.java:981)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.refreshPartitions(GridCachePartitionExchangeManager.java:964)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$2400(GridCachePartitionExchangeManager.java:131)
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ResendTimeoutObject$1.run(GridCachePartitionExchangeManager.java:2506)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6695)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)

sys-#1524152%dht.GridCachePartitionedNearDisabledOptimisticTxNodeRestartTest0%
prio=10 tid=0x7f07bc1eb800 nid=0x6abf waiting on condition 
[0x7f08d48ed000]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x000748e6d9f8> (a 
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197)
at 
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:945)
at 
org.apache.ignite.internal.util.StripedCompositeReadWriteLock$WriteLock.lock0(StripedCompositeReadWriteLock.java:154)
at 
org.apache.ignite.internal.util.StripedCompositeReadWriteLock$WriteLock.lock(StripedCompositeReadWriteLock.java:123)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.onEvicted(GridDhtPartitionTopologyImpl.java:2253)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.onPartitionEvicted(GridDhtPreloader.java:461)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.finishDestroy(GridDhtLocalPartition.java:731)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.clearEvicting(GridDhtLocalPartition.java:699)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:759)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:593)
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:580)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6639)
 

[jira] [Commented] (IGNITE-6123) First performance measurement of implemented ml algorithms

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-6123:


[~chief] I did as you suggested and re-run lic & javadoc check - please take a 
look (grouping is a really good idea, thank you)

> First performance measurement of implemented ml algorithms
> --
>
> Key: IGNITE-6123
> URL: https://issues.apache.org/jira/browse/IGNITE-6123
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml, yardstick
>Reporter: Yury Babak
>Assignee: Oleg Ignatenko
> Fix For: 2.4
>
>
> We want to start tracking our performance to avoid performance degradation. 
> Also we need some performance comparison with other ml libs.



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

[jira] [Assigned] (IGNITE-7168) Web Console: Cleanup webAgentDownloadVisibleStates

[Ilya Borisov (JIRA)]

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

Ilya Borisov reassigned IGNITE-7168:


Assignee: Andrey Novikov  (was: Ilya Borisov)

[~anovikov] please review.

> Web Console: Cleanup webAgentDownloadVisibleStates
> --
>
> Key: IGNITE-7168
> URL: https://issues.apache.org/jira/browse/IGNITE-7168
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
>Priority: Minor
> Fix For: 2.4
>
>
> We moved "Agent download" to footer.
> Lets cleanup unused code in header see "connectedClustersUnvisibleStates" in 
> app\components\web-console-header.



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

[jira] [Commented] (IGNITE-4750) SQL: Support GROUP_CONCAT function

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko commented on IGNITE-4750:
-

[~tledkov-gridgain],
Right, but {{GridSqlType}} is also associated with SQL keyword for 
corresponding type, and, although it does not affect current task, we should 
use right keyword which is {{VARCHAR}}.

> SQL: Support GROUP_CONCAT function
> --
>
> Key: IGNITE-4750
> URL: https://issues.apache.org/jira/browse/IGNITE-4750
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
> Fix For: 2.4
>
>
> GROUP_CONCAT function is not supported at the moment. Makes sense to fill 
> this gap:
> http://apache-ignite-users.70518.x6.nabble.com/GROUP-CONCAT-function-is-unsupported-td10757.html
> Presently the function doc is hidden:
> https://apacheignite-sql.readme.io/docs/group_concat
> Open it up once the ticket is released.



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

[jira] [Commented] (IGNITE-6171) Native facility to control excessive GC pauses

[Dmitriy Sorokin (JIRA)]

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

Dmitriy Sorokin commented on IGNITE-6171:
-

[~avinogradov], review my new patch, please. I think that passing of Ignite 
Basic test suite is enouth for this patch.

> Native facility to control excessive GC pauses
> --
>
> Key: IGNITE-6171
> URL: https://issues.apache.org/jira/browse/IGNITE-6171
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
>Assignee: Dmitriy Sorokin
>  Labels: iep-7, usability
> Fix For: 2.4
>
>
> Ignite is Java-based application. If node experiences long GC pauses it may 
> negatively affect other nodes. We need to find a way to detect long GC pauses 
> within the process and trigger some actions in response, e.g. node stop. 
> This is a kind of Inception \[1\], when you need to understand that you sleep 
> while sleeping. As all Java threads are blocked on safepoint, we cannot use 
> Java's thread to detect Java's GC. Native threads should be used instead.
> Proposed solution:
> 1) Thread 1 should periodically call dummy JNI method returning current time, 
> and set this time to shared variable;
> 2) Thread 2 should periodically check that variable. If it has not been 
> changed for some time - most likely we are in GC pause. Once certain 
> threashold is reached - trigger compensating action, whether this is a 
> warning, process kill, or what so ever.
> Justification: crossing native -> Java boundaries involves safepoints. This 
> way Thread 1 will be trapped if STW pause is in progress. Java method cannot 
> be empty, as JVM is smart enough and can deduce it to no-op. 
> \[1\] http://www.imdb.com/title/tt1375666/



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

[jira] [Commented] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-602:


[~SomeFire] We discussed early 
(https://issues.apache.org/jira/browse/IGNITE-602?focusedCommentId=16184176=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16184176)
 that it's very strange to change core classes when fix should affect only 
utility classes. Why {{@GridToStringExclude}} annotation in {{GridNioServer}} 
leads to failures?

> [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by 
> infinite recursion
> 
>
> Key: IGNITE-602
> URL: https://issues.apache.org/jira/browse/IGNITE-602
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Artem Shutak
>Assignee: Ryabov Dmitrii
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.4
>
>
> See test 
> org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention
>  and related TODO in same source file.
> Also take a look at 
> http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring
> Test should be unmuted on TC after fix.



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

[jira] [Comment Edited] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion

[Andrey Gura (JIRA)]

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

Andrey Gura edited comment on IGNITE-602 at 12/12/17 10:16 AM:
---

[~SomeFire] We discussed earlier 
(https://issues.apache.org/jira/browse/IGNITE-602?focusedCommentId=16184176=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16184176)
 that it's very strange to change core classes when fix should affect only 
utility classes. Why {{@GridToStringExclude}} annotation in {{GridNioServer}} 
leads to failures?


was (Author: agura):
[~SomeFire] We discussed early 
(https://issues.apache.org/jira/browse/IGNITE-602?focusedCommentId=16184176=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16184176)
 that it's very strange to change core classes when fix should affect only 
utility classes. Why {{@GridToStringExclude}} annotation in {{GridNioServer}} 
leads to failures?

> [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by 
> infinite recursion
> 
>
> Key: IGNITE-602
> URL: https://issues.apache.org/jira/browse/IGNITE-602
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Artem Shutak
>Assignee: Ryabov Dmitrii
>  Labels: MakeTeamcityGreenAgain, Muted_test
> Fix For: 2.4
>
>
> See test 
> org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention
>  and related TODO in same source file.
> Also take a look at 
> http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring
> Test should be unmuted on TC after fix.



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

[jira] [Commented] (IGNITE-4750) SQL: Support GROUP_CONCAT function

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-4750:
--

[~al.psc], thanks a lot! Fixed all comments except *p.7*.  {{GridSqlType}} is 
mapped to H2 types. See more 
[{{org.h2.value.Value}}|https://github.com/h2database/h2database/blob/f2d27a3ae44e2fa24c59b3cfeb431216da9c572c/h2/src/main/org/h2/value/Value.java#L43]

> SQL: Support GROUP_CONCAT function
> --
>
> Key: IGNITE-4750
> URL: https://issues.apache.org/jira/browse/IGNITE-4750
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
> Fix For: 2.4
>
>
> GROUP_CONCAT function is not supported at the moment. Makes sense to fill 
> this gap:
> http://apache-ignite-users.70518.x6.nabble.com/GROUP-CONCAT-function-is-unsupported-td10757.html
> Presently the function doc is hidden:
> https://apacheignite-sql.readme.io/docs/group_concat
> Open it up once the ticket is released.



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

[jira] [Issue Comment Deleted] (IGNITE-6333) Improve cache transaction metrics to better understand transactions efficiency.

[Pavel Pereslegin (JIRA)]

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

Pavel Pereslegin updated IGNITE-6333:
-
Comment: was deleted

(was: @ascherbakov, in common case deadlock detection starts if timeout was 
expired.
If timeout and deadlock are detected, do we need to count only deadlocks or 
both?)

> Improve cache transaction metrics to better understand transactions 
> efficiency.
> ---
>
> Key: IGNITE-6333
> URL: https://issues.apache.org/jira/browse/IGNITE-6333
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Alexei Scherbakov
>Assignee: Pavel Pereslegin
>  Labels: cache, newbie
>
> I suggest to add:
> 1. Count of rollbacks due to transaction timeout. Depends on IGNITE-6181
> 2. Count of rollbacks due to deadlocks.



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

[jira] [Commented] (IGNITE-6333) Improve cache transaction metrics to better understand transactions efficiency.

[Pavel Pereslegin (JIRA)]

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

Pavel Pereslegin commented on IGNITE-6333:
--

[~ascherbakov], in common case deadlock detection starts if timeout was expired.
If timeout and deadlock are detected, do we need to count only deadlocks or 
both?

> Improve cache transaction metrics to better understand transactions 
> efficiency.
> ---
>
> Key: IGNITE-6333
> URL: https://issues.apache.org/jira/browse/IGNITE-6333
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Alexei Scherbakov
>Assignee: Pavel Pereslegin
>  Labels: cache, newbie
>
> I suggest to add:
> 1. Count of rollbacks due to transaction timeout. Depends on IGNITE-6181
> 2. Count of rollbacks due to deadlocks.



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

[jira] [Commented] (IGNITE-6333) Improve cache transaction metrics to better understand transactions efficiency.

[Pavel Pereslegin (JIRA)]

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

Pavel Pereslegin commented on IGNITE-6333:
--

@ascherbakov, in common case deadlock detection starts if timeout was expired.
If timeout and deadlock are detected, do we need to count only deadlocks or 
both?

> Improve cache transaction metrics to better understand transactions 
> efficiency.
> ---
>
> Key: IGNITE-6333
> URL: https://issues.apache.org/jira/browse/IGNITE-6333
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Alexei Scherbakov
>Assignee: Pavel Pereslegin
>  Labels: cache, newbie
>
> I suggest to add:
> 1. Count of rollbacks due to transaction timeout. Depends on IGNITE-6181
> 2. Count of rollbacks due to deadlocks.



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

[jira] [Resolved] (IGNITE-5114) Parallel plus/multiply matrix algorithms.

[Yury Babak (JIRA)]

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

Yury Babak resolved IGNITE-5114.

Resolution: Done

Done in 5280, implemented SparseBlockDistributedMatrix which is more suitable 
for matrix calculations

> Parallel plus/multiply matrix algorithms.
> -
>
> Key: IGNITE-5114
> URL: https://issues.apache.org/jira/browse/IGNITE-5114
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
>  Labels: important
> Fix For: 2.4
>
>
> We need design and implement parallel(distributed?) versions of matrix 
> plus/multiply algorithms because current implementation is implemented by 
> definition. Those implementations is really slow.



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

[jira] [Commented] (IGNITE-4750) SQL: Support GROUP_CONCAT function

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko commented on IGNITE-4750:
-

[~tledkov-gridgain], my comments:

{{GridSqlAggregateFunction}}:
1. Please don't use strings addition together with {{StatementBuilder}} - use 
{{append}} instead.
2. Please use {{resetCount()}} before {{appendExceptFirst()}} - these 
operations are looking at the same counter, and therefore it should be reset 
every time you use {{appendExceptFirst()}}.
3. Methods {{setGroupConcat*}} have way too wordy param names, like this: 
{{setGroupConcatSeparator(groupConcatSeparator)}} - there's redundancy, you can 
use simply {{separator}} for param name without losing any clarity.

4. {{GridSqlQueryParser}}: Code conventions are violated - long lines.

{{GridSqlQuerySplitter}}:
5. Please throw {{IgniteSqlException}} instead of {{IgniteException}}, error 
code should be {{UNSUPPORTED_OPERATION}}.
6. Here: {{rdcAgg = aggregate(false, agg.type())}} please use {{GROUP_CONCAT}} 
as the second arg for clarity.

7. {{GridSqlType}}: I believe SQL keyword for strings is {{VARCHAR}}, not 
{{STRING}}, isn't it?

8. {{IgniteSqlGroupConcatCollocatedTest}}: please fix long lines.

> SQL: Support GROUP_CONCAT function
> --
>
> Key: IGNITE-4750
> URL: https://issues.apache.org/jira/browse/IGNITE-4750
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Denis Magda
>Assignee: Taras Ledkov
> Fix For: 2.4
>
>
> GROUP_CONCAT function is not supported at the moment. Makes sense to fill 
> this gap:
> http://apache-ignite-users.70518.x6.nabble.com/GROUP-CONCAT-function-is-unsupported-td10757.html
> Presently the function doc is hidden:
> https://apacheignite-sql.readme.io/docs/group_concat
> Open it up once the ticket is released.



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

[jira] [Resolved] (IGNITE-5847) API for Models

[Yury Babak (JIRA)]

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

Yury Babak resolved IGNITE-5847.

Resolution: Done

Model API introduced in 
[K-means|https://issues.apache.org/jira/browse/IGNITE-5825]
Trainer API introduced in [decision 
tree|https://issues.apache.org/jira/browse/IGNITE-5218]

> API for Models
> --
>
> Key: IGNITE-5847
> URL: https://issues.apache.org/jira/browse/IGNITE-5847
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
>  Labels: important
> Fix For: 2.4
>
>
> We want to design and implement API for Models.



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

[jira] [Commented] (IGNITE-7170) Fix javadoc MemoryConfiguration (20% instead of 80%)

[Alexey Popov (JIRA)]

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

Alexey Popov commented on IGNITE-7170:
--

[~ntikho...@apache.org], please review this cosmetic change

> Fix javadoc MemoryConfiguration (20% instead of 80%)
> 
>
> Key: IGNITE-7170
> URL: https://issues.apache.org/jira/browse/IGNITE-7170
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Trivial
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> org.apache.ignite.configuration.MemoryConfiguration#setDefaultMemoryPolicySize
>  - has wrong javadoc - there is info about 80%.
> It should be 20% 



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

[jira] [Commented] (IGNITE-7170) Fix javadoc MemoryConfiguration (20% instead of 80%)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7170:


GitHub user apopovgg opened a pull request:

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

IGNITE-7170 Fix javadoc MemoryConfiguration (20% instead of 80%)



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

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

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

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


commit 104b43cec4e8b07bbb8f2d00852bda6b762a5716
Author: apopov 
Date:   2017-12-12T09:20:40Z

IGNITE-7170 Fix javadoc MemoryConfiguration (20% instead of 80%)




> Fix javadoc MemoryConfiguration (20% instead of 80%)
> 
>
> Key: IGNITE-7170
> URL: https://issues.apache.org/jira/browse/IGNITE-7170
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Trivial
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> org.apache.ignite.configuration.MemoryConfiguration#setDefaultMemoryPolicySize
>  - has wrong javadoc - there is info about 80%.
> It should be 20% 



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

[jira] [Commented] (IGNITE-1267) JobStealingCollisionSpi never sends jobs to a node that joined after task was executed

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-1267:


Github user AMashenkov closed the pull request at:

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


> JobStealingCollisionSpi never sends jobs to a node that joined after task was 
> executed
> --
>
> Key: IGNITE-1267
> URL: https://issues.apache.org/jira/browse/IGNITE-1267
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Andrew Mashenkov
>  Labels: user-request
>
> Corresponding user thread (contains detailed description of the scenario that 
> doesn't work): 
> http://apache-ignite-users.70518.x6.nabble.com/Dynamic-ComputeTask-distribution-with-new-nodes-td997.html
> Essentially, {{JobStealingCollisionSpi}} always skips jobs that are not in 
> task topology (see line 713). Task topology is static and created when task 
> is executed, so newly joined node can't steal jobs. I think it should be able 
> to do this if it satisfies initial cluster group predicate.



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

[jira] [Commented] (IGNITE-4172) SQL: Add support for Java 8 Time API classes in date\time functions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4172:


Github user AMashenkov closed the pull request at:

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


> SQL: Add support for Java 8 Time API classes in date\time functions
> ---
>
> Key: IGNITE-4172
> URL: https://issues.apache.org/jira/browse/IGNITE-4172
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.0
>Reporter: Andrew Mashenkov
>Assignee: Alexandr Fedotov
>  Labels: usability
> Fix For: 2.4
>
>
> We have is issue with querying LocalDateTime objects with our SQL engine. 
> Next query can fails with error, if one of row localDateTimeField value has 
> zero-time: 
> select DATEDIFF('DAY', localDateTimeField, CURRENT_DATE ()) from t;
> Startpoint is IgniteH2Indexing.wrap() method. 
> We need add support to these classes: LocalDate, LocalTime, LocalDateTime.



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

[jira] [Updated] (IGNITE-7170) Fix javadoc MemoryConfiguration (20% instead of 80%)

[Alexey Popov (JIRA)]

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

Alexey Popov updated IGNITE-7170:
-
Description: 
org.apache.ignite.configuration.MemoryConfiguration#setDefaultMemoryPolicySize 
- has wrong javadoc - there is info about 80%.
It should be 20% 

> Fix javadoc MemoryConfiguration (20% instead of 80%)
> 
>
> Key: IGNITE-7170
> URL: https://issues.apache.org/jira/browse/IGNITE-7170
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>Priority: Trivial
>   Original Estimate: 5m
>  Remaining Estimate: 5m
>
> org.apache.ignite.configuration.MemoryConfiguration#setDefaultMemoryPolicySize
>  - has wrong javadoc - there is info about 80%.
> It should be 20% 



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

[jira] [Commented] (IGNITE-6984) Make cache creation slightly more verbose.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6984:


Github user AMashenkov closed the pull request at:

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


> Make cache creation slightly more verbose.
> --
>
> Key: IGNITE-6984
> URL: https://issues.apache.org/jira/browse/IGNITE-6984
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
>
> For now we do not print cacheId on cache start, but use cacheId instead of 
> name everywhere in logs.
> So, it is hard to investigate issues in production.
> Also actual number of backups can be helpful when restoring cache from 
> persistence.
> Lets, add cacheId and number of backups to the "cache start" message.



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

[jira] [Commented] (IGNITE-7157) Deadlock on partition eviction from multiple threads.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7157:


Github user AMashenkov closed the pull request at:

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


> Deadlock on partition eviction from multiple threads.
> -
>
> Key: IGNITE-7157
> URL: https://issues.apache.org/jira/browse/IGNITE-7157
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
> Fix For: 2.4
>
> Attachments: thread-dump
>
>
> When node receive partition update message, it acquire partition and 
> checkpoint locks in different order than asyncronous eviction.
> PFA thread dump.



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

[jira] [Created] (IGNITE-7170) Fix javadoc MemoryConfiguration (20% instead of 80%)

[Alexey Popov (JIRA)]

Alexey Popov created IGNITE-7170:


 Summary: Fix javadoc MemoryConfiguration (20% instead of 80%)
 Key: IGNITE-7170
 URL: https://issues.apache.org/jira/browse/IGNITE-7170
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.3
Reporter: Alexey Popov
Assignee: Alexey Popov
Priority: Trivial






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

[jira] [Assigned] (IGNITE-6976) Visor CMD: Add ability to put/get/remove data to caches via command line Visor.

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-6976:


Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

Please rename VisorModifyCommand to VisorCacheModifyCommand.
And -kv -> -k and -vv -> -v
Move "warn("Can not perform the operation because the cluster is inactive. 
" to single place.

> Visor CMD: Add ability to put/get/remove data to caches via command line 
> Visor.
> ---
>
> Key: IGNITE-6976
> URL: https://issues.apache.org/jira/browse/IGNITE-6976
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>




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

[jira] [Resolved] (IGNITE-6735) Java 9: fix Java version resolution/check logic

[of.salakhutdinov (JIRA)]

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

of.salakhutdinov resolved IGNITE-6735.
--
Resolution: Fixed

Pull request:
https://github.com/apache/ignite/pull/3005
Fix in branch master because it need in all versions.

> Java 9: fix Java version resolution/check logic
> ---
>
> Key: IGNITE-6735
> URL: https://issues.apache.org/jira/browse/IGNITE-6735
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: of.salakhutdinov
> Fix For: 2.4
>
>
> We have several places in the code where Java version is validated. First, 
> sometimes we do not take in count Java 9 at all. Second, sometimes we rely on 
> old version pattern {{1.x}}, while as of Java 9 it is just {{x}}. 
> Places to fix:
> 1) {{GridDiscoveryManager.nodeJavaMajorVersion}} - add support for new Java 
> version format without {{1.}} prefix.
> 2) {{IgnitionEx.}} - add Java 9 to the list of supported 
> versions.



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

[jira] [Resolved] (IGNITE-7169) Missed javadoc for IgniteToDoubleFunction

[Yury Babak (JIRA)]

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

Yury Babak resolved IGNITE-7169.

Resolution: Not A Problem

Already fixed per IGNITE-6949

> Missed javadoc for IgniteToDoubleFunction
> -
>
> Key: IGNITE-7169
> URL: https://issues.apache.org/jira/browse/IGNITE-7169
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.4
>
>
> Missed javadoc for IgniteToDoubleFunction



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