[jira] [Commented] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov commented on IGNITE-4374:
---

You can log GC activity to a file(s) with size limit and rotation


> Ignite should validate JVM and OS configuration and output warning in log
> -
>
> Key: IGNITE-4374
> URL: https://issues.apache.org/jira/browse/IGNITE-4374
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Yakov Zhdanov
>
> Currently we have GridPerformanceSuggestions that output suggestions to logs 
> on Ignite start on how Ignite can be improved.
> I suggest to go a little bit deeper and validate more configuration options 
> and add validation for JVM and OS settings.
> Ignite should output warning if:
> * GC logging is not enabled
> * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize)
> * Heap size is greater than 30,5G and JVM cannot use compressed oops
> * Any of the recommended OS setting described here 
> https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly 
> set 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-4374:

Component/s: documentation

> Ignite should validate JVM and OS configuration and output warning in log
> -
>
> Key: IGNITE-4374
> URL: https://issues.apache.org/jira/browse/IGNITE-4374
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Yakov Zhdanov
>
> Currently we have GridPerformanceSuggestions that output suggestions to logs 
> on Ignite start on how Ignite can be improved.
> I suggest to go a little bit deeper and validate more configuration options 
> and add validation for JVM and OS settings.
> Ignite should output warning if:
> * GC logging is not enabled
> * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize)
> * Heap size is greater than 30,5G and JVM cannot use compressed oops
> * Any of the recommended OS setting described here 
> https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly 
> set 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4374:
-

Also it makes sense to paste a reference to our tuning section in the log 
output (https://apacheignite.readme.io/docs/jvm-and-system-tuning), so that the 
user can get more advanced information on the topic.

> Ignite should validate JVM and OS configuration and output warning in log
> -
>
> Key: IGNITE-4374
> URL: https://issues.apache.org/jira/browse/IGNITE-4374
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation
>Reporter: Yakov Zhdanov
>
> Currently we have GridPerformanceSuggestions that output suggestions to logs 
> on Ignite start on how Ignite can be improved.
> I suggest to go a little bit deeper and validate more configuration options 
> and add validation for JVM and OS settings.
> Ignite should output warning if:
> * GC logging is not enabled
> * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize)
> * Heap size is greater than 30,5G and JVM cannot use compressed oops
> * Any of the recommended OS setting described here 
> https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly 
> set 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4374:
-

I'm not sure that GC logging is related to {{GridPerformanceSuggestions}} 
somehow. I would add it under kind of {{GridDebuggingSuggestions}} section.

In addition, I would suggest tune {{sqlOffHeapCacheRowSize}} if the off-heap 
mode is used for a cache.

> Ignite should validate JVM and OS configuration and output warning in log
> -
>
> Key: IGNITE-4374
> URL: https://issues.apache.org/jira/browse/IGNITE-4374
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Yakov Zhdanov
>
> Currently we have GridPerformanceSuggestions that output suggestions to logs 
> on Ignite start on how Ignite can be improved.
> I suggest to go a little bit deeper and validate more configuration options 
> and add validation for JVM and OS settings.
> Ignite should output warning if:
> * GC logging is not enabled
> * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize)
> * Heap size is greater than 30,5G and JVM cannot use compressed oops
> * Any of the recommended OS setting described here 
> https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly 
> set 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4230) Create documentation for the integration with Tableau

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-4230:

Description: 
Let's create a simple documentation that will show how to connect from Tableau 
to Ignite and what steps have to be performed to fulfill this.

The documentation has to be placed under this section:
https://apacheignite-mix.readme.io/docs/overview-1

Refer to this discussion for more details:
http://apache-ignite-developers.2346864.n4.nabble.com/Connecting-to-Ignite-from-Tableau-td12065.html

  was:
Let's create a simple documentation that will show how to connect from Tableau 
to Ignite and what steps have to be performed to fulfill this.

The documentation has to be placed under "Integrations" section on readme.io. 
The section is missing for now but will be introduced soon. Under this section 
we will have documentation for Zeppelin, Memcached, Mybatis, etc.

Refer to this discussion for more details:
http://apache-ignite-developers.2346864.n4.nabble.com/Connecting-to-Ignite-from-Tableau-td12065.html


> Create documentation for the integration with Tableau
> -
>
> Key: IGNITE-4230
> URL: https://issues.apache.org/jira/browse/IGNITE-4230
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.0
>
>
> Let's create a simple documentation that will show how to connect from 
> Tableau to Ignite and what steps have to be performed to fulfill this.
> The documentation has to be placed under this section:
> https://apacheignite-mix.readme.io/docs/overview-1
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Connecting-to-Ignite-from-Tableau-td12065.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4230) Create documentation for the integration with Tableau

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-4230:

Component/s: documentation

> Create documentation for the integration with Tableau
> -
>
> Key: IGNITE-4230
> URL: https://issues.apache.org/jira/browse/IGNITE-4230
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.0
>
>
> Let's create a simple documentation that will show how to connect from 
> Tableau to Ignite and what steps have to be performed to fulfill this.
> The documentation has to be placed under "Integrations" section on readme.io. 
> The section is missing for now but will be introduced soon. Under this 
> section we will have documentation for Zeppelin, Memcached, Mybatis, etc.
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Connecting-to-Ignite-from-Tableau-td12065.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4222) Document the usage of ComputeJobContinuation API

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-4222:

Component/s: documentation

> Document the usage of ComputeJobContinuation API
> 
>
> Key: IGNITE-4222
> URL: https://issues.apache.org/jira/browse/IGNITE-4222
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
> Fix For: 2.0
>
>
> The usage and applicability of `ComputeJobContinuation` have to be documented 
> on Apache Ignite Readme.io which will help out to avoid discussion like that 
> [1]. The new page has to be created for the topic and placed here [2].
> The content should consist not only of technical details but also provide use 
> cases for this API:
> - don't block a thread from the public pool if a job is waiting for some 
> result. Put the thread back into the pool and wait for the result 
> asynchronously.
> - splitting a job into several pieces that can be executed in parallel. Refer 
> to this example [3].
>  
> [1] 
> http://apache-ignite-users.70518.x6.nabble.com/Remote-Server-Thread-Not-exit-when-Job-finished-Cause-out-of-memory-tp8934p8947.html
> [2] https://apacheignite.readme.io/docs/compute-grid#section-features
> [3] 
> https://github.com/apache/ignite/blob/master/examples/src/main/java/org/apache/ignite/examples/computegrid/ComputeFibonacciContinuationExample.java



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4221) Document ComputeJobMasterLeaveAware interface usage

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-4221:

Component/s: documentation

> Document ComputeJobMasterLeaveAware interface usage
> ---
>
> Key: IGNITE-4221
> URL: https://issues.apache.org/jira/browse/IGNITE-4221
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
> Fix For: 2.0
>
>
> The usage and applicability of `ComputeJobMasterLeaveAware` have to be 
> documented on Apache Ignite Readme.io which will help out to avoid discussion 
> like that [1]. The new page has to be created for the topic and placed here 
> [2].
> In advance, the following example has to be contributed to Apache Ignite
> https://github.com/gridgain/gridgain-advanced-examples/blob/master/src/main/java/org/gridgain/examples/compute/masterleave/ComputeMasterLeaveAwareExample.java
>  
> [1] 
> http://apache-ignite-users.70518.x6.nabble.com/Remote-Server-Thread-Not-exit-when-Job-finished-Cause-out-of-memory-tp8934p8947.html
> [2] https://apacheignite.readme.io/docs/compute-grid#section-features



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4003) Slow or faulty client can stall the whole cluster.

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-4003:
-

Outgoing connection establishing reimplemented in asynchronous manner, so user 
thread should not be blocked. Most changes related with {{TcpCommunicationSpi}} 
and {{GridNioServer}} classes. 

Handshake functionality ({{TcpCommunicationSpi.safeHandshake()}} method) was 
keep for shmem IPC but rewritten for real network communication. For the last 
case it was moved to server listener's {{onMessage}} and 
{{onFirstMessageListener}}.

Also, now communication worker makes additional job in order to provide session 
management in async way.

