[jira] [Created] (IGNITE-6953) OOM on the client node freezes the whole cluster

[Denis Magda (JIRA)]

Denis Magda created IGNITE-6953:
---

 Summary: OOM on the client node freezes the whole cluster
 Key: IGNITE-6953
 URL: https://issues.apache.org/jira/browse/IGNITE-6953
 Project: Ignite
  Issue Type: Bug
Reporter: Denis Magda
 Fix For: 2.4


It's reported that if an OOM happens on the client side the whole cluster 
becomes unresponsive:
http://apache-ignite-users.70518.x6.nabble.com/Out-of-memory-in-client-node-freezes-complete-cluster-td18044.html

Let's reproduce and prevent this by bringing the client node down 
automatically.  



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

[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: Critical  (was: Major)

> 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
>Assignee: Vladimir Ozerov
>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
> org.apache.ignite.internal.util.nio.GridNioServer$DirectNioClientWorker.processRead(GridNioServer.java:1261)
> [ignite-core-2.3.0.jar:2.3.0]
>   at
> 

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

[Denis Magda (JIRA)]

Denis Magda created IGNITE-6952:
---

 Summary: 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
Assignee: Vladimir Ozerov
 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
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2272)
[ignite-core-2.3.0.jar:2.3.0]
at
org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2048)
[ignite-core-2.3.0.jar:2.3.0]
at

[jira] [Commented] (IGNITE-6944) Fail to execute task with immutable list string

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko commented on IGNITE-6944:
-

This is indeed a regression occurred after 
[IGNITE-6485|https://issues.apache.org/jira/browse/IGNITE-6485] was fixed. For 
some reason, since 2.3 it is looking for readResolve/writeReplace methods only 
in exact class that is being serialized, but not in the whole hierarchy.

[~agura], looks like you did that change. Can you please check?

> Fail to execute task with immutable list string
> ---
>
> Key: IGNITE-6944
> URL: https://issues.apache.org/jira/browse/IGNITE-6944
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: binary
>Affects Versions: 2.3
>Reporter: Edmond Tsang
>
> Exception occurs when executing task with immutable list of string due to not 
> able to find method readResolve/writeReplace for binary object.
> It appears this is caused by a side effect of Jira 
> https://issues.apache.org/jira/browse/IGNITE-6485 



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

[jira] [Commented] (IGNITE-6868) Implement new JMX metrics for TcpCommunicationSpi monitoring

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-6868:
--

[~alex_pl]
Please see codestyle and minor comments at upsource.

I'd like to propose to make another test.
Just start some nodes with redefined TcpCommunicationSpi which counts sent 
messages.
Do some work, cache operations, start stop nodes, etc. 
Then freeze TcpCommunicationSpis and check that what they counted equals to 
metrics result.

> Implement new JMX metrics for TcpCommunicationSpi monitoring
> 
>
> Key: IGNITE-6868
> URL: https://issues.apache.org/jira/browse/IGNITE-6868
> Project: Ignite
>  Issue Type: New Feature
>  Security Level: Public(Viewable by anyone) 
>Reporter: Aleksey Plekhanov
>Assignee: Aleksey Plekhanov
>  Labels: iep-6, jmx
>
> These additional metrics should be implemented in TcpCommunicationSpi MBean:
> * Received messages count grouped by message type
> * Received messages count grouped by sender node
> * Sent messages count grouped by message type
> * Sent messages count grouped by receiver node



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

[jira] [Commented] (IGNITE-5938) Implement WAL logs compaction and compression after checkpoint

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5938:


GitHub user glukos opened a pull request:

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

IGNITE-5938 Try to enable v2 serializer



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

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

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

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


commit 6e3f4043c6ab58f6ad5109bbdaf4832685bc7df8
Author: Ivan Rakov 
Date:   2017-11-17T18:34:54Z

IGNITE-5938 Try to enable v2 serializer




> Implement WAL logs compaction and compression after checkpoint
> --
>
> Key: IGNITE-5938
> URL: https://issues.apache.org/jira/browse/IGNITE-5938
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Ivan Rakov
> Fix For: 2.4
>
>
> Currently, we simply move WAL segments to archive when WAL segment is written 
> and delete when checkpoint history becomes too old. 
> Archived WAL segment contains physical delta records that are no longer 
> needed for rebalancing, so these records may be thrown away. In order to 
> optimize disk space and delta WAL rebalancing, we can do the following:
> 1) Clean the WAL segments from the physical records
> 2) Compress the cleaned segments (I expect this to be very effective since we 
> write full objects)



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

[jira] [Comment Edited] (IGNITE-5845) Benchmarks for ML algorithms.

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko edited comment on IGNITE-5845 at 11/17/17 6:05 PM:
--

Looks like a duplicate of IGNITE-6123 - [~chief] could you please re-check this?


was (Author: oignatenko):
Looks like a duplicate of IGNITE-6123

> Benchmarks for ML algorithms.
> -
>
> Key: IGNITE-5845
> URL: https://issues.apache.org/jira/browse/IGNITE-5845
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Reporter: Yury Babak
>
> We want to create some benchmarks for ML algorithms.



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

[jira] [Commented] (IGNITE-6948) SQL: Document new INLINE_SIZE option in CREATE INDEX command

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-6948:
-

[~kirill.shirokov],

Since that's the feature for 2.4 you should document it on this hidden page:
https://apacheignite-sql.readme.io/v2.3/docs/create-index_24_hidden

Assign the ticket to me for review once you're ready. The more ticket about the 
established documentation process can be found here:
https://cwiki.apache.org/confluence/display/IGNITE/How+to+Document

> SQL: Document new INLINE_SIZE option in CREATE INDEX command
> 
>
> Key: IGNITE-6948
> URL: https://issues.apache.org/jira/browse/IGNITE-6948
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: documentation
>Reporter: Kirill Shirokov
>Assignee: Kirill Shirokov
> Fix For: 2.4
>
>
> INLINE_SIZE is optional and accepts positive integer values. To specify the 
> default inline size user should omit the option.
> The corresponding documentation page is at:
> https://apacheignite-sql.readme.io/docs/create-index



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

[jira] [Assigned] (IGNITE-6940) Provide metric to monitor Thread Starvation

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov reassigned IGNITE-6940:


Assignee: Andrey Kuznetsov

> Provide metric to monitor Thread Starvation
> ---
>
> Key: IGNITE-6940
> URL: https://issues.apache.org/jira/browse/IGNITE-6940
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>  Labels: iep-7
>
> There is an existing code in {{IgniteKernal.start()}} that logs warnings when 
> detects starvation. It should be improved to support more thread pools and 
> update some metrics.



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

[jira] [Commented] (IGNITE-6839) Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-6839:


Hi [~avinogradov], 

It will require us to run it manually 48 times with run on specific agent 
(binded at start). It is manual work. If someone in community can help with 
this I would be glad :)

>From the developer's point of view it is simpler to insert cleanup as build 
>step. Moreover, for some tests repo clean may be required also.

As result I suggest to insert clean for ignite.* at 1st step. If Ignite PDS 
Compatiblity will be come dramatically slower, we will return to this question 
again. What do you think?

> Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2
> 
>
> Key: IGNITE-6839
> URL: https://issues.apache.org/jira/browse/IGNITE-6839
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: persistence
>Affects Versions: 2.3
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> Ignite Compatibility: 2 test are flaky:
>   
> org.apache.ignite.compatibility.testsuites.IgniteCompatibilityBasicTestSuite: 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1
>  (fails: 2/55): 
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-1418165996957466785=%3Cdefault%3E=testDetails
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=1638023358531502921=testDetails_Ignite20Tests=%3Cdefault%3E
> {noformat}
> junit.framework.AssertionFailedError: Directory [binary_meta, 
> 135628fa_5763_46a1_88ff_8c0c8e51fc4e] is expected to exist 
> [/data/teamcity/work/820be461cd64b574/work/binary_meta/135628fa_5763_46a1_88ff_8c0c8e51fc4e]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertDirectoryExist(FoldersReuseCompatibilityTest.java:220)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertPdsDirsDefaultExist(FoldersReuseCompatibilityTest.java:193)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.runFoldersReuse(FoldersReuseCompatibilityTest.java:108)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1(FoldersReuseCompatibilityTest.java:86)
> {noformat}
> Test probaly indicates a bug in 
> https://issues.apache.org/jira/browse/IGNITE-6285



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

[jira] [Commented] (IGNITE-6839) Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-6839:
--

[~dpavlov]
We should fix current problem. Lets clean all org.apache.ignite.* ONCE but 
everywhere.
Can we make such task and run it once?
There is no need to perform clean all org.apache.ignite.* until someone will 
install broken libs again :) 

> Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2
> 
>
> Key: IGNITE-6839
> URL: https://issues.apache.org/jira/browse/IGNITE-6839
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: persistence
>Affects Versions: 2.3
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> Ignite Compatibility: 2 test are flaky:
>   
> org.apache.ignite.compatibility.testsuites.IgniteCompatibilityBasicTestSuite: 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1
>  (fails: 2/55): 
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-1418165996957466785=%3Cdefault%3E=testDetails
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=1638023358531502921=testDetails_Ignite20Tests=%3Cdefault%3E
> {noformat}
> junit.framework.AssertionFailedError: Directory [binary_meta, 
> 135628fa_5763_46a1_88ff_8c0c8e51fc4e] is expected to exist 
> [/data/teamcity/work/820be461cd64b574/work/binary_meta/135628fa_5763_46a1_88ff_8c0c8e51fc4e]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertDirectoryExist(FoldersReuseCompatibilityTest.java:220)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertPdsDirsDefaultExist(FoldersReuseCompatibilityTest.java:193)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.runFoldersReuse(FoldersReuseCompatibilityTest.java:108)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1(FoldersReuseCompatibilityTest.java:86)
> {noformat}
> Test probaly indicates a bug in 
> https://issues.apache.org/jira/browse/IGNITE-6285



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

