[jira] [Commented] (IGNITE-4157) Use discovery custom messages instead of marshaller and system cache

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov commented on IGNITE-4157:
-

Refactored all existing components to use new discovery data sharing solution.

> Use discovery custom messages instead of marshaller and system cache
> 
>
> Key: IGNITE-4157
> URL: https://issues.apache.org/jira/browse/IGNITE-4157
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Sergey Chugunov
> Fix For: 2.0
>
>
> Currently we use system caches for keeping classname to class ID mapping and 
> for storing binary metadata
> This has several serious disadvantages:
> 1) We need to introduce at least two additional thread pools for each of 
> these caches
> 2) Since cache operations require stable topology, registering a class ID or 
> updating metadata inside a transaction or another cache operation is tricky 
> and deadlock-prone.
> 3) It may be beneficial in some cases to have nodes with no caches at all, 
> currently this is impossible because system caches are always present.
> 4) Reading binary metadata leads to huge local contention, caching metadata 
> values in a local map doubles memory consumption
> I suggest we use discovery custom events for these purposes. Each node will 
> have a corresponding local map (state) which will be updated inside custom 
> event handler. From the first point of view, this should remove all the 
> disadvantages above.



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

[jira] [Updated] (IGNITE-4239) Public thread pool starvation is cause of deadlock when user's jobs calls cache.size()

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4239:
-
Description: 
The users job are hang when a lot of jobs that calculates cache size are 
submitted.

The log contains message:
{code}
WARNING: Possible thread pool starvation detected (no task completed in last 
3ms, is executorService pool size large enough?)
{code}

After a while all the thread of a public thread pool are locked on waiting the 
SizeTask future. 

  was:
The users job are hang when a lot of jobs that calculates cache size are 
submitted.

The log contains message:
{code}
WARNING: Possible thread pool starvation detected (no task completed in last 
3ms, is executorService pool size large enough?)
{code}

After a while all the thread of a public threadpool are locked on waiting the 
SizeTask future. 


> Public thread pool starvation is cause of deadlock when user's jobs calls 
> cache.size()
> --
>
> Key: IGNITE-4239
> URL: https://issues.apache.org/jira/browse/IGNITE-4239
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, compute
>Affects Versions: 1.6
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Critical
> Fix For: 1.9
>
>
> The users job are hang when a lot of jobs that calculates cache size are 
> submitted.
> The log contains message:
> {code}
> WARNING: Possible thread pool starvation detected (no task completed in last 
> 3ms, is executorService pool size large enough?)
> {code}
> After a while all the thread of a public thread pool are locked on waiting 
> the SizeTask future. 



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

[jira] [Commented] (IGNITE-4239) Public thread pool starvation is cause of deadlock when user's jobs calls cache.size()

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-4239:
--

Root cause: SizeJob is always executed in the public thread pool.

> Public thread pool starvation is cause of deadlock when user's jobs calls 
> cache.size()
> --
>
> Key: IGNITE-4239
> URL: https://issues.apache.org/jira/browse/IGNITE-4239
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, compute
>Affects Versions: 1.6
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Critical
> Fix For: 1.9
>
>
> The users job are hang when a lot of jobs that calculates cache size are 
> submitted.
> The log contains message:
> {code}
> WARNING: Possible thread pool starvation detected (no task completed in last 
> 3ms, is executorService pool size large enough?)
> {code}
> After a while all the thread of a public thread pool are locked on waiting 
> the SizeTask future. 



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

[jira] [Created] (IGNITE-4239) Public thread pool starvation is cause of deadlock when user's jobs calls cache.size()

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-4239:


 Summary: Public thread pool starvation is cause of deadlock when 
user's jobs calls cache.size()
 Key: IGNITE-4239
 URL: https://issues.apache.org/jira/browse/IGNITE-4239
 Project: Ignite
  Issue Type: Bug
  Components: cache, compute
Affects Versions: 1.6
Reporter: Taras Ledkov
Assignee: Taras Ledkov
Priority: Critical
 Fix For: 1.9


The users job are hang when a lot of jobs that calculates cache size are 
submitted.

The log contains message:
{code}
WARNING: Possible thread pool starvation detected (no task completed in last 
3ms, is executorService pool size large enough?)
{code}

After a while all the thread of a public threadpool are locked on waiting the 
SizeTask future. 



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

[jira] [Commented] (IGNITE-4163) Wrong SQL generated by org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-4163:


Merged.

> Wrong SQL generated by 
> org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery
> 
>
> Key: IGNITE-4163
> URL: https://issues.apache.org/jira/browse/IGNITE-4163
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Anghel Botos
>Assignee: Pavel Konstantinov
> Fix For: 1.8
>
> Attachments: IGNITE_4163_Fixed_load_range_queries_Review.patch, 
> IGNITE_4163_Fixed_load_range_queries_for_MS_SQL_Server_.patch, 
> IGNITE_4163_Fixed_load_range_queries_for_different_databases.patch, 
> IGNITE_4163_Index_column_in_upper_case.patch, 
> IGNITE_4163_Oracle_specific_for_load_range_query_.patch, test4163-project.zip
>
>
> The SQL statement generated by 
> org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery
>  looks like this:
> {{SELECT KEY_COLUMN_1,KEY_COLUMN_2 FROM (SELECT KEY_COLUMN_1,KEY_COLUMN_2, 
> ROWNUM() AS rn FROM SOME_TABLE ORDER BY KEY_COLUMN_1,KEY_COLUMN_2) WHERE 
> mod(rn, ?) = 0}}
> For Oracle this is incorrect, as Oracle does not have a {{ROWNUM()}} 
> function. For the above query the following error is thrown: {{ORA-00923: 
> FROM keyword not found where expected}}
> Regarding row numbering Oracle has:
> * a {{ROWNUM}} pseudocolumn, in which case the query should have {{ROWNUM AS 
> rn}}
> * a {{ROW_NUMBER()}} function, in which case the query would become more 
> complicated. See 
> https://docs.oracle.com/database/121/SQLRF/functions170.htm#SQLRF06100 for 
> more details about {{ROW_NUMBER()}}
> Please make the neccessary adjustments to either {{BasicJdbcDialect}} or 
> {{OracleDialect}} so that a correct query is produced.



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

[jira] [Updated] (IGNITE-4238) Example for spatial queries

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-4238:

Assignee: Sergi Vladykin  (was: Denis Magda)

> Example for spatial queries
> ---
>
> Key: IGNITE-4238
> URL: https://issues.apache.org/jira/browse/IGNITE-4238
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Sergi Vladykin
>Priority: Blocker
> Fix For: 1.8
>
>
> The geospatial example is missing in Apache examples. It makes sense to add 
> it.



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

[jira] [Commented] (IGNITE-4238) Example for spatial queries

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4238:
-

Added the example to "lgpl" section of the project. Here is the pull-request:
https://github.com/apache/ignite/pull/1241

[~avinogradov], please review that everything is properly done at Maven pom.xml 
layer. There is a chance that I missed something that is related to the fact 
that a binary version of {{ignite-spatial}} is not located in Maven Central and 
I have to add the GG remote repo URL to the pom if someone decides to run the 
example after downloading Apache Ignite binary and opening examples project.

[~sergi.vladykin], looks like that geospatial module is broken in the master. 
The example that I'm willing to merge works perfectly fine for version 1.7 and 
earliest but fails in the master with the exception below. Please have a look 
at the issue. This is the link to the same example that runs successfully on 
version 1.7 (https://github.com/apache/ignite/pull/1241/files).

{code}
[17:19:29,635][ERROR][main][GridMapQueryExecutor] Failed to execute local query.
class org.apache.ignite.IgniteCheckedException: Failed to execute SQL query.
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQuery(IgniteH2Indexing.java:929)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:981)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeSqlQueryWithTimer(IgniteH2Indexing.java:956)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest0(GridMapQueryExecutor.java:567)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onQueryRequest(GridMapQueryExecutor.java:449)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridMapQueryExecutor.onMessage(GridMapQueryExecutor.java:203)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:167)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor$1.applyx(GridReduceQueryExecutor.java:165)
at 
org.apache.ignite.internal.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.send(IgniteH2Indexing.java:1836)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.send(GridReduceQueryExecutor.java:1184)
at 
org.apache.ignite.internal.processors.query.h2.twostep.GridReduceQueryExecutor.query(GridReduceQueryExecutor.java:614)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$5.iterator(IgniteH2Indexing.java:1089)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:81)
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$6.iterator(IgniteH2Indexing.java:1127)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.iterator(QueryCursorImpl.java:81)
at 
org.apache.ignite.internal.processors.cache.QueryCursorImpl.getAll(QueryCursorImpl.java:100)
at 
org.apache.ignite.examples.datagrid.SpatialQueryExample.main(SpatialQueryExample.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:144)
Caused by: org.h2.jdbc.JdbcSQLException: General error: 
"com.vividsolutions.jts.io.ParseException: Unknown geometry type: 
com.vividsolutions.jts.geom.Polygon (line 1)"; SQL statement:
SELECT
"SpatialQueryExample".MAPPOINT._KEY __C0,
"SpatialQueryExample".MAPPOINT._VAL __C1
FROM "SpatialQueryExample".MAPPOINT
WHERE INTERSECTS(COORDS, ?1) [5-191]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)
at org.h2.message.DbException.get(DbException.java:168)
at org.h2.message.DbException.convert(DbException.java:295)
at org.h2.value.ValueGeometry.get(ValueGeometry.java:105)
at org.h2.value.Value.convertTo(Value.java:948)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2SpatialIndex.getEnvelope(GridH2SpatialIndex.java:175)
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2SpatialIndex.findByGeometry(GridH2SpatialIndex.java:337)
at org.h2.index.IndexCursor.find(IndexCursor.java:166)
at org.h2.table.TableFilter.next(TableFilter.java:460)
at org.h2.command.dml.Select.queryFlat(Select.java:541)
at 

[jira] [Updated] (IGNITE-4238) Example for spatial queries

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-4238:

Priority: Blocker  (was: Major)

> Example for spatial queries
> ---
>
> Key: IGNITE-4238
> URL: https://issues.apache.org/jira/browse/IGNITE-4238
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Blocker
> Fix For: 1.8
>
>
> The geospatial example is missing in Apache examples. It makes sense to add 
> it.



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

[jira] [Created] (IGNITE-4238) Example for spatial queries

[Denis Magda (JIRA)]

Denis Magda created IGNITE-4238:
---

 Summary: Example for spatial queries
 Key: IGNITE-4238
 URL: https://issues.apache.org/jira/browse/IGNITE-4238
 Project: Ignite
  Issue Type: Task
Reporter: Denis Magda
Assignee: Denis Magda
 Fix For: 1.8


The geospatial example is missing in Apache examples. It makes sense to add it.





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

[jira] [Updated] (IGNITE-3066) Set of Redis commands that can be easily implemented via existing REST commands

[Roman Shtykh (JIRA)]

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

Roman Shtykh updated IGNITE-3066:
-
Fix Version/s: 1.8

> Set of Redis commands that can be easily implemented via existing REST 
> commands
> ---
>
> Key: IGNITE-3066
> URL: https://issues.apache.org/jira/browse/IGNITE-3066
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 1.8
>
>
> As the 1st iteration of IGNITE-2788 the following commands can be implemented 
> via existing REST commands,
> GET
> MGET
> SET
> MSET
> INCR
> DECR
> INCRBY
> DECRBY
> APPEND
> STRLEN
> GETSET
> SETRANGE
> GETRANGE
> DEL
> EXISTS
> DBSIZE
> http://redis.io/commands



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

[jira] [Updated] (IGNITE-3066) Set of Redis commands that can be easily implemented via existing REST commands

[Roman Shtykh (JIRA)]

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

Roman Shtykh updated IGNITE-3066:
-
Labels: redis  (was: )

> Set of Redis commands that can be easily implemented via existing REST 
> commands
> ---
>
> Key: IGNITE-3066
> URL: https://issues.apache.org/jira/browse/IGNITE-3066
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 1.8
>
>
> As the 1st iteration of IGNITE-2788 the following commands can be implemented 
> via existing REST commands,
> GET
> MGET
> SET
> MSET
> INCR
> DECR
> INCRBY
> DECRBY
> APPEND
> STRLEN
> GETSET
> SETRANGE
> GETRANGE
> DEL
> EXISTS
> DBSIZE
> http://redis.io/commands



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

[jira] [Updated] (IGNITE-3084) Investigate how Ignite can support Spark DataFrame

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-3084:

Assignee: Valentin Kulichenko  (was: Vladimir Ozerov)

> Investigate how Ignite can support Spark DataFrame
> --
>
> Key: IGNITE-3084
> URL: https://issues.apache.org/jira/browse/IGNITE-3084
> Project: Ignite
>  Issue Type: Task
>  Components: Ignite RDD
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Valentin Kulichenko
>Priority: Critical
>  Labels: bigdata
> Fix For: 2.0
>
>
> We see increasing demand on nice DataFrame support for our Spark integration. 
> Need to investigate how could we do that.
> Looks like we can investigate how MemSQL do that and take it as a starting 
> point.



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

[jira] [Updated] (IGNITE-3822) Update ignite-spark to 2.11 v2.0.0

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-3822:

Assignee: Valentin Kulichenko

> Update ignite-spark to 2.11 v2.0.0
> --
>
> Key: IGNITE-3822
> URL: https://issues.apache.org/jira/browse/IGNITE-3822
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 1.7
>Reporter: Dovid Kopel
>Assignee: Valentin Kulichenko
>  Labels: important
> Fix For: 2.0
>
>
> Update ignite-spark to newest release version of Apache Spark:
> https://mvnrepository.com/artifact/org.apache.spark/spark-core_2.11/2.0.0



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

[jira] [Commented] (IGNITE-3958) Client node should not start rest processor

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov commented on IGNITE-3958:
--