See [PR #1318|https://github.com/apache/ignite/pull/1318]

> Slow or faulty client can stall the whole cluster.
> --
>
> Key: IGNITE-4003
> URL: https://issues.apache.org/jira/browse/IGNITE-4003
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrey Gura
>Priority: Critical
> Fix For: 2.0
>
>
> Steps to reproduce:
> 1) Start two server nodes and some data to cache.
> 2) Start a client from Docker subnet, which is not visible from the outside. 
> Client will join the cluster.
> 3) Try to put something to cache or start another node to force rabalance.
> Cluster is stuck at this moment. Root cause - servers are constantly trying 
> to establish outgoing connection to the client, but fail as Docker subnet is 
> not visible from the outside. It may stop virtually all cluster operations.
> Typical thread dump:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to send message (node may 
> have left the grid or TCP connection cannot be established due to firewall 
> issues) [node=TcpDiscoveryNode [id=a15d74c2-1ec2-4349-9640-aeacd70d8714, 
> addrs=[127.0.0.1, 172.17.0.6], sockAddrs=[/127.0.0.1:0, /127.0.0.1:0, 
> /172.17.0.6:0], discPort=0, order=7241, intOrder=3707, 
> lastExchangeTime=1474096941045, loc=false, ver=1.5.23#20160526-sha1:259146da, 
> isClient=true], topic=T4 [topic=TOPIC_CACHE, 
> id1=949732fd-1360-3a58-8d9e-0ff6ea6182cc, 
> id2=a15d74c2-1ec2-4349-9640-aeacd70d8714, id3=2], msg=GridContinuousMessage 
> [type=MSG_EVT_NOTIFICATION, routineId=7e13c48e-6933-48b2-9f15-8d92007930db, 
> data=null, futId=null], policy=2]
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1129)
>  [ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.sendOrderedMessage(GridIoManager.java:1347)
>  [ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1227)
>  ~[ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1198)
>  ~[ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1180)
>  ~[ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendNotification(GridContinuousProcessor.java:841)
>  ~[ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.addNotification(GridContinuousProcessor.java:800)
>  ~[ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:787)
>  [ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$700(CacheContinuousQueryHandler.java:91)
>  [ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:412)
>  [ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:343)
>  [ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryManager.onEntryUpdated(CacheContinuousQueryManager.java:250)
>  [ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:3476)
>  [ignite-core-1.5.23.jar:1.5.23]
>   at 
> 

[jira] [Comment Edited] (IGNITE-4003) Slow or faulty client can stall the whole cluster.

[Andrey Gura (JIRA)]

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

Andrey Gura edited comment on IGNITE-4003 at 12/7/16 12:22 AM:
---

Outgoing connection establishing reimplemented in asynchronous manner, so user 
thread should not be blocked. Most changes related with {{TcpCommunicationSpi}} 
and {{GridNioServer}} classes. 

Handshake functionality ({{TcpCommunicationSpi.safeHandshake()}} method) was 
keep for shmem IPC but rewritten for real network communication. For the last 
case it was moved to server listener's {{onMessage}} and {{onFirstMessage}} 
methods.

Also, now communication worker makes additional job in order to provide session 
management in async way.

See [PR #1318|https://github.com/apache/ignite/pull/1318]


was (Author: agura):
Outgoing connection establishing reimplemented in asynchronous manner, so user 
thread should not be blocked. Most changes related with {{TcpCommunicationSpi}} 
and {{GridNioServer}} classes. 

Handshake functionality ({{TcpCommunicationSpi.safeHandshake()}} method) was 
keep for shmem IPC but rewritten for real network communication. For the last 
case it was moved to server listener's {{onMessage}} and 
{{onFirstMessageListener}}.

Also, now communication worker makes additional job in order to provide session 
management in async way.

See [PR #1318|https://github.com/apache/ignite/pull/1318]

> Slow or faulty client can stall the whole cluster.
> --
>
> Key: IGNITE-4003
> URL: https://issues.apache.org/jira/browse/IGNITE-4003
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, general
>Affects Versions: 1.7
>Reporter: Vladimir Ozerov
>Assignee: Andrey Gura
>Priority: Critical
> Fix For: 2.0
>
>
> Steps to reproduce:
> 1) Start two server nodes and some data to cache.
> 2) Start a client from Docker subnet, which is not visible from the outside. 
> Client will join the cluster.
> 3) Try to put something to cache or start another node to force rabalance.
> Cluster is stuck at this moment. Root cause - servers are constantly trying 
> to establish outgoing connection to the client, but fail as Docker subnet is 
> not visible from the outside. It may stop virtually all cluster operations.
> Typical thread dump:
> {code}
> org.apache.ignite.IgniteCheckedException: Failed to send message (node may 
> have left the grid or TCP connection cannot be established due to firewall 
> issues) [node=TcpDiscoveryNode [id=a15d74c2-1ec2-4349-9640-aeacd70d8714, 
> addrs=[127.0.0.1, 172.17.0.6], sockAddrs=[/127.0.0.1:0, /127.0.0.1:0, 
> /172.17.0.6:0], discPort=0, order=7241, intOrder=3707, 
> lastExchangeTime=1474096941045, loc=false, ver=1.5.23#20160526-sha1:259146da, 
> isClient=true], topic=T4 [topic=TOPIC_CACHE, 
> id1=949732fd-1360-3a58-8d9e-0ff6ea6182cc, 
> id2=a15d74c2-1ec2-4349-9640-aeacd70d8714, id3=2], msg=GridContinuousMessage 
> [type=MSG_EVT_NOTIFICATION, routineId=7e13c48e-6933-48b2-9f15-8d92007930db, 
> data=null, futId=null], policy=2]
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1129)
>  [ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.sendOrderedMessage(GridIoManager.java:1347)
>  [ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1227)
>  ~[ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1198)
>  ~[ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendWithRetries(GridContinuousProcessor.java:1180)
>  ~[ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.sendNotification(GridContinuousProcessor.java:841)
>  ~[ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.addNotification(GridContinuousProcessor.java:800)
>  ~[ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.onEntryUpdate(CacheContinuousQueryHandler.java:787)
>  [ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler.access$700(CacheContinuousQueryHandler.java:91)
>  [ignite-core-1.5.23.jar:1.5.23]
>   at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryHandler$1.onEntryUpdated(CacheContinuousQueryHandler.java:412)
>  [ignite-core-1.5.23.jar:1.5.23]
> 

[jira] [Updated] (IGNITE-4379) SQL: Local SQL field query broken in master

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-4379:
-
Description: 
Local SQL field query returns entries from backup partition.

For now query context is being cleared in 
IgniteH2Indexing.queryLocalSqlFields() method before query is really executed.

It seems, GridQueryFieldsResultAdapter should restore query context before 
query run in iterator() method or move back query execution to outside 
GridQueryFieldsResultAdapter.


  was:
Local SQL field query returns entries from backup partition.

For now query context is being cleared in
IgniteH2Indexing.queryLocalSqlFields() method before query is really executed.

It seems, GridQueryFieldsResultAdapter should restore query context before 
query run in iterator() method.



> SQL: Local SQL field query broken in master
> ---
>
> Key: IGNITE-4379
> URL: https://issues.apache.org/jira/browse/IGNITE-4379
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Andrew Mashenkov
> Fix For: 2.0
>
>
> Local SQL field query returns entries from backup partition.
> For now query context is being cleared in 
> IgniteH2Indexing.queryLocalSqlFields() method before query is really executed.
> It seems, GridQueryFieldsResultAdapter should restore query context before 
> query run in iterator() method or move back query execution to outside 
> GridQueryFieldsResultAdapter.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4379) SQL: Local SQL field query broken in master

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-4379:
--

[~ascherbakov], would you please explain if it is really need to move query 
execution to GridQueryFieldsResultAdapter.iterator() method?

> SQL: Local SQL field query broken in master
> ---
>
> Key: IGNITE-4379
> URL: https://issues.apache.org/jira/browse/IGNITE-4379
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Andrew Mashenkov
> Fix For: 2.0
>
>
> Local SQL field query returns entries from backup partition.
> For now query context is being cleared in
> IgniteH2Indexing.queryLocalSqlFields() method before query is really executed.
> It seems, GridQueryFieldsResultAdapter should restore query context before 
> query run in iterator() method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4341) Add TeraSort example as a unit test to Ignite

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky commented on IGNITE-4341:
-

patch relative to master branch: https://github.com/apache/ignite/pull/1321 

> Add TeraSort example as a unit test to Ignite
> -
>
> Key: IGNITE-4341
> URL: https://issues.apache.org/jira/browse/IGNITE-4341
> Project: Ignite
>  Issue Type: Test
>  Components: hadoop
>Affects Versions: 1.7
>Reporter: Ivan Veselovsky
>Assignee: Vladimir Ozerov
> Fix For: 2.0
>
>
> Add canonical TeraSort example as a unit test. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4379) SQL: Local SQL field query broken in master

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-4379:
--

It looks like, it was broken in 
[https://issues.apache.org/jira/browse/IGNITE-2680]

> SQL: Local SQL field query broken in master
> ---
>
> Key: IGNITE-4379
> URL: https://issues.apache.org/jira/browse/IGNITE-4379
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Andrew Mashenkov
> Fix For: 2.0
>
>
> Local SQL field query returns entries from backup partition.
> For now query context is being cleared in
> IgniteH2Indexing.queryLocalSqlFields() method before query is really executed.
> It seems, GridQueryFieldsResultAdapter should restore query context before 
> query run in iterator() method.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4379) SQL: Local SQL field query broken in master

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-4379:


 Summary: SQL: Local SQL field query broken in master
 Key: IGNITE-4379
 URL: https://issues.apache.org/jira/browse/IGNITE-4379
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Reporter: Andrew Mashenkov
 Fix For: 2.0


Local SQL field query returns entries from backup partition.

For now query context is being cleared in
IgniteH2Indexing.queryLocalSqlFields() method before query is really executed.

It seems, GridQueryFieldsResultAdapter should restore query context before 
query run in iterator() method.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4046) C++: Support DML API

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-4046:
-

We need to provide for user a way to generate hash code the same way it happens 
in Java for binary objects. In C++ users should explicitly implement hashing 
for binary objects by themselves, so the only way I can think about is to 
provide them a method, which they can call from 
{{BinaryType::GetHashCode()}} to generate the same hash code as Java side 
does. Currently, I'm going to implement this approach and find out how well 
does it work.

> C++: Support DML API
> 
>
> Key: IGNITE-4046
> URL: https://issues.apache.org/jira/browse/IGNITE-4046
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Igor Sapego
>  Labels: roadmap
> Fix For: 2.0
>
>
> Ignite's Java component will provide support for DML soon (IGNITE-2294). At 
> she same time DML will be supported at the level of ODBC and JDBC drivers.
> As the next step we should include the similar functionality into Ignite.C++ 
> by doing the following:
> - Implement DML API;
> - Enhance {{query_example.cpp}} by doing INSERTs instead of cache.puts and 
> adding UPDATE and DELETE operation examples.
> - Add documentation to Ignite.C++ readme.io covering the feature. Most like 
> most of the content can be take from the general documentation when this 
> ticket IGNITE-4018 is ready.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4378) Affinity function should support selecting nodes based on node attributes

[Dmitriy Setrakyan (JIRA)]

Dmitriy Setrakyan created IGNITE-4378:
-

 Summary: Affinity function should support selecting nodes based on 
node attributes
 Key: IGNITE-4378
 URL: https://issues.apache.org/jira/browse/IGNITE-4378
 Project: Ignite
  Issue Type: New Feature
  Components: cache
Reporter: Dmitriy Setrakyan
Assignee: Alexei Scherbakov
 Fix For: 2.0


# Every node receives a set of attributes on startup
# Affinity function should receive pluggable {{AffinityResolver}} responsible 
for selecting primary and backups based on the node attributes.

Need to suggest API for the pluggable {{AffinityResolver}} 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4377) Cannot find schema for object with compact footer

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4377:
--

 Summary: Cannot find schema for object with compact footer
 Key: IGNITE-4377
 URL: https://issues.apache.org/jira/browse/IGNITE-4377
 Project: Ignite
  Issue Type: Bug
  Components: cache, compute
Affects Versions: 1.7, 1.8
Reporter: Pavel Tupitsyn
Priority: Critical
 Fix For: 1.9


When invoking a computation which returns an object from *client* node, "Cannot 
find schema for object with compact footer" exception occurs some times (only 
during first invocation)

{code}
class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for 
object with compact footer [typeId=2005649068, schemaId=-1206298342]

at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
at 
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{code}

Reproducer:
{code}
package org.apache.ignite;

import org.apache.ignite.platform.PlatformComputeBinarizable;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;

public class ClientModeCompactFooterTest extends GridCommonAbstractTest {
public ClientModeCompactFooterTest() {
super(false);
}

public void test() throws Exception {
for (int i =0; i < 100; i++) {
startGrid("server", 
"C:\\W\\incubator-ignite\\modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid1.xml");
Ignite client = startGrid("client", 
"C:\\W\\incubator-ignite\\modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid3.xml");

IgniteCompute compute = 
client.compute(client.cluster().forServers());

PlatformComputeBinarizable res = 
compute.execute("org.apache.ignite.platform.PlatformComputeEchoTask", 12);
System.out.println(res.field);

assertEquals(1, res.field);

stopAllGrids();
}
}
}
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4367) .NET: Fix flaky tests

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-4367 at 12/6/16 3:59 PM:
-

BinaryCompactFooterInteropTest.TestFromJava(True):
This happens purely on Java side. Reproduced in a Java test, filed IGNITE-4377.


was (Author: ptupitsyn):
BinaryCompactFooterInteropTest.TestFromJava(True):
Reproduced locally (fails only some times), investigating. This happens purely 
on Java side: server node sends a job result to client node, and unmarshalling 
fails due to missing schema.

> .NET: Fix flaky tests
> -
>
> Key: IGNITE-4367
> URL: https://issues.apache.org/jira/browse/IGNITE-4367
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
>  Labels: .NET
> Fix For: 1.9
>
>
> TeamCity has detected a number of flaky tests in .NET: 
> http://ci.ignite.apache.org/project.html?projectId=IgniteTests=flakyTests



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4377) Cannot find schema for object with compact footer

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4377:
---
Description: 
When invoking a computation which returns an object from *client* node, "Cannot 
find schema for object with compact footer" exception occurs some times (only 
during first invocation)