[jira] [Commented] (IGNITE-6839) Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-6839:


Hi [~avinogradov], [~daradurvs],

I guess if we implement clean all org.apache.ignite.* at agents m2 it will not 
affect task performance as it can be affected by whole repository clean.

What do you think about cleaning ignite related artifacts before PDS 
compatibility suite run?

> Ignite Compatibility: flaky test testFoldersReuseCompatibility_2_1 & 2_2
> 
>
> Key: IGNITE-6839
> URL: https://issues.apache.org/jira/browse/IGNITE-6839
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: persistence
>Affects Versions: 2.3
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> Ignite Compatibility: 2 test are flaky:
>   
> org.apache.ignite.compatibility.testsuites.IgniteCompatibilityBasicTestSuite: 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1
>  (fails: 2/55): 
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-1418165996957466785=%3Cdefault%3E=testDetails
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=1638023358531502921=testDetails_Ignite20Tests=%3Cdefault%3E
> {noformat}
> junit.framework.AssertionFailedError: Directory [binary_meta, 
> 135628fa_5763_46a1_88ff_8c0c8e51fc4e] is expected to exist 
> [/data/teamcity/work/820be461cd64b574/work/binary_meta/135628fa_5763_46a1_88ff_8c0c8e51fc4e]
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertDirectoryExist(FoldersReuseCompatibilityTest.java:220)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.assertPdsDirsDefaultExist(FoldersReuseCompatibilityTest.java:193)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.runFoldersReuse(FoldersReuseCompatibilityTest.java:108)
> at 
> org.apache.ignite.compatibility.persistence.FoldersReuseCompatibilityTest.testFoldersReuseCompatibility_2_1(FoldersReuseCompatibilityTest.java:86)
> {noformat}
> Test probaly indicates a bug in 
> https://issues.apache.org/jira/browse/IGNITE-6285



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

[jira] [Commented] (IGNITE-6949) Cleanup OLS code

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6949:


GitHub user zaleslaw opened a pull request:

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

IGNITE-6949: Add support of distributed matrices for OLS regression



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

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

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

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


commit b84d1b6ae284edaa510f7eefa84f5594dd1cb83e
Author: zaleslaw 
Date:   2017-11-17T14:44:05Z

Removed incorrect patch

commit 401a464c6bde19bbf1f11d0d32a2aea9facc
Author: zaleslaw 
Date:   2017-11-17T15:11:09Z

Added OLS Distributed support

commit 9701adc7957ef20cc84eeef3394634dabb6a9af0
Author: zaleslaw 
Date:   2017-11-17T15:55:07Z

Fixed code style




> Cleanup OLS code
> 
>
> Key: IGNITE-6949
> URL: https://issues.apache.org/jira/browse/IGNITE-6949
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: ml
>Reporter: Yury Babak
>Assignee: Aleksey Zinoviev
> Fix For: 2.4
>
>
> We want fix wrong styles like wildcards in imports, unnecessary empty lines, 
> missed empty lines and if-else blocks format in OLS related files.



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

[jira] [Commented] (IGNITE-6818) In case of incoming communication connection ping the old one if it's alive

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6818:


GitHub user alamar opened a pull request:

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

Backport IGNITE-6818, fix test



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

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

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

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


commit 4a1415ad01ff9fde30d5c7c02e6d938f1515178d
Author: Andrey V. Mashenkov 
Date:   2017-04-12T10:01:25Z

IGNITE-4907: Fixed excessive service instances can be started with dynamic 
deployment. This closes #1766.

(cherry picked from commit 0f7ef74)

commit e206b9f1fd3dbf927f940d558144a4796479ed5d
Author: vsisko 
Date:   2017-04-14T11:32:30Z

IGNITE-4871 Added Kubernetes IP finder to Cluster configuration screen.
(cherry picked from commit f978ff2)

commit b22738080101536a8af1ed60e70d693897e9bc7c
Author: dkarachentsev 
Date:   2017-04-14T14:54:02Z

ignite-4173 Fix test. Permits must be released on node fail.

(cherry picked from commit 1f867c6)

commit 41c5288606710b9c42983780ac7464a746d09eb0
Author: dkarachentsev 
Date:   2017-04-14T14:56:25Z

Merge remote-tracking branch 'origin/ignite-1.8.6' into ignite-1.8.6

commit 1985496ea98f4d7112a0b99727297427f343e9b2
Author: dkarachentsev 
Date:   2017-04-17T07:20:41Z

Add missed license headers.

commit ae794ab45b22abe1e570d5d29661396ea7c0f951
Author: dkarachentsev 
Date:   2017-04-17T10:40:28Z

IGNITE-4159 Fix version.

commit bf1049741f7a64728bd433f78262ba273f969848
Author: Andrey V. Mashenkov 
Date:   2017-04-17T16:00:30Z

IGNITE-4954 - Configurable expiration timeout for Cassandra session. This 
closes #1785.

commit aca67066ceaf762fcd44ef0715a4ba0f941226a8
Author: dkarachentsev 
Date:   2017-04-18T09:23:28Z

Merge branch 'ignite-1.8.5-p1' into ignite-1.8.6

commit a4c70f12305c15cbf15a6e5eb7c500f883a8b317
Author: agura 
Date:   2017-04-20T17:45:58Z

ignite-5041 NPE in deadlock detection fixed

commit d94172e7bb7ff4ebab422997e5c70f8cd03c0ae4
Author: agura 
Date:   2017-04-26T12:16:46Z

Redundant test removed

commit f9ecacc625b458539775e6550bd9b7613ed38f21
Author: dkarachentsev 
Date:   2017-04-28T08:46:23Z

IGNITE-5077 - Support service security permissions

backport from master
(cherry picked from commit 6236b5f)

commit 91c899b909383c78b78b9bf0c8f233b8c75ef29e
Author: Valentin Kulichenko 
Date:   2017-04-28T12:48:57Z

IGNITE-5081 - Removed redundant duplication of permissions in 
SecurityPermissionSetBuilder

commit b48a26b9b1e97fb8eb52c2a2f36005770922ac3d
Author: Valentin Kulichenko 
Date:   2017-04-28T12:53:33Z

IGNITE-5080 - Fixes in SecurityBasicPermissionSet

commit f66c23cbb9a6f2c923ebf75c58f00afaf1c0b5f3
Author: Evgenii Zhuravlev 
Date:   2017-05-03T14:47:45Z

IGNITE-4939 Receive event before cache initialized fix

commit 45b4d6316145d0b4b46713409f5e8fbe55ff4c41
Author: Evgenii Zhuravlev 
Date:   2017-05-04T09:11:37Z

IGNITE-4939 Receive event before cache initialized fix

commit 075bcfca0ea22633be13cd02647e359ad6fdca16
Author: Andrey V. Mashenkov 
Date:   2017-05-04T09:21:04Z

Fix flacky service deployment tests.

commit 25c06b50d46937cb39534cdf4147b862217289a2
Author: rfqu 
Date:   2017-05-02T16:46:44Z

ignite-4220 Support statements for JDBC and Cassandra store

commit 987c182686962673e70398395cb27e94f894713b
Author: nikolay_tikhonov 
Date:   2017-05-15T08:54:16Z

Fixed "IGNITE-5214 ConcurrentModificationException with enable DEBUG log 
level"

Signed-off-by: nikolay_tikhonov 

commit a5d2b9ba3ed1e72ef3970ecfed499a97f925ff2c
Author: Andrey V. Mashenkov 
Date:   2017-05-15T14:39:52Z

Fixed thread pools incorrect shutdown.

(cherry picked from commit dacf973)

commit 5e08c2951522a640bf84b6c60f03f29edd970ffc
Author: Andrey V. Mashenkov 
Date:   2017-05-15T17:24:10Z

IGNITE-5225: Fix NPE caused by changes in IGNITE-4577.

(cherry picked from commit d463840)

commit 62765b5b7598ab2a82b9c595e4a1276d9f2f5860

[jira] [Updated] (IGNITE-6949) Cleanup OLS code

[Aleksey Zinoviev (JIRA)]

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

Aleksey Zinoviev updated IGNITE-6949:
-
Component/s: ml

> Cleanup OLS code
> 
>
> Key: IGNITE-6949
> URL: https://issues.apache.org/jira/browse/IGNITE-6949
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: ml
>Reporter: Yury Babak
>Assignee: Aleksey Zinoviev
> Fix For: 2.4
>
>
> We want fix wrong styles like wildcards in imports, unnecessary empty lines, 
> missed empty lines and if-else blocks format in OLS related files.



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

[jira] [Updated] (IGNITE-6948) SQL: Document new INLINE_SIZE option in CREATE INDEX command

[Kirill Shirokov (JIRA)]

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

Kirill Shirokov updated IGNITE-6948:

Description: 
INLINE_SIZE is optional and accepts positive integer values. To specify the 
default inline size user should omit the option.

The corresponding documentation page is at:
https://apacheignite-sql.readme.io/docs/create-index

  was:INLINE_SIZE is optional and accepts positive integer values. To specify 
the default inline size user should omit the option.


> SQL: Document new INLINE_SIZE option in CREATE INDEX command
> 
>
> Key: IGNITE-6948
> URL: https://issues.apache.org/jira/browse/IGNITE-6948
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: documentation
>Reporter: Kirill Shirokov
>Assignee: Kirill Shirokov
> Fix For: 2.4
>
>
> INLINE_SIZE is optional and accepts positive integer values. To specify the 
> default inline size user should omit the option.
> The corresponding documentation page is at:
> https://apacheignite-sql.readme.io/docs/create-index



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

[jira] [Commented] (IGNITE-6927) Web Console: Create build with maven for Web Console direct-install.