Guys,
I've implemented the following approach 
(https://github.com/apache/ignite/pull/1240):
* By default REST processor does not start on clinet nodes;
* For start REST processor on client node need to add envirement property 
IGNITE_REST_START_ON_CLIENT;
* When REST processor does not start on client in logs prints message "REST 
protocols have not been started. For start the protocols on a client node add 
-DIGNITE_REST_START_ON_CLIENT=true";

> Client node should not start rest processor
> ---
>
> Key: IGNITE-3958
> URL: https://issues.apache.org/jira/browse/IGNITE-3958
> Project: Ignite
>  Issue Type: Bug
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Tikhonov
> Fix For: 2.0
>
>




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

[jira] [Updated] (IGNITE-4137) .NET: add example for Atomic Types

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-4137:

Assignee: Pavel Tupitsyn  (was: Denis Magda)

> .NET: add example for Atomic Types
> --
>
> Key: IGNITE-4137
> URL: https://issues.apache.org/jira/browse/IGNITE-4137
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Add the example that will showcase the usage of all Atomic Types that are 
> presently supported in .NET.



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

[jira] [Commented] (IGNITE-4137) .NET: add example for Atomic Types

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4137:
-

Replied.

> .NET: add example for Atomic Types
> --
>
> Key: IGNITE-4137
> URL: https://issues.apache.org/jira/browse/IGNITE-4137
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.8
>
>
> Add the example that will showcase the usage of all Atomic Types that are 
> presently supported in .NET.



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

[jira] [Commented] (IGNITE-4137) .NET: add example for Atomic Types

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4137:


It works now, fixed some things and replied.

> .NET: add example for Atomic Types
> --
>
> Key: IGNITE-4137
> URL: https://issues.apache.org/jira/browse/IGNITE-4137
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Add the example that will showcase the usage of all Atomic Types that are 
> presently supported in .NET.



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

[jira] [Commented] (IGNITE-4125) .NET: documentation and example for off-heap and swap tieres

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4125:
-

Let's restrict it to a single node example only then for the simplicity 
purposes explaining to the user why we did this.

> .NET: documentation and example for off-heap and swap  tieres
> -
>
> Key: IGNITE-4125
> URL: https://issues.apache.org/jira/browse/IGNITE-4125
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Presently the documentation and example about the off-heap and swap tieres 
> are missing on .NET side. Let's fill this gap.
> Documentation can be taken from Java side 
> https://apacheignite.readme.io/docs/off-heap-memory
> The example that can be (should be) added to the distribution is the 
> following 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/MultiTieredCacheExample.cs



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

[jira] [Commented] (IGNITE-4137) .NET: add example for Atomic Types

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4137:
-

Sorry, forgot to click on "Submit Review" button. Now you should see my minor 
comments in GitHub.

> .NET: add example for Atomic Types
> --
>
> Key: IGNITE-4137
> URL: https://issues.apache.org/jira/browse/IGNITE-4137
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.8
>
>
> Add the example that will showcase the usage of all Atomic Types that are 
> presently supported in .NET.



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

[jira] [Updated] (IGNITE-4184) Document how ODBC drivers works with the cluster

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-4184:

Assignee: Prachi Garg  (was: Denis Magda)

> Document how ODBC drivers works with the cluster
> 
>
> Key: IGNITE-4184
> URL: https://issues.apache.org/jira/browse/IGNITE-4184
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.0
>
>
> There are no any details on how ODBC driver connects to the cluster and sends 
> queries to it for the execution. 
> Let's make our documentation more technical by adding the following blocks to 
> this page [1]:
> - ODBC Driver necessity and usage on Java side
> - ODBC Configuration parameter
> - Details on how ODBC connection works on C++ side and how you can alter 
> specific parameters using Configuration object
> [1] https://apacheignite.readme.io/docs/odbc-driver



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

[jira] [Commented] (IGNITE-3955) IgniteCache.invokeAll returns empty result set in ATOMIC cache

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov commented on IGNITE-3955:
---

branch with test fixed: 
https://github.com/gridgain/apache-ignite/commits/ignite-3955

> IgniteCache.invokeAll returns empty result set in ATOMIC cache
> --
>
> Key: IGNITE-3955
> URL: https://issues.apache.org/jira/browse/IGNITE-3955
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Konstantin Dudkov
> Fix For: 1.8
>
>
> When entry processor is invoked from multiple threads, result set is 
> sometimes empty.
> This happens with ATOMIC cache, but not with TRANSACTIONAL.
> To reproduce, paste the following into GridCacheAbstractFullApiSelfTest.java:
> {code}
> public void testInvokeAllMultithreaded() throws Exception {
> final IgniteCache cache = jcache();
> final int threadCnt = 4;
> final int cnt = 9;
> final Set keys = Collections.singleton("myKey");
> GridTestUtils.runMultiThreaded(new Runnable() {
> @Override public void run() {
> for (int i = 0; i < cnt; i++) {
> final Map res =
> cache.invokeAll(keys, new CacheEntryProcessor Integer, Integer>() {
> @Override
> public Integer process(MutableEntry Integer> entry,
> Object... objects) throws 
> EntryProcessorException {
> Integer val = entry.getValue();
> if (val == null)
> val = 0;
> val++;
> entry.setValue(val);
> return val;
> }
> });
> assertEquals(1, res.size());
> }
> }
> }, threadCnt, "testInvokeAllMultithreaded");
> assertEquals(cnt*threadCnt, (int)cache.get("myKey"));
> }
> {code}
> Run this test as part of GridCacheAtomicFullApiSelfTest.java.



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

[jira] [Updated] (IGNITE-2266) Several examples fail with Optimized marshaller

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2266:

Fix Version/s: (was: 1.8)
   2.0

> Several examples fail with Optimized marshaller
> ---
>
> Key: IGNITE-2266
> URL: https://issues.apache.org/jira/browse/IGNITE-2266
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
> Environment: Apache Ignite 1.5.0.final build #128 
>Reporter: Vasilisa  Sidorova
> Fix For: 2.0
>
>
> -
> DESCRIPTION
> -
> CacheQueryExample and StreamVisitorExample fail if it's running with 
> Optimized marshaller (instead deafult Binary marshaller)
> -
> STEPS FOR REPRODUCE
> -
> # Build examples in IDE
> # Add property Into example-ignite.xml:
> {noformat}
> 
>  class="org.apache.ignite.marshaller.optimized.OptimizedMarshaller"> 
> 
> 
> 
> 
> {noformat}
> # Run CacheQueryExample
> -
> ACTUAL RESULT
> -
> Example fails with exception:
> {noformat}
> [15:41:02,466][ERROR][sys-#31%null%][GridCacheDistributedQueryManager] 
>  Failed to run query [qry=GridCacheQueryInfo 
> [loc=false, trans=null, rdc=null, qry=GridCacheQueryAdapter [type=SCAN, 
> clsName=null, clause=null, 
> filter=o.a.i.examples.datagrid.CacheQueryExample$1@136abff1, part=null, 
> incMeta=false, metrics=null, pageSize=1024, timeout=0, keepAll=false, 
> incBackups=false, dedup=false, prj=null, keepBinary=true, 
> subjId=d4d84708-9109-4706-8454-5cbae2fff7bb, taskHash=0], locFut=null, 
> sndId=d4d84708-9109-4706-8454-5cbae2fff7bb, reqId=28, incMeta=false, 
> all=false], node=d4d84708-9109-4706-8454-5cbae2fff7bb]
> class org.apache.ignite.IgniteCheckedException: 
> org.apache.ignite.cache.affinity.AffinityKey cannot be cast to 
> org.apache.ignite.binary.BinaryObject
>   at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7005)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:166)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$CachedResult.iterator(GridCacheQueryManager.java:2825)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.runQuery(GridCacheQueryManager.java:1390)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager.processQueryRequest(GridCacheDistributedQueryManager.java:227)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheDistributedQueryManager$7.call(GridCacheDistributedQueryManager.java:764)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6397)
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:929)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassCastException: 
> org.apache.ignite.cache.affinity.AffinityKey cannot be cast to 
> org.apache.ignite.binary.BinaryObject
>   at 
> org.apache.ignite.examples.datagrid.CacheQueryExample$1.apply(CacheQueryExample.java:133)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$5.checkPredicate(GridCacheQueryManager.java:963)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$5.advance(GridCacheQueryManager.java:929)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager$5.(GridCacheQueryManager.java:874)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.scanIterator(GridCacheQueryManager.java:829)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.executeQuery(GridCacheQueryManager.java:593)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.queryResult(GridCacheQueryManager.java:1687)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.queryResult(GridCacheQueryManager.java:1654)
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.runQuery(GridCacheQueryManager.java:1385)
>   ... 8 

[jira] [Updated] (IGNITE-2180) Javadocs for some modules are missing from Maven repository

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2180:

Fix Version/s: (was: 1.8)
   2.0

> Javadocs for some modules  are missing from Maven repository 
> -
>
> Key: IGNITE-2180
> URL: https://issues.apache.org/jira/browse/IGNITE-2180
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Affects Versions: 1.5.0.final
> Environment: Apache Ignite 1.5.0-b2 build #112
>Reporter: Vasilisa  Sidorova
> Fix For: 2.0
>
>
> Javadocs are missing from Maven repository for following modules:
> * ignite-clients
> * ignite-extdata-uri
> * ignite-osgi-karaf
> * ignite-osgi-paxlogging
> * ignite-scalar
> * ignite-scalar_2.10
> * ignite-spark
> * ignite-spark_2.10
> * ignite-visor-console
> * ignite-visor-console_2.10
> Please, fix it



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

[jira] [Updated] (IGNITE-1967) ignitevisorcmd: external keys description should be updated

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1967:

Fix Version/s: (was: 1.8)
   2.0

> ignitevisorcmd: external keys description should be updated
> ---
>
> Key: IGNITE-1967
> URL: https://issues.apache.org/jira/browse/IGNITE-1967
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.5.0.final
> Environment: Apache Ignite 1.5.0 build #70
>Reporter: Vasilisa  Sidorova
>Priority: Trivial
> Fix For: 2.0
>
>
> -
> DESCRIPTION
> -
> Some external keys for visorcmd starting are obsoleted. At least, "?" key
>  
> -
> STEPS FOR REPRODUCE
> -
> # Run visorcmd from IGNITE_HOME/bin "./ignitevisorcmd.sh ?"
> -
> ACTUAL RESULT
> -
> visorcmd is started 
> -
> EXPECTED RESULT
> -
> help message for visorcmd is displayed.  Proposal: delete key "?" from help



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

[jira] [Updated] (IGNITE-1784) [Failed Test] GridEventConsumeSelfTest.testMultithreadedWithNodeRestart fails on TC sometimes.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1784:

Fix Version/s: (was: 1.8)
   2.0

> [Failed Test] GridEventConsumeSelfTest.testMultithreadedWithNodeRestart fails 
> on TC sometimes.
> --
>
> Key: IGNITE-1784
> URL: https://issues.apache.org/jira/browse/IGNITE-1784
> Project: Ignite
>  Issue Type: Test
>Reporter: Artem Shutak
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
> Attachments: Ignite_Tests_Ignite_Basic_3553.log.zip
>
>
> GridEventConsumeSelfTest.testMultithreadedWithNodeRestart fails on TC 
> sometimes.
> Looks like after fail in the test all other tests hanged.
> See logs.



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

[jira] [Updated] (IGNITE-1757) [Failed test] CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails on TC sometimes

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1757:

Fix Version/s: (was: 1.8)
   2.0

> [Failed test] CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails 
> on TC sometimes
> 
>
> Key: IGNITE-1757
> URL: https://issues.apache.org/jira/browse/IGNITE-1757
> Project: Ignite
>  Issue Type: Test
>Reporter: Artem Shutak
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
>
> CacheHibernateBlobStoreSelfTest.testSimpleMultithreading fails on TC 
> sometimes.
> {noformat}
> java.lang.NullPointerException: null
> at 
> org.apache.maven.surefire.shade.org.apache.commons.io.output.DeferredFileOutputStream.thresholdReached(DeferredFileOutputStream.java:179)
> at 
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.checkThreshold(ThresholdingOutputStream.java:224)
> at 
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.write(ThresholdingOutputStream.java:128)
> at 
> org.apache.maven.plugin.surefire.report.Utf8RecodingDeferredFileOutputStream.write(Utf8RecodingDeferredFileOutputStream.java:59)
> at 
> org.apache.maven.plugin.surefire.report.TestSetRunListener.writeTestOutput(TestSetRunListener.java:98)
> at 
> org.apache.maven.surefire.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:91)
> at 
> org.hibernate.engine.jdbc.spi.SqlStatementLogger.logStatement(SqlStatementLogger.java:106)
> at 
> org.hibernate.engine.jdbc.spi.SqlStatementLogger.logStatement(SqlStatementLogger.java:95)
> at 
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl$StatementPreparationTemplate.prepareStatement(StatementPreparerImpl.java:180)
> at 
> org.hibernate.engine.jdbc.internal.StatementPreparerImpl.prepareStatement(StatementPreparerImpl.java:85)
> at 
> org.hibernate.persister.entity.AbstractEntityPersister.getDatabaseSnapshot(AbstractEntityPersister.java:1513)
> at 
> org.hibernate.engine.internal.StatefulPersistenceContext.getDatabaseSnapshot(StatefulPersistenceContext.java:316)
> at 
> org.hibernate.engine.internal.ForeignKeys.isTransient(ForeignKeys.java:217)
> at 
> org.hibernate.event.internal.AbstractSaveEventListener.getEntityState(AbstractSaveEventListener.java:497)
> at 
> org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:100)
> at 
> org.hibernate.event.internal.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:90)
> at 
> org.hibernate.internal.SessionImpl.fireSaveOrUpdate(SessionImpl.java:735)
> at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:727)
> at org.hibernate.internal.SessionImpl.saveOrUpdate(SessionImpl.java:723)
> at 
> org.apache.ignite.cache.store.hibernate.CacheHibernateBlobStore.write(CacheHibernateBlobStore.java:190)
> at 
> org.apache.ignite.testframework.junits.cache.GridAbstractCacheStoreSelfTest$1.call(GridAbstractCacheStoreSelfTest.java:396)
> at 
> org.apache.ignite.testframework.GridTestThread.run(GridTestThread.java:86)
> --- Stderr: ---
> [21:04:18,410][WARN 
> ][hibernate.CacheHibernateBlobStoreSelfTest-1][CacheHibernateBlobStore] No 
> Hibernate configuration has been provided for store (will use default).
> [21:04:18,495][WARN 
> ][hibernate.CacheHibernateBlobStoreSelfTest-1][DriverManagerConnectionProviderImpl]
>  HHH000148: No JDBC Driver class was specified by property 
> hibernate.connection.driver_class
> Failure in thread: Thread [id=711, 
> name=hibernate.CacheHibernateBlobStoreSelfTest-5]
> java.lang.NullPointerException
> at 
> org.apache.maven.surefire.shade.org.apache.commons.io.output.DeferredFileOutputStream.thresholdReached(DeferredFileOutputStream.java:179)
> at 
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.checkThreshold(ThresholdingOutputStream.java:224)
> at 
> org.apache.maven.surefire.shade.org.apache.commons.io.output.ThresholdingOutputStream.write(ThresholdingOutputStream.java:128)
> at 
> org.apache.maven.plugin.surefire.report.Utf8RecodingDeferredFileOutputStream.write(Utf8RecodingDeferredFileOutputStream.java:59)
> at 
> org.apache.maven.plugin.surefire.report.TestSetRunListener.writeTestOutput(TestSetRunListener.java:98)
> at 
> org.apache.maven.surefire.report.ConsoleOutputCapture$ForwardingPrintStream.println(ConsoleOutputCapture.java:91)
> at 
> org.hibernate.engine.jdbc.spi.SqlStatementLogger.logStatement(SqlStatementLogger.java:106)
> at 
> 

[jira] [Updated] (IGNITE-1738) [Test Failed] IgniteClientReconnectCacheTest.testReconnect

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1738:

Fix Version/s: (was: 1.8)
   2.0