{code}
class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for 
object with compact footer [typeId=2005649068, schemaId=-1206298342]

at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
at 
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{code}

Reproducer:
{code}
package org.apache.ignite;

import org.apache.ignite.platform.PlatformComputeBinarizable;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;

public class ClientModeCompactFooterTest extends GridCommonAbstractTest {
public ClientModeCompactFooterTest() {
super(false);
}

public void test() throws Exception {
for (int i =0; i < 100; i++) {
startGrid("server", 
"modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid1.xml");
Ignite client = startGrid("client", 
"modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid3.xml");

PlatformComputeBinarizable res = 
client.compute().execute("org.apache.ignite.platform.PlatformComputeEchoTask", 
12);
assertEquals(1, res.field);

stopAllGrids();
}
}
}
{code}

  was:
When invoking a computation which returns an object from *client* node, "Cannot 
find schema for object with compact footer" exception occurs some times (only 
during first invocation)

{code}
class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for 
object with compact footer [typeId=2005649068, schemaId=-1206298342]

at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
at 
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
at 

[jira] [Updated] (IGNITE-4377) Cannot find schema for object with compact footer

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4377:
---
Description: 
When invoking a computation which returns an object from *client* node, "Cannot 
find schema for object with compact footer" exception occurs some times (only 
during first invocation)

{code}
class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for 
object with compact footer [typeId=2005649068, schemaId=-1206298342]

at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
at 
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
{code}

Reproducer:
{code}
package org.apache.ignite;

import org.apache.ignite.platform.PlatformComputeBinarizable;
import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;

public class ClientModeCompactFooterTest extends GridCommonAbstractTest {
public ClientModeCompactFooterTest() {
super(false);
}

public void test() throws Exception {
for (int i =0; i < 100; i++) {
startGrid("server", 
"modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid1.xml");
Ignite client = startGrid("client", 
"modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid3.xml");

IgniteCompute compute = 
client.compute(client.cluster().forServers());

PlatformComputeBinarizable res = 
compute.execute("org.apache.ignite.platform.PlatformComputeEchoTask", 12);
System.out.println(res.field);

assertEquals(1, res.field);

stopAllGrids();
}
}
}
{code}

  was:
When invoking a computation which returns an object from *client* node, "Cannot 
find schema for object with compact footer" exception occurs some times (only 
during first invocation)

{code}
class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for 
object with compact footer [typeId=2005649068, schemaId=-1206298342]

at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
at 
org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
at 
org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
at 
org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
at 
org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
at 
org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
at 

[jira] [Commented] (IGNITE-3474) Grid hung during load test with warning "Failed to wait for partition map exchange"

[Mark Summers (JIRA)]

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

Mark Summers commented on IGNITE-3474:
--

Me too with 1.7.0