[Oleg Ostanin (JIRA)]

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

Oleg Ostanin commented on IGNITE-6927:
--

[~avinogradov]
":" tells Maven to build defined modules. I've checked, it works.
I've removed '$IGNITE_HOME' from DEVNOTES.TXT

> Web Console: Create build with maven for Web Console direct-install.
> 
>
> Key: IGNITE-6927
> URL: https://issues.apache.org/jira/browse/IGNITE-6927
> Project: Ignite
>  Issue Type: Sub-task
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
>Priority: Minor
> Fix For: 2.4
>
>
> * Add build to maven for Web Console direct-install.
> * Add section with instructions into DEVNOTES.txt



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

[jira] [Assigned] (IGNITE-6948) SQL: Document new INLINE_SIZE option in CREATE INDEX command

[Kirill Shirokov (JIRA)]

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

Kirill Shirokov reassigned IGNITE-6948:
---

Assignee: Kirill Shirokov

> SQL: Document new INLINE_SIZE option in CREATE INDEX command
> 
>
> Key: IGNITE-6948
> URL: https://issues.apache.org/jira/browse/IGNITE-6948
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: documentation
>Reporter: Kirill Shirokov
>Assignee: Kirill Shirokov
> Fix For: 2.4
>
>
> INLINE_SIZE is optional and accepts positive integer values. To specify the 
> default inline size user should omit the option.



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

[jira] [Assigned] (IGNITE-6950) Update documentation for user facing CREATE TABLE params

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko reassigned IGNITE-6950:
---

Assignee: Denis Magda  (was: Alexander Paschenko)

> Update documentation for user facing CREATE TABLE params
> 
>
> Key: IGNITE-6950
> URL: https://issues.apache.org/jira/browse/IGNITE-6950
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: documentation, sql
>Affects Versions: 2.4
>Reporter: Alexander Paschenko
>Assignee: Denis Magda
> Fix For: 2.4
>
>
> Changes to documentation should be made to reflect additional spelling for 
> some {{CREATE TABLE}} params added in IGNITE-6270.



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

[jira] [Created] (IGNITE-6951) .NET: BinaryWriter should throw exception on pointer fields

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-6951:
--

 Summary: .NET: BinaryWriter should throw exception on pointer 
fields
 Key: IGNITE-6951
 URL: https://issues.apache.org/jira/browse/IGNITE-6951
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
  Components: platforms
Reporter: Pavel Tupitsyn
 Fix For: 2.4


Serializing pointers does not make sense. We already throw on {{IntPtr}} 
fields, should do the same for any other pointer ({{long*}}, {{void*}}, etc).



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

[jira] [Commented] (IGNITE-6931) Simplify index rebuild

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-6931:
--

[~vozerov], fixed.

> Simplify index rebuild
> --
>
> Key: IGNITE-6931
> URL: https://issues.apache.org/jira/browse/IGNITE-6931
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: cache, sql
>Affects Versions: 2.3
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
> Fix For: 2.4
>
>
> There are two quite similar operations: CREATE INDEX rebuildIndexFromHach but 
> used approaches are absolutely different. We need to generalize an used 
> approach.



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

[jira] [Assigned] (IGNITE-6335) .NET: Thin client: cache binary mode

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-6335:
--

Assignee: Pavel Tupitsyn

> .NET: Thin client: cache binary mode
> 
>
> Key: IGNITE-6335
> URL: https://issues.apache.org/jira/browse/IGNITE-6335
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> {{WithKeepBinary}}, all operations in binary mode, {{IIgnite.GetBinary()}}.



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

[jira] [Assigned] (IGNITE-6912) .NET: Thin client: Cache iterator

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-6912:
--

Assignee: (was: Pavel Tupitsyn)

> .NET: Thin client: Cache iterator
> -
>
> Key: IGNITE-6912
> URL: https://issues.apache.org/jira/browse/IGNITE-6912
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> {{ICacheClient}} should be {{IEnumerable>}}, same as 
> {{ICache}}.
> This can be easily implemented with a {{ScanQuery}} without a filter.
> Same thing for {{GetLocalEntries}}.



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

[jira] [Commented] (IGNITE-6337) .NET: Thin client: SQL queries

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6337:


Github user asfgit closed the pull request at:

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


> .NET: Thin client: SQL queries
> --
>
> Key: IGNITE-6337
> URL: https://issues.apache.org/jira/browse/IGNITE-6337
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> SQL and Fields queries in thin client.



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

[jira] [Updated] (IGNITE-6335) .NET: Thin client: cache binary mode

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-6335:
---
Fix Version/s: 2.4

> .NET: Thin client: cache binary mode
> 
>
> Key: IGNITE-6335
> URL: https://issues.apache.org/jira/browse/IGNITE-6335
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> {{WithKeepBinary}}, all operations in binary mode, {{IIgnite.GetBinary()}}.



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

[jira] [Commented] (IGNITE-6337) .NET: Thin client: SQL queries

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6337:


Merged to master: {{0bd712ddb3df9408b80bf0da6d19480ef737b7bc}}.

> .NET: Thin client: SQL queries
> --
>
> Key: IGNITE-6337
> URL: https://issues.apache.org/jira/browse/IGNITE-6337
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> SQL and Fields queries in thin client.



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

[jira] [Created] (IGNITE-6950) Update documentation for user facing CREATE TABLE params

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-6950:
---

 Summary: Update documentation for user facing CREATE TABLE params
 Key: IGNITE-6950
 URL: https://issues.apache.org/jira/browse/IGNITE-6950
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: documentation, sql
Affects Versions: 2.4
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko
 Fix For: 2.4


Changes to documentation should be made to reflect additional spelling for some 
{{CREATE TABLE}} params added in IGNITE-6270.



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

[jira] [Commented] (IGNITE-6270) Rename user facing CREATE TABLE param names to split words properly

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6270:


Github user asfgit closed the pull request at:

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


> Rename user facing CREATE TABLE param names to split words properly
> ---
>
> Key: IGNITE-6270
> URL: https://issues.apache.org/jira/browse/IGNITE-6270
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
>  Labels: important, usability
> Fix For: 2.4
>
>
> Currently, some {{CREATE TABLE}} params specified inside {{WITH}} clause look 
> like this: {{AFFINITYKEY}}, i.e. words are not separated by dashes as they 
> should be.



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

[jira] [Updated] (IGNITE-6835) ODBC driver should handle ungraceful tcp disconnects

[Alexey Popov (JIRA)]

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

Alexey Popov updated IGNITE-6835:
-
Description: 
It is found that ungraceful TCP disconnect makes ODBC driver stuck at socket 
recv().
Ungraceful TCP disconnect could be caused:
1. Network failure (or new firewall rules)
2. Remote party shutdown (Half Closed Connection)

So, the proposal is:
setup socket  options: 
1) SO_KEEPALIVE enabled
2) TCP_KEEPIDLE to 60 sec. It is 2 hour by default
3) TCP_KEEPINTVL to 1 sec. It is 1 sec at Win and 75 sec at Linux by default.
4) send/receive buffers to some greater value (8k by default)


  was:
It is found that ungraceful TCP disconnect makes ODBC driver stuck at socket 
recv().
Ungraceful TCP disconnect could be caused:
1. Network failure (or new firewall rules)
2. Remote party shutdown (Half Closed Connection)

So, the proposal is:
setup socket  options: 
1) SO_KEEPALIVE enabled
2) TCP_KEEPIDLE to 60 sec. It is 2 hour by default
3) TCP_KEEPINTVL to 5 (\?) sec. It is 1 sec at Win and 75 sec at Linux by 
default.
4) send/receive buffers to some greater value (8k by default)



> ODBC driver should handle ungraceful tcp disconnects
> 
>
> Key: IGNITE-6835
> URL: https://issues.apache.org/jira/browse/IGNITE-6835
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: odbc
>Affects Versions: 2.1
>Reporter: Alexey Popov
>Assignee: Igor Sapego
>  Labels: odbc
> Fix For: 2.4
>
>
> It is found that ungraceful TCP disconnect makes ODBC driver stuck at socket 
> recv().
> Ungraceful TCP disconnect could be caused:
> 1. Network failure (or new firewall rules)
> 2. Remote party shutdown (Half Closed Connection)
> So, the proposal is:
> setup socket  options: 
> 1) SO_KEEPALIVE enabled
> 2) TCP_KEEPIDLE to 60 sec. It is 2 hour by default
> 3) TCP_KEEPINTVL to 1 sec. It is 1 sec at Win and 75 sec at Linux by default.
> 4) send/receive buffers to some greater value (8k by default)



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

[jira] [Created] (IGNITE-6949) Cleanup OLS code

[Yury Babak (JIRA)]

Yury Babak created IGNITE-6949:
--

 Summary: Cleanup OLS code
 Key: IGNITE-6949
 URL: https://issues.apache.org/jira/browse/IGNITE-6949
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Yury Babak
Assignee: Aleksey Zinoviev
 Fix For: 2.4


We want fix wrong styles like wildcards in imports, unnecessary empty lines, 
missed empty lines and if-else blocks format in OLS related files.



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

[jira] [Commented] (IGNITE-6907) .NET: Check LINQ join tests for errors

[Alexey Popov (JIRA)]

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

Alexey Popov commented on IGNITE-6907:
--

https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests_Ignite20Tests=pull%2F3049%2Fhead
 for history

> .NET: Check LINQ join tests for errors
> --
>
> Key: IGNITE-6907
> URL: https://issues.apache.org/jira/browse/IGNITE-6907
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>  Labels: .NET
>
> 1) Please check join tests with LINQ.
> 2) Fix any issues you can find )



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

[jira] [Created] (IGNITE-6948) SQL: Document new INLINE_SIZE option in CREATE INDEX command

[Kirill Shirokov (JIRA)]