> [Test Failed] IgniteClientReconnectCacheTest.testReconnect
> --
>
> Key: IGNITE-1738
> URL: https://issues.apache.org/jira/browse/IGNITE-1738
> Project: Ignite
>  Issue Type: Test
>Reporter: Artem Shutak
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
>
> Test fails on TC sometime. Could not reproduce locally.
> Test log
> {noformat}
> junit.framework.AssertionFailedError: expected:<21> but was:<20>
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.failNotEquals(Assert.java:329)
> at junit.framework.Assert.assertEquals(Assert.java:78)
> at junit.framework.Assert.assertEquals(Assert.java:86)
> at junit.framework.TestCase.assertEquals(TestCase.java:253)
> at 
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnect(IgniteClientReconnectCacheTest.java:280)
> --- Stdout: ---
> [20:07:22,890][INFO ][main][root] >>> Starting test: testReconnect <<<
> [20:07:22,896][INFO ][main][IgniteClientReconnectCacheTest0] 
> >>>__    
> >>>   /  _/ ___/ |/ /  _/_  __/ __/  
> >>>  _/ // (7 7// /  / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/   
> >>> 
> >>> ver. 1.5.0-SNAPSHOT#20151019-sha1:10ef06a1
> >>> 2015 Copyright(C) Apache Software Foundation
> >>> 
> >>> Ignite documentation: http://ignite.apache.org
> [20:07:22,896][INFO ][main][IgniteClientReconnectCacheTest0] Config URL: n/a
> [20:07:22,896][INFO ][main][IgniteClientReconnectCacheTest0] Daemon mode: off
> [20:07:22,896][INFO ][main][IgniteClientReconnectCacheTest0] OS: Linux 
> 2.6.32-74-generic amd64
> [20:07:22,896][INFO ][main][IgniteClientReconnectCacheTest0] OS user: teamcity
> [20:07:22,896][INFO ][main][IgniteClientReconnectCacheTest0] Language 
> runtime: Java Platform API Specification ver. 1.7
> [20:07:22,896][INFO ][main][IgniteClientReconnectCacheTest0] VM information: 
> Java(TM) SE Runtime Environment 1.7.0_21-b11 Oracle Corporation Java 
> HotSpot(TM) 64-Bit Server VM 23.21-b01
> [20:07:22,896][INFO ][main][IgniteClientReconnectCacheTest0] VM total memory: 
> 2.7GB
> [20:07:22,896][INFO ][main][IgniteClientReconnectCacheTest0] Remote 
> Management [restart: off, REST: off, JMX (remote: off)]
> [20:07:22,896][INFO ][main][IgniteClientReconnectCacheTest0] 
> IGNITE_HOME=/usr/local/TeamCityAgent/work/f87ae3766fbb88e2
> [20:07:22,897][INFO ][main][IgniteClientReconnectCacheTest0] VM arguments: 
> [-DJAVA_HOME=/home/teamcity/jdk1.7.0_21, -DMCAST_GRP=229.15.1.2, 
> -Dagent.home.dir=/usr/local/TeamCityAgent, -Dagent.name=teamcity-5, 
> -Dagent.ownPort=9090, -Dagent.work.dir=/usr/local/TeamCityAgent/work, 
> -Dbuild.number=560, 
> -Dbuild.vcs.number=10ef06a14245c73cbfe66b744406a0391c4a9c08, 
> -Dbuild.vcs.number.1=10ef06a14245c73cbfe66b744406a0391c4a9c08, 
> -Dbuild.vcs.number.ApacheIgniteMirrorOnGitHub=10ef06a14245c73cbfe66b744406a0391c4a9c08,
>  -Dclassworlds.conf=/usr/local/TeamCityAgent/temp/buildTmp/teamcity.m2.conf, 
> -Dcom.jetbrains.maven.watcher.report.file=/usr/local/TeamCityAgent/temp/buildTmp/maven-build-info.xml,
>  -Djava.io.tmpdir=/usr/local/TeamCityAgent/temp/buildTmp, 
> -Dmaven.home=/usr/local/TeamCityAgent/tools/maven3, 
> -Dmaven.repo.local=/home/teamcity/.m2/repository, 
> -Dteamcity.agent.cpuBenchmark=665, 
> -Dteamcity.agent.dotnet.agent_url=http://localhost:9090/RPC2, 
> -Dteamcity.agent.dotnet.build_id=554010, 
> -Dteamcity.auth.password=NZJLF36rtgBzyZan9Rlqx1nibYhaTdzk, 
> -Dteamcity.auth.userId=TeamCityBuildId=554010, 
> -Dteamcity.build.changedFiles.file=/usr/local/TeamCityAgent/temp/buildTmp/changedFiles2364753307910338165.txt,
>  -Dteamcity.build.checkoutDir=/usr/local/TeamCityAgent/work/f87ae3766fbb88e2, 
> -Dteamcity.build.id=554010, 
> -Dteamcity.build.properties.file=/usr/local/TeamCityAgent/temp/buildTmp/teamcity.build7009344645725909149.properties,
>  -Dteamcity.build.tempDir=/usr/local/TeamCityAgent/temp/buildTmp, 
> -Dteamcity.build.workingDir=/usr/local/TeamCityAgent/work/f87ae3766fbb88e2, 
> -Dteamcity.buildConfName=Ignite Client Nodes, 
> -Dteamcity.buildType.id=Ignite_IgniteClients, 
> -Dteamcity.configuration.properties.file=/usr/local/TeamCityAgent/temp/buildTmp/teamcity.config8423242305191431229.properties,
>  -Dteamcity.idea.home=/usr/local/TeamCityAgent/plugins/idea, 
> -Dteamcity.maven.watcher.home=/usr/local/TeamCityAgent/plugins/mavenPlugin/maven-watcher,
>  -Dteamcity.projectName=Ignite Tests, 
> -Dteamcity.runner.properties.file=/usr/local/TeamCityAgent/temp/buildTmp/teamcity.runner2097693476768347057.properties,
>  
> 

[jira] [Updated] (IGNITE-1795) TcpCommunicationSpi tests fail only on Mac

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1795:

Fix Version/s: (was: 1.8)
   2.0

> TcpCommunicationSpi tests fail only on Mac
> --
>
> Key: IGNITE-1795
> URL: https://issues.apache.org/jira/browse/IGNITE-1795
> Project: Ignite
>  Issue Type: Test
>Reporter: Artem Shutak
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
> Attachments: Ignite_Tests_Ignite_SPI_3373.log.zip
>
>
> Next tests fail only on Mac
> GridTcpCommunicationSpiRecoveryFailureDetectionSelfTest.testBlockRead1
>  GridTcpCommunicationSpiRecoveryFailureDetectionSelfTest.testBlockRead2   
>  GridTcpCommunicationSpiRecoveryFailureDetectionSelfTest.testBlockRead3   
>  GridTcpCommunicationSpiRecoverySelfTest.testBlockRead1   
>  GridTcpCommunicationSpiRecoverySelfTest.testBlockRead2   
>  GridTcpCommunicationSpiRecoverySelfTest.testBlockRead3   



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

[jira] [Updated] (IGNITE-1776) [Test Failed] TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails sometimes

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1776:

Fix Version/s: (was: 1.8)
   2.0

> [Test Failed] TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails 
> sometimes
> ---
>
> Key: IGNITE-1776
> URL: https://issues.apache.org/jira/browse/IGNITE-1776
> Project: Ignite
>  Issue Type: Test
>Reporter: Artem Shutak
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
>
> TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer fails on TC 
> sometimes.
> Looks like a test bug, need just increase awaitTime(). I see Node FAILED 
> message exactly after 10 seconds. But it's strange that it's require too long 
> time. May be something wrong on agent.
> Logs:
> {noformat}
> junit.framework.AssertionFailedError: Latch count: 1
> at junit.framework.Assert.fail(Assert.java:57)
> at junit.framework.Assert.assertTrue(Assert.java:22)
> at junit.framework.TestCase.assertTrue(TestCase.java:192)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.await(TcpClientDiscoverySpiSelfTest.java:2030)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.testClientNodeFailOneServer(TcpClientDiscoverySpiSelfTest.java:811)
> --- Stdout: ---
> [03:18:46,228][INFO ][main][root] >>> Starting test: 
> testClientNodeFailOneServer <<<
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] 
> >>>__    
> >>>   /  _/ ___/ |/ /  _/_  __/ __/  
> >>>  _/ // (7 7// /  / / / _/
> >>> /___/\___/_/|_/___/ /_/ /___/   
> >>> 
> >>> ver. 1.5.0-SNAPSHOT#19700101-sha1:DEV
> >>> 2015 Copyright(C) Apache Software Foundation
> >>> 
> >>> Ignite documentation: http://ignite.apache.org
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Config URL: n/a
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Daemon mode: off
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] OS: Mac OS X 10.7.5 
> x86_64
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] OS user: teamcity
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Language runtime: 
> Java Platform API Specification ver. 1.7
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] VM information: 
> Java(TM) SE Runtime Environment 1.7.0_67-b01 Oracle Corporation Java 
> HotSpot(TM) 64-Bit Server VM 24.65-b04
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] VM total memory: 
> 2.7GB
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] Remote Management 
> [restart: off, REST: off, JMX (remote: off)]
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] 
> IGNITE_HOME=/Users/teamcity/buildAgent/work/871ff4a46e450b13
> [03:18:46,233][INFO ][test-runner][IgniteKernal%server-0] VM arguments: 
> [-DJAVA_HOME=/Library/Java/JavaVirtualMachines/jdk1.7.0_67.jdk/Contents/Home, 
> -DMCAST_GRP=229.116.1.2, -Dagent.home.dir=/Users/teamcity/buildAgent, 
> -Dagent.name=ip_192.168.1.116, -Dagent.ownPort=9090, 
> -Dagent.work.dir=/Users/teamcity/buildAgent/work, -Dbuild.number=3345, 
> -Dbuild.vcs.number=91e31e99c2574f7cede8d80ec9b8d981ccc34bcb, 
> -Dbuild.vcs.number.1=91e31e99c2574f7cede8d80ec9b8d981ccc34bcb, 
> -Dbuild.vcs.number.ApacheIgniteMirrorOnGitHub=91e31e99c2574f7cede8d80ec9b8d981ccc34bcb,
>  
> -Dclassworlds.conf=/Users/teamcity/buildAgent/temp/buildTmp/teamcity.m2.conf, 
> -Dcom.jetbrains.maven.watcher.report.file=/Users/teamcity/buildAgent/temp/buildTmp/maven-build-info.xml,
>  -Djava.io.tmpdir=/Users/teamcity/buildAgent/temp/buildTmp, 
> -Dmaven.home=/Users/teamcity/buildAgent/tools/maven3, 
> -Dmaven.repo.local=/Users/teamcity/.m2/repository, 
> -Dteamcity.agent.cpuBenchmark=605, 
> -Dteamcity.agent.dotnet.agent_url=http://localhost:9090/RPC2, 
> -Dteamcity.agent.dotnet.build_id=555612, 
> -Dteamcity.auth.password=j1gKlVPBOa3H6Wnrjp3Q3sK7ZqR4biuf, 
> -Dteamcity.auth.userId=TeamCityBuildId=555612, 
> -Dteamcity.build.changedFiles.file=/Users/teamcity/buildAgent/temp/buildTmp/changedFiles5940678572218707636.txt,
>  
> -Dteamcity.build.checkoutDir=/Users/teamcity/buildAgent/work/871ff4a46e450b13,
>  -Dteamcity.build.id=555612, 
> -Dteamcity.build.properties.file=/Users/teamcity/buildAgent/temp/buildTmp/teamcity.build3844607694634646095.properties,
>  -Dteamcity.build.tempDir=/Users/teamcity/buildAgent/temp/buildTmp, 
> -Dteamcity.build.workingDir=/Users/teamcity/buildAgent/work/871ff4a46e450b13, 
> -Dteamcity.buildConfName=Ignite SPI, -Dteamcity.buildType.id=Ignite_Spi, 
> -Dteamcity.configuration.properties.file=/Users/teamcity/buildAgent/temp/buildTmp/teamcity.config8915518964213838573.properties,
>  

[jira] [Updated] (IGNITE-1823) Peer class loading can produce ClassCastException with DeploymentMode.SHARED (default)

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1823:

Fix Version/s: (was: 1.8)
   2.0

> Peer class loading can produce ClassCastException with DeploymentMode.SHARED 
> (default)
> --
>
> Key: IGNITE-1823
> URL: https://issues.apache.org/jira/browse/IGNITE-1823
> Project: Ignite
>  Issue Type: Bug
>  Components: 1.4
>Affects Versions: ignite-1.4, 1.5.0.final
>Reporter: Artem Shutak
>  Labels: community
> Fix For: 2.0
>
> Attachments: client-run-1.log, client-run-2.log, server.log
>
>
> Peer class loading can produce ClassCastException with DeploymentMode.SHARED 
> (default).
> Steps to reproduce (tested with 1.4 and 1.5-SNAPSHOT).
> - Build Ignite under java 7. 
> - Run ignite.sh with default configuration and enabled peer class loading 
> under Java 8
> - Run Test class under java8
> - Run Test class under java8 again. On second run you will get 
> ClassCastException.
> Looks like the issue is Ignite use different classloaders for first and 
> second run of Test (Task class deployed and undeployed each time).
> Workarounds:
> - Use another DeploymentMode. For example in this case Ignite works fine with 
> CONTINUOUS deployment mode.
> - Don't use peer class loading and add jars with custom tasks to classpath of 
> server nodes.
> Exception:
> {noformat}
> [19:56:03,013][SEVERE][ignite-#18%sys-null%][GridTaskWorker] Failed to obtain 
> remote job result policy for result from ComputeTask.result(..) method (will 
> fail the whole task): GridJobResultImpl [job=C2 [], sib=GridJobSiblingImpl 
> [sesId=37a6da9b051-7d576228-e0e4-492c-a325-35ce4fc40ea0, 
> jobId=47a6da9b051-cadb35ba-9bc8-4f05-b9ce-03344883743f, 
> nodeId=cadb35ba-9bc8-4f05-b9ce-03344883743f, isJobDone=false], 
> jobCtx=GridJobContextImpl 
> [jobId=47a6da9b051-cadb35ba-9bc8-4f05-b9ce-03344883743f, timeoutObj=null, 
> attrs={}], node=TcpDiscoveryNode [id=cadb35ba-9bc8-4f05-b9ce-03344883743f, 
> addrs=[0:0:0:0:0:0:0:1%lo, 127.0.0.1, 192.168.1.159], 
> sockAddrs=[/192.168.1.159:47500, /0:0:0:0:0:0:0:1%lo:47500, /127.0.0.1:47500, 
> /192.168.1.159:47500], discPort=47500, order=1, intOrder=1, 
> lastExchangeTime=1446224162137, loc=false, ver=1.5.0#20151029-sha1:91059ba8, 
> isClient=false], ex=class o.a.i.IgniteException: mypackage.Task cannot be 
> cast to mypackage.Task, hasRes=true, isCancelled=false, isOccupied=true]
> class org.apache.ignite.IgniteException: Remote job threw user exception 
> (override or implement ComputeTask.result(..) method if you would like to 
> have automatic failover for this exception).
>   at 
> org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:903)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$3.apply(GridTaskWorker.java:896)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6403)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:896)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:792)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:995)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1219)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:811)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1500(GridIoManager.java:106)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:774)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteException: mypackage.Task cannot be 
> cast to mypackage.Task
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1792)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:509)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6371)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:503)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:456)
>   at 
> 

[jira] [Updated] (IGNITE-1793) [Failed Test] IgnitePartitionedCountDownLatchSelfTest.testLatch hangs on TC sometimes

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1793:

Fix Version/s: (was: 1.8)
   2.0

> [Failed Test] IgnitePartitionedCountDownLatchSelfTest.testLatch   hangs 
> on TC sometimes
> -
>
> Key: IGNITE-1793
> URL: https://issues.apache.org/jira/browse/IGNITE-1793
> Project: Ignite
>  Issue Type: Test
>Reporter: Artem Shutak
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
> Attachments: test.logs
>
>
> IgnitePartitionedCountDownLatchSelfTest.testLatch hangs on TC sometimes.
> Test hangs on IgniteCountDownLatch.count() method.
> {noformat}
> Thread [name="test-runner", id=24157, state=WAITING, blockCnt=0, waitCnt=96]
> Lock [object=o.a.i.i.util.future.GridFutureAdapter$ChainFuture@1e542154, 
> ownerName=null, ownerId=-1]
> at sun.misc.Unsafe.park(Native Method)
> at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:994)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1303)
> at 
> o.a.i.i.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:157)
> at 
> o.a.i.i.util.future.GridFutureAdapter.get(GridFutureAdapter.java:115)
> at 
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:4525)
> at 
> o.a.i.i.processors.cache.GridCacheAdapter.get(GridCacheAdapter.java:1544)
> at 
> o.a.i.i.processors.datastructures.GridCacheCountDownLatchImpl$GetCountCallable.call(GridCacheCountDownLatchImpl.java:348)
> at 
> o.a.i.i.processors.datastructures.GridCacheCountDownLatchImpl$GetCountCallable.call(GridCacheCountDownLatchImpl.java:342)
> at 
> o.a.i.i.processors.cache.GridCacheUtils.outTx(GridCacheUtils.java:962)
> at 
> o.a.i.i.processors.datastructures.GridCacheCountDownLatchImpl.count(GridCacheCountDownLatchImpl.java:143)
> at 
> o.a.i.i.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest.checkRemovedLatch(IgniteCountDownLatchAbstractSelfTest.java:159)
> at 
> o.a.i.i.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest.checkCountDown(IgniteCountDownLatchAbstractSelfTest.java:232)
> at 
> o.a.i.i.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest.checkLatch(IgniteCountDownLatchAbstractSelfTest.java:84)
> at 
> o.a.i.i.processors.cache.datastructures.IgniteCountDownLatchAbstractSelfTest.testLatch(IgniteCountDownLatchAbstractSelfTest.java:72)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> o.a.i.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1658)
> at 
> o.a.i.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:112)
> at 
> o.a.i.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1596)
> {noformat}



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