> Grid hung during load test with warning "Failed to wait for partition map 
> exchange"
> ---
>
> Key: IGNITE-3474
> URL: https://issues.apache.org/jira/browse/IGNITE-3474
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Ksenia Rybakova
>Assignee: Semen Boikov
>Priority: Critical
> Attachments: 132548_id2_172.25.1.33_part.log, 
> ignite-base-load-config.xml, run-load.properties, run-load.xml
>
>
> During load test grid hung:
> {noformat}
> [09:22:17,688][WARN 
> ][exchange-worker-#137%null%][GridCachePartitionExchangeManager] Failed to 
> wait for partition map exchange [topVer=AffinityTopologyVersion [topVer=97, 
> minorTopVer=0], node=0fe0c0f2-65e1-4ad5-a8c9-92db997fcb7d]. Dumpin
> g pending objects that might be the cause:
> ...
> {noformat}
> See attached file with more info from logs.
> Notes:
> The issue was also reproduced with IGNITE-3239 fixed. So, IGNITE-3239 doesn't 
> seem to be a root cause. 
> Configs:
> 1)
>  - Benchmark name: IgniteCacheRandomOperationBenchmark 
>  - Operations: put, put_all, get, get_all, invoke, invoke_all, remove, 
> remove_all, put_if_absent, replace
> - Heap: 4Gb for servers, 1Gb for clients
> - 80 clients, 20 servers, 8 hosts
> - Number of caches: 100
> - Preload amount 250K
> - Key range 500K
> - Types of caches (atomicity mode): different (atomic, transactional)
> - Types of caches (tiered storage mode): different (onheap without eviction, 
> onheap with eviction, offheap_tired, offheap_values)
> - Types of caches (indexing): different (with and without indexes)
> - Types of caches (cache mode): different (partitioned, replicated)
> - Backups count: 1
> - Duration: 1h
> 2) 
> - Benchmark name: IgniteCacheRandomOperationBenchmark 
> - Operations: scan_query, sql_query, continuous_query
> - Heap: 4Gb for servers, 1Gb for clients
> - 20 clients, 80 servers, 8 hosts
> - Number of caches: 12
> - Types of caches (atomicity mode): different (atomic, transactional)
> - Types of caches (tiered storage mode): different (onheap without eviction, 
> onheap with eviction, offheap_tired, offheap_values)
> - Types of caches (indexing): different (with and without indexes)
> - Types of caches (cache mode): different (partitioned, replicated)
> - Backups count: 1
> - Duration: 1h
> Attachments:
> - part of log with the problem (for one of the servers) for config #2
> - xml configs and property file that were used to run yardstick for config #2
> Complete logs can be provided on demand.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4376) SQL: Failed to run reduce query locally with a valid query

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-4376 at 12/6/16 2:21 PM:
-

I can reproduce this with empty cache, just configure query entities and 
execute the query. .NET query entities are mapped to Java query entities, but 
I'm not sure how to produce Spring XML out of existing Java CacheConfiguration 
at runtime.


was (Author: ptupitsyn):
I can reproduce this with empty cache, just configure query entities and 
execute the query.