Kirill Shirokov created IGNITE-6948:
---

 Summary: SQL: Document new INLINE_SIZE option in CREATE INDEX 
command
 Key: IGNITE-6948
 URL: https://issues.apache.org/jira/browse/IGNITE-6948
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: documentation
Reporter: Kirill Shirokov
 Fix For: 2.4


INLINE_SIZE is optional and accepts positive integer values. To specify the 
default inline size user should omit the option.



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

[jira] [Commented] (IGNITE-6931) Simplify index rebuild

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6931:
-

[~gvvinblade], my comments:
1) Please remove anonymous class from 
{{GridQueryProcessor.processSchemaOperationLocal}}, as it may break binary 
compatibility silently, due to changes in auto-generated anonymous class names. 
We had such an issue several days ago in another class.
2) Same thing for {{IgnitH2Indexing.rebuildIndexesFromHash}} - this is exactly 
where aforementioned issue were observed.


> Simplify index rebuild
> --
>
> Key: IGNITE-6931
> URL: https://issues.apache.org/jira/browse/IGNITE-6931
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: cache, sql
>Affects Versions: 2.3
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
> Fix For: 2.4
>
>
> There are two quite similar operations: CREATE INDEX rebuildIndexFromHach but 
> used approaches are absolutely different. We need to generalize an used 
> approach.



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

[jira] [Commented] (IGNITE-2662) .NET Core support (run on Linux)

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2662:


TeamCity configuration created: 
https://ci.ignite.apache.org/admin/editRequirements.html?id=buildType:Ignite20Tests_IgnitePlatformNetCoreLinux

> .NET Core support (run on Linux)
> 
>
> Key: IGNITE-2662
> URL: https://issues.apache.org/jira/browse/IGNITE-2662
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 1.1.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .net, xplat
> Fix For: 2.4
>
>
> Ignite.NET should target .NET Standard so it is available on maximum number 
> of platforms, see
> https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/
> https://weblog.west-wind.com/posts/2016/Nov/23/NET-Standard-20-Making-Sense-of-NET-Again
> https://github.com/dotnet/core/blob/master/roadmap.md
> Make sure that all used APIs are supported on all platforms, see API Analyzer 
> tool:
> https://channel9.msdn.com/coding4fun/blog/Your-New-Virtual-API-Review-Assistant
> This will allow us to run on Windows, OSX, and Linux, and target .NET Core in 
> additional to good old regular .NET.
> Possible difficulties:
> * JNI interop. Core has dllImport and it works on linux, and our C++ client 
> works on linux, so it should be possible
> * Reflection. We use it a lot, and API has changed.



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

[jira] [Comment Edited] (IGNITE-2662) .NET Core support (run on Linux)

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-2662 at 11/17/17 1:42 PM:
--

GitHub user ptupitsyn opened a pull request:

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

IGNITE-2662 .NET Core support (run on Linux)



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

$ git pull https://github.com/ptupitsyn/ignite ignite-2662

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

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


was (Author: githubbot):
GitHub user ptupitsyn opened a pull request:

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

IGNITE-2662 .NET Core support (run on Linux)



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

$ git pull https://github.com/ptupitsyn/ignite ignite-2662

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

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


commit dc2ad8777d6c11fe7f5b457f073c2d1a5d7f9933
Author: Pavel Tupitsyn 
Date:   2017-11-15T18:43:42Z

IGNITE-2662 .NET Core support (run on Linux)

commit 79ad83dc4dcbb9baa16ef3ec569f91c592cb8103
Author: Pavel Tupitsyn 
Date:   2017-11-15T18:48:11Z

Add solution file

commit 90888b0385b87ef3ff0b171224f318a5abb3a32a
Author: Pavel Tupitsyn 
Date:   2017-11-15T18:56:30Z

First test implemented

commit c900fc5a91b39b629f6643f457515db626de772e
Author: Pavel Tupitsyn 
Date:   2017-11-15T18:58:04Z

wip

commit 1349c71a3b2bb4b91612426d4b09fd3b5d8341af
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:00:06Z

wip

commit 8489bfdb0887f59e81265a8c49289f680b5105c0
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:10:37Z

Fix callbacks initialization on Core

commit 6c0e6c7b204d2e8c886e0129c09b116770368848
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:11:38Z

wip

commit a6d7081f90bd02e56f3b1e1eb91f7a7ce6d63186
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:12:08Z

Ignore exe files

commit 6f618ff83b2f8b74a5f640d4bce782fc0b89edb8
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:20:31Z

Add unix check

commit 9a660799d8d706a93deeb235a46a38061366cdae
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:47:54Z

Fix NuGet version issues

commit a56fd81e41f0d4969bf06d03c98df75910cec797
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:53:38Z

Fix readme

commit 0c434e7622affd119ee77fa9904f765825c7188a
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:58:58Z

Adding test scripts

commit 0684ff1b5484918b2be46d8fa58d4c24bf8cc828
Author: Pavel Tupitsyn 
Date:   2017-11-15T20:04:53Z

Fix line breaks

commit 3373839cf9de4fce7b435ee7f4b0686332c5f313
Author: Pavel Tupitsyn 
Date:   2017-11-15T20:05:38Z

wip

commit 8f0212cf8c5fb5fc06dcd1a0e1de7fbf5d063dd4
Author: Pavel Tupitsyn 
Date:   2017-11-15T20:09:19Z

Fixing test script

commit ed5f0508e8ad02c0f4807f5ecb6cbe5ed284c5cf
Author: Pavel Tupitsyn 
Date:   2017-11-15T20:17:59Z

WSL script works!

commit 4f851234b9f90ee07d2f4f55010cb00b5334dcb0
Author: Pavel Tupitsyn 
Date:   2017-11-16T06:33:13Z

Fix test script

commit 2e9ee68622c70dc21b17a66877dae45e1c1e96ae
Author: Pavel Tupitsyn 
Date:   2017-11-16T09:00:38Z

Merge branch 'master' into ignite-2662

commit 6241a66735456aa2b22fe8f7c6d2298cdb348349
Author: Pavel Tupitsyn 
Date:   2017-11-16T09:21:22Z

xplat dll loader

commit 18037a44809ffe7f9474db23358cffa55db84583
Author: Pavel Tupitsyn 
Date:   2017-11-16T09:38:14Z

Implementing Java detection on Linux

commit 1e674877d25df345e0c258d275f009416eb48aa2
Author: Pavel Tupitsyn 
Date:   2017-11-16T09:54:01Z

Refactoring dll loading

commit 19699d72bfdda806d464f9515078327703bda93c
Author: Pavel Tupitsyn 
Date:   2017-11-16T09:55:01Z

wip dll loading

commit aba0381c265075c44aeeff76f03c75c945ab44d2
Author: Pavel Tupitsyn 
Date:   2017-11-16T10:03:55Z

Fix config copy

commit 999d1536d2475f501a846950dc1dd2a3a57f984e
Author: Pavel Tupitsyn 
Date:   2017-11-16T10:11:18Z

Fix JVM class to be 

[jira] [Commented] (IGNITE-2662) .NET Core support (run on Linux)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2662:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-2662 .NET Core support (run on Linux)



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

$ git pull https://github.com/ptupitsyn/ignite ignite-2662

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

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


commit dc2ad8777d6c11fe7f5b457f073c2d1a5d7f9933
Author: Pavel Tupitsyn 
Date:   2017-11-15T18:43:42Z

IGNITE-2662 .NET Core support (run on Linux)

commit 79ad83dc4dcbb9baa16ef3ec569f91c592cb8103
Author: Pavel Tupitsyn 
Date:   2017-11-15T18:48:11Z

Add solution file

commit 90888b0385b87ef3ff0b171224f318a5abb3a32a
Author: Pavel Tupitsyn 
Date:   2017-11-15T18:56:30Z

First test implemented

commit c900fc5a91b39b629f6643f457515db626de772e
Author: Pavel Tupitsyn 
Date:   2017-11-15T18:58:04Z

wip

commit 1349c71a3b2bb4b91612426d4b09fd3b5d8341af
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:00:06Z

wip

commit 8489bfdb0887f59e81265a8c49289f680b5105c0
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:10:37Z

Fix callbacks initialization on Core

commit 6c0e6c7b204d2e8c886e0129c09b116770368848
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:11:38Z

wip

commit a6d7081f90bd02e56f3b1e1eb91f7a7ce6d63186
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:12:08Z

Ignore exe files

commit 6f618ff83b2f8b74a5f640d4bce782fc0b89edb8
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:20:31Z

Add unix check

commit 9a660799d8d706a93deeb235a46a38061366cdae
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:47:54Z

Fix NuGet version issues

commit a56fd81e41f0d4969bf06d03c98df75910cec797
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:53:38Z

Fix readme

commit 0c434e7622affd119ee77fa9904f765825c7188a
Author: Pavel Tupitsyn 
Date:   2017-11-15T19:58:58Z

Adding test scripts

commit 0684ff1b5484918b2be46d8fa58d4c24bf8cc828
Author: Pavel Tupitsyn 
Date:   2017-11-15T20:04:53Z

Fix line breaks

commit 3373839cf9de4fce7b435ee7f4b0686332c5f313
Author: Pavel Tupitsyn 
Date:   2017-11-15T20:05:38Z

wip

commit 8f0212cf8c5fb5fc06dcd1a0e1de7fbf5d063dd4
Author: Pavel Tupitsyn 
Date:   2017-11-15T20:09:19Z

Fixing test script

commit ed5f0508e8ad02c0f4807f5ecb6cbe5ed284c5cf
Author: Pavel Tupitsyn 
Date:   2017-11-15T20:17:59Z

WSL script works!

commit 4f851234b9f90ee07d2f4f55010cb00b5334dcb0
Author: Pavel Tupitsyn 
Date:   2017-11-16T06:33:13Z

Fix test script