[jira] [Updated] (IGNITE-1268) CacheAPIExample should have non-empty result

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1268:

Fix Version/s: (was: 1.8)
   2.0

> CacheAPIExample should have non-empty result 
> -
>
> Key: IGNITE-1268
> URL: https://issues.apache.org/jira/browse/IGNITE-1268
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: ignite-1.4
> Environment: Ubuntu 14.04, apache-ignite-1.3.0-incubating
>Reporter: Vasilisa  Sidorova
>Priority: Minor
> Fix For: 2.0
>
>
> -
> DESCRIPTION
> -
> CacheAPIExample have empty result. It's non informational and non 
> user-friendly.
> -
> STEPS FOR REPRODUCE
> -
> 1. Download apache-ignite-1.3.0-incubating from ignite.apache.org
> 2. Build examples in the IDE
> 3. Run CacheAPIExample
> -
> ACTUAL RESULT
> -
> CacheAPIExample have empty result:
> {noformat}
> >>> Cache API example started.
> >>> Cache atomic map operation examples.
> {noformat}
> -
> EXPECTED RESULT
> -
> CacheAPIExample have informational result. It could be, for example, the 
> information about cache contents before and after put operations



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

[jira] [Updated] (IGNITE-802) [Test] [Rare] GridCachePartitionedQueueEntryMoveSelfTest.testQueue

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-802:
---
Fix Version/s: (was: 1.8)
   2.0

> [Test] [Rare] GridCachePartitionedQueueEntryMoveSelfTest.testQueue
> --
>
> Key: IGNITE-802
> URL: https://issues.apache.org/jira/browse/IGNITE-802
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Artem Shutak
>  Labels: Muted_test
> Fix For: 2.0
>
> Attachments: 
> Ignite_Tests_Ignite_Binary_Objects_Data_Strucutures_268_artifacts.zip, 
> ignite-802.patch
>
>
> The test had been already fixed (see GG-5620), but it was not uncommented 
> after. Now it fails.



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

[jira] [Resolved] (IGNITE-4234) .NET: Propagate missing CacheMetrics properties

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-4234.

Resolution: Fixed
  Assignee: (was: Pavel Tupitsyn)

> .NET: Propagate missing CacheMetrics properties
> ---
>
> Key: IGNITE-4234
> URL: https://issues.apache.org/jira/browse/IGNITE-4234
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> CacheMetrics in Java has a lot more properties than ICacheMetrics in .NET



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

[jira] [Assigned] (IGNITE-4236) .NET: ICache.LocalMetrics and overloads

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-4236:
--

Assignee: Pavel Tupitsyn

> .NET: ICache.LocalMetrics and overloads
> ---
>
> Key: IGNITE-4236
> URL: https://issues.apache.org/jira/browse/IGNITE-4236
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> Ignite in Java has three cache metrics methods:
> {code}
> CacheMetrics metrics();
> CacheMetrics metrics(ClusterGroup grp);
> CacheMetrics localMetrics();
> {code}
> Ignite.NET should provide these too. See how IGNITE-1071 changed the meaning 
> of methods.



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

[jira] [Commented] (IGNITE-4234) .NET: Propagate missing CacheMetrics properties

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4234:


Github user asfgit closed the pull request at:

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


> .NET: Propagate missing CacheMetrics properties
> ---
>
> Key: IGNITE-4234
> URL: https://issues.apache.org/jira/browse/IGNITE-4234
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> CacheMetrics in Java has a lot more properties than ICacheMetrics in .NET



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

[jira] [Assigned] (IGNITE-3958) Client node should not start rest processor

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov reassigned IGNITE-3958:


Assignee: Nikolay Tikhonov

> Client node should not start rest processor
> ---
>
> Key: IGNITE-3958
> URL: https://issues.apache.org/jira/browse/IGNITE-3958
> Project: Ignite
>  Issue Type: Bug
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Tikhonov
> Fix For: 2.0
>
>




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

[jira] [Updated] (IGNITE-3862) GridServiceProxy invocation never times out

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-3862:

Fix Version/s: (was: 1.8)
   2.0

> GridServiceProxy invocation never times out
> ---
>
> Key: IGNITE-3862
> URL: https://issues.apache.org/jira/browse/IGNITE-3862
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 2.0
>
>
> {{GridServiceProxy}} uses compute for remote invocation. In some cases an 
> exception on server side can cause the closure execution never finish. For 
> example, this happens when the exception is thrown during the serialization 
> of the result.
> Need to add additional {{IgniteServices.serviceProxy(..)}} method that will 
> additionally allow to specify custom timeout.
> This timeout should limit the number of retries (there is an infinite loop 
> now) and also be passed to {{callAsyncNoFailover}} to avoid hangs.



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

[jira] [Updated] (IGNITE-3569) Set copyOnRead property to FALSE for marshaller cache

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3569:

Fix Version/s: (was: 2.0)
   1.8

> Set copyOnRead property to FALSE for marshaller cache
> -
>
> Key: IGNITE-3569
> URL: https://issues.apache.org/jira/browse/IGNITE-3569
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Yakov Zhdanov
>Assignee: Yakov Zhdanov
> Fix For: 1.8
>
>
> Ignite unmarshalls type metadata when accessing it which is an overhead. Need 
> to fix this for marshaller cache and, probably, for other internal caches 
> (this needs to be investigated).



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

[jira] [Commented] (IGNITE-4234) .NET: Propagate missing CacheMetrics properties

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4234:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-4234 .NET: Propagate missing CacheMetrics properties



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

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

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

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


commit 74cc4590a0443fc8b9db076df9221b966bf9d4e9
Author: Pavel Tupitsyn 
Date:   2016-11-16T13:12:28Z

IGNITE-4234 .NET: Propagate missing CacheMetrics properties - update 
interface

commit cc914c56f65d18679ba2756d550c17b7d8d58701
Author: Pavel Tupitsyn 
Date:   2016-11-16T13:21:50Z

Update class

commit 3f7b2797afc6b11fe27d26722f6169c49662383a
Author: Pavel Tupitsyn 
Date:   2016-11-16T13:27:19Z

wip

commit 976d000cc3595b8cce0bad2a45cbcbbf62daac2f
Author: Pavel Tupitsyn 
Date:   2016-11-16T13:27:34Z

wip

commit 94d831664a5c78c424afee0383da4d55961f30da
Author: Pavel Tupitsyn 
Date:   2016-11-16T13:56:34Z

Update writer

commit a1ef83c649237da4530b1a6b7cd4a0847b025496
Author: Pavel Tupitsyn 
Date:   2016-11-16T13:57:35Z

wip

commit d01c6ee10bf8b10c14826729f7e0b953c822c41b
Author: Pavel Tupitsyn 
Date:   2016-11-16T14:04:13Z

Update tests

commit 3fe906080b3d21cd2a8c8822b2f3d0d299cab0c6
Author: Pavel Tupitsyn 
Date:   2016-11-16T14:14:06Z

Add metrics test task

commit 9be706162c9c194a27027de493402393bb6df815
Author: Pavel Tupitsyn 
Date:   2016-11-16T14:16:32Z

Adding test

commit f578f775d95c469aa381a5fe8e423eb3a3144aab
Author: Pavel Tupitsyn 
Date:   2016-11-16T14:31:41Z

wip

commit 6b469620702a9deff481f07c0bce17d7667b48ca
Author: Pavel Tupitsyn 
Date:   2016-11-16T14:39:15Z

test done




> .NET: Propagate missing CacheMetrics properties
> ---
>
> Key: IGNITE-4234
> URL: https://issues.apache.org/jira/browse/IGNITE-4234
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 1.8
>
>
> CacheMetrics in Java has a lot more properties than ICacheMetrics in .NET



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

[jira] [Updated] (IGNITE-618) binary release should be buildable without git, but revision should stay

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-618:
---
Fix Version/s: (was: 1.8)
   2.0

> binary release should be buildable without git, but revision should stay
> 
>
> Key: IGNITE-618
> URL: https://issues.apache.org/jira/browse/IGNITE-618
> Project: Ignite
>  Issue Type: Task
>Reporter: Yakov Zhdanov
> Fix For: 2.0
>
>
> Probably, this may help - 
> http://git-scm.com/book/it/v2/Customizing-Git-Git-Attributes#Keyword-Expansion



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

[jira] [Updated] (IGNITE-3569) Set copyOnRead property to FALSE for marshaller cache

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3569:

Fix Version/s: (was: 1.8)
   2.0

> Set copyOnRead property to FALSE for marshaller cache
> -
>
> Key: IGNITE-3569
> URL: https://issues.apache.org/jira/browse/IGNITE-3569
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Yakov Zhdanov
>Assignee: Yakov Zhdanov
> Fix For: 2.0
>
>
> Ignite unmarshalls type metadata when accessing it which is an overhead. Need 
> to fix this for marshaller cache and, probably, for other internal caches 
> (this needs to be investigated).



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

[jira] [Updated] (IGNITE-3958) Client node should not start rest processor

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3958:

Fix Version/s: (was: 1.8)
   2.0

> Client node should not start rest processor
> ---
>
> Key: IGNITE-3958
> URL: https://issues.apache.org/jira/browse/IGNITE-3958
> Project: Ignite
>  Issue Type: Bug
>Reporter: Yakov Zhdanov
> Fix For: 2.0
>
>




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

[jira] [Updated] (IGNITE-2698) CacheKeyConfiguration is used only with BinaryMarshaller

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2698:

Fix Version/s: (was: 1.9)
   2.0

> CacheKeyConfiguration is used only with BinaryMarshaller
> 
>
> Key: IGNITE-2698
> URL: https://issues.apache.org/jira/browse/IGNITE-2698
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
> Fix For: 2.0
>
>
> Now if CacheKeyConfiguration is specified it is used only with 
> BinaryMarshaller. Need to take it into account with others marshallers as 
> well or update documentation.



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

[jira] [Updated] (IGNITE-4020) Move ODBC documentation to C++ Readme.io

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4020:

Fix Version/s: 1.8

> Move ODBC documentation to C++ Readme.io
> 
>
> Key: IGNITE-4020
> URL: https://issues.apache.org/jira/browse/IGNITE-4020
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Critical
> Fix For: 1.8
>
>
> Let's move ODBC Driver documentation [1] from main Apache Ignite Readme.io to 
> C++ Readme.io [2] doing the following in addition:
> 1) rename the section from ODBC Driver to ODBC.
> 2) add a page called ODBC Driver providing a basic overview on the 
> functionality and putting the table of content that will refer to all the 
> pages we have for ODBC at the moment.
> 3) create a page with the basic overview on the main Apache Ignite Readme.io 
> adding to Data Grid [3] grid section and placing below JDBC page in the menu. 
> The page must refer to 2). 
> [1] https://apacheignite.readme.io/docs/odbc-driver
> [2] https://apacheignite-cpp.readme.io 
> [3] https://apacheignite.readme.io/docs/data-grid



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

[jira] [Created] (IGNITE-4237) Implement interface to local Ignite instance over IPC

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4237:
---

 Summary: Implement interface to local Ignite instance over IPC
 Key: IGNITE-4237
 URL: https://issues.apache.org/jira/browse/IGNITE-4237
 Project: Ignite
  Issue Type: Task
  Components: general
Affects Versions: 1.8
Reporter: Vladimir Ozerov
 Fix For: 2.0


This way we can cover some important cases:
1) User has short-lived processes which require access to Ignite.
2) User do not want or cannot have JVM in the same process.

No failover is needed here at all.



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

[jira] [Commented] (IGNITE-3075) Implement single key-value pair DHT request/response for ATOMIC cache.

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov commented on IGNITE-3075:
---

Semen,

Thanks for your comments. 
* done
* I've added hasConflictData() method to GridNearAtomicAbstractUpdateRequest, 
so now I check request expiry, ctx.expiry and request conflict data in 
GridDhtAtomicSingleUpdateFuture.canUseSingleRequest.
* Expiry Policy suite now runs good, I'll check all other suites.

> Implement single key-value pair DHT request/response for ATOMIC cache.
> --
>
> Key: IGNITE-3075
> URL: https://issues.apache.org/jira/browse/IGNITE-3075
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
>  Labels: performance
> Fix For: 1.8
>
>
> Need to implement specialized light-weight version of DHT request/response to 
> make the most common case - single KV update - more performant.



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

[jira] [Updated] (IGNITE-2664) Cache.invokeAll() returns a map with BinaryObjects instead of user objects

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2664:

Assignee: (was: Artem Shutak)