> SQL: Failed to run reduce query locally with a valid query
> --
>
> Key: IGNITE-4376
> URL: https://issues.apache.org/jira/browse/IGNITE-4376
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Sergi Vladykin
> Fix For: 1.9
>
>
> Reported by Ignite.NET user:
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:754)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
> at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
> at 
> org.apache.ignite.internal.processors.platform.cache.query.PlatformAbstractQueryCursor.processInLongOutLong(PlatformAbstractQueryCursor.java:142)
> at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inLongOutLong(PlatformAbstractTarget.java:66)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse 
> SQL query: SELECT
> __C0 NATURALKEY,
> ((PR.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * SUM(__C1)) AS EXPR1
> FROM PUBLIC.__T0
> GROUP BY __C0, __C2
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.preparedStatementWithParams(IgniteH2Indexing.java:913)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:985)
> at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:709)
> ... 4 more
> Caused by: org.h2.jdbc.JdbcSQLException: Column 
> "PR.PR_PER_PROJECTS_PERCENTCOMPLETED" not found; SQL statement:
> SELECT
> __C0 NATURALKEY,
> ((PR.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * SUM(__C1)) AS EXPR1
> FROM PUBLIC.__T0
> GROUP BY __C0, __C2 [42122-191]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.expression.ExpressionColumn.optimize(ExpressionColumn.java:147)
> at org.h2.expression.Operation.optimize(Operation.java:181)
> at org.h2.expression.Operation.optimize(Operation.java:181)
> at org.h2.expression.Alias.optimize(Alias.java:51)
> at org.h2.command.dml.Select.prepare(Select.java:852)
> at org.h2.command.Parser.prepareCommand(Parser.java:257)
> at org.h2.engine.Session.prepareLocal(Session.java:560)
> at org.h2.engine.Session.prepareCommand(Session.java:501)
> at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1188)
> at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
> at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:276)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:425)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.preparedStatementWithParams(IgniteH2Indexing.java:910)
> ... 6 more
> {code}
> Query (works in H2 console):
> {code}
> select pr.NATURALKEY, (pr.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * 
> sum(a.AS_RIO_ASSIGNMENTS_PERIODCOST) as Expr1
> from "Landscape".MI_MILESTONES mi 
> Inner join "Landscape".PR_HAS_MI_A t0 on t0.MI_ID_A = MI.NATURALKEY 
> Inner join "Landscape".PR_HAS_AS_A t1 on t1.PR_ID_HAS = t0.PR_ID_HAS 
> Inner join "Landscape".PR_HAS_OW_A t2 on t2.PR_ID_HAS = t0.PR_ID_HAS 
> Inner join "Landscape".AS_ASSIGNMENTS a on a.NATURALKEY = t1.AS_ID_A 
> inner join "Landscape".PR_PROJECTS pr on pr.NATURALKEY = t0.PR_ID_HAS 
> inner join "Landscape".OW_OWNERSHIP ow on ow.NATURALKEY=t2.OW_ID_A 
> group by 
> pr.NATURALKEY, pr.PR_PER_PROJECTS_PERCENTCOMPLETED
> {code}
> Query entity config:
> {code}
> 
>  valueTypeName="PR_Projects">
>   
>fieldTypeName="java.lang.Long" />
>fieldTypeName="java.lang.String" />
>fieldType="System.String" fieldTypeName="java.lang.String" />
>fieldType="System.String" fieldTypeName="java.lang.String" />
>

[jira] [Commented] (IGNITE-4376) SQL: Failed to run reduce query locally with a valid query

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin commented on IGNITE-4376:


I see what the problem is. Will fix it as part of IGNITE-3860

> SQL: Failed to run reduce query locally with a valid query
> --
>
> Key: IGNITE-4376
> URL: https://issues.apache.org/jira/browse/IGNITE-4376
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Sergi Vladykin
> Fix For: 1.9
>
>
> Reported by Ignite.NET user:
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:754)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
> at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
> at 
> org.apache.ignite.internal.processors.platform.cache.query.PlatformAbstractQueryCursor.processInLongOutLong(PlatformAbstractQueryCursor.java:142)
> at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inLongOutLong(PlatformAbstractTarget.java:66)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse 
> SQL query: SELECT
> __C0 NATURALKEY,
> ((PR.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * SUM(__C1)) AS EXPR1
> FROM PUBLIC.__T0
> GROUP BY __C0, __C2
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.preparedStatementWithParams(IgniteH2Indexing.java:913)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:985)
> at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:709)
> ... 4 more
> Caused by: org.h2.jdbc.JdbcSQLException: Column 
> "PR.PR_PER_PROJECTS_PERCENTCOMPLETED" not found; SQL statement:
> SELECT
> __C0 NATURALKEY,
> ((PR.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * SUM(__C1)) AS EXPR1
> FROM PUBLIC.__T0
> GROUP BY __C0, __C2 [42122-191]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.expression.ExpressionColumn.optimize(ExpressionColumn.java:147)
> at org.h2.expression.Operation.optimize(Operation.java:181)
> at org.h2.expression.Operation.optimize(Operation.java:181)
> at org.h2.expression.Alias.optimize(Alias.java:51)
> at org.h2.command.dml.Select.prepare(Select.java:852)
> at org.h2.command.Parser.prepareCommand(Parser.java:257)
> at org.h2.engine.Session.prepareLocal(Session.java:560)
> at org.h2.engine.Session.prepareCommand(Session.java:501)
> at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1188)
> at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
> at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:276)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:425)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.preparedStatementWithParams(IgniteH2Indexing.java:910)
> ... 6 more
> {code}
> Query (works in H2 console):
> {code}
> select pr.NATURALKEY, (pr.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * 
> sum(a.AS_RIO_ASSIGNMENTS_PERIODCOST) as Expr1
> from "Landscape".MI_MILESTONES mi 
> Inner join "Landscape".PR_HAS_MI_A t0 on t0.MI_ID_A = MI.NATURALKEY 
> Inner join "Landscape".PR_HAS_AS_A t1 on t1.PR_ID_HAS = t0.PR_ID_HAS 
> Inner join "Landscape".PR_HAS_OW_A t2 on t2.PR_ID_HAS = t0.PR_ID_HAS 
> Inner join "Landscape".AS_ASSIGNMENTS a on a.NATURALKEY = t1.AS_ID_A 
> inner join "Landscape".PR_PROJECTS pr on pr.NATURALKEY = t0.PR_ID_HAS 
> inner join "Landscape".OW_OWNERSHIP ow on ow.NATURALKEY=t2.OW_ID_A 
> group by 
> pr.NATURALKEY, pr.PR_PER_PROJECTS_PERCENTCOMPLETED
> {code}
> Query entity config:
> {code}
> 
>  valueTypeName="PR_Projects">
>   
>fieldTypeName="java.lang.Long" />
>fieldTypeName="java.lang.String" />
>fieldType="System.String" fieldTypeName="java.lang.String" />
>fieldType="System.String" fieldTypeName="java.lang.String" />
>fieldType="System.DateTime" fieldTypeName="java.sql.Timestamp" />
>fieldType="System.DateTime" fieldTypeName="java.sql.Timestamp" />
>fieldType="System.DateTime" fieldTypeName="java.sql.Timestamp" />
>fieldTypeName="java.lang.Integer" />
>fieldType="System.Int32" fieldTypeName="java.lang.Integer" />
>

[jira] [Commented] (IGNITE-4376) SQL: Failed to run reduce query locally with a valid query

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4376:


I can reproduce this with empty cache, just configure query entities and 
execute the query.

> SQL: Failed to run reduce query locally with a valid query
> --
>
> Key: IGNITE-4376
> URL: https://issues.apache.org/jira/browse/IGNITE-4376
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Sergi Vladykin
> Fix For: 1.9
>
>
> Reported by Ignite.NET user:
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:754)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
> at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
> at 
> org.apache.ignite.internal.processors.platform.cache.query.PlatformAbstractQueryCursor.processInLongOutLong(PlatformAbstractQueryCursor.java:142)
> at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inLongOutLong(PlatformAbstractTarget.java:66)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse 
> SQL query: SELECT
> __C0 NATURALKEY,
> ((PR.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * SUM(__C1)) AS EXPR1
> FROM PUBLIC.__T0
> GROUP BY __C0, __C2
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.preparedStatementWithParams(IgniteH2Indexing.java:913)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:985)
> at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:709)
> ... 4 more
> Caused by: org.h2.jdbc.JdbcSQLException: Column 
> "PR.PR_PER_PROJECTS_PERCENTCOMPLETED" not found; SQL statement:
> SELECT
> __C0 NATURALKEY,
> ((PR.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * SUM(__C1)) AS EXPR1
> FROM PUBLIC.__T0
> GROUP BY __C0, __C2 [42122-191]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.expression.ExpressionColumn.optimize(ExpressionColumn.java:147)
> at org.h2.expression.Operation.optimize(Operation.java:181)
> at org.h2.expression.Operation.optimize(Operation.java:181)
> at org.h2.expression.Alias.optimize(Alias.java:51)
> at org.h2.command.dml.Select.prepare(Select.java:852)
> at org.h2.command.Parser.prepareCommand(Parser.java:257)
> at org.h2.engine.Session.prepareLocal(Session.java:560)
> at org.h2.engine.Session.prepareCommand(Session.java:501)
> at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1188)
> at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
> at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:276)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:425)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.preparedStatementWithParams(IgniteH2Indexing.java:910)
> ... 6 more
> {code}
> Query (works in H2 console):
> {code}
> select pr.NATURALKEY, (pr.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * 
> sum(a.AS_RIO_ASSIGNMENTS_PERIODCOST) as Expr1
> from "Landscape".MI_MILESTONES mi 
> Inner join "Landscape".PR_HAS_MI_A t0 on t0.MI_ID_A = MI.NATURALKEY 
> Inner join "Landscape".PR_HAS_AS_A t1 on t1.PR_ID_HAS = t0.PR_ID_HAS 
> Inner join "Landscape".PR_HAS_OW_A t2 on t2.PR_ID_HAS = t0.PR_ID_HAS 
> Inner join "Landscape".AS_ASSIGNMENTS a on a.NATURALKEY = t1.AS_ID_A 
> inner join "Landscape".PR_PROJECTS pr on pr.NATURALKEY = t0.PR_ID_HAS 
> inner join "Landscape".OW_OWNERSHIP ow on ow.NATURALKEY=t2.OW_ID_A 
> group by 
> pr.NATURALKEY, pr.PR_PER_PROJECTS_PERCENTCOMPLETED
> {code}
> Query entity config:
> {code}
> 
>  valueTypeName="PR_Projects">
>   
>fieldTypeName="java.lang.Long" />
>fieldTypeName="java.lang.String" />
>fieldType="System.String" fieldTypeName="java.lang.String" />
>fieldType="System.String" fieldTypeName="java.lang.String" />
>fieldType="System.DateTime" fieldTypeName="java.sql.Timestamp" />
>fieldType="System.DateTime" fieldTypeName="java.sql.Timestamp" />
>fieldType="System.DateTime" fieldTypeName="java.sql.Timestamp" />
>fieldTypeName="java.lang.Integer" />
>fieldType="System.Int32" 

[jira] [Assigned] (IGNITE-4376) SQL: Failed to run reduce query locally with a valid query

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin reassigned IGNITE-4376:
--

Assignee: Sergi Vladykin

> SQL: Failed to run reduce query locally with a valid query
> --
>
> Key: IGNITE-4376
> URL: https://issues.apache.org/jira/browse/IGNITE-4376
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Sergi Vladykin
> Fix For: 1.9
>
>
> Reported by Ignite.NET user:
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:754)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
> at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
> at 
> org.apache.ignite.internal.processors.platform.cache.query.PlatformAbstractQueryCursor.processInLongOutLong(PlatformAbstractQueryCursor.java:142)
> at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inLongOutLong(PlatformAbstractTarget.java:66)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse 
> SQL query: SELECT
> __C0 NATURALKEY,
> ((PR.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * SUM(__C1)) AS EXPR1
> FROM PUBLIC.__T0
> GROUP BY __C0, __C2
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.preparedStatementWithParams(IgniteH2Indexing.java:913)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:985)
> at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:709)
> ... 4 more
> Caused by: org.h2.jdbc.JdbcSQLException: Column 
> "PR.PR_PER_PROJECTS_PERCENTCOMPLETED" not found; SQL statement:
> SELECT
> __C0 NATURALKEY,
> ((PR.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * SUM(__C1)) AS EXPR1
> FROM PUBLIC.__T0
> GROUP BY __C0, __C2 [42122-191]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.expression.ExpressionColumn.optimize(ExpressionColumn.java:147)
> at org.h2.expression.Operation.optimize(Operation.java:181)
> at org.h2.expression.Operation.optimize(Operation.java:181)
> at org.h2.expression.Alias.optimize(Alias.java:51)
> at org.h2.command.dml.Select.prepare(Select.java:852)
> at org.h2.command.Parser.prepareCommand(Parser.java:257)
> at org.h2.engine.Session.prepareLocal(Session.java:560)
> at org.h2.engine.Session.prepareCommand(Session.java:501)
> at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1188)
> at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
> at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:276)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:425)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.preparedStatementWithParams(IgniteH2Indexing.java:910)
> ... 6 more
> {code}
> Query (works in H2 console):
> {code}
> select pr.NATURALKEY, (pr.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * 
> sum(a.AS_RIO_ASSIGNMENTS_PERIODCOST) as Expr1
> from "Landscape".MI_MILESTONES mi 
> Inner join "Landscape".PR_HAS_MI_A t0 on t0.MI_ID_A = MI.NATURALKEY 
> Inner join "Landscape".PR_HAS_AS_A t1 on t1.PR_ID_HAS = t0.PR_ID_HAS 
> Inner join "Landscape".PR_HAS_OW_A t2 on t2.PR_ID_HAS = t0.PR_ID_HAS 
> Inner join "Landscape".AS_ASSIGNMENTS a on a.NATURALKEY = t1.AS_ID_A 
> inner join "Landscape".PR_PROJECTS pr on pr.NATURALKEY = t0.PR_ID_HAS 
> inner join "Landscape".OW_OWNERSHIP ow on ow.NATURALKEY=t2.OW_ID_A 
> group by 
> pr.NATURALKEY, pr.PR_PER_PROJECTS_PERCENTCOMPLETED
> {code}
> Query entity config:
> {code}
> 
>  valueTypeName="PR_Projects">
>   
>fieldTypeName="java.lang.Long" />
>fieldTypeName="java.lang.String" />
>fieldType="System.String" fieldTypeName="java.lang.String" />
>fieldType="System.String" fieldTypeName="java.lang.String" />
>fieldType="System.DateTime" fieldTypeName="java.sql.Timestamp" />
>fieldType="System.DateTime" fieldTypeName="java.sql.Timestamp" />
>fieldType="System.DateTime" fieldTypeName="java.sql.Timestamp" />
>fieldTypeName="java.lang.Integer" />
>fieldType="System.Int32" fieldTypeName="java.lang.Integer" />
>fieldType="System.Int32" fieldTypeName="java.lang.Integer" />
>

[jira] [Updated] (IGNITE-4376) SQL: Failed to run reduce query locally with a valid query

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4376:
---
Assignee: (was: Pavel Tupitsyn)

> SQL: Failed to run reduce query locally with a valid query
> --
>
> Key: IGNITE-4376
> URL: https://issues.apache.org/jira/browse/IGNITE-4376
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
> Fix For: 1.9
>
>
> Reported by Ignite.NET user:
> {code}
> javax.cache.CacheException: Failed to run reduce query locally.
> at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:754)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
> at 
> org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
> at 
> org.apache.ignite.internal.processors.platform.cache.query.PlatformAbstractQueryCursor.processInLongOutLong(PlatformAbstractQueryCursor.java:142)
> at 
> org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inLongOutLong(PlatformAbstractTarget.java:66)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse 
> SQL query: SELECT
> __C0 NATURALKEY,
> ((PR.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * SUM(__C1)) AS EXPR1
> FROM PUBLIC.__T0
> GROUP BY __C0, __C2
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.preparedStatementWithParams(IgniteH2Indexing.java:913)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:985)
> at 
> org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:709)
> ... 4 more
> Caused by: org.h2.jdbc.JdbcSQLException: Column 
> "PR.PR_PER_PROJECTS_PERCENTCOMPLETED" not found; SQL statement:
> SELECT
> __C0 NATURALKEY,
> ((PR.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * SUM(__C1)) AS EXPR1
> FROM PUBLIC.__T0
> GROUP BY __C0, __C2 [42122-191]
> at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
> at org.h2.message.DbException.get(DbException.java:179)
> at org.h2.message.DbException.get(DbException.java:155)
> at org.h2.expression.ExpressionColumn.optimize(ExpressionColumn.java:147)
> at org.h2.expression.Operation.optimize(Operation.java:181)
> at org.h2.expression.Operation.optimize(Operation.java:181)
> at org.h2.expression.Alias.optimize(Alias.java:51)
> at org.h2.command.dml.Select.prepare(Select.java:852)
> at org.h2.command.Parser.prepareCommand(Parser.java:257)
> at org.h2.engine.Session.prepareLocal(Session.java:560)
> at org.h2.engine.Session.prepareCommand(Session.java:501)
> at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1188)
> at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
> at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:276)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:425)
> at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.preparedStatementWithParams(IgniteH2Indexing.java:910)
> ... 6 more
> {code}
> Query (works in H2 console):
> {code}
> select pr.NATURALKEY, (pr.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * 
> sum(a.AS_RIO_ASSIGNMENTS_PERIODCOST) as Expr1
> from "Landscape".MI_MILESTONES mi 
> Inner join "Landscape".PR_HAS_MI_A t0 on t0.MI_ID_A = MI.NATURALKEY 
> Inner join "Landscape".PR_HAS_AS_A t1 on t1.PR_ID_HAS = t0.PR_ID_HAS 
> Inner join "Landscape".PR_HAS_OW_A t2 on t2.PR_ID_HAS = t0.PR_ID_HAS 
> Inner join "Landscape".AS_ASSIGNMENTS a on a.NATURALKEY = t1.AS_ID_A 
> inner join "Landscape".PR_PROJECTS pr on pr.NATURALKEY = t0.PR_ID_HAS 
> inner join "Landscape".OW_OWNERSHIP ow on ow.NATURALKEY=t2.OW_ID_A 
> group by 
> pr.NATURALKEY, pr.PR_PER_PROJECTS_PERCENTCOMPLETED
> {code}
> Query entity config:
> {code}
> 
>  valueTypeName="PR_Projects">
>   
>fieldTypeName="java.lang.Long" />
>fieldTypeName="java.lang.String" />
>fieldType="System.String" fieldTypeName="java.lang.String" />
>fieldType="System.String" fieldTypeName="java.lang.String" />
>fieldType="System.DateTime" fieldTypeName="java.sql.Timestamp" />
>fieldType="System.DateTime" fieldTypeName="java.sql.Timestamp" />
>fieldType="System.DateTime" fieldTypeName="java.sql.Timestamp" />
>fieldTypeName="java.lang.Integer" />
>fieldType="System.Int32" fieldTypeName="java.lang.Integer" />
>fieldType="System.Int32" fieldTypeName="java.lang.Integer" />
>fieldType="System.String" 

[jira] [Created] (IGNITE-4376) SQL: Failed to run reduce query locally with a valid query

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4376:
--

 Summary: SQL: Failed to run reduce query locally with a valid query
 Key: IGNITE-4376
 URL: https://issues.apache.org/jira/browse/IGNITE-4376
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Affects Versions: 1.7
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.9


Reported by Ignite.NET user:

{code}
javax.cache.CacheException: Failed to run reduce query locally.
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:754)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1119)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:98)
at 
org.apache.ignite.internal.processors.platform.cache.query.PlatformAbstractQueryCursor.processInLongOutLong(PlatformAbstractQueryCursor.java:142)
at 
org.apache.ignite.internal.processors.platform.PlatformAbstractTarget.inLongOutLong(PlatformAbstractTarget.java:66)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to parse SQL 
query: SELECT
__C0 NATURALKEY,
((PR.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * SUM(__C1)) AS EXPR1
FROM PUBLIC.__T0
GROUP BY __C0, __C2
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.preparedStatementWithParams(IgniteH2Indexing.java:913)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:985)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:709)
... 4 more
Caused by: org.h2.jdbc.JdbcSQLException: Column 
"PR.PR_PER_PROJECTS_PERCENTCOMPLETED" not found; SQL statement:
SELECT
__C0 NATURALKEY,
((PR.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * SUM(__C1)) AS EXPR1
FROM PUBLIC.__T0
GROUP BY __C0, __C2 [42122-191]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.expression.ExpressionColumn.optimize(ExpressionColumn.java:147)
at org.h2.expression.Operation.optimize(Operation.java:181)
at org.h2.expression.Operation.optimize(Operation.java:181)
at org.h2.expression.Alias.optimize(Alias.java:51)
at org.h2.command.dml.Select.prepare(Select.java:852)
at org.h2.command.Parser.prepareCommand(Parser.java:257)
at org.h2.engine.Session.prepareLocal(Session.java:560)
at org.h2.engine.Session.prepareCommand(Session.java:501)
at org.h2.jdbc.JdbcConnection.prepareCommand(JdbcConnection.java:1188)
at org.h2.jdbc.JdbcPreparedStatement.(JdbcPreparedStatement.java:73)
at org.h2.jdbc.JdbcConnection.prepareStatement(JdbcConnection.java:276)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.prepareStatement(IgniteH2Indexing.java:425)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.preparedStatementWithParams(IgniteH2Indexing.java:910)
... 6 more
{code}

Query (works in H2 console):
{code}
select pr.NATURALKEY, (pr.PR_PER_PROJECTS_PERCENTCOMPLETED / 100.0) * 
sum(a.AS_RIO_ASSIGNMENTS_PERIODCOST) as Expr1
from "Landscape".MI_MILESTONES mi 
Inner join "Landscape".PR_HAS_MI_A t0 on t0.MI_ID_A = MI.NATURALKEY 
Inner join "Landscape".PR_HAS_AS_A t1 on t1.PR_ID_HAS = t0.PR_ID_HAS 
Inner join "Landscape".PR_HAS_OW_A t2 on t2.PR_ID_HAS = t0.PR_ID_HAS 
Inner join "Landscape".AS_ASSIGNMENTS a on a.NATURALKEY = t1.AS_ID_A 
inner join "Landscape".PR_PROJECTS pr on pr.NATURALKEY = t0.PR_ID_HAS 
inner join "Landscape".OW_OWNERSHIP ow on ow.NATURALKEY=t2.OW_ID_A 
group by 
pr.NATURALKEY, pr.PR_PER_PROJECTS_PERCENTCOMPLETED
{code}

Query entity config:
{code}


  


















  
  

  

  

  


  

















  
  

  

  

  


  











  
  

  

  

  


  







  
  

  

  

  


  


  
  

  

  

  


  


  
  

  

  

  


  


  
  

  

  

  


  


 

[jira] [Commented] (IGNITE-3292) Yardstick: add logging of preloading progress

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov commented on IGNITE-3292:
--

[~oleg-ostanin]
Thank you for your contribution! I've looked at changes and left comment on 
review board http://reviews.ignite.apache.org/ignite/review/IGNT-CR-29. Please 
look on it. Also could you provide the sample of logs with new functionality?

> Yardstick: add logging of preloading progress
> -
>
> Key: IGNITE-3292
> URL: https://issues.apache.org/jira/browse/IGNITE-3292
> Project: Ignite
>  Issue Type: Wish
>  Components: yardstick
>Reporter: Ksenia Rybakova
>Assignee: Oleg Ostanin
> Fix For: 1.9
>
>
> Please, add logging of preloading progress. This is really useful when we 
> load a lot of entries or they are large. 
> For instance: "Preloading: 200 of 1000 loaded".
> Also adding an option that controls frequency of such output makes sense. For 
> instance, this might be a step (number of entries loaded) - if entries are 
> large, we set small step, if entries are integers,  the step will be large.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4367) .NET: Fix flaky tests

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-4367 at 12/6/16 1:34 PM:
-