commit 2e9ee68622c70dc21b17a66877dae45e1c1e96ae
Author: Pavel Tupitsyn 
Date:   2017-11-16T09:00:38Z

Merge branch 'master' into ignite-2662

commit 6241a66735456aa2b22fe8f7c6d2298cdb348349
Author: Pavel Tupitsyn 
Date:   2017-11-16T09:21:22Z

xplat dll loader

commit 18037a44809ffe7f9474db23358cffa55db84583
Author: Pavel Tupitsyn 
Date:   2017-11-16T09:38:14Z

Implementing Java detection on Linux

commit 1e674877d25df345e0c258d275f009416eb48aa2
Author: Pavel Tupitsyn 
Date:   2017-11-16T09:54:01Z

Refactoring dll loading

commit 19699d72bfdda806d464f9515078327703bda93c
Author: Pavel Tupitsyn 
Date:   2017-11-16T09:55:01Z

wip dll loading

commit aba0381c265075c44aeeff76f03c75c945ab44d2
Author: Pavel Tupitsyn 
Date:   2017-11-16T10:03:55Z

Fix config copy

commit 999d1536d2475f501a846950dc1dd2a3a57f984e
Author: Pavel Tupitsyn 
Date:   2017-11-16T10:11:18Z

Fix JVM class to be xplat

commit 323c8708e68eb47fdd6b87d867a6726dc13ff006
Author: Pavel Tupitsyn 
Date:   2017-11-16T10:15:20Z

Add logging to test

commit 0e05f74922336c48a52a5ae64fb7b82cf256f3cb
Author: Pavel Tupitsyn 
Date:   2017-11-16T11:20:57Z

Fix NuGet home detection

commit 910747328e48664364ade24ae1740a5960afaa73
Author: Pavel Tupitsyn 
Date:   2017-11-16T11:21:47Z

fix home detection on Linux

commit 881ed862b29851262a8c563a170cdae33f521a23
Author: Pavel Tupitsyn 
Date:   2017-11-16T11:28:52Z

Fix NuGet folder name casing

commit 

[jira] [Updated] (IGNITE-6496) Client node does not reconnect to server node when the latter is restarted.

[Vyacheslav Koptilin (JIRA)]

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

Vyacheslav Koptilin updated IGNITE-6496:

Fix Version/s: 2.4

> Client node does not reconnect to server node when the latter is restarted.
> ---
>
> Key: IGNITE-6496
> URL: https://issues.apache.org/jira/browse/IGNITE-6496
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures
>Affects Versions: 1.9
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
> Fix For: 2.4
>
> Attachments: ExampleNodeStartup.java
>
>
> The following scenario may result in deadlock on the client node:
>  - start server node and one client
>  - client node invokes IgniteQueue#take() method, that requires acquiring 
> both GridCacheGateway#readLock and GridCacheQueueAdapter#readSem.
>  - client node disconnects from the cluster for some reason (for example, 
> server node was stopped)
>in that case, GridCacheQueueAdapter does not release readSem and, 
> therefore, GridCacheGateway#readLock is also not released.
>  - 'tcp-client-disco-msg-worker' hangs due to unable acquiring 
> GridCacheGateway.writeLock
> "tcp-client-disco-msg-worker-#10%datastructures.GridCacheQueueClientReconnect1%"
>  #101 prio=5 os_prio=0 tid=0x21634000 nid=0x49a8 waiting on condition 
> [0x3a61e000]
>java.lang.Thread.State: WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> parking to wait for  <0x00076fa988f8> (a 
> java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:870)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1199)
> at 
> java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:943)
> 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.GridCacheGateway.writeLock(GridCacheGateway.java:278)
> at 
> org.apache.ignite.internal.IgniteKernal.onDisconnected(IgniteKernal.java:3873)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:768)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:573)
> locked <0x00076f9f4048> (a java.lang.Object)
> at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2415)
> at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2394)
> at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1710)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)



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

[jira] [Commented] (IGNITE-6850) SQL: integrate index inline size to CREATE INDEX syntax

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6850:


Github user asfgit closed the pull request at:

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


> SQL: integrate index inline size to CREATE INDEX syntax
> ---
>
> Key: IGNITE-6850
> URL: https://issues.apache.org/jira/browse/IGNITE-6850
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Kirill Shirokov
> Fix For: 2.4
>
>
> Index value inline is important optimization which used to minimize amount of 
> data page reads when doing index lookup (see {{InlineIndexHelper}}). 
> Currently the only way to set it is {{QueryIndex.inlineSize}} property, so it 
> cannot be set from SQL command. We need to integrate it to our SQL syntax 
> (see {{SqlCreateIndexCommand}}) and make sure it is propagated properly.
> Sample syntax:
> {code}
> CREATE INDEX idx ON tbl(field) INLINE_SIZE 20;
> {code}



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

[jira] [Commented] (IGNITE-358) Read external split from V2 Context and V1 Reporter #getInputSplit

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-358:
---

Github user asfgit closed the pull request at:

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


> Read external split from V2 Context and V1 Reporter #getInputSplit
> --
>
> Key: IGNITE-358
> URL: https://issues.apache.org/jira/browse/IGNITE-358
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: sprint-1
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
> Fix For: 2.4
>
>
> Migrated from GG JIRA (GG-8755).



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

[jira] [Commented] (IGNITE-5846) Add support of distributed matrices for OLS regression.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5846:


Github user asfgit closed the pull request at:

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


> Add support of distributed matrices for OLS regression.
> ---
>
> Key: IGNITE-5846
> URL: https://issues.apache.org/jira/browse/IGNITE-5846
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Reporter: Yury Babak
>Assignee: Aleksey Zinoviev
> Fix For: 2.4
>
>
> Currently OSL regression works only with local matrices.



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

[jira] [Commented] (IGNITE-6932) GridQueryProcessor.querySqlFieldsNoCache should check for cluster active/inactive state

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6932:


Github user asfgit closed the pull request at:

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


> GridQueryProcessor.querySqlFieldsNoCache should check for cluster 
> active/inactive state
> ---
>
> Key: IGNITE-6932
> URL: https://issues.apache.org/jira/browse/IGNITE-6932
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.4
>
>
> Currently we do not check for this, so operation may hang silently. Let's add 
> a check for this before starting query execution. See 
> {{IgniteKernal.checkClusterState}} and it's usages.



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

[jira] [Updated] (IGNITE-6923) Cache metrics are updated in timeout-worker potentially delaying critical code execution due to current implementation issues.

[Alexei Scherbakov (JIRA)]

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

Alexei Scherbakov updated IGNITE-6923:
--
Description: 
Some metrics are using cache iteration for calculation. If number of caches 
rather large this can be slow.

Similar code is running in discovery thread.

See stack trace for example.

{noformat}
"grid-timeout-worker-#39%DPL_GRID%DplGridNodeName%" #152 prio=5 os_prio=0 
tid=0x7f1009a03000 nid=0x5caa runnable [0x7f0f059d9000] 
   java.lang.Thread.State: RUNNABLE 
at java.util.HashMap.containsKey(HashMap.java:595) 
at java.util.HashSet.contains(HashSet.java:203) 
at 
java.util.Collections$UnmodifiableCollection.contains(Collections.java:1032) 
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.apply(IgniteCacheOffheapManagerImpl.java:339)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.apply(IgniteCacheOffheapManagerImpl.java:337)
at 
org.apache.ignite.internal.util.lang.gridfunc.TransformFilteringIterator.hasNext:@TransformFilteringIterator.java:90)
at 
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
 
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.cacheEntriesCount(IgniteCacheOffheapManagerImpl.java:293)
at 
org.apache.ignite.internal.processors.cache.CacheMetricsImpl.getOffHeapPrimaryEntriesCount(CacheMetricsImpl.java:240)
at 
org.apache.ignite.internal.processors.cache.CacheMetricsSnapshot.(CacheMetricsSnapshot.java:271)
 
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.localMetrics(GridCacheAdapter.java:3217)
 
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.cacheMetrics(GridDiscoveryManager.java:1151)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.nonHeapMemoryUsed(GridDiscoveryManager.java:1121)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.metrics(GridDiscoveryManager.java:1087)
 
at 
org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNode.metrics(TcpDiscoveryNode.java:269)
 
at 
org.apache.ignite.internal.IgniteKernal$3.run(IgniteKernal.java:1175) 
at 
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask.onTimeout(GridTimeoutProcessor.java:256)
- locked <0x7f115f5bf890> (a 
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask)
at 
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:158)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
at java.lang.Thread.run(Thread.java:748)
{noformat}

  was:
Some metrics are using cache iteration for calculation.

See stack trace for example.

{noformat}
"grid-timeout-worker-#39%DPL_GRID%DplGridNodeName%" #152 prio=5 os_prio=0 
tid=0x7f1009a03000 nid=0x5caa runnable [0x7f0f059d9000] 
   java.lang.Thread.State: RUNNABLE 
at java.util.HashMap.containsKey(HashMap.java:595) 
at java.util.HashSet.contains(HashSet.java:203) 
at 
java.util.Collections$UnmodifiableCollection.contains(Collections.java:1032) 
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.apply(IgniteCacheOffheapManagerImpl.java:339)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.apply(IgniteCacheOffheapManagerImpl.java:337)
at 
org.apache.ignite.internal.util.lang.gridfunc.TransformFilteringIterator.hasNext:@TransformFilteringIterator.java:90)
at 
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
 
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.cacheEntriesCount(IgniteCacheOffheapManagerImpl.java:293)
at 
org.apache.ignite.internal.processors.cache.CacheMetricsImpl.getOffHeapPrimaryEntriesCount(CacheMetricsImpl.java:240)
at 
org.apache.ignite.internal.processors.cache.CacheMetricsSnapshot.(CacheMetricsSnapshot.java:271)
 
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.localMetrics(GridCacheAdapter.java:3217)
 
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.cacheMetrics(GridDiscoveryManager.java:1151)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.nonHeapMemoryUsed(GridDiscoveryManager.java:1121)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.metrics(GridDiscoveryManager.java:1087)
 