> Cache.invokeAll() returns a map with BinaryObjects instead of user objects
> --
>
> Key: IGNITE-2664
> URL: https://issues.apache.org/jira/browse/IGNITE-2664
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Artem Shutak
> Fix For: 2.0
>
>
> {{Cache.invokeAll()}} return a map with {{BinaryObjectImpl}} instead of user 
> objects.
> Cache.invoke() works fine.
> I see a different behavior for Transactional and Atomic caches. But both of 
> them return {{BinaryObjectImpl}} instead of user objects at keys/values of a 
> result map.
> It can be reproduced with 
> CacheFullApiNewSelfTest.testInvokeAllOptimisticReadCommitted1() (and others). 
> Note: It does not work for plane object and serializable object, but it works 
> fine for EXTERNALIZABLE. 
> Or use the following code example
> {code}
> public static void main(String[] args) throws Exception {
> CacheConfiguration cc = new CacheConfiguration()
> .setMemoryMode(CacheMemoryMode.ONHEAP_TIERED)
> .setCacheMode(CacheMode.PARTITIONED)
> .setAtomicityMode(CacheAtomicityMode.ATOMIC)
> .setLoadPreviousValue(true)
> .setSwapEnabled(true)
> .setCacheStoreFactory(new 
> CacheAbstractNewSelfTest.TestStoreFactory())
> 
> .setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
> .setAtomicWriteOrderMode(CacheAtomicWriteOrderMode.PRIMARY)
> ;
> cc.setReadThrough(true);
> cc.setWriteThrough(true);
> try(Ignite ignite = Ignition.start(getConfiguration("1"));
> Ignite ignite2 = Ignition.start(getConfiguration("2"));
> Ignite ignite3 = Ignition.start(getConfiguration("3"));
> Ignite ignite4 = Ignition.start(getConfiguration("4"))) {
> System.out.println(ignite.configuration().getMarshaller());
> IgniteCache cache = ignite.getOrCreateCache(cc);
> // Await partition map exchange.
> Thread.sleep(10_000);
> CacheFullApiNewSelfTest.DataMode mode = 
> CacheFullApiNewSelfTest.DataMode.SERIALIZABLE;
> final TestObject key = key(1, mode);
> final TestObject val = value(1, mode);
> // InvokeAll
> cache.put(key, val);
> Map mapRes = 
> cache.invokeAll(F.asSet(key), CacheFullApiNewSelfTest.RMV_PROCESSOR);
> for (Map.Entry e : 
> mapRes.entrySet()) {
> TestObject eKey = e.getKey();
> System.out.println(eKey);
> if (!(eKey instanceof TestObject))
> throw new IllegalStateException("key=" + eKey + ", 
> class=" + eKey.getClass());
> TestObject eVal = e.getValue().get();
> if (!(eVal instanceof TestObject))
> throw new IllegalStateException("val=" + eVal + ", 
> class=" + eVal.getClass());
> }
> }
> }
> private static IgniteConfiguration getConfiguration(String s) {
> TcpDiscoverySpi spi = new TcpDiscoverySpi();
> TcpDiscoveryMulticastIpFinder finder = new 
> TcpDiscoveryMulticastIpFinder();
> finder.setAddresses(Collections.singleton("127.0.0.1:" + 
> TcpDiscoverySpi.DFLT_PORT));
> spi.setIpFinder(finder);
> return new IgniteConfiguration()
> .setPeerClassLoadingEnabled(true)
> .setSwapSpaceSpi(new GridTestSwapSpaceSpi())
> .setGridName(s)
> .setDiscoverySpi(spi)
> .setLocalHost("127.0.0.1")
> ;
> }
> {code}
> I've investigated the issue and found the root cause. Ignite does not unwrap 
> BinaryObject before get it to user. See {GridCacheReturn.finishUnmarshal()} 
> and org/apache/ignite/internal/processors/cache/GridCacheReturn.java:332. We 
> need to pass {{keepBinary}} flag at this place according to used cache.



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

[jira] [Updated] (IGNITE-2664) Cache.invokeAll() returns a map with BinaryObjects instead of user objects

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2664:

Fix Version/s: (was: 1.8)
   2.0

> Cache.invokeAll() returns a map with BinaryObjects instead of user objects
> --
>
> Key: IGNITE-2664
> URL: https://issues.apache.org/jira/browse/IGNITE-2664
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
>Reporter: Artem Shutak
> Fix For: 2.0
>
>
> {{Cache.invokeAll()}} return a map with {{BinaryObjectImpl}} instead of user 
> objects.
> Cache.invoke() works fine.
> I see a different behavior for Transactional and Atomic caches. But both of 
> them return {{BinaryObjectImpl}} instead of user objects at keys/values of a 
> result map.
> It can be reproduced with 
> CacheFullApiNewSelfTest.testInvokeAllOptimisticReadCommitted1() (and others). 
> Note: It does not work for plane object and serializable object, but it works 
> fine for EXTERNALIZABLE. 
> Or use the following code example
> {code}
> public static void main(String[] args) throws Exception {
> CacheConfiguration cc = new CacheConfiguration()
> .setMemoryMode(CacheMemoryMode.ONHEAP_TIERED)
> .setCacheMode(CacheMode.PARTITIONED)
> .setAtomicityMode(CacheAtomicityMode.ATOMIC)
> .setLoadPreviousValue(true)
> .setSwapEnabled(true)
> .setCacheStoreFactory(new 
> CacheAbstractNewSelfTest.TestStoreFactory())
> 
> .setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_SYNC)
> .setAtomicWriteOrderMode(CacheAtomicWriteOrderMode.PRIMARY)
> ;
> cc.setReadThrough(true);
> cc.setWriteThrough(true);
> try(Ignite ignite = Ignition.start(getConfiguration("1"));
> Ignite ignite2 = Ignition.start(getConfiguration("2"));
> Ignite ignite3 = Ignition.start(getConfiguration("3"));
> Ignite ignite4 = Ignition.start(getConfiguration("4"))) {
> System.out.println(ignite.configuration().getMarshaller());
> IgniteCache cache = ignite.getOrCreateCache(cc);
> // Await partition map exchange.
> Thread.sleep(10_000);
> CacheFullApiNewSelfTest.DataMode mode = 
> CacheFullApiNewSelfTest.DataMode.SERIALIZABLE;
> final TestObject key = key(1, mode);
> final TestObject val = value(1, mode);
> // InvokeAll
> cache.put(key, val);
> Map mapRes = 
> cache.invokeAll(F.asSet(key), CacheFullApiNewSelfTest.RMV_PROCESSOR);
> for (Map.Entry e : 
> mapRes.entrySet()) {
> TestObject eKey = e.getKey();
> System.out.println(eKey);
> if (!(eKey instanceof TestObject))
> throw new IllegalStateException("key=" + eKey + ", 
> class=" + eKey.getClass());
> TestObject eVal = e.getValue().get();
> if (!(eVal instanceof TestObject))
> throw new IllegalStateException("val=" + eVal + ", 
> class=" + eVal.getClass());
> }
> }
> }
> private static IgniteConfiguration getConfiguration(String s) {
> TcpDiscoverySpi spi = new TcpDiscoverySpi();
> TcpDiscoveryMulticastIpFinder finder = new 
> TcpDiscoveryMulticastIpFinder();
> finder.setAddresses(Collections.singleton("127.0.0.1:" + 
> TcpDiscoverySpi.DFLT_PORT));
> spi.setIpFinder(finder);
> return new IgniteConfiguration()
> .setPeerClassLoadingEnabled(true)
> .setSwapSpaceSpi(new GridTestSwapSpaceSpi())
> .setGridName(s)
> .setDiscoverySpi(spi)
> .setLocalHost("127.0.0.1")
> ;
> }
> {code}
> I've investigated the issue and found the root cause. Ignite does not unwrap 
> BinaryObject before get it to user. See {GridCacheReturn.finishUnmarshal()} 
> and org/apache/ignite/internal/processors/cache/GridCacheReturn.java:332. We 
> need to pass {{keepBinary}} flag at this place according to used cache.



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

[jira] [Updated] (IGNITE-2176) Not valid exceptions in case when example can't works with remote node started with server classpath (Java 8)

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2176:

Fix Version/s: (was: 1.8)
   2.0

> Not valid exceptions in case when example can't works with remote node 
> started with server classpath (Java 8)
> -
>
> Key: IGNITE-2176
> URL: https://issues.apache.org/jira/browse/IGNITE-2176
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.5.0.final
> Environment: jdk 1.7
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Assignee: Yakov Zhdanov
>Priority: Critical
> Fix For: 2.0
>
>
> Steps for reproduce:
> 1. Start one node from IDEA and one more from terminal
> 2. Run StreamVisitorExample (Java 8):
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class 
> org.apache.ignite.binary.BinaryInvalidTypeException: 
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
>   at 
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
>   at 
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1284)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readClass(BinaryReaderExImpl.java:339)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.readFixedType(BinaryFieldAccessor.java:835)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.readField(BinaryReaderExImpl.java:1646)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.read(BinaryFieldAccessor.java:645)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.read(BinaryClassDescriptor.java:696)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1450)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:267)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.processRequest(DataStreamProcessor.java:271)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor.access$000(DataStreamProcessor.java:49)
>   at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamProcessor$1.onMessage(DataStreamProcessor.java:76)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:819)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:103)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:782)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: 
> org.apache.ignite.examples.java8.streaming.StreamVisitorExample
>   at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>   at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>   at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>   at java.lang.Class.forName0(Native Method)
>   at java.lang.Class.forName(Class.java:348)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8172)
>   at 
> org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:458)
>   ... 22 more
> {noformat}
> 3. Run StreamTransformerExample (Java 8)
> Exception:
> {noformat}
> Exception in thread "pub-#2%null%" class 
> org.apache.ignite.binary.BinaryInvalidTypeException: 
> org.apache.ignite.examples.java8.streaming.StreamTransformerExample
>   at 
> org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:467)
>   at 
> org.apache.ignite.internal.binary.BinaryUtils.doReadClass(BinaryUtils.java:1330)
>   at 
> 

[jira] [Updated] (IGNITE-2107) Splitting TX example and adding new

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2107:

Fix Version/s: (was: 1.8)
   2.0

> Splitting TX example and adding new
> ---
>
> Key: IGNITE-2107
> URL: https://issues.apache.org/jira/browse/IGNITE-2107
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: ignite-1.4, 1.5.0.final
>Reporter: Yakov Zhdanov
>Assignee: Yakov Zhdanov
> Fix For: 2.0
>
>
> We need to introduce {{tx}} package and add examples demonstrating different 
> types of txs:
> # pessimistic repeatable read
> # optimistic repeatable read
> # optimistic serializable - we need to accent that this is deadlock free mode.



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

[jira] [Comment Edited] (IGNITE-4125) .NET: documentation and example for off-heap and swap tieres

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-4125 at 11/16/16 12:35 PM:
---

Blocked by IGNITE-4234 (offheap and swap metrics are missing) and IGNITE-4236 
(non-local metrics should be used)


was (Author: ptupitsyn):
Blocked by IGNITE-4234: Offheap and swap metrics are missing.

> .NET: documentation and example for off-heap and swap  tieres
> -
>
> Key: IGNITE-4125
> URL: https://issues.apache.org/jira/browse/IGNITE-4125
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Presently the documentation and example about the off-heap and swap tieres 
> are missing on .NET side. Let's fill this gap.
> Documentation can be taken from Java side 
> https://apacheignite.readme.io/docs/off-heap-memory
> The example that can be (should be) added to the distribution is the 
> following 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/MultiTieredCacheExample.cs



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