BinaryCompactFooterInteropTest.TestFromJava(True):
Reproduced locally (fails only some times), investigating. This happens purely 
on Java side: server node sends a job result to client node, and unmarshalling 
fails due to missing schema.


was (Author: ptupitsyn):
BinaryCompactFooterInteropTest.TestFromJava(True):
Reproduced locally (fails only some times), investigating.

> .NET: Fix flaky tests
> -
>
> Key: IGNITE-4367
> URL: https://issues.apache.org/jira/browse/IGNITE-4367
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
>  Labels: .NET
> Fix For: 1.9
>
>
> TeamCity has detected a number of flaky tests in .NET: 
> http://ci.ignite.apache.org/project.html?projectId=IgniteTests=flakyTests



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-2703) .NET: Dynamically registered classes must use binary serialization if possible

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2703:


Another iteration of merging with IGNITE-4157

> .NET: Dynamically registered classes must use binary serialization if possible
> --
>
> Key: IGNITE-2703
> URL: https://issues.apache.org/jira/browse/IGNITE-2703
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>Priority: Critical
>  Labels: .net, breaking-api, roadmap
> Fix For: 2.0
>
>
> At present we support dynamic class registration in .NET, but they are 
> written using deafult .NET mechanism. This is counterintuitive for users and 
> not consistent with Java, where such classes are written in binary form.
> Proposed implementation plan:
> 1) For each dynamically registered class we must understand whether it could 
> be serialized through binary or not. If not - print a warning and fallback to 
> .NET.
> 2) Before writing a class we must ensure that it's [typeId -> name] pair is 
> known to the cluster. If not - write full class name instead of type ID. Java 
> already do that.
> 3) Last, to support backward compatibility we must be able to fallback to 
> current mode with help of some boolean flag.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky commented on IGNITE-4374:
-