at 
org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNode.metrics(TcpDiscoveryNode.java:269)
 
at 
org.apache.ignite.internal.IgniteKernal$3.run(IgniteKernal.java:1175) 
 

[jira] [Commented] (IGNITE-6337) .NET: Thin client: SQL queries

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6337:
-

[~ptupitsyn], looks good to me.

> .NET: Thin client: SQL queries
> --
>
> Key: IGNITE-6337
> URL: https://issues.apache.org/jira/browse/IGNITE-6337
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> SQL and Fields queries in thin client.



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

[jira] [Assigned] (IGNITE-6929) Preserve mvcc versions on index rebuild

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-6929:
---

Assignee: Alexander Paschenko  (was: Vladimir Ozerov)

> Preserve mvcc versions on index rebuild
> ---
>
> Key: IGNITE-6929
> URL: https://issues.apache.org/jira/browse/IGNITE-6929
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: sql
>Reporter: Igor Seliverstov
>Assignee: Alexander Paschenko
>
> Currently we may loose next available version for an index row on index 
> rebuild 
> ({{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#updateIndexes}})



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

[jira] [Assigned] (IGNITE-6929) Preserve mvcc versions on index rebuild

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-6929:
---

Assignee: Vladimir Ozerov  (was: Igor Seliverstov)

> Preserve mvcc versions on index rebuild
> ---
>
> Key: IGNITE-6929
> URL: https://issues.apache.org/jira/browse/IGNITE-6929
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: sql
>Reporter: Igor Seliverstov
>Assignee: Vladimir Ozerov
>
> Currently we may loose next available version for an index row on index 
> rebuild 
> ({{org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.CacheDataStoreImpl#updateIndexes}})



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

[jira] [Created] (IGNITE-6947) Near optimistic prepare future should abandon remap after failed map attempt

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-6947:


 Summary: Near optimistic prepare future should abandon remap after 
failed map attempt
 Key: IGNITE-6947
 URL: https://issues.apache.org/jira/browse/IGNITE-6947
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk


Otherwise, it leads to an NPE if there are no affinity nodes.



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

[jira] [Resolved] (IGNITE-6924) CacheStoreSessionListener#onSessionStart() is not called in case of 'WriteBehind' mode is enabled and 'writeCache' size exceeds critical size.

[Vyacheslav Koptilin (JIRA)]

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

Vyacheslav Koptilin resolved IGNITE-6924.
-
   Resolution: Fixed
Fix Version/s: 2.4

merged into master e3099cc47e4086605312d88aeda3ca85e1e6aeff

> CacheStoreSessionListener#onSessionStart() is not called in case of 
> 'WriteBehind' mode is enabled and 'writeCache' size exceeds critical size.
> --
>
> Key: IGNITE-6924
> URL: https://issues.apache.org/jira/browse/IGNITE-6924
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: cache
>Affects Versions: 2.4
>Reporter: Vyacheslav Koptilin
>Assignee: Vyacheslav Koptilin
> Fix For: 2.4
>
>




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

[jira] [Updated] (IGNITE-358) Read external split from V2 Context and V1 Reporter #getInputSplit

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov updated IGNITE-358:
-
Fix Version/s: 2.4

> Read external split from V2 Context and V1 Reporter #getInputSplit
> --
>
> Key: IGNITE-358
> URL: https://issues.apache.org/jira/browse/IGNITE-358
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: sprint-1
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
> Fix For: 2.4
>
>
> Migrated from GG JIRA (GG-8755).



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

[jira] [Commented] (IGNITE-6927) Web Console: Create build with maven for Web Console direct-install.

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-6927:
--

[~anovikov], 
Hi again, so questions: 

1) what is ":"at command
{{imvn clean package -pl :ignite-web-agent,:ignite-web-console -am -P 
web-console -DskipTests=true}}
I never seen such style before.

2) Not sure following line is correct
Assembled archive can be found here: 
`$IGNITE_HOME/modules/web-console/target/ignite-web-console-direct-install-*.zip`.
since, for example, I haму no $IGNITE_HOME env variable

Other looks good to me.


> Web Console: Create build with maven for Web Console direct-install.
> 
>
> Key: IGNITE-6927
> URL: https://issues.apache.org/jira/browse/IGNITE-6927
> Project: Ignite
>  Issue Type: Sub-task
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
>Priority: Minor
> Fix For: 2.4
>
>
> * Add build to maven for Web Console direct-install.
> * Add section with instructions into DEVNOTES.txt



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

[jira] [Comment Edited] (IGNITE-6927) Web Console: Create build with maven for Web Console direct-install.

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov edited comment on IGNITE-6927 at 11/17/17 12:13 PM:
-

[~anovikov], 
Hi again, so questions: 

1) what is ":"at command
{{imvn clean package -pl :ignite-web-agent,:ignite-web-console -am -P 
web-console -DskipTests=true}}
I never seen such style before.

2) Not sure following line is correct
Assembled archive can be found here: 
`$IGNITE_HOME/modules/web-console/target/ignite-web-console-direct-install-*.zip`.
since, for example, I have no $IGNITE_HOME env variable

Other looks good to me.



was (Author: avinogradov):
[~anovikov], 
Hi again, so questions: 

1) what is ":"at command
{{imvn clean package -pl :ignite-web-agent,:ignite-web-console -am -P 
web-console -DskipTests=true}}
I never seen such style before.

2) Not sure following line is correct
Assembled archive can be found here: 
`$IGNITE_HOME/modules/web-console/target/ignite-web-console-direct-install-*.zip`.
since, for example, I haму no $IGNITE_HOME env variable

Other looks good to me.


> Web Console: Create build with maven for Web Console direct-install.
> 
>
> Key: IGNITE-6927
> URL: https://issues.apache.org/jira/browse/IGNITE-6927
> Project: Ignite
>  Issue Type: Sub-task
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
>Priority: Minor
> Fix For: 2.4
>
>
> * Add build to maven for Web Console direct-install.
> * Add section with instructions into DEVNOTES.txt



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

[jira] [Commented] (IGNITE-358) Read external split from V2 Context and V1 Reporter #getInputSplit

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-358:
---

GitHub user kdudkov opened a pull request:

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

IGNITE-358 add InputSplit to HadoopV1Reporter



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

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

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

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


commit 23253093e26a875602c0617d8b1e2e7a873cda77
Author: Konstantin Dudkov 
Date:   2017-11-17T12:09:43Z

IGNITE-358 add InputSplit to HadoopV1Reporter




> Read external split from V2 Context and V1 Reporter #getInputSplit
> --
>
> Key: IGNITE-358
> URL: https://issues.apache.org/jira/browse/IGNITE-358
> Project: Ignite
>  Issue Type: Task
>  Components: hadoop
>Affects Versions: sprint-1
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
>
> Migrated from GG JIRA (GG-8755).



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

[jira] [Commented] (IGNITE-6927) Web Console: Create build with maven for Web Console direct-install.

[Oleg Ostanin (JIRA)]

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

Oleg Ostanin commented on IGNITE-6927:
--

[~avinogradov] PR:
https://github.com/apache/ignite/pull/3058

> Web Console: Create build with maven for Web Console direct-install.
> 
>
> Key: IGNITE-6927
> URL: https://issues.apache.org/jira/browse/IGNITE-6927
> Project: Ignite
>  Issue Type: Sub-task
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
>Priority: Minor
> Fix For: 2.4
>
>
> * Add build to maven for Web Console direct-install.
> * Add section with instructions into DEVNOTES.txt



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

[jira] [Updated] (IGNITE-6923) Cache metrics are updated in timeout-worker potentially delaying critical code execution due to current implementation issues.

[Alexei Scherbakov (JIRA)]

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

Alexei Scherbakov updated IGNITE-6923:
--
Issue Type: Improvement  (was: Bug)

> Cache metrics are updated in timeout-worker potentially delaying critical 
> code execution due to current implementation issues.
> --
>
> Key: IGNITE-6923
> URL: https://issues.apache.org/jira/browse/IGNITE-6923
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>Affects Versions: 2.3
>Reporter: Alexei Scherbakov
> Fix For: 2.4
>
>
> Some metrics are using cache iteration for calculation.
> See stack trace for example.
> {noformat}
> "grid-timeout-worker-#39%DPL_GRID%DplGridNodeName%" #152 prio=5 os_prio=0 
> tid=0x7f1009a03000 nid=0x5caa runnable [0x7f0f059d9000] 
>java.lang.Thread.State: RUNNABLE 
> at java.util.HashMap.containsKey(HashMap.java:595) 
> at java.util.HashSet.contains(HashSet.java:203) 
> at 
> java.util.Collections$UnmodifiableCollection.contains(Collections.java:1032) 
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.apply(IgniteCacheOffheapManagerImpl.java:339)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.apply(IgniteCacheOffheapManagerImpl.java:337)
> at 
> org.apache.ignite.internal.util.lang.gridfunc.TransformFilteringIterator.hasNext:@TransformFilteringIterator.java:90)
> at 
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
>  
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.cacheEntriesCount(IgniteCacheOffheapManagerImpl.java:293)
> at 
> org.apache.ignite.internal.processors.cache.CacheMetricsImpl.getOffHeapPrimaryEntriesCount(CacheMetricsImpl.java:240)
> at 
> org.apache.ignite.internal.processors.cache.CacheMetricsSnapshot.(CacheMetricsSnapshot.java:271)
>  
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.localMetrics(GridCacheAdapter.java:3217)
>  
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.cacheMetrics(GridDiscoveryManager.java:1151)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.nonHeapMemoryUsed(GridDiscoveryManager.java:1121)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.metrics(GridDiscoveryManager.java:1087)
>  
> at 
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNode.metrics(TcpDiscoveryNode.java:269)
>  
> at 
> org.apache.ignite.internal.IgniteKernal$3.run(IgniteKernal.java:1175) 
> at 
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask.onTimeout(GridTimeoutProcessor.java:256)
> - locked <0x7f115f5bf890> (a 
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask)
> at 
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:158)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> at java.lang.Thread.run(Thread.java:748)
> {noformat}



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