[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-4235:
---
Description: Can get user exception if was on remote node. Reproducer in 
attached file. For reproduce, run node1 first, second node 2, check logs. If 
remove  cluster group, for deploy service1, for node1, all will be okay, but if 
stay it, will be error, see attached log.  (was: Can get user exception if was 
on remote node. Reproducer in attached file . For reproduce, run node1 first, 
second node 2, check logs. If remove  cluster group, for deploy service1, for 
node1, all will be okay, but if stay it, will be error, see attached log.)

> Can't get user exception if was on remote service
> -
>
> Key: IGNITE-4235
> URL: https://issues.apache.org/jira/browse/IGNITE-4235
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Dmitriy Govorukhin
> Fix For: 2.0
>
> Attachments: Reproducer.java, node1.log, node2.log
>
>
> Can get user exception if was on remote node. Reproducer in attached file. 
> For reproduce, run node1 first, second node 2, check logs. If remove  cluster 
> group, for deploy service1, for node1, all will be okay, but if stay it, will 
> be error, see attached log.



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

[jira] [Created] (IGNITE-4236) .NET: ICache.LocalMetrics and overloads

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4236:
--

 Summary: .NET: ICache.LocalMetrics and overloads
 Key: IGNITE-4236
 URL: https://issues.apache.org/jira/browse/IGNITE-4236
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
 Fix For: 1.8


Ignite in Java has three cache metrics methods:
{code}
CacheMetrics metrics();
CacheMetrics metrics(ClusterGroup grp);
CacheMetrics localMetrics();
{code}

Ignite.NET should provide these too. See how IGNITE-1071 changed the meaning of 
methods.



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

[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-4235:
---
Description: Can get user exception if was on remote node. Reproducer in 
attached file . For reproduce, run node1 first, second node 2, check logs. If 
remove  cluster group, for deploy service1, for node1, all will be okay, but if 
stay it, will be error, see attached log.  (was: Can get user exception if was 
on remote node. Reproducer in attached file . For reproduce, run node1 first, 
second node 2, check logs. If remove  cluster group, for node1, all will be 
okay, but if stay it, will be error, see attached log.)

> Can't get user exception if was on remote service
> -
>
> Key: IGNITE-4235
> URL: https://issues.apache.org/jira/browse/IGNITE-4235
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Dmitriy Govorukhin
> Fix For: 2.0
>
> Attachments: Reproducer.java, node1.log, node2.log
>
>
> Can get user exception if was on remote node. Reproducer in attached file . 
> For reproduce, run node1 first, second node 2, check logs. If remove  cluster 
> group, for deploy service1, for node1, all will be okay, but if stay it, will 
> be error, see attached log.



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

[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-4235:
---
Attachment: node2.log
node1.log

> Can't get user exception if was on remote service
> -
>
> Key: IGNITE-4235
> URL: https://issues.apache.org/jira/browse/IGNITE-4235
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Dmitriy Govorukhin
> Fix For: 2.0
>
> Attachments: Reproducer.java, node1.log, node2.log
>
>
> Can get user exception if was on remote node. Reproducer in attached file . 
> For reproduce, run node1 first, second node 2, check logs. If remove  cluster 
> group, for node1, all will be okay, but if stay it, will be error, see 
> attached log.



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

[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-4235:
---
Description: Can get user exception if was on remote node. Reproducer in 
attached file . For reproduce, run node1 first, second node 2, check logs. If 
remove  cluster group, for node1, all will be okay, but if stay it, will be 
error, see attached log.  (was: Can get user exception if was on remote node. 
Reproducer in attached file .)

> Can't get user exception if was on remote service
> -
>
> Key: IGNITE-4235
> URL: https://issues.apache.org/jira/browse/IGNITE-4235
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Dmitriy Govorukhin
> Fix For: 2.0
>
> Attachments: Reproducer.java
>
>
> Can get user exception if was on remote node. Reproducer in attached file . 
> For reproduce, run node1 first, second node 2, check logs. If remove  cluster 
> group, for node1, all will be okay, but if stay it, will be error, see 
> attached log.



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

[jira] [Updated] (IGNITE-4235) Can't get user exception if was on remote service

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-4235:
---
Attachment: Reproducer.java

> Can't get user exception if was on remote service
> -
>
> Key: IGNITE-4235
> URL: https://issues.apache.org/jira/browse/IGNITE-4235
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.7
>Reporter: Dmitriy Govorukhin
> Fix For: 2.0
>
> Attachments: Reproducer.java
>
>
> Can get user exception if was on remote node. Reproducer in attached file .



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

[jira] [Created] (IGNITE-4235) Can't get user exception if was on remote service

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-4235:
--

 Summary: Can't get user exception if was on remote service
 Key: IGNITE-4235
 URL: https://issues.apache.org/jira/browse/IGNITE-4235
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.7
Reporter: Dmitriy Govorukhin
 Fix For: 2.0


Can get user exception if was on remote node. Reproducer in attached file .



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

[jira] [Updated] (IGNITE-3454) Used Thread.getContextClassLoader() classloader for P2P

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov updated IGNITE-3454:
-
Fix Version/s: (was: 1.8)
   2.0

> Used Thread.getContextClassLoader() classloader for P2P
> ---
>
> Key: IGNITE-3454
> URL: https://issues.apache.org/jira/browse/IGNITE-3454
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Nikolay Tikhonov
> Fix For: 2.0
>
> Attachments: DeployTest.patch, DeployTest_new.patch
>
>
> {{GridClassLoaderCache#detectClassLoader}} tries to load class by 
> {{Thread.getContextClassLoader()}} when it possible. In some cases it to lead 
> to errors in cache operations:
> {noformat}
> Suppressed: class org.apache.ignite.IgniteCheckedException: Encountered 
> incompatible class loaders for cache [class1=[C, 
> class2=org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap]
> at 
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.registerClass(GridCacheDeploymentManager.java:666)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.registerClass(GridCacheDeploymentManager.java:611)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMessage.prepareObject(GridCacheMessage.java:214)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMessage.marshalInvokeArguments(GridCacheMessage.java:430)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateRequest.prepareMarshal(GridNearAtomicUpdateRequest.java:607)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onSend(GridCacheIoManager.java:620)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:642)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.send(GridCacheIoManager.java:803)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridNearAtomicUpdateFuture.mapSingle(GridNearAtomicUpdateFuture.java:469)
> ... 44 more
> {noformat}
> Test which reproduced the issue in attachment and see on 
> {{GridCacheDeploymentManager#registerClass(java.lang.Class, 
> java.lang.ClassLoader)}}.



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

[jira] [Updated] (IGNITE-3614) Failed test: CacheContinuousQueryFailoverTxReplicatedSelfTest.testUpdatePartitionCounter

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov updated IGNITE-3614:
-
Fix Version/s: (was: 1.8)
   2.0

> Failed test: 
> CacheContinuousQueryFailoverTxReplicatedSelfTest.testUpdatePartitionCounter
> 
>
> Key: IGNITE-3614
> URL: https://issues.apache.org/jira/browse/IGNITE-3614
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Tikhonov
> Fix For: 2.0
>
>
> Test periodically fail with the following stack trace:
> {code}
> java.lang.Exception: Failed to find a server node.
> at 
> org.apache.ignite.internal.processors.cache.query.continuous.CacheContinuousQueryFailoverAbstractSelfTest.testUpdatePartitionCounter(CacheContinuousQueryFailoverAbstractSelfTest.java:390)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1760)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:118)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$4.run(GridAbstractTest.java:1698)
> at java.lang.Thread.run(Thread.java:745)
> {code}
> Apparently, this is a bug in the test - somehow it cannot return cache 
> reliably.



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

[jira] [Updated] (IGNITE-2699) Starvation when CacheEntryListenerConfiguration.isSynchronous is true

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov updated IGNITE-2699:
-
Fix Version/s: (was: 1.8)
   2.0

> Starvation when CacheEntryListenerConfiguration.isSynchronous is true
> -
>
> Key: IGNITE-2699
> URL: https://issues.apache.org/jira/browse/IGNITE-2699
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Nikolay Tikhonov
> Fix For: 2.0
>
>
> When event notifications in {{CacheEntryListener}} configured as synchronous 
> possible situation that all thread in {{SYSTEM}} pool will be stuck on 
> waiting ack messages. It is necessary to make the processing of acknowledge 
> messages in another thread pool.



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

[jira] [Updated] (IGNITE-3653) P2P doesn't work for remote filter and filter factory.

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov updated IGNITE-3653:
-
Fix Version/s: (was: 1.8)
   2.0

> P2P doesn't work for remote filter and filter factory.
> --
>
> Key: IGNITE-3653
> URL: https://issues.apache.org/jira/browse/IGNITE-3653
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
>Reporter: Nikolay Tikhonov
> Fix For: 2.0
>
> Attachments: CCP2PTest.patch
>
>
> Remote filter and filter factory classes were not deployed on nodes which 
> join to cluster after their initialization. Test attached.



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

[jira] [Updated] (IGNITE-887) Fix ContinuousQueries to support initial state as well as in-focus and out-of-focus events

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-887:
---
Assignee: (was: Andrey Kornev)

> Fix ContinuousQueries to support initial state as well as in-focus and 
> out-of-focus events
> --
>
> Key: IGNITE-887
> URL: https://issues.apache.org/jira/browse/IGNITE-887
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Dmitriy Setrakyan
> Fix For: 2.0
>
>
> The discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Continuous-Query-td136.html



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

[jira] [Updated] (IGNITE-887) Fix ContinuousQueries to support initial state as well as in-focus and out-of-focus events

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-887:
---
Fix Version/s: (was: 1.8)
   2.0

> Fix ContinuousQueries to support initial state as well as in-focus and 
> out-of-focus events
> --
>
> Key: IGNITE-887
> URL: https://issues.apache.org/jira/browse/IGNITE-887
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Dmitriy Setrakyan
> Fix For: 2.0
>
>
> The discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Continuous-Query-td136.html



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

[jira] [Updated] (IGNITE-435) Visor should use smart format for time values

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-435:
---
Fix Version/s: (was: 1.8)
   2.0

> Visor should use smart format for time values
> -
>
> Key: IGNITE-435
> URL: https://issues.apache.org/jira/browse/IGNITE-435
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: sprint-2
>Reporter: Pavel Konstantinov
>Assignee: YoungGyu Chun
>Priority: Minor
>  Labels: visor
> Fix For: 2.0
>
>
> {code}
>  Maximum job execute time| 60009ms  - should show 1m
>  Curent job execute time | 120ms
>  Average job execute time| 1126.57ms - should show 1s
>  Total busy time | 70769ms - should show 1m 10s
> {code}
> Also please fix the typo 'Curent' - should be 'Current'



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

[jira] [Updated] (IGNITE-1185) Locate configuration in class path

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1185:

Fix Version/s: (was: 1.8)
   2.0

> Locate configuration in class path
> --
>
> Key: IGNITE-1185
> URL: https://issues.apache.org/jira/browse/IGNITE-1185
> Project: Ignite
>  Issue Type: Improvement
>  Components: newbie
>Reporter: Yakov Zhdanov
>  Labels: newbie
> Fix For: 2.0
>
> Attachments: master_ignite-1185_3.patch
>
>
> Need ability to locate configuration in classpath, so nodes can be started 
> like this:
> {{ignite.sh classpath:config/mycfg.xml}}



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

[jira] [Updated] (IGNITE-1185) Locate configuration in class path

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-1185:

Assignee: (was: Artem Shutak)

> Locate configuration in class path
> --
>
> Key: IGNITE-1185
> URL: https://issues.apache.org/jira/browse/IGNITE-1185
> Project: Ignite
>  Issue Type: Improvement
>  Components: newbie
>Reporter: Yakov Zhdanov
>  Labels: newbie
> Fix For: 2.0
>
> Attachments: master_ignite-1185_3.patch
>
>
> Need ability to locate configuration in classpath, so nodes can be started 
> like this:
> {{ignite.sh classpath:config/mycfg.xml}}



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

[jira] [Assigned] (IGNITE-3862) GridServiceProxy invocation never times out

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev reassigned IGNITE-3862:
---

Assignee: Dmitry Karachentsev  (was: Semen Boikov)

> GridServiceProxy invocation never times out
> ---
>
> Key: IGNITE-3862
> URL: https://issues.apache.org/jira/browse/IGNITE-3862
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
>Priority: Critical
> Fix For: 1.8
>
>
> {{GridServiceProxy}} uses compute for remote invocation. In some cases an 
> exception on server side can cause the closure execution never finish. For 
> example, this happens when the exception is thrown during the serialization 
> of the result.
> Need to add additional {{IgniteServices.serviceProxy(..)}} method that will 
> additionally allow to specify custom timeout.
> This timeout should limit the number of retries (there is an infinite loop 
> now) and also be passed to {{callAsyncNoFailover}} to avoid hangs.



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

[jira] [Updated] (IGNITE-2110) Replace workarond for local node flag in TcpDiscoveryNode with better solution

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2110:

Fix Version/s: (was: 1.8)
   2.0

> Replace workarond for local node flag in TcpDiscoveryNode with better solution
> --
>
> Key: IGNITE-2110
> URL: https://issues.apache.org/jira/browse/IGNITE-2110
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ershov
>Assignee: Artem Shutak
>Priority: Minor
> Fix For: 2.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> We should get read of this workaround in
> GridDhtAffinityAssignmentResponse#finishUnmarshal
> {code:java}
> // TODO IGNITE-10: setting 'local' for nodes not needed when 
> IGNITE-10 is implemented.
> int assignments = affAssignment.size();
> for (int n = 0; n < assignments; n++) {
> List nodes = affAssignment.get(n);
> int size = nodes.size();
> for (int i = 0; i < size; i++) {
> ClusterNode node = nodes.get(i);
> if (node instanceof TcpDiscoveryNode)
> 
> ((TcpDiscoveryNode)node).local(node.id().equals(ctx.localNodeId()));
> }
> }
> {code}
> by designing new solution for TcpDiscoveryNode.local transient flag



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

[jira] [Updated] (IGNITE-2110) Replace workarond for local node flag in TcpDiscoveryNode with better solution

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-2110:

Assignee: (was: Artem Shutak)

> Replace workarond for local node flag in TcpDiscoveryNode with better solution
> --
>
> Key: IGNITE-2110
> URL: https://issues.apache.org/jira/browse/IGNITE-2110
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: ignite-1.4
>Reporter: Vladimir Ershov
>Priority: Minor
> Fix For: 2.0
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> We should get read of this workaround in
> GridDhtAffinityAssignmentResponse#finishUnmarshal
> {code:java}
> // TODO IGNITE-10: setting 'local' for nodes not needed when 
> IGNITE-10 is implemented.
> int assignments = affAssignment.size();
> for (int n = 0; n < assignments; n++) {
> List nodes = affAssignment.get(n);
> int size = nodes.size();
> for (int i = 0; i < size; i++) {
> ClusterNode node = nodes.get(i);
> if (node instanceof TcpDiscoveryNode)
> 
> ((TcpDiscoveryNode)node).local(node.id().equals(ctx.localNodeId()));
> }
> }
> {code}
> by designing new solution for TcpDiscoveryNode.local transient flag



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

[jira] [Commented] (IGNITE-4125) .NET: documentation and example for off-heap and swap tieres

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4125:


Blocked by IGNITE-4234: Offheap and swap metrics are missing.

> .NET: documentation and example for off-heap and swap  tieres
> -
>
> Key: IGNITE-4125
> URL: https://issues.apache.org/jira/browse/IGNITE-4125
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Presently the documentation and example about the off-heap and swap tieres 
> are missing on .NET side. Let's fill this gap.
> Documentation can be taken from Java side 
> https://apacheignite.readme.io/docs/off-heap-memory
> The example that can be (should be) added to the distribution is the 
> following 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/MultiTieredCacheExample.cs



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

[jira] [Issue Comment Deleted] (IGNITE-4125) .NET: documentation and example for off-heap and swap tieres

[Pavel Tupitsyn (JIRA)]

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

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

(was: Blocked by IGNITE-4234: Offheap and swap metrics are missing.)

> .NET: documentation and example for off-heap and swap  tieres
> -
>
> Key: IGNITE-4125
> URL: https://issues.apache.org/jira/browse/IGNITE-4125
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Presently the documentation and example about the off-heap and swap tieres 
> are missing on .NET side. Let's fill this gap.
> Documentation can be taken from Java side 
> https://apacheignite.readme.io/docs/off-heap-memory
> The example that can be (should be) added to the distribution is the 
> following 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/MultiTieredCacheExample.cs



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

[jira] [Commented] (IGNITE-4125) .NET: documentation and example for off-heap and swap tieres

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4125:


Blocked by IGNITE-4234: Offheap and swap metrics are missing.

> .NET: documentation and example for off-heap and swap  tieres
> -
>
> Key: IGNITE-4125
> URL: https://issues.apache.org/jira/browse/IGNITE-4125
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Presently the documentation and example about the off-heap and swap tieres 
> are missing on .NET side. Let's fill this gap.
> Documentation can be taken from Java side 
> https://apacheignite.readme.io/docs/off-heap-memory
> The example that can be (should be) added to the distribution is the 
> following 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/MultiTieredCacheExample.cs



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

[jira] [Created] (IGNITE-4234) .NET: Propagate missing CacheMetrics properties

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4234:
--

 Summary: .NET: Propagate missing CacheMetrics properties
 Key: IGNITE-4234
 URL: https://issues.apache.org/jira/browse/IGNITE-4234
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 1.8


CacheMetrics in Java has a lot more properties than ICacheMetrics in .NET



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

[jira] [Comment Edited] (IGNITE-4125) .NET: documentation and example for off-heap and swap tieres

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-4125 at 11/16/16 11:38 AM:
---

I'm ok with adding swap space code there, but we will have to restrict this 
example to local node only, since it is difficult to configure swap space base 
dir for standalone nodes.


was (Author: ptupitsyn):
I'm ok with adding swap space code there, but it's not clear to me how to deal 
with multi-node scenario for this example. How do we specify the base directory 
for swap? Should we restrict the example to one node?

> .NET: documentation and example for off-heap and swap  tieres
> -
>
> Key: IGNITE-4125
> URL: https://issues.apache.org/jira/browse/IGNITE-4125
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Pavel Tupitsyn
> Fix For: 1.8
>
>
> Presently the documentation and example about the off-heap and swap tieres 
> are missing on .NET side. Let's fill this gap.
> Documentation can be taken from Java side 
> https://apacheignite.readme.io/docs/off-heap-memory
> The example that can be (should be) added to the distribution is the 
> following 
> https://github.com/gridgain/apache-ignite/blob/ignite-net-advanced-examples/modules/platforms/dotnet/examples/Apache.Ignite.Examples/Advanced/MultiTieredCacheExample.cs



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

[jira] [Created] (IGNITE-4233) Add documentation for REDIS support

[Andrey Novikov (JIRA)]

Andrey Novikov created IGNITE-4233:
--

 Summary: Add documentation for REDIS support
 Key: IGNITE-4233
 URL: https://issues.apache.org/jira/browse/IGNITE-4233
 Project: Ignite
  Issue Type: Sub-task
Affects Versions: 1.8
Reporter: Andrey Novikov
 Fix For: 1.8






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

[jira] [Assigned] (IGNITE-4163) Wrong SQL generated by org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery

[Andrey Novikov (JIRA)]

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

Andrey Novikov reassigned IGNITE-4163:
--

Assignee: Andrey Novikov  (was: Alexey Kuznetsov)

> Wrong SQL generated by 
> org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery
> 
>
> Key: IGNITE-4163
> URL: https://issues.apache.org/jira/browse/IGNITE-4163
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.7
>Reporter: Anghel Botos
>Assignee: Andrey Novikov
> Attachments: IGNITE_4163_Fixed_load_range_queries_Review.patch, 
> IGNITE_4163_Fixed_load_range_queries_for_MS_SQL_Server_.patch, 
> IGNITE_4163_Fixed_load_range_queries_for_different_databases.patch, 
> IGNITE_4163_Index_column_in_upper_case.patch, 
> IGNITE_4163_Oracle_specific_for_load_range_query_.patch, test4163-project.zip
>
>
> The SQL statement generated by 
> org.apache.ignite.cache.store.jdbc.dialect.BasicJdbcDialect#loadCacheSelectRangeQuery
>  looks like this:
> {{SELECT KEY_COLUMN_1,KEY_COLUMN_2 FROM (SELECT KEY_COLUMN_1,KEY_COLUMN_2, 
> ROWNUM() AS rn FROM SOME_TABLE ORDER BY KEY_COLUMN_1,KEY_COLUMN_2) WHERE 
> mod(rn, ?) = 0}}
> For Oracle this is incorrect, as Oracle does not have a {{ROWNUM()}} 
> function. For the above query the following error is thrown: {{ORA-00923: 
> FROM keyword not found where expected}}
> Regarding row numbering Oracle has:
> * a {{ROWNUM}} pseudocolumn, in which case the query should have {{ROWNUM AS 
> rn}}
> * a {{ROW_NUMBER()}} function, in which case the query would become more 
> complicated. See 
> https://docs.oracle.com/database/121/SQLRF/functions170.htm#SQLRF06100 for 
> more details about {{ROW_NUMBER()}}
> Please make the neccessary adjustments to either {{BasicJdbcDialect}} or 
> {{OracleDialect}} so that a correct query is produced.



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

[jira] [Comment Edited] (IGNITE-4137) .NET: add example for Atomic Types

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-4137 at 11/16/16 11:05 AM:
---

Denis, I don't see any comments in GitHub. Can you post them here in JIRA?

Upsource is in evaluation mode until we make a decision, we have reached 
account limit in there.

I've added AtomicSequenceReserveSize with explanation.


was (Author: ptupitsyn):
Denis, I don't see any comments in GitHub. Can you post them here in JIRA?

Upsource is in evaluation mode until we make a decision, we have reached 
account limit in there.

> .NET: add example for Atomic Types
> --
>
> Key: IGNITE-4137
> URL: https://issues.apache.org/jira/browse/IGNITE-4137
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 1.8
>
>
> Add the example that will showcase the usage of all Atomic Types that are 
> presently supported in .NET.



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

[jira] [Commented] (IGNITE-3066) Set of Redis commands that can be easily implemented via existing REST commands

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3066:


Github user asfgit closed the pull request at:

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


> Set of Redis commands that can be easily implemented via existing REST 
> commands
> ---
>
> Key: IGNITE-3066
> URL: https://issues.apache.org/jira/browse/IGNITE-3066
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>
> As the 1st iteration of IGNITE-2788 the following commands can be implemented 
> via existing REST commands,
> GET
> MGET
> SET
> MSET
> INCR
> DECR
> INCRBY
> DECRBY
> APPEND
> STRLEN
> GETSET
> SETRANGE
> GETRANGE
> DEL
> EXISTS
> DBSIZE
> http://redis.io/commands



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

[jira] [Commented] (IGNITE-4184) Document how ODBC drivers works with the cluster

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-4184:
-

Denis,

I'm not quite sure what can I write additionally on how ODBC connection works 
on C++ side except for it working over TCP and configured with connection 
string. I've added sentence at the end of the section with reference to the 
Connection String page [1].

Please, take a look and let me know if you have some suggestions on how can I 
improve it.

[1] - http://apacheignite.readme.io/docs/connecting-string

> Document how ODBC drivers works with the cluster
> 
>
> Key: IGNITE-4184
> URL: https://issues.apache.org/jira/browse/IGNITE-4184
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Igor Sapego
> Fix For: 2.0
>
>
> There are no any details on how ODBC driver connects to the cluster and sends 
> queries to it for the execution. 
> Let's make our documentation more technical by adding the following blocks to 
> this page [1]:
> - ODBC Driver necessity and usage on Java side
> - ODBC Configuration parameter
> - Details on how ODBC connection works on C++ side and how you can alter 
> specific parameters using Configuration object
> [1] https://apacheignite.readme.io/docs/odbc-driver



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

[jira] [Updated] (IGNITE-1618) [Test failed] TransactionHeuristicException: Failed to locally write to cache

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-1618:

Fix Version/s: (was: 1.8)
   2.0

> [Test failed] TransactionHeuristicException: Failed to locally write to cache
> -
>
> Key: IGNITE-1618
> URL: https://issues.apache.org/jira/browse/IGNITE-1618
> Project: Ignite
>  Issue Type: Test
>Affects Versions: ignite-1.4
>Reporter: Andrey Gura
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
> Attachments: test_deployment.log
>
>
> The following test fail:
>   * {{GridCacheDeploymentOffHeapSelfTest.testDeployment}}
>   * {{GridCacheDeploymentOffHeapSelfTest.testDeployment6}}
>   * {{GridCacheDeploymentOffHeapSelfTest.testDeployment7}}
> The stack trace:
> {noformat}
> org.apache.ignite.IgniteException: class 
> org.apache.ignite.transactions.TransactionHeuristicException: Failed to 
> locally write to cache (all transaction entries will be invalidated, however 
> there was a window when entries for this transaction were visible to others): 
> GridDhtTxLocal [nearNodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
> nearFutId=c5e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearMiniId=d5e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearFinFutId=46e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearFinMiniId=b6e88ca3051-87e59273-3dfd-4d87-a40c-dfe902c4bbc9, 
> nearXidVer=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
> globalTime=1444061036097, order=1444061035918], super=GridDhtTxLocalAdapter 
> [dhtThreadId=33042, needsCompletedVers=true, nearOnOriginatingNode=true, 
> nearNodes=[], dhtNodes=[100ca1fe-f561-4ddd-b6d9-88d7cf12e001], 
> explicitLock=false, super=IgniteTxLocalAdapter [txMap={IgniteTxKey 
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], cacheId=1]=IgniteTxEntry 
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], cacheId=1, 
> txKey=IgniteTxKey [key=KeyCacheObjectImpl [val=13, hasValBytes=true], 
> cacheId=1], val=[op=CREATE, val=UserCacheObjectImpl 
> [val=org.apache.ignite.tests.p2p.CacheDeploymentTestValue@6c8704b3, 
> hasValBytes=true]], prevVal=[op=NOOP, val=null], entryProcessorsCol=null, 
> entryProcessorCalcVal=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=[], filtersPassed=false, 
> filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], 
> locPart=GridDhtLocalPartition [id=546, mapPubSize=1, 
> rmvQueue=GridCircularBuffer [sizeMask=127, idxGen=0], state=OWNING, 
> reservations=0, empty=false, createTime=10/05/2015 16:03:56, mapPubSize=1], 
> super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=KeyCacheObjectImpl [val=13, hasValBytes=true], val=null, 
> startVer=1444061035921, ver=GridCacheVersion [topVer=55541037, 
> nodeOrderDrId=2, globalTime=1444061036098, order=1444061035921], 
> hash=462848615, extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
> [locs=[GridCacheMvccCandidate [nodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
> ver=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
> globalTime=1444061036098, order=1444061035920], timeout=0, ts=1444061036094, 
> threadId=33042, id=2544576, topVer=AffinityTopologyVersion [topVer=2, 
> minorTopVer=0], reentry=null, 
> otherNodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, otherVer=GridCacheVersion 
> [topVer=55541037, nodeOrderDrId=2, globalTime=1444061036097, 
> order=1444061035918], mappedDhtNodes=null, mappedNearNodes=null, 
> ownerVer=null, key=KeyCacheObjectImpl [val=13, hasValBytes=true], 
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=1|dht_local=1|near_local=0|removed=0,
>  prevVer=null, nextVer=null]], rmts=null]], flags=0]]], prepared=true, 
> locked=false, nodeId=null, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, xidVer=null]}, completedBase=null, 
> sndTransformedVals=false, super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=55541037, nodeOrderDrId=2, globalTime=1444061036098, 
> order=1444061035920], writeVer=GridCacheVersion [topVer=55541037, 
> nodeOrderDrId=2, globalTime=1444061036098, order=1444061035922], 
> implicit=true, implicitSingle=true, loc=true, threadId=33042, 
> startTime=1444061036094, nodeId=203fa7b5-ee81-4cf2-8671-d61284b4d002, 
> startVer=GridCacheVersion [topVer=55541037, nodeOrderDrId=2, 
> globalTime=1444061036098, order=1444061035920], endVer=null, 
> isolation=READ_COMMITTED, concurrency=OPTIMISTIC, timeout=0, 
> sysInvalidate=false, sys=false, plc=2, commitVer=null, 
> finalizing=USER_FINISH, preparing=false, invalidParts={}, state=COMMITTING, 
> timedOut=false, topVer=AffinityTopologyVersion [topVer=2, minorTopVer=0], 
> duration=10ms, onePhaseCommit=true], size=1]]]
> at 
> 