- GC logging (in particular, PrintGCDetails and PrintGCApplicationStoppedTime) 
may flood the process output a lot;
- MaxDirectMemorySize does not limit Unsafe memory allocations, as far as I 
know;

> Ignite should validate JVM and OS configuration and output warning in log
> -
>
> Key: IGNITE-4374
> URL: https://issues.apache.org/jira/browse/IGNITE-4374
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Yakov Zhdanov
>
> Currently we have GridPerformanceSuggestions that output suggestions to logs 
> on Ignite start on how Ignite can be improved.
> I suggest to go a little bit deeper and validate more configuration options 
> and add validation for JVM and OS settings.
> Ignite should output warning if:
> * GC logging is not enabled
> * MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize)
> * Heap size is greater than 30,5G and JVM cannot use compressed oops
> * Any of the recommended OS setting described here 
> https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly 
> set 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4367) .NET: Fix flaky tests

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4367:


BinaryCompactFooterInteropTest.TestFromJava(True):
Reproduced locally (fails only some times), investigating.

> .NET: Fix flaky tests
> -
>
> Key: IGNITE-4367
> URL: https://issues.apache.org/jira/browse/IGNITE-4367
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
>  Labels: .NET
> Fix For: 1.9
>
>
> TeamCity has detected a number of flaky tests in .NET: 
> http://ci.ignite.apache.org/project.html?projectId=IgniteTests=flakyTests



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (IGNITE-3269) Benchmark driver stops working when one of servers left grid and backupcount 0

[Oleg Ostanin (JIRA)]

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

Oleg Ostanin reassigned IGNITE-3269:


Assignee: Oleg Ostanin

> Benchmark driver stops working when one of servers left grid and backupcount 0
> --
>
> Key: IGNITE-3269
> URL: https://issues.apache.org/jira/browse/IGNITE-3269
> Project: Ignite
>  Issue Type: Bug
>  Components: yardstick
>Affects Versions: 1.7
>Reporter: Ksenia Rybakova
>Assignee: Oleg Ostanin
>Priority: Critical
> Attachments: failed_client_log.zip
>
>
> Test config: 4 hosts with 4 clients and 1 server each, backup count = 0.
> During the test one of the servers was killed. After that one of the clients
> stopped working:
> {noformat}
> [15:31:45,248][WARN ][sys-#27%null%][TcpCommunicationSpi] Connect timed out 
> (consider increasing 'failureDetectionTimeout' configuration property) 
> [addr=fosters-216/10.20.0.216:47100, failureDetectionTimeout=1]
> [15:31:45,256][WARN ][sys-#27%null%][TcpCommunicationSpi] Failed to connect 
> to a remote node (make sure that destination node is alive and operating 
> system firewall is disabled on local and remote hosts) 
> [addrs=[fosters-216/10.20.0.216:4
> [15:31:45,276][WARN ][disco-event-worker-#52%null%][GridDiscoveryManager] 
> Node FAILED: TcpDiscoveryNode [id=f5bcc4d3-aa56-4e51-8672-e799a42990a6, 
> addrs=[10.20.0.216, 127.0.0.1], sockAddrs=[fosters-216/10.20.0.216:47500, 
> /10.20.0.216:4750
> [15:31:45,324][INFO ][disco-event-worker-#52%null%][GridDiscoveryManager] 
> Topology snapshot [ver=22, servers=3, clients=16, CPUs=64, heap=150.0GB]
> ERROR: The benchmark of random operation failed.
> Type '--help' for usage.
> Finishing main test [ts=1465252305413, date=Mon Jun 06 15:31:45 PDT 2016]
> [15:31:45] (err) Failed to execute compound future reducer: 
> GridNearTxFinishFuture 
> [futId=9c7413d2551-758034b3-0248-4d62-b901-be86d119183c, tx=GridNearTxLocal 
> [mappings=IgniteTxMappingsImpl [], nearLocallyMapped=false, colocatedLocallyMa
> Type '--help' for usage.
> [15:31:45] (err) Failed to execute compound future reducer: 
> GridNearTxFinishFuture 
> [futId=6f7413d2551-758034b3-0248-4d62-b901-be86d119183c, tx=GridNearTxLocal 
> [mappings=IgniteTxMappingsImpl [], nearLocallyMapped=false, colocatedLocallyMa
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:700)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:644)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:607)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:135)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:133)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:624)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:322)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:246)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:83)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:205)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:847)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:105)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:810)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> [15:31:45] (err) Failed to execute compound future reducer: 
> GridNearTxFinishFuture 
> [futId=ff7413d2551-758034b3-0248-4d62-b901-be86d119183c, tx=GridNearTxLocal 
> [mappings=IgniteTxMappingsImpl [], nearLocallyMapped=false, colocatedLocallyMa
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:700)
> at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:644)
> at 
> 

[jira] [Assigned] (IGNITE-3290) Yarstick: log when preloading/warmup started/finished

[Oleg Ostanin (JIRA)]

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

Oleg Ostanin reassigned IGNITE-3290:


Assignee: Oleg Ostanin

> Yarstick: log when preloading/warmup started/finished
> -
>
> Key: IGNITE-3290
> URL: https://issues.apache.org/jira/browse/IGNITE-3290
> Project: Ignite
>  Issue Type: Wish
>  Components: yardstick
>Reporter: Ksenia Rybakova
>Assignee: Oleg Ostanin
>
> Please, add messages to log that whould indicate that:
> 1) preloading started
> 2) preloading finished
> 3) warmup started



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4375) Ignite should stop on some events and Exception types

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-4375:
-

 Summary: Ignite should stop on some events and Exception types
 Key: IGNITE-4375
 URL: https://issues.apache.org/jira/browse/IGNITE-4375
 Project: Ignite
  Issue Type: Improvement
Reporter: Yakov Zhdanov


Ignite should automatically stop if
* tcp server thread in discovery exits abnormally
* discovery message worker exits abnormally
* acceptor in communication exits abnormally
* nio worker in communication exits abnormally
* exchange worker exits abnormally
* Too many open files is thrown