[jira] [Updated] (IGNITE-6923) Cache metrics are updated in timeout-worker potentially delaying critical code execution due to current implementation issues.

[Alexei Scherbakov (JIRA)]

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

Alexei Scherbakov updated IGNITE-6923:
--
Description: 
Some metrics are using cache iteration for calculation.

See stack trace for example.

{noformat}
"grid-timeout-worker-#39%DPL_GRID%DplGridNodeName%" #152 prio=5 os_prio=0 
tid=0x7f1009a03000 nid=0x5caa runnable [0x7f0f059d9000] 
   java.lang.Thread.State: RUNNABLE 
at java.util.HashMap.containsKey(HashMap.java:595) 
at java.util.HashSet.contains(HashSet.java:203) 
at 
java.util.Collections$UnmodifiableCollection.contains(Collections.java:1032) 
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.apply(IgniteCacheOffheapManagerImpl.java:339)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.apply(IgniteCacheOffheapManagerImpl.java:337)
at 
org.apache.ignite.internal.util.lang.gridfunc.TransformFilteringIterator.hasNext:@TransformFilteringIterator.java:90)
at 
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
 
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.cacheEntriesCount(IgniteCacheOffheapManagerImpl.java:293)
at 
org.apache.ignite.internal.processors.cache.CacheMetricsImpl.getOffHeapPrimaryEntriesCount(CacheMetricsImpl.java:240)
at 
org.apache.ignite.internal.processors.cache.CacheMetricsSnapshot.(CacheMetricsSnapshot.java:271)
 
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.localMetrics(GridCacheAdapter.java:3217)
 
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.cacheMetrics(GridDiscoveryManager.java:1151)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.nonHeapMemoryUsed(GridDiscoveryManager.java:1121)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.metrics(GridDiscoveryManager.java:1087)
 
at 
org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNode.metrics(TcpDiscoveryNode.java:269)
 
at 
org.apache.ignite.internal.IgniteKernal$3.run(IgniteKernal.java:1175) 
at 
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask.onTimeout(GridTimeoutProcessor.java:256)
- locked <0x7f115f5bf890> (a 
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask)
at 
org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:158)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
at java.lang.Thread.run(Thread.java:748)
{noformat}

  was:
Some metrics are using full cache iteration for calculation.

See stack trace for example.

{noformat}
"grid-timeout-worker-#39%DPL_GRID%DplGridNodeName%" #152 prio=5 os_prio=0 
tid=0x7f1009a03000 nid=0x5caa runnable [0x7f0f059d9000] 
   java.lang.Thread.State: RUNNABLE 
at java.util.HashMap.containsKey(HashMap.java:595) 
at java.util.HashSet.contains(HashSet.java:203) 
at 
java.util.Collections$UnmodifiableCollection.contains(Collections.java:1032) 
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.apply(IgniteCacheOffheapManagerImpl.java:339)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.apply(IgniteCacheOffheapManagerImpl.java:337)
at 
org.apache.ignite.internal.util.lang.gridfunc.TransformFilteringIterator.hasNext:@TransformFilteringIterator.java:90)
at 
org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
 
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.cacheEntriesCount(IgniteCacheOffheapManagerImpl.java:293)
at 
org.apache.ignite.internal.processors.cache.CacheMetricsImpl.getOffHeapPrimaryEntriesCount(CacheMetricsImpl.java:240)
at 
org.apache.ignite.internal.processors.cache.CacheMetricsSnapshot.(CacheMetricsSnapshot.java:271)
 
at 
org.apache.ignite.internal.processors.cache.GridCacheAdapter.localMetrics(GridCacheAdapter.java:3217)
 
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.cacheMetrics(GridDiscoveryManager.java:1151)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.nonHeapMemoryUsed(GridDiscoveryManager.java:1121)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.metrics(GridDiscoveryManager.java:1087)
 
at 
org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNode.metrics(TcpDiscoveryNode.java:269)
 
at 
org.apache.ignite.internal.IgniteKernal$3.run(IgniteKernal.java:1175) 
at 

[jira] [Commented] (IGNITE-6923) Cache metrics are updated in timeout-worker potentially delaying critical code execution due to current implementation issues.

[Alexander Belyak (JIRA)]

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

Alexander Belyak commented on IGNITE-6923:
--

It look like partitions iteration, not full cache iteration.

> Cache metrics are updated in timeout-worker potentially delaying critical 
> code execution due to current implementation issues.
> --
>
> Key: IGNITE-6923
> URL: https://issues.apache.org/jira/browse/IGNITE-6923
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Affects Versions: 2.3
>Reporter: Alexei Scherbakov
> Fix For: 2.4
>
>
> Some metrics are using full cache iteration for calculation.
> See stack trace for example.
> {noformat}
> "grid-timeout-worker-#39%DPL_GRID%DplGridNodeName%" #152 prio=5 os_prio=0 
> tid=0x7f1009a03000 nid=0x5caa runnable [0x7f0f059d9000] 
>java.lang.Thread.State: RUNNABLE 
> at java.util.HashMap.containsKey(HashMap.java:595) 
> at java.util.HashSet.contains(HashSet.java:203) 
> at 
> java.util.Collections$UnmodifiableCollection.contains(Collections.java:1032) 
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.apply(IgniteCacheOffheapManagerImpl.java:339)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$3.apply(IgniteCacheOffheapManagerImpl.java:337)
> at 
> org.apache.ignite.internal.util.lang.gridfunc.TransformFilteringIterator.hasNext:@TransformFilteringIterator.java:90)
> at 
> org.apache.ignite.internal.util.lang.GridIteratorAdapter.hasNext(GridIteratorAdapter.java:45)
>  
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.cacheEntriesCount(IgniteCacheOffheapManagerImpl.java:293)
> at 
> org.apache.ignite.internal.processors.cache.CacheMetricsImpl.getOffHeapPrimaryEntriesCount(CacheMetricsImpl.java:240)
> at 
> org.apache.ignite.internal.processors.cache.CacheMetricsSnapshot.(CacheMetricsSnapshot.java:271)
>  
> at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter.localMetrics(GridCacheAdapter.java:3217)
>  
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.cacheMetrics(GridDiscoveryManager.java:1151)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.nonHeapMemoryUsed(GridDiscoveryManager.java:1121)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.metrics(GridDiscoveryManager.java:1087)
>  
> at 
> org.apache.ignite.spi.discovery.tcp.internal.TcpDiscoveryNode.metrics(TcpDiscoveryNode.java:269)
>  
> at 
> org.apache.ignite.internal.IgniteKernal$3.run(IgniteKernal.java:1175) 
> at 
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask.onTimeout(GridTimeoutProcessor.java:256)
> - locked <0x7f115f5bf890> (a 
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$CancelableTask)
> at 
> org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:158)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> at java.lang.Thread.run(Thread.java:748)
> {noformat}



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

[jira] [Commented] (IGNITE-6927) Web Console: Create build with maven for Web Console direct-install.

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-6927:
--

[~anovikov],
Seems you forgot to specify what you asking me to review :) 

> Web Console: Create build with maven for Web Console direct-install.
> 
>
> Key: IGNITE-6927
> URL: https://issues.apache.org/jira/browse/IGNITE-6927
> Project: Ignite
>  Issue Type: Sub-task
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
>Priority: Minor
> Fix For: 2.4
>
>
> * Add build to maven for Web Console direct-install.
> * Add section with instructions into DEVNOTES.txt



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

[jira] [Assigned] (IGNITE-6914) Web console: 'Export All' for scan stucks in Chrome but successfully finish in FireFox

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-6914:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: 'Export All' for scan stucks in Chrome but successfully finish 
> in FireFox
> --
>
> Key: IGNITE-6914
> URL: https://issues.apache.org/jira/browse/IGNITE-6914
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>
> I populated a cache with 100K of data.
> Then I opened Query screen and execute Scan for that cache.
> Then I executed Export All - under Chrome it stuck



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

[jira] [Closed] (IGNITE-6623) Web console: export query result set doesn't work on Edge

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-6623.
--

> Web console: export query result set doesn't work on Edge
> -
>
> Key: IGNITE-6623
> URL: https://issues.apache.org/jira/browse/IGNITE-6623
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>
> Execute any query and try to Export\ExportAll in result table



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

[jira] [Assigned] (IGNITE-6623) Web console: export query result set doesn't work on Edge

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-6623:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> Web console: export query result set doesn't work on Edge
> -
>
> Key: IGNITE-6623
> URL: https://issues.apache.org/jira/browse/IGNITE-6623
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Alexey Kuznetsov
>
> Execute any query and try to Export\ExportAll in result table



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

[jira] [Resolved] (IGNITE-6914) Web console: 'Export All' for scan stucks in Chrome but successfully finish in FireFox

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov resolved IGNITE-6914.

Resolution: Fixed

Tested in branch, can be merged into target branch

> Web console: 'Export All' for scan stucks in Chrome but successfully finish 
> in FireFox
> --
>
> Key: IGNITE-6914
> URL: https://issues.apache.org/jira/browse/IGNITE-6914
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>
> I populated a cache with 100K of data.
> Then I opened Query screen and execute Scan for that cache.
> Then I executed Export All - under Chrome it stuck



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

[jira] [Commented] (IGNITE-6623) Web console: export query result set doesn't work on Edge

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6623:


Tested

> Web console: export query result set doesn't work on Edge
> -
>
> Key: IGNITE-6623
> URL: https://issues.apache.org/jira/browse/IGNITE-6623
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>
> Execute any query and try to Export\ExportAll in result table



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

[jira] [Assigned] (IGNITE-6623) Web console: export query result set doesn't work on Edge

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin reassigned IGNITE-6623:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

This issue was fixed along with IGNITE-6914

> Web console: export query result set doesn't work on Edge
> -
>
> Key: IGNITE-6623
> URL: https://issues.apache.org/jira/browse/IGNITE-6623
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
>
> Execute any query and try to Export\ExportAll in result table



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

[jira] [Commented] (IGNITE-6907) .NET: Check LINQ join tests for errors

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6907:


Github user asfgit closed the pull request at:

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


> .NET: Check LINQ join tests for errors
> --
>
> Key: IGNITE-6907
> URL: https://issues.apache.org/jira/browse/IGNITE-6907
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>  Labels: .NET
>
> 1) Please check join tests with LINQ.
> 2) Fix any issues you can find )



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

[jira] [Updated] (IGNITE-6907) .NET: Check LINQ join tests for errors

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-6907:
---
Summary: .NET: Check LINQ join tests for errors  (was: Check LINQ join 
tests for errors)

> .NET: Check LINQ join tests for errors
> --
>
> Key: IGNITE-6907
> URL: https://issues.apache.org/jira/browse/IGNITE-6907
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>  Labels: .NET
>
> 1) Please check join tests with LINQ.
> 2) Fix any issues you can find )



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

[jira] [Updated] (IGNITE-6907) Check LINQ join tests for errors

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-6907:
---
Labels: .NET  (was: )

> Check LINQ join tests for errors
> 
>
> Key: IGNITE-6907
> URL: https://issues.apache.org/jira/browse/IGNITE-6907
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>  Labels: .NET
>
> 1) Please check join tests with LINQ.
> 2) Fix any issues you can find )



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

[jira] [Resolved] (IGNITE-6907) Check LINQ join tests for errors

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-6907.

Resolution: Fixed

> Check LINQ join tests for errors
> 
>
> Key: IGNITE-6907
> URL: https://issues.apache.org/jira/browse/IGNITE-6907
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>
> 1) Please check join tests with LINQ.
> 2) Fix any issues you can find )



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

[jira] [Commented] (IGNITE-6907) Check LINQ join tests for errors

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6907:


Looks good to me, merged to master: 
{{1ebeee00e96f18fab851930e672525a62c29fdd0}}.

> Check LINQ join tests for errors
> 
>
> Key: IGNITE-6907
> URL: https://issues.apache.org/jira/browse/IGNITE-6907
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Affects Versions: 2.3
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>
> 1) Please check join tests with LINQ.
> 2) Fix any issues you can find )



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

[jira] [Created] (IGNITE-6946) Change Ignite Logger configuration on the fly

[Alexey Popov (JIRA)]

Alexey Popov created IGNITE-6946:


 Summary: Change Ignite Logger configuration on the fly
 Key: IGNITE-6946
 URL: https://issues.apache.org/jira/browse/IGNITE-6946
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
  Components: general
Affects Versions: 2.3
Reporter: Alexey Popov


It would be great if we can change Ignite Logger configuration on the fly 
without restarting the cluster node. I will really help to debug an issue while 
it is reproducible at the current cluster state.
It should be done within the configured type of a logger, i.e. it is enough to 
change logging levels without changing the Logger type itself.

Such configuration change should be done for all supported logger types (JUL, 
log4j, log4i2 and others).

Also it should be done easily, for instance, via Visor, WebConsole or any other 
user-friendly tool ).



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

[jira] [Updated] (IGNITE-6934) SQL: evaluate performance of onheap row caching

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6934:

Fix Version/s: (was: 2.4)

> SQL: evaluate performance of onheap row caching
> ---
>
> Key: IGNITE-6934
> URL: https://issues.apache.org/jira/browse/IGNITE-6934
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: sql
>Reporter: Vladimir Ozerov
>  Labels: performance
>
> Ignite has so-called "on heap cache" feature. When cache entry is accessed, 
> we copy it from offheap to heap and put it into a temporal concurrent hash 
> map ([1], [2]), where it resides during usage. When operation is finished, 
> entry is evicted. This is default behavior which keeps GC pressure low even 
> for large in-memory data sets.
> The downside is that we loose time on copying from offheap to heap. To 
> mitigate this problem user can enable on-heap cache through 
> {{IgniteCache.onheapCacheEnabled}}. In this mode entry will not be evicted 
> from on-heap map, so it can be reused between different operations without 
> additional copying. Eviction rules are managed through eviction policy. 
> Unfortunately, SQL cannot use this optimization. As a result if key or value 
> is large enough, we loose a lot of time on memory copying. And we cannot use 
> current on-heap cache directly, we in SQL operate on row links, rather than 
> on keys. So to apply this optimization to SQL we should either create 
> additional row cache, or hack existing cache somehow.
> As a first step I propose to evaluate the impact with quick and dirty 
> solution:
> 1) Just add another map from link to K-V pair in the same cache, putting all 
> concurrency issues aside.
> 2) Use this cache from SQL engine.
> 3) Measure the impact. 
> [1] {{org.apache.ignite.internal.processors.cache.GridCacheConcurrentMapImpl}}
> [2] 
> {{org.apache.ignite.internal.processors.cache.GridCacheConcurrentMap.CacheMapHolder}}



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

[jira] [Assigned] (IGNITE-6934) SQL: evaluate performance of onheap row caching

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-6934:
---

Assignee: (was: Taras Ledkov)

> SQL: evaluate performance of onheap row caching
> ---
>
> Key: IGNITE-6934
> URL: https://issues.apache.org/jira/browse/IGNITE-6934
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: sql
>Reporter: Vladimir Ozerov
>  Labels: performance
>
> Ignite has so-called "on heap cache" feature. When cache entry is accessed, 
> we copy it from offheap to heap and put it into a temporal concurrent hash 
> map ([1], [2]), where it resides during usage. When operation is finished, 
> entry is evicted. This is default behavior which keeps GC pressure low even 
> for large in-memory data sets.
> The downside is that we loose time on copying from offheap to heap. To 
> mitigate this problem user can enable on-heap cache through 
> {{IgniteCache.onheapCacheEnabled}}. In this mode entry will not be evicted 
> from on-heap map, so it can be reused between different operations without 
> additional copying. Eviction rules are managed through eviction policy. 
> Unfortunately, SQL cannot use this optimization. As a result if key or value 
> is large enough, we loose a lot of time on memory copying. And we cannot use 
> current on-heap cache directly, we in SQL operate on row links, rather than 
> on keys. So to apply this optimization to SQL we should either create 
> additional row cache, or hack existing cache somehow.
> As a first step I propose to evaluate the impact with quick and dirty 
> solution:
> 1) Just add another map from link to K-V pair in the same cache, putting all 
> concurrency issues aside.
> 2) Use this cache from SQL engine.
> 3) Measure the impact. 
> [1] {{org.apache.ignite.internal.processors.cache.GridCacheConcurrentMapImpl}}
> [2] 
> {{org.apache.ignite.internal.processors.cache.GridCacheConcurrentMap.CacheMapHolder}}



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

[jira] [Assigned] (IGNITE-5296) Web console: Wrong queries list on clear of cookies

[Alexander Kalinin (JIRA)]

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

Alexander Kalinin reassigned IGNITE-5296:
-

Assignee: Pavel Konstantinov  (was: Alexander Kalinin)

> Web console: Wrong queries list on clear of cookies
> ---
>
> Key: IGNITE-5296
> URL: https://issues.apache.org/jira/browse/IGNITE-5296
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>
> # Create some queries lists.
> # Clear all cookies
> # Refresh page and login.
> After login list of queries showed as empty. It is sowed after refresh.



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

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

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6945:
---

 Summary: 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
  Security Level: Public (Viewable by anyone)
  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] [Comment Edited] (IGNITE-6932) GridQueryProcessor.querySqlFieldsNoCache should check for cluster active/inactive state

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-6932 at 11/17/17 9:19 AM:


[~vozerov], please review the patch.
Tests are OK.


was (Author: tledkov-gridgain):
[~vozerov], please review the patch.

> GridQueryProcessor.querySqlFieldsNoCache should check for cluster 
> active/inactive state
> ---
>
> Key: IGNITE-6932
> URL: https://issues.apache.org/jira/browse/IGNITE-6932
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: sql
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.4
>
>
> Currently we do not check for this, so operation may hang silently. Let's add 
> a check for this before starting query execution. See 
> {{IgniteKernal.checkClusterState}} and it's usages.



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

[jira] [Commented] (IGNITE-5731) Wrong metrics calculation in ClusterMetricsSnapshot

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5731:


GitHub user Denis-Log opened a pull request:

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

IGNITE-5731: curWaitingJobs and avgJobWaitTime calculation fixed



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

$ git pull https://github.com/Denis-Log/ignite IGNITE-5731

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

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


commit 71b01e53ba0987027c82666080700839bd656671
Author: Denis Loginov 
Date:   2017-11-17T08:24:50Z

IGNITE-5731: curWaitingJobs and avgJobWaitTime calculation fixed




> Wrong metrics calculation in ClusterMetricsSnapshot
> ---
>
> Key: IGNITE-5731
> URL: https://issues.apache.org/jira/browse/IGNITE-5731
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Evgenii Zhuravlev
>Assignee: Denis Loginov
>Priority: Minor
>
>  Error in ClusterMetricsSnapshot constructor:
>  curWaitingJobs += m.getCurrentJobWaitTime();
>  avgWaitingJobs += m.getCurrentWaitingJobs();



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