[jira] [Updated] (IGNITE-4184) Document how ODBC drivers works with the cluster

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4184:

Assignee: Denis Magda  (was: Igor Sapego)

> Document how ODBC drivers works with the cluster
> 
>
> Key: IGNITE-4184
> URL: https://issues.apache.org/jira/browse/IGNITE-4184
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Denis Magda
> Fix For: 2.0
>
>
> There are no any details on how ODBC driver connects to the cluster and sends 
> queries to it for the execution. 
> Let's make our documentation more technical by adding the following blocks to 
> this page [1]:
> - ODBC Driver necessity and usage on Java side
> - ODBC Configuration parameter
> - Details on how ODBC connection works on C++ side and how you can alter 
> specific parameters using Configuration object
> [1] https://apacheignite.readme.io/docs/odbc-driver



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

[jira] [Updated] (IGNITE-1624) [Test failed] Ignite SPI: TcpClientDiscoverySpiSelfTest.testJoinError failed

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-1624:

Fix Version/s: (was: 1.8)
   2.0

> [Test failed] Ignite SPI:  TcpClientDiscoverySpiSelfTest.testJoinError failed
> -
>
> Key: IGNITE-1624
> URL: https://issues.apache.org/jira/browse/IGNITE-1624
> Project: Ignite
>  Issue Type: Test
>Reporter: Andrey Gura
>Priority: Critical
>  Labels: Muted_test
> Fix For: 2.0
>
>
> The following test periodically fail on TC:
>  * {{TcpClientDiscoverySpiSelfTest.testJoinError}}
>  * {{TcpClientDiscoverySpiFailureTimeoutSelfTest.testJoinError}}
> {noformat}
> [18:07:52,332][ERROR][test-runner][IgniteKernal%client-0] Got exception while 
> starting (will rollback startup routine).
> class org.apache.ignite.IgniteCheckedException: Failed to start manager: 
> GridManagerAdapter [enabled=true, 
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at 
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1488)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:908)
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1617)
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1484)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:965)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:526)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:724)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:708)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.startClientNodes(TcpClientDiscoverySpiSelfTest.java:1850)
> at 
> org.apache.ignite.spi.discovery.tcp.TcpClientDiscoverySpiSelfTest.testJoinError(TcpClientDiscoverySpiSelfTest.java:1085)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1665)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:111)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest$6.run(GridAbstractTest.java:1603)
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start 
> SPI: TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000, 
> reconCnt=10, maxAckTimeout=60, forceSrvMode=false, 
> clientReconnectDisabled=false]
> at 
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:255)
> at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:666)
> at 
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1485)
> ... 17 more
> Caused by: class org.apache.ignite.spi.IgniteSpiException: Join process timed 
> out, did not receive response for join request (consider increasing 
> 'joinTimeout' configuration property) [joinTimeout=8000, 
> sock=Socket[addr=/127.0.0.1,port=47500,localport=43551]]
> at 
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1324)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [18:07:52,357][ERROR][main][root] Test failed.
> class org.apache.ignite.IgniteCheckedException: Failed to start manager: 
> GridManagerAdapter [enabled=true, 
> name=org.apache.ignite.internal.managers.discovery.GridDiscoveryManager]
> at 
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1488)
> at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:908)
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1617)
> at 
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1484)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:965)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:526)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:724)
> at 
> org.apache.ignite.testframework.junits.GridAbstractTest.startGrid(GridAbstractTest.java:708)
> at 
> 

[jira] [Assigned] (IGNITE-2646) IgniteCompute.withAsync can execute tasks synchronously

[Andrey Gura (JIRA)]

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

Andrey Gura reassigned IGNITE-2646:
---

Assignee: (was: Andrey Gura)

> IgniteCompute.withAsync can execute tasks synchronously
> ---
>
> Key: IGNITE-2646
> URL: https://issues.apache.org/jira/browse/IGNITE-2646
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 1.5.0.final
>Reporter: Andrey Gura
>
> {{GridTaskWorker}} can invoke {{reduce}} method in caller thread.
> If task isn't annotated by {{@ComputeTaskMapAsync}} then job mapping will be 
> run in caller thread. Since job mapping will be finished 
> {{processDelayedResponses}} method will be invoked and if delayed responses 
> queue isn't empty then caller thread can invoke {{reduce}} method eventually 
> and perform reducing synchronously.
> It can be usefull in case of synchronous execution but it is strange behavior 
> for asynchronous case because user expects that method will return after 
> creation of task.
> Similar behavior is possible for all places where code invokes 
> {{GridTaskProcessor.execute()}} method ({{IgniteCompute.broadcast()}}, 
> {{IgniteCache.size()}}, REST handlers, etc.)
> Related discussion on dev-list: [IgniteCompute.withAsync can execute tasks 
> synchronously|http://apache-ignite-developers.2346864.n4.nabble.com/IgniteCompute-withAsync-can-execute-tasks-synchronously-td7262.html]



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

[jira] [Updated] (IGNITE-4165) ignite-spark module scaladocs isn't included in Scala API docs

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-4165:

Fix Version/s: 1.8

> ignite-spark module scaladocs isn't included in Scala API docs
> --
>
> Key: IGNITE-4165
> URL: https://issues.apache.org/jira/browse/IGNITE-4165
> Project: Ignite
>  Issue Type: Bug
>Reporter: Andrey Gura
> Fix For: 1.8
>
>
> Ignie Scala API docs contains only Scalar scaladoc but not ignite-spark 
> scaladoc.



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

[jira] [Updated] (IGNITE-1021) There isn't $IGNITE_HOME/docs/javadoc/resources directory

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov updated IGNITE-1021:
-
Fix Version/s: (was: 1.8)
   1.9

> There isn't  $IGNITE_HOME/docs/javadoc/resources directory
> --
>
> Key: IGNITE-1021
> URL: https://issues.apache.org/jira/browse/IGNITE-1021
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: sprint-6
> Environment: jdk1.7.0_71
> OS X 10.10.2
>Reporter: Ilya Suntsov
>Priority: Minor
> Fix For: 1.9
>
> Attachments: LinkCheckerResults.html
>
>
> Steps for reproduce:
> 1. Build ignite from sources: 
> {noformat} mvn clean package -DskipTests -Prelease,lgpl -Dscala-2.10
> {noformat}
> 2. Check links in 
> {noformat}$IGNITE_HOME/docs/javadoc{noformat}
>  (result file in attachment). 
> LinkChecker doesn't find
>  {noformat}$IGNITE_HOME/docs/javadoc/resources directory{noformat}



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

[jira] [Resolved] (IGNITE-2847) Failed atomic-offheap-invoke-retry load consistency test

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov resolved IGNITE-2847.
--
Resolution: Won't Fix
  Assignee: Ilya Suntsov  (was: Artem Shutak)

> Failed atomic-offheap-invoke-retry load consistency test
> 
>
> Key: IGNITE-2847
> URL: https://issues.apache.org/jira/browse/IGNITE-2847
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
> Environment: Yardstick driver's host: 
> Ubuntu 14.04.3 LTS
> Yardstick server's hosts: Ubuntu 14.04.3 LTS and CentOS release 6.7 (Final)
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: logs_1_backup.zip, logs_configs.zip
>
>
> I ran load test with 2 backups in client mode (1 client, 4 servers) on 3 
> hosts (host1 - client, hosts-2,3 - 2 data nodes on each) and got the 
> following exception after 5h of work of test:
> {noformat}
> <13:49:20> Got 
> exception: 
> org.apache.ignite.yardstick.cache.failover.IgniteConsistencyException: Cache 
> and local map are in inconsistent state [badKeys=[key-62687]]
> org.apache.ignite.yardstick.cache.failover.IgniteConsistencyException: Cache 
> and local map are in inconsistent state 
> [badKeys=[key-62687]]<13:49:20> Full thread 
> dump of the current node below.
> {noformat}
> Logs in attachment.



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

[jira] [Closed] (IGNITE-2867) IgniteConsistencyException during running load test (cache-atomic-invoke-retry-validator)

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov closed IGNITE-2867.


> IgniteConsistencyException during running load test 
> (cache-atomic-invoke-retry-validator)
> -
>
> Key: IGNITE-2867
> URL: https://issues.apache.org/jira/browse/IGNITE-2867
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
> Environment: Yardstick driver's host: Ubuntu 14.04.3 LTS
> Yardstick server's hosts: Ubuntu 14.04.3 LTS and CentOS release 6.7 (Final)
> Yardstick configuration: 2 clients, 3 servers, PRIMARY_SYNC, 1 and 2 backups
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: logs_configs_2103.zip
>
>
> I've add one more client and run load test with 2 clients and 3 servers (all 
> on different hosts).
> Test runs for ~ 3 min and stops with exception:
> {noformat}
>  Got exception: 
> org.apache.ignite.yardstick.cache.failover.IgniteConsistencyException: Cache 
> and local map are in inconsistent state.
> {noformat}
> Logs and configs you can find in attachment. 



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

[jira] [Closed] (IGNITE-2847) Failed atomic-offheap-invoke-retry load consistency test

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov closed IGNITE-2847.


> Failed atomic-offheap-invoke-retry load consistency test
> 
>
> Key: IGNITE-2847
> URL: https://issues.apache.org/jira/browse/IGNITE-2847
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
> Environment: Yardstick driver's host: 
> Ubuntu 14.04.3 LTS
> Yardstick server's hosts: Ubuntu 14.04.3 LTS and CentOS release 6.7 (Final)
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: logs_1_backup.zip, logs_configs.zip
>
>
> I ran load test with 2 backups in client mode (1 client, 4 servers) on 3 
> hosts (host1 - client, hosts-2,3 - 2 data nodes on each) and got the 
> following exception after 5h of work of test:
> {noformat}
> <13:49:20> Got 
> exception: 
> org.apache.ignite.yardstick.cache.failover.IgniteConsistencyException: Cache 
> and local map are in inconsistent state [badKeys=[key-62687]]
> org.apache.ignite.yardstick.cache.failover.IgniteConsistencyException: Cache 
> and local map are in inconsistent state 
> [badKeys=[key-62687]]<13:49:20> Full thread 
> dump of the current node below.
> {noformat}
> Logs in attachment.



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

[jira] [Closed] (IGNITE-2896) IgniteFutureTimeoutException during load test (yardstick)

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov closed IGNITE-2896.


> IgniteFutureTimeoutException during load test (yardstick)
> -
>
> Key: IGNITE-2896
> URL: https://issues.apache.org/jira/browse/IGNITE-2896
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
> Environment: Environment:
>  - vCPU 8
>  - RAM 15GiB
>  - OS Ubuntu 14.04
>  - Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
> Yardstick configuration:
>  - client mode (15 servers, 5 clients)
>  - PRIMARY SYNC
>  - 128 threads
>  - 1 backup
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: drivers_lods_conf.zip, logs_configs_new_p1.zip, 
> logs_configs_new_p2.zip, servers_logs_p1.zip, servers_logs_p2.zip
>
>
> I got the following exception during the run of load test with 1 baskup (+ 
> sql caches and sql benchmarks) :
> {noformat}
>  Got exception: class 
> org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout was reached 
> before computation completed.
> class org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout was 
> reached before computation completed.
>   at 
> org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:754)
>   at 
> org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:752)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:895)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:54)
>   at 
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:132)
>   at 
> org.apache.ignite.yardstick.cache.failover.IgniteTransactionalInvokeRetryBenchmark$1.run(IgniteTransactionalInvokeRetryBenchmark.java:83)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.IgniteFutureTimeoutCheckedException: Timeout was 
> reached before computation completed.
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:186)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:135)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:126)
>   at 
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:129)
>   ... 2 more
> {noformat}
> Logs and configs you can find in attachment.



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