we simply can run 
{noformat}
new Thread(new Runnable() {
@Override public void run() {
G.stop("name", true);
}
}).start();
{noformat}
or 
{noformat}
Runtime.getRuntime().halt(1);
{noformat}

depending on situation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4374) Ignite should validate JVM and OS configuration and output warning in log

[Yakov Zhdanov (JIRA)]

Yakov Zhdanov created IGNITE-4374:
-

 Summary: Ignite should validate JVM and OS configuration and 
output warning in log
 Key: IGNITE-4374
 URL: https://issues.apache.org/jira/browse/IGNITE-4374
 Project: Ignite
  Issue Type: Improvement
Reporter: Yakov Zhdanov


Currently we have GridPerformanceSuggestions that output suggestions to logs on 
Ignite start on how Ignite can be improved.

I suggest to go a little bit deeper and validate more configuration options and 
add validation for JVM and OS settings.

Ignite should output warning if:
* GC logging is not enabled
* MaxDirectMemorySize is not set (-XX:MaxDirectMemorySize)
* Heap size is greater than 30,5G and JVM cannot use compressed oops
* Any of the recommended OS setting described here 
https://apacheignite.readme.io/docs/jvm-and-system-tuning are not properly set 




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4367) .NET: Fix flaky tests

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4367:


ServicesTest.TestDeploy(False):
Sometimes service is cancelled immediately after deployment. Not sure if this 
is caused by a failure in Execute method, which in turn is caused by failed 
"Assert.IsFalse(Cancelled);". There might be a race on Cancelled property. I've 
added locks to check this assumption.

> .NET: Fix flaky tests
> -
>
> Key: IGNITE-4367
> URL: https://issues.apache.org/jira/browse/IGNITE-4367
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Trivial
>  Labels: .NET
> Fix For: 1.9
>
>
> TeamCity has detected a number of flaky tests in .NET: 
> http://ci.ignite.apache.org/project.html?projectId=IgniteTests=flakyTests



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-3376) IGFS: Allow direct PROXY mode invocations.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3376:

Priority: Major  (was: Critical)

> IGFS: Allow direct PROXY mode invocations.
> --
>
> Key: IGNITE-3376
> URL: https://issues.apache.org/jira/browse/IGNITE-3376
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>  Labels: roadmap
> Fix For: 1.9
>
>
> Currently we do not have special handling for PROXY mode. So we will either 
> hit AssertionError during dev, or will go to incorrect code path in 
> productions systems.
> We need to fix that - PROXY mode should be handled correctly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (IGNITE-4369) ReentrantLock hangs on unlock when node is stopped.

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-4369:
--
Summary: ReentrantLock hangs on unlock when node is stopped.  (was: 
ReentrantLocks hangs on unlock when node is stopped.)

> ReentrantLock hangs on unlock when node is stopped.
> ---
>
> Key: IGNITE-4369
> URL: https://issues.apache.org/jira/browse/IGNITE-4369
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Taras Ledkov
> Fix For: 1.9
>
>  Time Spent: 4m
>  Remaining Estimate: 0h
>
> The thread hangs on GridCacheLockImpl.unlock when other node is stopped.
> {code}
> at java.lang.Thread.yield(Native Method)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl$Sync.tryRelease(GridCacheLockImpl.java:469)
>   at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1260)
>   at 
> org.apache.ignite.internal.processors.datastructures.GridCacheLockImpl.unlock(GridCacheLockImpl.java:1296)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (IGNITE-4372) Set up code coverage reports

[Ksenia Rybakova (JIRA)]

Ksenia Rybakova created IGNITE-4372:
---

 Summary: Set up code coverage reports
 Key: IGNITE-4372
 URL: https://issues.apache.org/jira/browse/IGNITE-4372
 Project: Ignite
  Issue Type: Improvement
Reporter: Ksenia Rybakova
Assignee: Ksenia Rybakova






--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4106) SQL: parallelize sql queries over cache local partitions

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov edited comment on IGNITE-4106 at 12/6/16 9:08 AM:
---

* Segmented tree index implementation moved to separate class. 
* ReduceQueryExecutor now sends only one query request per node. 
* MapQueryExecutor bothered with starting query threads if needed.
* Corresponding configuration options added.




was (Author: amashenkov):
Segmented tree index implementation moved to separate class. 
ReduceQueryExecutor now sends only one query request per node. 
MapQueryExecutor bothered with starting query threads if needed.
Corresponding configuration options added.



> SQL: parallelize sql queries over cache local partitions
> 
>
> Key: IGNITE-4106
> URL: https://issues.apache.org/jira/browse/IGNITE-4106
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.6, 1.7
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>  Labels: performance, sql
> Fix For: 2.0
>
> Attachments: 1node-4thread.jfr, 4node-1thread.jfr
>
>
> If we run SQL query on cache partitioned over several cluster nodes, it will 
> be split into several queries running in parallel. But really we will have 
> one thread per query on each node.
> So, for now, to improve SQL query performance we need to run more Ignite 
> instances or split caches manually.
> It seems to be better to split local SQL queries over cache partitions, so we 
> would be able to parallelize SQL query on every single node and utilize CPU 
> more efficiently.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (IGNITE-4301) Hadoop: send only one shuffle ack at the very end of shuffle processing.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4301:


GitHub user devozerov opened a pull request:

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

IGNITE-4301



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

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

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

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


commit b614b8d107007d59ff951f146a3a66df2526d9f8
Author: devozerov 
Date:   2016-12-05T14:14:20Z

Added messages.

commit a1ae3f223940519a62688ff484641eecf1a7cec6
Author: devozerov 
Date:   2016-12-05T14:38:19Z

WIP, but will have to restore shuffle callbacks to support out-proc mode.

commit bc3341687c92479977a785fc06a1ea78a7d10be5
Author: devozerov 
Date:   2016-12-05T14:58:17Z

Added embedded mode flag.

commit 034b0c90a68099afa0493fa5f51556a29c73a9f6
Author: devozerov 
Date:   2016-12-06T08:18:44Z

Returned shuffle ack to message factory.

commit 7e4c5a97580222be6ad41c8e1afe380dfa02d32b
Author: devozerov 
Date:   2016-12-06T08:19:44Z

Minor reverts.

commit b312ce50ad22ba87071737a18ceb5e6aaf8742e8
Author: devozerov 
Date:   2016-12-06T08:24:21Z

WIP.

commit c0b6d501ba4639ec3db3985423edbffa52938f96
Author: devozerov 
Date:   2016-12-06T08:25:41Z

Restored compilation.

commit 4d932556d4c4886c1d1a4eb6e6defc050f942bf5
Author: devozerov 
Date:   2016-12-06T08:29:41Z

WIP.

commit cad4ab8ab10293d3ab4113a61db6f9e6423adeb7
Author: devozerov 
Date:   2016-12-06T08:40:22Z

Reworked send/flush routines.

commit a696e2267c5412715e78a3ee9640b83192c57df7
Author: devozerov 
Date:   2016-12-06T08:43:23Z

Restored shuffle ack sending.

commit fdfa0e14fcea1d45f008315b712f947ada298531
Author: devozerov 
Date:   2016-12-06T08:48:23Z

Finalization.

commit 72712a37bea560b06da5847ad886c4cb65afa72d
Author: devozerov 
Date:   2016-12-06T08:50:37Z

Setting debug messages.

commit 7c98b1f99bce26b893fa4e004be4c231c913d871
Author: devozerov 
Date:   2016-12-06T08:52:28Z

Setting debug messages (2).

commit ff26ad2ef6234869e2e23a680c2cc6ed78c74026
Author: devozerov 
Date:   2016-12-06T08:53:56Z

Minor refactoring.




> Hadoop: send only one shuffle ack at the very end of shuffle processing.
> 
>
> Key: IGNITE-4301
> URL: https://issues.apache.org/jira/browse/IGNITE-4301
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general, hadoop
>Affects Versions: 1.7, 1.8
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>  Labels: performance
> Fix For: 2.0
>
>
> This shuffle acks will be processed ASAP, hence minimizing wait during 
> completion.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (IGNITE-4263) Hadoop: abstract out offheap/heap memory management.

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-4263 at 12/6/16 8:56 AM:
---

Code review: 
[IGNT-CR-28|http://reviews.ignite.apache.org/ignite/review/IGNT-CR-28]


was (Author: tledkov-gridgain):
Code 
review:[IGNT-CR-28|http://reviews.ignite.apache.org/ignite/review/IGNT-CR-28]

> Hadoop: abstract out offheap/heap memory management.
> 
>
> Key: IGNITE-4263
> URL: https://issues.apache.org/jira/browse/IGNITE-4263
> Project: Ignite
>  Issue Type: Sub-task
>  Components: hadoop
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
>  Labels: performance
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)