[jira] [Resolved] (IGNITE-2896) IgniteFutureTimeoutException during load test (yardstick)

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov resolved IGNITE-2896.
--
Resolution: Won't Fix
  Assignee: Ilya Suntsov  (was: Artem Shutak)

> IgniteFutureTimeoutException during load test (yardstick)
> -
>
> Key: IGNITE-2896
> URL: https://issues.apache.org/jira/browse/IGNITE-2896
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
> Environment: Environment:
>  - vCPU 8
>  - RAM 15GiB
>  - OS Ubuntu 14.04
>  - Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
> Yardstick configuration:
>  - client mode (15 servers, 5 clients)
>  - PRIMARY SYNC
>  - 128 threads
>  - 1 backup
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: drivers_lods_conf.zip, logs_configs_new_p1.zip, 
> logs_configs_new_p2.zip, servers_logs_p1.zip, servers_logs_p2.zip
>
>
> I got the following exception during the run of load test with 1 baskup (+ 
> sql caches and sql benchmarks) :
> {noformat}
>  Got exception: class 
> org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout was reached 
> before computation completed.
> class org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout was 
> reached before computation completed.
>   at 
> org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:754)
>   at 
> org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:752)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:895)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:54)
>   at 
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:132)
>   at 
> org.apache.ignite.yardstick.cache.failover.IgniteTransactionalInvokeRetryBenchmark$1.run(IgniteTransactionalInvokeRetryBenchmark.java:83)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.IgniteFutureTimeoutCheckedException: Timeout was 
> reached before computation completed.
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:186)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:135)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:126)
>   at 
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:129)
>   ... 2 more
> {noformat}
> Logs and configs you can find in attachment.



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

[jira] [Resolved] (IGNITE-2867) IgniteConsistencyException during running load test (cache-atomic-invoke-retry-validator)

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov resolved IGNITE-2867.
--
Resolution: Won't Fix
  Assignee: Ilya Suntsov  (was: Artem Shutak)

> IgniteConsistencyException during running load test 
> (cache-atomic-invoke-retry-validator)
> -
>
> Key: IGNITE-2867
> URL: https://issues.apache.org/jira/browse/IGNITE-2867
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.6
> Environment: Yardstick driver's host: Ubuntu 14.04.3 LTS
> Yardstick server's hosts: Ubuntu 14.04.3 LTS and CentOS release 6.7 (Final)
> Yardstick configuration: 2 clients, 3 servers, PRIMARY_SYNC, 1 and 2 backups
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: logs_configs_2103.zip
>
>
> I've add one more client and run load test with 2 clients and 3 servers (all 
> on different hosts).
> Test runs for ~ 3 min and stops with exception:
> {noformat}
>  Got exception: 
> org.apache.ignite.yardstick.cache.failover.IgniteConsistencyException: Cache 
> and local map are in inconsistent state.
> {noformat}
> Logs and configs you can find in attachment. 



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

[jira] [Resolved] (IGNITE-2932) IgniteFutureTimeoutException during the run of load test (cache-tx-invoke)

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov resolved IGNITE-2932.
--
Resolution: Won't Fix
  Assignee: Ilya Suntsov  (was: Artem Shutak)

> IgniteFutureTimeoutException during the run of load test (cache-tx-invoke)
> --
>
> Key: IGNITE-2932
> URL: https://issues.apache.org/jira/browse/IGNITE-2932
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
> Environment: Environment:
> vCPU 8
> RAM 15GiB
> OS Ubuntu 14.04
> Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
> Yardstick configuration:
> client mode (15 servers, 5 clients)
> PRIMARY SYNC
> 128 threads
> 1 backup
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: logs_configs.zip
>
>
> I got the following exception during the run of load test with 2 backups (+ 
> sql caches and sql benchmarks) :
> {noformat}
> <16:39:52> Got exception: class 
> org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout was reached 
> before computation completed.
> <16:39:52> Full thread dump of the current 
> node below.class org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout 
> was reached before computation completed.
>   at 
> org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:754)
>   at 
> org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:752)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:895)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:54)
>   at 
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:132)
>   at 
> org.apache.ignite.yardstick.cache.failover.IgniteTransactionalInvokeRetryBenchmark$1.run(IgniteTransactionalInvokeRetryBenchmark.java:83)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.IgniteFutureTimeoutCheckedException: Timeout was 
> reached before computation completed.
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:186)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:135)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:126)
>   at 
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:129)
>   ... 2 more
> [16:39:52] (wrn) No deadlocked threads detected.
> Finishing main test [ts=1459442392910, date=Thu Mar 31 16:39:52 UTC 2016]
> {noformat}
> Logs and configs you can find in attachment.



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

[jira] [Closed] (IGNITE-2932) IgniteFutureTimeoutException during the run of load test (cache-tx-invoke)

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov closed IGNITE-2932.


> IgniteFutureTimeoutException during the run of load test (cache-tx-invoke)
> --
>
> Key: IGNITE-2932
> URL: https://issues.apache.org/jira/browse/IGNITE-2932
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.6
> Environment: Environment:
> vCPU 8
> RAM 15GiB
> OS Ubuntu 14.04
> Java(TM) SE Runtime Environment (build 1.7.0_80-b15)
> Yardstick configuration:
> client mode (15 servers, 5 clients)
> PRIMARY SYNC
> 128 threads
> 1 backup
>Reporter: Ilya Suntsov
>Assignee: Ilya Suntsov
>Priority: Critical
> Fix For: 1.8
>
> Attachments: logs_configs.zip
>
>
> I got the following exception during the run of load test with 2 backups (+ 
> sql caches and sql benchmarks) :
> {noformat}
> <16:39:52> Got exception: class 
> org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout was reached 
> before computation completed.
> <16:39:52> Full thread dump of the current 
> node below.class org.apache.ignite.lang.IgniteFutureTimeoutException: Timeout 
> was reached before computation completed.
>   at 
> org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:754)
>   at 
> org.apache.ignite.internal.util.IgniteUtils$4.apply(IgniteUtils.java:752)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:895)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheFutureImpl.convertException(IgniteCacheFutureImpl.java:54)
>   at 
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:132)
>   at 
> org.apache.ignite.yardstick.cache.failover.IgniteTransactionalInvokeRetryBenchmark$1.run(IgniteTransactionalInvokeRetryBenchmark.java:83)
>   at java.lang.Thread.run(Thread.java:745)
> Caused by: class 
> org.apache.ignite.internal.IgniteFutureTimeoutCheckedException: Timeout was 
> reached before computation completed.
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:186)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:135)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:126)
>   at 
> org.apache.ignite.internal.util.future.IgniteFutureImpl.get(IgniteFutureImpl.java:129)
>   ... 2 more
> [16:39:52] (wrn) No deadlocked threads detected.
> Finishing main test [ts=1459442392910, date=Thu Mar 31 16:39:52 UTC 2016]
> {noformat}
> Logs and configs you can find in attachment.



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

[jira] [Updated] (IGNITE-3103) No description in javadoc (kafka module)

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov updated IGNITE-3103:
-
Fix Version/s: (was: 1.8)
   1.9

> No description in javadoc (kafka module)
> 
>
> Key: IGNITE-3103
> URL: https://issues.apache.org/jira/browse/IGNITE-3103
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Affects Versions: 1.6
>Reporter: Ilya Suntsov
>Priority: Minor
> Fix For: 1.9
>
>
> No description in javadoc for classes:
> * org.apache.ignite.stream.kafka.connect
>  * org.apache.ignite.stream.kafka.connect.serialization



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

[jira] [Comment Edited] (IGNITE-3176) Need to create gc log for each client separately [ yardstick-ignite ]

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov edited comment on IGNITE-3176 at 11/16/16 10:45 AM:
-

I told about a little different use case:
1. Set in properties file number of servers and drivers (drivers are clients if 
we set --client parameter, please take a look at attachment) e.g:
{noformat}
# Comma-separated list of the hosts to run BenchmarkServers on. 2 nodes on 
local host are enabled by default.
SERVER_HOSTS=localhost,localhost,localhost

# Comma-separated list of the hosts to run BenchmarkDrivers on. 1 node on local 
host is enabled by default.
DRIVER_HOSTS=localhost,localhost
{noformat}

2. bin/benchmark-run-all.sh config/benchmark.properties only in one terminal.

In this case we receive 2 gc files.


was (Author: ustas):
I told about a little different use case:
1. Set in properties file number of servers and drivers (drivers are clients if 
we set --client parameter, please take a look at attachment) e.g:
{noformat}
# Comma-separated list of the hosts to run BenchmarkServers on. 2 nodes on 
local host are enabled by default.
SERVER_HOSTS=localhost,localhost,localhost

# Comma-separated list of the hosts to run BenchmarkDrivers on. 1 node on local 
host is enabled by default.
DRIVER_HOSTS=localhost,localhost
{noformat}

2. bin/benchmark-run-all.sh config/benchmark.properties only in one terminal.

I this case we receive 2 gc files.

> Need to create gc log for each client separately [ yardstick-ignite ]
> -
>
> Key: IGNITE-3176
> URL: https://issues.apache.org/jira/browse/IGNITE-3176
> Project: Ignite
>  Issue Type: Bug
>  Components: clients, general
>Affects Versions: 1.6
>Reporter: Ilya Suntsov
>Assignee: Chandresh Pancholi
>Priority: Critical
> Fix For: 1.8
>
> Attachments: benchmark.properties
>
>
> In case when started more than one client/server on one host yardstick 
> re-write GC logs.
> GC options contain in *.properties files:
> {noformat}
> now0=`date +'%H%M%S'`
> # JVM options.
> JVM_OPTS=${JVM_OPTS}" -DIGNITE_QUIET=false"
> # Uncomment to enable concurrent garbage collection (GC) if you encounter 
> long GC pauses.
> JVM_OPTS=${JVM_OPTS}" \
> -Xloggc:./gc${now0}.log \
> -XX:+PrintGCDetails \
> -verbose:gc \
> -XX:+UseParNewGC \
> -XX:+UseConcMarkSweepGC \
> -XX:+UseTLAB \
> -XX:NewSize=128m \
> -XX:MaxNewSize=128m \
> -XX:MaxTenuringThreshold=0 \
> -XX:SurvivorRatio=1024 \
> -XX:+UseCMSInitiatingOccupancyOnly \
> -XX:CMSInitiatingOccupancyFraction=60 \
> {noformat}
> As you can see here will be created 1 log file and if you start another 
> driver/server with the same properties file will be re-write.



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

[jira] [Updated] (IGNITE-3176) Need to create gc log for each client separately [ yardstick-ignite ]

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov updated IGNITE-3176:
-
Attachment: benchmark.properties

> Need to create gc log for each client separately [ yardstick-ignite ]
> -
>
> Key: IGNITE-3176
> URL: https://issues.apache.org/jira/browse/IGNITE-3176
> Project: Ignite
>  Issue Type: Bug
>  Components: clients, general
>Affects Versions: 1.6
>Reporter: Ilya Suntsov
>Assignee: Chandresh Pancholi
>Priority: Critical
> Fix For: 1.8
>
> Attachments: benchmark.properties
>
>
> In case when started more than one client/server on one host yardstick 
> re-write GC logs.
> GC options contain in *.properties files:
> {noformat}
> now0=`date +'%H%M%S'`
> # JVM options.
> JVM_OPTS=${JVM_OPTS}" -DIGNITE_QUIET=false"
> # Uncomment to enable concurrent garbage collection (GC) if you encounter 
> long GC pauses.
> JVM_OPTS=${JVM_OPTS}" \
> -Xloggc:./gc${now0}.log \
> -XX:+PrintGCDetails \
> -verbose:gc \
> -XX:+UseParNewGC \
> -XX:+UseConcMarkSweepGC \
> -XX:+UseTLAB \
> -XX:NewSize=128m \
> -XX:MaxNewSize=128m \
> -XX:MaxTenuringThreshold=0 \
> -XX:SurvivorRatio=1024 \
> -XX:+UseCMSInitiatingOccupancyOnly \
> -XX:CMSInitiatingOccupancyFraction=60 \
> {noformat}
> As you can see here will be created 1 log file and if you start another 
> driver/server with the same properties file will be re-write.



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

[jira] [Commented] (IGNITE-3176) Need to create gc log for each client separately [ yardstick-ignite ]

[Ilya Suntsov (JIRA)]

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

Ilya Suntsov commented on IGNITE-3176:
--

I told about a little different use case:
1. Set in properties file number of servers and drivers (drivers are clients if 
we set --client parameter, please take a look at attachment) e.g:
{noformat}
# Comma-separated list of the hosts to run BenchmarkServers on. 2 nodes on 
local host are enabled by default.
SERVER_HOSTS=localhost,localhost,localhost

# Comma-separated list of the hosts to run BenchmarkDrivers on. 1 node on local 
host is enabled by default.
DRIVER_HOSTS=localhost,localhost
{noformat}

2. bin/benchmark-run-all.sh config/benchmark.properties only in one terminal.

I this case we receive 2 gc files.

> Need to create gc log for each client separately [ yardstick-ignite ]
> -
>
> Key: IGNITE-3176
> URL: https://issues.apache.org/jira/browse/IGNITE-3176
> Project: Ignite
>  Issue Type: Bug
>  Components: clients, general
>Affects Versions: 1.6
>Reporter: Ilya Suntsov
>Assignee: Chandresh Pancholi
>Priority: Critical
> Fix For: 1.8
>
>
> In case when started more than one client/server on one host yardstick 
> re-write GC logs.
> GC options contain in *.properties files:
> {noformat}
> now0=`date +'%H%M%S'`
> # JVM options.
> JVM_OPTS=${JVM_OPTS}" -DIGNITE_QUIET=false"
> # Uncomment to enable concurrent garbage collection (GC) if you encounter 
> long GC pauses.
> JVM_OPTS=${JVM_OPTS}" \
> -Xloggc:./gc${now0}.log \
> -XX:+PrintGCDetails \
> -verbose:gc \
> -XX:+UseParNewGC \
> -XX:+UseConcMarkSweepGC \
> -XX:+UseTLAB \
> -XX:NewSize=128m \
> -XX:MaxNewSize=128m \
> -XX:MaxTenuringThreshold=0 \
> -XX:SurvivorRatio=1024 \
> -XX:+UseCMSInitiatingOccupancyOnly \
> -XX:CMSInitiatingOccupancyFraction=60 \
> {noformat}
> As you can see here will be created 1 log file and if you start another 
> driver/server with the same properties file will be re-write.



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

[jira] [Commented] (IGNITE-1192) Provide integration with Spring Data

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev commented on IGNITE-1192:
---

If you want you some storage and Ignite as cache layer, you could look here - 
https://apacheignite.readme.io/docs/spring-caching..

This ticket about querying Ignite itself via Spring Data. Not about caching 
queries for some storage.

> Provide integration with Spring Data
> 
>
> Key: IGNITE-1192
> URL: https://issues.apache.org/jira/browse/IGNITE-1192
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.1.4
>Reporter: Valentin Kulichenko
>Assignee: Eduard Shangareev
>Priority: Minor
>  Labels: Newbie
> Fix For: 2.0
>
>
> Spring Data docs:
> * http://docs.spring.io/spring-data/data-commons/docs/current/reference/html/
> * http://docs.spring.io/spring-data/data-commons/docs/current/api/



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