[jira] [Assigned] (IGNITE-6398) WebConsole: support ClientConnectorConfiguration

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-6398:
--

Assignee: Alexey Kuznetsov  (was: Pavel Konstantinov)

> WebConsole: support ClientConnectorConfiguration
> 
>
> Key: IGNITE-6398
> URL: https://issues.apache.org/jira/browse/IGNITE-6398
> Project: Ignite
>  Issue Type: Task
>  Components: thin client, wizards
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>
> See {{IgniteConfiguration.clientConnectorConfiguration}}. We will use it 
> instead of {{IgniteConfiguration.sqlConnectorConfiguration}}.



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

[jira] [Commented] (IGNITE-6398) WebConsole: support ClientConnectorConfiguration

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-6398:


Tested in branch

> WebConsole: support ClientConnectorConfiguration
> 
>
> Key: IGNITE-6398
> URL: https://issues.apache.org/jira/browse/IGNITE-6398
> Project: Ignite
>  Issue Type: Task
>  Components: thin client, wizards
>Reporter: Vladimir Ozerov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> See {{IgniteConfiguration.clientConnectorConfiguration}}. We will use it 
> instead of {{IgniteConfiguration.sqlConnectorConfiguration}}.



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

[jira] [Updated] (IGNITE-6747) Use _HOST instead of FDQN when configuring principal for IgfsSecondaryFileSystem with kerberos enable

[Reid Chan (JIRA)]

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

Reid Chan updated IGNITE-6747:
--
Description: 
So far, igfs can access to kerberized hdfs by providing {{keyTab}} and 
{{keyTabPrincipal}}:
{code}


{code}
But it becomes nightmare when number of grid nodes is more than hundreds or 
even thousands which is in my case, since i have to configure FDQN for each 
node.
Hadoop's package already provides an easy way which uses "_HOST" instead of 
FDQN, i think it's better to use it.

Suggestions are welcomed.

> Use _HOST instead of FDQN when configuring principal for 
> IgfsSecondaryFileSystem with kerberos enable
> -
>
> Key: IGNITE-6747
> URL: https://issues.apache.org/jira/browse/IGNITE-6747
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: hadoop
>Affects Versions: 2.2
>Reporter: Reid Chan
>
> So far, igfs can access to kerberized hdfs by providing {{keyTab}} and 
> {{keyTabPrincipal}}:
> {code}
> 
>  value="ignite/fully.qualified.domain.name@REALM"/>
> {code}
> But it becomes nightmare when number of grid nodes is more than hundreds or 
> even thousands which is in my case, since i have to configure FDQN for each 
> node.
> Hadoop's package already provides an easy way which uses "_HOST" instead of 
> FDQN, i think it's better to use it.
> Suggestions are welcomed.



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

[jira] [Updated] (IGNITE-6747) Use _HOST instead of FDQN when configuring principal for IgfsSecondaryFileSystem with kerberos enable

[Reid Chan (JIRA)]

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

Reid Chan updated IGNITE-6747:
--
Affects Version/s: 2.2

> Use _HOST instead of FDQN when configuring principal for 
> IgfsSecondaryFileSystem with kerberos enable
> -
>
> Key: IGNITE-6747
> URL: https://issues.apache.org/jira/browse/IGNITE-6747
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: hadoop
>Affects Versions: 2.2
>Reporter: Reid Chan
>




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

[jira] [Created] (IGNITE-6747) Use _HOST instead of FDQN when configuring principal for IgfsSecondaryFileSystem with kerberos enable

[Reid Chan (JIRA)]

Reid Chan created IGNITE-6747:
-

 Summary: Use _HOST instead of FDQN when configuring principal for 
IgfsSecondaryFileSystem with kerberos enable
 Key: IGNITE-6747
 URL: https://issues.apache.org/jira/browse/IGNITE-6747
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
  Components: hadoop
Reporter: Reid Chan






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

[jira] [Updated] (IGNITE-6521) Review default JVM options for better performance

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-6521:
-
Fix Version/s: 2.4

> Review default JVM options for better performance
> -
>
> Key: IGNITE-6521
> URL: https://issues.apache.org/jira/browse/IGNITE-6521
> Project: Ignite
>  Issue Type: Improvement
>  Components: general, visor
>Affects Versions: 2.1
>Reporter: Alexandr Kuramshin
>Assignee: Dmitriy Govorukhin
> Fix For: 2.4
>
>
> Non-optimal recommendations are present in ignite startup scrips
> {noformat}
> ::
> :: Uncomment the following GC settings if you see spikes in your throughput 
> due to Garbage Collection.
> ::
> :: set JVM_OPTS=%JVM_OPTS% -XX:+UseParNewGC -XX:+UseConcMarkSweepGC 
> -XX:+UseTLAB -XX:NewSize=128m -XX:MaxNewSize=128m
> :: set JVM_OPTS=%JVM_OPTS% -XX:MaxTenuringThreshold=0 -XX:SurvivorRatio=1024 
> -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=60
> {noformat}
> Some utilities (like Visor) are hanged up in continuous GCs when connected to 
> large clusters (above one hundred nodes). Even after using large heap (about 
> 32 Gb).
> I'd like to propose to remove this lines and modify default JVM_OPTS as 
> follows
> {noformat}
> set JVM_OPTS=-Xms1g -Xmx8g -XX:+UseG1GC -server -XX:+AggressiveOpts 
> -XX:MaxPermSize=256m
> {noformat}



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

[jira] [Assigned] (IGNITE-6671) [Web Console] Wrong java type used in generated config from DB schema

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-6671:


Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Looks good. Merged to master.
Please retest.

> [Web Console] Wrong java type used in generated config from DB schema
> -
>
> Key: IGNITE-6671
> URL: https://issues.apache.org/jira/browse/IGNITE-6671
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Affects Versions: 2.2
>Reporter: Dmitry Karachentsev
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> We should be confident that java types in generated config are able to fit in 
> values from DB. For example, WC generates short for Oracle's NUMBER(5), when 
> short could be max 32767, but NUMBER(5) - 9.
> That may produce errors like below during DB import:
> {noformat}
>  Exception in thread "main" javax.cache.integration.CacheLoaderException: 
> Failed to load cache: test
>at 
> org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore.loadCache(CacheAbstractJdbcStore.java:798)
>at 
> org.apache.ignite.internal.processors.cache.store.GridCacheStoreManagerAdapter.loadCache(GridCacheStoreManagerAdapter.java:502)
>at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheAdapter.localLoadCache(GridDhtCacheAdapter.java:486)
>at 
> org.apache.ignite.internal.processors.cache.GridCacheProxyImpl.localLoadCache(GridCacheProxyImpl.java:217)
>at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheJob.localExecute(GridCacheAdapter.java:5439)
>at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$LoadCacheJobV2.localExecute(GridCacheAdapter.java:5488)
>at 
> org.apache.ignite.internal.processors.cache.GridCacheAdapter$TopologyVersionAwareJob.execute(GridCacheAdapter.java:6103)
>at 
> org.apache.ignite.compute.ComputeJobAdapter.call(ComputeJobAdapter.java:132)
>at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1842)
>at 
> org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:566)
>at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6621)
>at 
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:560)
>at 
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
>at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>at 
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1114)
>at 
> org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1907)
>at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1257)
>at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:885)
>at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:114)
>at 
> org.apache.ignite.internal.managers.communication.GridIoManager$7.run(GridIoManager.java:802)
>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: javax.cache.CacheException: Failed to read binary object: 
> org.apache.TestModel
>at 
> org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStore.buildBinaryObject(CacheJdbcPojoStore.java:255)
>at 
> org.apache.ignite.cache.store.jdbc.CacheJdbcPojoStore.buildObject(CacheJdbcPojoStore.java:136)
>at 
> org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore$1.call(CacheAbstractJdbcStore.java:463)
>at 
> org.apache.ignite.cache.store.jdbc.CacheAbstractJdbcStore$1.call(CacheAbstractJdbcStore.java:430)
>at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>... 3 more
> Caused by: java.sql.SQLException: Numeric Overflow
>at 
> oracle.jdbc.driver.NumberCommonAccessor.throwOverflow(NumberCommonAccessor.java:4170)
>at 
> oracle.jdbc.driver.NumberCommonAccessor.getShort(NumberCommonAccessor.java:311)
>at 
> oracle.jdbc.driver.GeneratedStatement.getShort(GeneratedStatement.java:305)
>at 
> oracle.jdbc.driver.GeneratedScrollableResultSet.getShort(GeneratedScrollableResultSet.java:879)
>at 
> 

[jira] [Assigned] (IGNITE-6398) WebConsole: support ClientConnectorConfiguration

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-6398:


Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Please test in branch ignite-6398.

> WebConsole: support ClientConnectorConfiguration
> 
>
> Key: IGNITE-6398
> URL: https://issues.apache.org/jira/browse/IGNITE-6398
> Project: Ignite
>  Issue Type: Task
>  Components: thin client, wizards
>Reporter: Vladimir Ozerov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> See {{IgniteConfiguration.clientConnectorConfiguration}}. We will use it 
> instead of {{IgniteConfiguration.sqlConnectorConfiguration}}.



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

[jira] [Updated] (IGNITE-6398) WebConsole: support ClientConnectorConfiguration

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-6398:
-
Fix Version/s: 2.4

> WebConsole: support ClientConnectorConfiguration
> 
>
> Key: IGNITE-6398
> URL: https://issues.apache.org/jira/browse/IGNITE-6398
> Project: Ignite
>  Issue Type: Task
>  Components: thin client, wizards
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>
> See {{IgniteConfiguration.clientConnectorConfiguration}}. We will use it 
> instead of {{IgniteConfiguration.sqlConnectorConfiguration}}.



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

[jira] [Assigned] (IGNITE-6617) Web console: there is no error message that cluster is not active on Queries screen

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-6617:
--

Assignee: Vasiliy Sisko  (was: Pavel Konstantinov)

> Web console: there is no error message that cluster is not active on Queries 
> screen
> ---
>
> Key: IGNITE-6617
> URL: https://issues.apache.org/jira/browse/IGNITE-6617
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>
> start cluster with persistent
> start web agent connected to this cluster
> open Queries on web console
> try to execute any 'select' query
> there is no error message that cluster is not active
> NOTE: 'Use selected cache as default schema name' checkbox must be OFF



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

[jira] [Updated] (IGNITE-6617) Web console: there is no error message that cluster is not active on Queries screen

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-6617:
---
Description: 
start cluster with persistent
start web agent connected to this cluster
open Queries on web console
try to execute any 'select' query
there is no error message that cluster is not active

NOTE: 'Use selected cache as default schema name' checkbox must be OFF

  was:
start cluster with persistent
start web agent connected to this cluster
open Queries on web console
try to execute any 'select' query
there is no error message that cluster is not active


> Web console: there is no error message that cluster is not active on Queries 
> screen
> ---
>
> Key: IGNITE-6617
> URL: https://issues.apache.org/jira/browse/IGNITE-6617
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> start cluster with persistent
> start web agent connected to this cluster
> open Queries on web console
> try to execute any 'select' query
> there is no error message that cluster is not active
> NOTE: 'Use selected cache as default schema name' checkbox must be OFF



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

[jira] [Assigned] (IGNITE-6670) Web console: Check demo node configuration

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-6670:


Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

I merged with latest master and demo start to fail.
Please debug.

> Web console: Check demo node configuration
> --
>
> Key: IGNITE-6670
> URL: https://issues.apache.org/jira/browse/IGNITE-6670
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>
> On start of demo the Web agent shows a lot of debug messages in log. 
> Configuration should be changed to reduce information shown on start.



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

[jira] [Assigned] (IGNITE-6617) Web console: there is no error message that cluster is not active on Queries screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-6617:
-

Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> Web console: there is no error message that cluster is not active on Queries 
> screen
> ---
>
> Key: IGNITE-6617
> URL: https://issues.apache.org/jira/browse/IGNITE-6617
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
>
> start cluster with persistent
> start web agent connected to this cluster
> open Queries on web console
> try to execute any 'select' query
> there is no error message that cluster is not active



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

[jira] [Commented] (IGNITE-6617) Web console: there is no error message that cluster is not active on Queries screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-6617:
---

Not reproduced. Error message showed on place of query result.

> Web console: there is no error message that cluster is not active on Queries 
> screen
> ---
>
> Key: IGNITE-6617
> URL: https://issues.apache.org/jira/browse/IGNITE-6617
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>
> start cluster with persistent
> start web agent connected to this cluster
> open Queries on web console
> try to execute any 'select' query
> there is no error message that cluster is not active



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

[jira] [Assigned] (IGNITE-6617) Web console: there is no error message that cluster is not active on Queries screen

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-6617:
-

Assignee: Vasiliy Sisko

> Web console: there is no error message that cluster is not active on Queries 
> screen
> ---
>
> Key: IGNITE-6617
> URL: https://issues.apache.org/jira/browse/IGNITE-6617
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
>
> start cluster with persistent
> start web agent connected to this cluster
> open Queries on web console
> try to execute any 'select' query
> there is no error message that cluster is not active



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

[jira] [Updated] (IGNITE-6670) Web console: Check demo node configuration

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-6670:
-
Fix Version/s: 2.4

> Web console: Check demo node configuration
> --
>
> Key: IGNITE-6670
> URL: https://issues.apache.org/jira/browse/IGNITE-6670
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
>
> On start of demo the Web agent shows a lot of debug messages in log. 
> Configuration should be changed to reduce information shown on start.



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

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

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-3084:
-

[~vkulichenko], [~avinogradov], hello.

Please, review my changes.

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



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

[jira] [Issue Comment Deleted] (IGNITE-3084) Spark Data Frames Support in Apache Ignite

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov updated IGNITE-3084:

Comment: was deleted

(was: upsource review for prototype - 
https://reviews.ignite.apache.org/ignite/review/IGNT-CR-354)

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



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

[jira] [Commented] (IGNITE-6705) .NET: CacheConfiguration missing properties

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6705:


Done, waiting for TC.

> .NET: CacheConfiguration missing properties
> ---
>
> Key: IGNITE-6705
> URL: https://issues.apache.org/jira/browse/IGNITE-6705
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET
> Fix For: 2.4
>
>
> IGNITE-6263 revealed a number of missing {{CacheConfiguration}} properties:
> {code}
> "IsOnheapCacheEnabled",
> "StoreConcurrentLoadAllThreshold",
> "isOnheapCacheEnabled",
> "RebalanceOrder",
> "RebalanceBatchesPrefetchCount",
> "MaxQueryIteratorsCount",
> "QueryDetailMetricsSize",
> "SqlSchema",
> "QueryParallelism"
> {code}



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

[jira] [Commented] (IGNITE-6705) .NET: CacheConfiguration missing properties

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6705:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-6705 .NET: CacheConfiguration missing properties



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

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

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

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






> .NET: CacheConfiguration missing properties
> ---
>
> Key: IGNITE-6705
> URL: https://issues.apache.org/jira/browse/IGNITE-6705
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .NET
> Fix For: 2.4
>
>
> IGNITE-6263 revealed a number of missing {{CacheConfiguration}} properties:
> {code}
> "IsOnheapCacheEnabled",
> "StoreConcurrentLoadAllThreshold",
> "isOnheapCacheEnabled",
> "RebalanceOrder",
> "RebalanceBatchesPrefetchCount",
> "MaxQueryIteratorsCount",
> "QueryDetailMetricsSize",
> "SqlSchema",
> "QueryParallelism"
> {code}



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

[jira] [Resolved] (IGNITE-4615) Ignite should be compilable under JDK 9

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov resolved IGNITE-4615.
-
   Resolution: Duplicate
Fix Version/s: (was: 2.4)

> Ignite should be compilable under JDK 9
> ---
>
> Key: IGNITE-4615
> URL: https://issues.apache.org/jira/browse/IGNITE-4615
> Project: Ignite
>  Issue Type: Task
>Reporter: Anton Vinogradov
> Attachments: ignite.jar.dot
>
>
> The original discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Should-we-take-care-of-Java-9-in-Ignite-2-0-scope-td14018.html



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

[jira] [Closed] (IGNITE-4615) Ignite should be compilable under JDK 9

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov closed IGNITE-4615.
---

> Ignite should be compilable under JDK 9
> ---
>
> Key: IGNITE-4615
> URL: https://issues.apache.org/jira/browse/IGNITE-4615
> Project: Ignite
>  Issue Type: Task
>Reporter: Anton Vinogradov
> Attachments: ignite.jar.dot
>
>
> The original discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/Should-we-take-care-of-Java-9-in-Ignite-2-0-scope-td14018.html



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

[jira] [Comment Edited] (IGNITE-6726) Licenses for Sqlline are missing

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov edited comment on IGNITE-6726 at 10/24/17 3:49 PM:


[~oleg-ostanin]
Why you added BSD license to sqlline/pom.xml?

Also, I see no build based on these changes.


was (Author: avinogradov):
[~oleg-ostanin]
Why you ad BSD license to sqlline/pom.xml?

Also, I see no build based on these changes.

> Licenses for Sqlline are missing
> 
>
> Key: IGNITE-6726
> URL: https://issues.apache.org/jira/browse/IGNITE-6726
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: build
>Affects Versions: 2.3
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> Licenses for Sqlline are missing



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

[jira] [Commented] (IGNITE-6726) Licenses for Sqlline are missing

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-6726:
--

[~oleg-ostanin]
Why you ad BSD license to sqlline/pom.xml?

Also, I see no build based on these changes.

> Licenses for Sqlline are missing
> 
>
> Key: IGNITE-6726
> URL: https://issues.apache.org/jira/browse/IGNITE-6726
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: build
>Affects Versions: 2.3
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> Licenses for Sqlline are missing



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

[jira] [Commented] (IGNITE-6690) DiscoverySpi: Clientmode Ignite should not fail on handshake errors

[Alexey Popov (JIRA)]

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

Alexey Popov commented on IGNITE-6690:
--

[~ntikho...@apache.org] Please review

> DiscoverySpi: Clientmode Ignite should not fail on handshake errors
> ---
>
> Key: IGNITE-6690
> URL: https://issues.apache.org/jira/browse/IGNITE-6690
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: general
>Affects Versions: 2.2
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>  Labels: discovery
> Fix For: 2.4
>
>
> Ignite in Client mode should not fail on handshake unmarshalling errors. It 
> should go to the next IP/port from ipFinder list
> http://apache-ignite-developers.2346864.n4.nabble.com/DiscoverySpi-Handshake-unmarshalling-errors-at-Client-client-mode-td23467.html



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

[jira] [Created] (IGNITE-6745) Java 9: rework usages of URLClassLoader.getURLs()

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6745:
---

 Summary: Java 9: rework usages of URLClassLoader.getURLs()
 Key: IGNITE-6745
 URL: https://issues.apache.org/jira/browse/IGNITE-6745
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: general
Reporter: Vladimir Ozerov
 Fix For: 2.4


We use this method in multiple places:
1) {{MessageCodeGenerator}}
2) {{BinaryContext}}
3) {{ClassesGenerator}}
4) {{GridUriDeploymentFileProcessor}}

The problem is that in Java 9 application class loader is not 
{{URLClassLoader}}, so we cannot get URLs easily. Instead typically it is 
{{BuiltinClassLoader}}, which refers to {{URLClassLoader}} in it's internal 
field {{ucp}}.

Let's refactor all usages of {{URLClassLoader.getURLs}} to some utility method, 
which will be able to handle both Java 7/8 and Java 9 (through reflection).




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

[jira] [Created] (IGNITE-6746) Add system persistent cache

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-6746:


 Summary: Add system persistent cache
 Key: IGNITE-6746
 URL: https://issues.apache.org/jira/browse/IGNITE-6746
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk


After IGNITE-6030 was fixed, the system cache is not persisted even when some 
of the caches are persisted. We need to introduce another system cache that 
will be persisted.



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

[jira] [Created] (IGNITE-6744) Java 9: create TC infrastructure to run unit tests

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6744:
---

 Summary: Java 9: create TC infrastructure to run unit tests
 Key: IGNITE-6744
 URL: https://issues.apache.org/jira/browse/IGNITE-6744
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: build
Reporter: Vladimir Ozerov
 Fix For: 2.4


We need to be able to test Ignite on both Java 7/8 and Java 9 on out CI server.



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

[jira] [Assigned] (IGNITE-5646) Use affinity keys for distributed matrice blocks

[Aleksey Zinoviev (JIRA)]

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

Aleksey Zinoviev reassigned IGNITE-5646:


Assignee: Aleksey Zinoviev

> Use affinity keys for distributed matrice blocks
> 
>
> Key: IGNITE-5646
> URL: https://issues.apache.org/jira/browse/IGNITE-5646
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Aleksey Zinoviev
>
> We want to implement affinity collocation for distributed matrices.
> We must guarantee that the new block for computation result will be stored in 
> the same node like the initial blocks



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

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

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6743:
---

 Summary: Java 9: rework DirectBuffer.cleaner().clean() usage in 
GridNioServer
 Key: IGNITE-6743
 URL: https://issues.apache.org/jira/browse/IGNITE-6743
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: general
Reporter: Vladimir Ozerov
 Fix For: 2.4


When session is closed we clean allocated {{DirectByteBuffer}}-s using 
{{sun.misc.Cleaner}}. Need to rework this piece to reflection-based approach 
which will work for supported Java versions.



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

[jira] [Created] (IGNITE-6742) Java 9: rework Cleaner usage in PlatformMemoryPool class

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6742:
---

 Summary: Java 9: rework Cleaner usage in PlatformMemoryPool class
 Key: IGNITE-6742
 URL: https://issues.apache.org/jira/browse/IGNITE-6742
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: platforms
Reporter: Vladimir Ozerov
 Fix For: 2.4


We attach special cleaner to {{PlatformMemoryPool}} using 
{{sun.misc.Cleaner.create}} method. This way we ensure that thread-local native 
memory (which is used to pass data between platform and Java) is released 
properly. 

Need to rework this API to reflection-based approach, which works for both Java 
7/8 and Java 9.



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

[jira] [Commented] (IGNITE-6723) ScalarCreditRiskExample failed with StackOverflowError

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6723:


Github user asfgit closed the pull request at:

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


> ScalarCreditRiskExample failed with StackOverflowError
> --
>
> Key: IGNITE-6723
> URL: https://issues.apache.org/jira/browse/IGNITE-6723
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: examples
>Affects Versions: 2.3
>Reporter: Sergey Kozlov
>Priority: Critical
> Fix For: 2.3
>
>
> 1. Open in IDEA {{ignite-examples}} project
> 2. Start {{ExampleNodeStartup}}
> 3. Run {{ScalarCreditRiskExample}}. It fails:
> {noformat}
> java.lang.StackOverflowError
>   at java.util.IdentityHashMap.maskNull(IdentityHashMap.java:192)
>   at java.util.IdentityHashMap.put(IdentityHashMap.java:426)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterHandles.put(BinaryWriterHandles.java:88)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.tryWriteAsHandle(BinaryWriterExImpl.java:1879)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.preWrite(BinaryClassDescriptor.java:888)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:790)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 

[jira] [Assigned] (IGNITE-6723) ScalarCreditRiskExample failed with StackOverflowError

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-6723:
---

Assignee: Taras Ledkov

> ScalarCreditRiskExample failed with StackOverflowError
> --
>
> Key: IGNITE-6723
> URL: https://issues.apache.org/jira/browse/IGNITE-6723
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: examples
>Affects Versions: 2.3
>Reporter: Sergey Kozlov
>Assignee: Taras Ledkov
>Priority: Critical
> Fix For: 2.3
>
>
> 1. Open in IDEA {{ignite-examples}} project
> 2. Start {{ExampleNodeStartup}}
> 3. Run {{ScalarCreditRiskExample}}. It fails:
> {noformat}
> java.lang.StackOverflowError
>   at java.util.IdentityHashMap.maskNull(IdentityHashMap.java:192)
>   at java.util.IdentityHashMap.put(IdentityHashMap.java:426)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterHandles.put(BinaryWriterHandles.java:88)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.tryWriteAsHandle(BinaryWriterExImpl.java:1879)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.preWrite(BinaryClassDescriptor.java:888)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:790)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> 

[jira] [Comment Edited] (IGNITE-6723) ScalarCreditRiskExample failed with StackOverflowError

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-6723 at 10/24/17 2:43 PM:


*Root cause:* {{StackOverflowError}} on serialization scala sequence collection 
(because Ignite binary serializer doesn't handle scala's linked list as 
collections, so the collection with 5K elements is too deep for ordinary object 
serialization).
*Fix:* change type to Array for member of the serialized closure.

[Examples tests 
results|https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2919%2Fhead]
 are OK.

[~vozerov], [~kuaw26], please review the patch.


was (Author: tledkov-gridgain):
*Root cause:* {{StackOverflowError}} on serialization scala sequence collection 
(because Ignite binary serializer doesn't handle scala's linked list as 
collections, so the collection with 5K elements is too deep for ordinary object 
serialization).
*Fix:* change type to Array for member of the serialized closure.

[Examples tests 
results|https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2919%2Fhead]

[~vozerov], [~kuaw26], please review the patch.

> ScalarCreditRiskExample failed with StackOverflowError
> --
>
> Key: IGNITE-6723
> URL: https://issues.apache.org/jira/browse/IGNITE-6723
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: examples
>Affects Versions: 2.3
>Reporter: Sergey Kozlov
>Priority: Critical
> Fix For: 2.3
>
>
> 1. Open in IDEA {{ignite-examples}} project
> 2. Start {{ExampleNodeStartup}}
> 3. Run {{ScalarCreditRiskExample}}. It fails:
> {noformat}
> java.lang.StackOverflowError
>   at java.util.IdentityHashMap.maskNull(IdentityHashMap.java:192)
>   at java.util.IdentityHashMap.put(IdentityHashMap.java:426)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterHandles.put(BinaryWriterHandles.java:88)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.tryWriteAsHandle(BinaryWriterExImpl.java:1879)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.preWrite(BinaryClassDescriptor.java:888)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:790)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> 

[jira] [Updated] (IGNITE-6741) GridRestProcessor doesn't support authorization on CLUSTER_ACTIVE command.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-6741:
-
Fix Version/s: 2.4

> GridRestProcessor doesn't support authorization on CLUSTER_ACTIVE command.
> --
>
> Key: IGNITE-6741
> URL: https://issues.apache.org/jira/browse/IGNITE-6741
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: rest
>Affects Versions: 2.2
>Reporter: Andrew Mashenkov
> Fix For: 2.4
>
>
> I've found we have a enum GridRestCommand.CLUSTER_ACTIVE, 
> but looks like it is not supported by GridRestProcessor and 
> enum SecurityPermission doesn't support any permission for cluster 
> activation. 
> Also CLUSTER_INACTIVE has same issues.
> So, cluster can't be activated with security plugin due to ERROR.
> See userlist thread for details [#\[1\]]
> {code:java}
> id=d2e2b816-61e3-47ff-9d88-ae4c8b3eb2ae, login=null 
> 10-23 20:48:30.051 [rest-#47%cdev_cluster%] ERROR 
> internal.processors.rest.GridRestProcessor - Client request execution failed 
> with error. 
> java.lang.AssertionError: Unexpected command: CLUSTER_ACTIVE 
> at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor.authorize(GridRestProcessor.java:817)
>  
> at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:250)
>  
> at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:91)
>  
> at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:157)
>  
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  
> at 
> {code}
> [^http://apache-ignite-users.70518.x6.nabble.com/Cannot-activate-Ignite-with-custom-security-plugin-tt17687.html]



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

[jira] [Updated] (IGNITE-6741) GridRestProcessor doesn't support authorization on CLUSTER_ACTIVE command.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-6741:
-
Component/s: rest

> GridRestProcessor doesn't support authorization on CLUSTER_ACTIVE command.
> --
>
> Key: IGNITE-6741
> URL: https://issues.apache.org/jira/browse/IGNITE-6741
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: rest
>Affects Versions: 2.2
>Reporter: Andrew Mashenkov
> Fix For: 2.4
>
>
> I've found we have a enum GridRestCommand.CLUSTER_ACTIVE, 
> but looks like it is not supported by GridRestProcessor and 
> enum SecurityPermission doesn't support any permission for cluster 
> activation. 
> Also CLUSTER_INACTIVE has same issues.
> So, cluster can't be activated with security plugin due to ERROR.
> See userlist thread for details [#\[1\]]
> {code:java}
> id=d2e2b816-61e3-47ff-9d88-ae4c8b3eb2ae, login=null 
> 10-23 20:48:30.051 [rest-#47%cdev_cluster%] ERROR 
> internal.processors.rest.GridRestProcessor - Client request execution failed 
> with error. 
> java.lang.AssertionError: Unexpected command: CLUSTER_ACTIVE 
> at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor.authorize(GridRestProcessor.java:817)
>  
> at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:250)
>  
> at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:91)
>  
> at 
> org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:157)
>  
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  
> at 
> {code}
> [^http://apache-ignite-users.70518.x6.nabble.com/Cannot-activate-Ignite-with-custom-security-plugin-tt17687.html]



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

[jira] [Created] (IGNITE-6741) GridRestProcessor doesn't support authorization on CLUSTER_ACTIVE command.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-6741:


 Summary: GridRestProcessor doesn't support authorization on 
CLUSTER_ACTIVE command.
 Key: IGNITE-6741
 URL: https://issues.apache.org/jira/browse/IGNITE-6741
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Affects Versions: 2.2
Reporter: Andrew Mashenkov


I've found we have a enum GridRestCommand.CLUSTER_ACTIVE, 
but looks like it is not supported by GridRestProcessor and 
enum SecurityPermission doesn't support any permission for cluster activation. 

Also CLUSTER_INACTIVE has same issues.

So, cluster can't be activated with security plugin due to ERROR.
See userlist thread for details [#\[1\]]

{code:java}
id=d2e2b816-61e3-47ff-9d88-ae4c8b3eb2ae, login=null 
10-23 20:48:30.051 [rest-#47%cdev_cluster%] ERROR 
internal.processors.rest.GridRestProcessor - Client request execution failed 
with error. 
java.lang.AssertionError: Unexpected command: CLUSTER_ACTIVE 
at 
org.apache.ignite.internal.processors.rest.GridRestProcessor.authorize(GridRestProcessor.java:817)
 
at 
org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:250)
 
at 
org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:91)
 
at 
org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:157)
 
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
at 
{code}

[^http://apache-ignite-users.70518.x6.nabble.com/Cannot-activate-Ignite-with-custom-security-plugin-tt17687.html]



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

[jira] [Created] (IGNITE-6740) Java 9: rework DirectBuffer.address() usages

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6740:
---

 Summary: Java 9: rework DirectBuffer.address() usages
 Key: IGNITE-6740
 URL: https://issues.apache.org/jira/browse/IGNITE-6740
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: general
Reporter: Vladimir Ozerov
 Fix For: 2.4


We have two usages of {{DirectBuffer.address()}} method which is no longer 
accessible in Java 9: 
1) {{DirectByteBufferStreamImplV1}}
2) {{DirectByteBufferStreamImplV2}}

Need to rework this code using reflection and/or {{Unsafe}}, so that it 
compiles and work on all Java versions.



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

[jira] [Comment Edited] (IGNITE-6723) ScalarCreditRiskExample failed with StackOverflowError

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-6723 at 10/24/17 2:28 PM:


*Root cause:* {{StackOverflowError}} on serialization scala sequence collection 
(because Ignite binary serializer doesn't handle scala's linked list as 
collections, so the collection with 5K elements is too deep for ordinary object 
serialization).
*Fix:* change type to Array for member of the serialized closure.

[Examples tests 
results|https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2919%2Fhead]

[~vozerov], [~kuaw26], please review the patch.


was (Author: tledkov-gridgain):
*Root cause:* {{StackOverflowError}} on serialization scala sequence collection.
*Fix:* change type to Array for member of the serialized closure.

[Examples tests 
results|https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2919%2Fhead]


> ScalarCreditRiskExample failed with StackOverflowError
> --
>
> Key: IGNITE-6723
> URL: https://issues.apache.org/jira/browse/IGNITE-6723
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: examples
>Affects Versions: 2.3
>Reporter: Sergey Kozlov
>Priority: Critical
> Fix For: 2.3
>
>
> 1. Open in IDEA {{ignite-examples}} project
> 2. Start {{ExampleNodeStartup}}
> 3. Run {{ScalarCreditRiskExample}}. It fails:
> {noformat}
> java.lang.StackOverflowError
>   at java.util.IdentityHashMap.maskNull(IdentityHashMap.java:192)
>   at java.util.IdentityHashMap.put(IdentityHashMap.java:426)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterHandles.put(BinaryWriterHandles.java:88)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.tryWriteAsHandle(BinaryWriterExImpl.java:1879)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.preWrite(BinaryClassDescriptor.java:888)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:790)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>  

[jira] [Commented] (IGNITE-6723) ScalarCreditRiskExample failed with StackOverflowError

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-6723:
--

*Root cause:* {{StackOverflowError}} on serialization scala sequence collection.
*Fix:* change type to Array for member of the serialized closure.

[Examples tests 
results|https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2919%2Fhead]


> ScalarCreditRiskExample failed with StackOverflowError
> --
>
> Key: IGNITE-6723
> URL: https://issues.apache.org/jira/browse/IGNITE-6723
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: examples
>Affects Versions: 2.3
>Reporter: Sergey Kozlov
>Priority: Critical
> Fix For: 2.3
>
>
> 1. Open in IDEA {{ignite-examples}} project
> 2. Start {{ExampleNodeStartup}}
> 3. Run {{ScalarCreditRiskExample}}. It fails:
> {noformat}
> java.lang.StackOverflowError
>   at java.util.IdentityHashMap.maskNull(IdentityHashMap.java:192)
>   at java.util.IdentityHashMap.put(IdentityHashMap.java:426)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterHandles.put(BinaryWriterHandles.java:88)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.tryWriteAsHandle(BinaryWriterExImpl.java:1879)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.preWrite(BinaryClassDescriptor.java:888)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:790)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> 

[jira] [Commented] (IGNITE-6723) ScalarCreditRiskExample failed with StackOverflowError

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6723:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-6723: example fix: change type from scala sequence to scala Ar…

…ray for member of serialized closure

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

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

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

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


commit 6f4e31602ff073b71089fc688f09e0227a509478
Author: tledkov-gridgain 
Date:   2017-10-24T14:18:34Z

IGNITE-6723: example fix: change type from scala sequence to scala Array 
for member of serialized closure




> ScalarCreditRiskExample failed with StackOverflowError
> --
>
> Key: IGNITE-6723
> URL: https://issues.apache.org/jira/browse/IGNITE-6723
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: examples
>Affects Versions: 2.3
>Reporter: Sergey Kozlov
>Priority: Critical
> Fix For: 2.3
>
>
> 1. Open in IDEA {{ignite-examples}} project
> 2. Start {{ExampleNodeStartup}}
> 3. Run {{ScalarCreditRiskExample}}. It fails:
> {noformat}
> java.lang.StackOverflowError
>   at java.util.IdentityHashMap.maskNull(IdentityHashMap.java:192)
>   at java.util.IdentityHashMap.put(IdentityHashMap.java:426)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterHandles.put(BinaryWriterHandles.java:88)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.tryWriteAsHandle(BinaryWriterExImpl.java:1879)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.preWrite(BinaryClassDescriptor.java:888)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:790)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
>   at 
> org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
>   at 
> org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
>   at 
> org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)

[jira] [Created] (IGNITE-6739) Add tests verifying queries functionality is not broken if mvcc is enabled

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-6739:


 Summary: Add tests verifying queries functionality is not broken 
if mvcc is enabled
 Key: IGNITE-6739
 URL: https://issues.apache.org/jira/browse/IGNITE-6739
 Project: Ignite
  Issue Type: Sub-task
Reporter: Semen Boikov


Add tests verifying queries functionality is not broken if mvcc is enabled:
- full text indexes
- queries with indexing spi
- CacheConfiguration with setQueryParallelism
- lazy queries (SqlFieldsQuery.setLazy(true))
- collocated queries (SqlFieldsQuery.setCollocated)



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

[jira] [Created] (IGNITE-6738) Support mvcc filter for local sql queries

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-6738:


 Summary: Support mvcc filter for local sql queries
 Key: IGNITE-6738
 URL: https://issues.apache.org/jira/browse/IGNITE-6738
 Project: Ignite
  Issue Type: Sub-task
Reporter: Semen Boikov


Need receive/release mvcc version for queries with setLocal flag set, there are 
already some tests in CacheMvccSqlQueriesTest.



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

[jira] [Updated] (IGNITE-6737) GridDeploymentPerVersionStore retries loading class infinitely

[Vladislav Pyatkov (JIRA)]

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

Vladislav Pyatkov updated IGNITE-6737:
--
Description: 
{noformat}
2017-10-24 14:34:06 [DEBUG] 
[org.apache.ignite.internal.managers.deployment.GridDeploymentLocalStore] 
[pub-#5258%DPL_GRID%DplGridNodeName%] - Deployment meta for local deployment: 
GridDeploymentMetadata [depMode=SHARED, 
alias=com.sbt.bgp.task.AffinityApplicationTaskCallable, 
clsName=com.sbt.bgp.task.AffinityApplicationTaskCallable, userVer=null, 
sndNodeId=1b852edd-1f41-4489-af78-dbe8226a9b16, clsLdrId=null, clsLdr=null, 
participants=null, parentLdr=null, record=true, nodeFilter=null, seqNum=n/a]

2017-10-24 14:34:06 [DEBUG] 
[org.apache.ignite.internal.managers.deployment.GridDeploymentLocalStore] 
[pub-#5258%DPL_GRID%DplGridNodeName%] - Failed to load class for local 
auto-deployment 
[ldr=grid:com.sbt.core.envelope.container.FileClassLoader@3e4327dc, 
meta=GridDeploymentMetadata [depMode=SHARED, 
alias=com.sbt.bgp.task.AffinityApplicationTaskCallable, 
clsName=com.sbt.bgp.task.AffinityApplicationTaskCallable, userVer=null, 
sndNodeId=1b852edd-1f41-4489-af78-dbe8226a9b16, clsLdrId=null, clsLdr=null, 
participants=null, parentLdr=null, record=true, nodeFilter=null, seqNum=n/a]]

2017-10-24 14:34:06 [DEBUG] 
[org.apache.ignite.internal.managers.deployment.GridDeploymentPerVersionStore] 
[pub-#5258%DPL_GRID%DplGridNodeName%] - Deployment cannot be reused (class does 
not exist on participating nodes) [dep=SharedDeployment [rmv=false, 
super=GridDeployment [ts=1508810401226, depMode=SHARED, 
clsLdr=GridDeploymentClassLoader 
[id=7953e0c4f51-1b852edd-1f41-4489-af78-dbe8226a9b16, singleNode=false, 
nodeLdrMap={bc5a1eaa-e056-4bd8-b7d3-684e75522b81=373cd8c4f51-bc5a1eaa-e056-4bd8-b7d3-684e75522b81,
 
3018f0bb-7c94-410e-9a0f-028c3fbc8aab=a5b822c4f51-3018f0bb-7c94-410e-9a0f-028c3fbc8aab,
 
f1774f8d-84e9-43c3-86a3-d7a47c291f45=afd441c4f51-f1774f8d-84e9-43c3-86a3-d7a47c291f45,
 
5a0b56e8-a8ae-4742-834c-d688592866c4=a6e985c4f51-5a0b56e8-a8ae-4742-834c-d688592866c4,
 
65fdae9e-78c7-49a2-b9ee-a8e99dbb87ea=bcd257c4f51-65fdae9e-78c7-49a2-b9ee-a8e99dbb87ea,
 
045ddd4d-3e39-4b25-bf52-c264f59efbc6=e6ec81c4f51-045ddd4d-3e39-4b25-bf52-c264f59efbc6,
 
afadbbce-542d-435c-b85a-78d395b463a5=967664c4f51-afadbbce-542d-435c-b85a-78d395b463a5,
 
4b2662e9-d525-4d96-936c-8cc645464e65=591541c4f51-4b2662e9-d525-4d96-936c-8cc645464e65},
 p2pTimeout=5000, usrVer=0, depMode=SHARED, quiet=false], 
clsLdrId=7953e0c4f51-1b852edd-1f41-4489-af78-dbe8226a9b16, userVer=0, 
loc=false, 
sampleClsName=com.sbt.fea_cc.services.business.autoStopTurnkeySettings.AutoStopTurnkeySettingsService$FindOrderTurnkeyForSuspend,
 pendingUndeploy=false, undeployed=false, usage=0]], 
meta=GridDeploymentMetadata [depMode=SHARED, 
alias=com.sbt.bgp.task.AffinityApplicationTaskCallable, 
clsName=com.sbt.bgp.task.AffinityApplicationTaskCallable, userVer=0, 
sndNodeId=4457016c-5f93-450f-b2a7-86bd25f536cf, 
clsLdrId=898962c4f51-4457016c-5f93-450f-b2a7-86bd25f536cf, clsLdr=null, 
participants=null, parentLdr=null, record=true, nodeFilter=null, 
seqNum=150888744]]


2017-10-24 14:34:06 [DEBUG] 
[org.apache.ignite.internal.managers.deployment.GridDeploymentPerVersionStore] 
[pub-#5258%DPL_GRID%DplGridNodeName%] - Deployment cannot be reused (random 
class could not be loaded from sender node) [dep=SharedDeployment [rmv=false, 
super=GridDeployment [ts=1508810401226, depMode=SHARED, 
clsLdr=GridDeploymentClassLoader 
[id=7953e0c4f51-1b852edd-1f41-4489-af78-dbe8226a9b16, singleNode=false, 
nodeLdrMap={bc5a1eaa-e056-4bd8-b7d3-684e75522b81=373cd8c4f51-bc5a1eaa-e056-4bd8-b7d3-684e75522b81,
 
3018f0bb-7c94-410e-9a0f-028c3fbc8aab=a5b822c4f51-3018f0bb-7c94-410e-9a0f-028c3fbc8aab,
 
f1774f8d-84e9-43c3-86a3-d7a47c291f45=afd441c4f51-f1774f8d-84e9-43c3-86a3-d7a47c291f45,
 
5a0b56e8-a8ae-4742-834c-d688592866c4=a6e985c4f51-5a0b56e8-a8ae-4742-834c-d688592866c4,
 
65fdae9e-78c7-49a2-b9ee-a8e99dbb87ea=bcd257c4f51-65fdae9e-78c7-49a2-b9ee-a8e99dbb87ea,
 
045ddd4d-3e39-4b25-bf52-c264f59efbc6=e6ec81c4f51-045ddd4d-3e39-4b25-bf52-c264f59efbc6,
 
afadbbce-542d-435c-b85a-78d395b463a5=967664c4f51-afadbbce-542d-435c-b85a-78d395b463a5,
 
4b2662e9-d525-4d96-936c-8cc645464e65=591541c4f51-4b2662e9-d525-4d96-936c-8cc645464e65},
 p2pTimeout=5000, usrVer=0, depMode=SHARED, quiet=false], 
clsLdrId=7953e0c4f51-1b852edd-1f41-4489-af78-dbe8226a9b16, userVer=0, 
loc=false, 
sampleClsName=com.sbt.fea_cc.services.business.autoStopTurnkeySettings.AutoStopTurnkeySettingsService$FindOrderTurnkeyForSuspend,
 pendingUndeploy=false, undeployed=false, usage=0]], 
meta=GridDeploymentMetadata [depMode=SHARED, 
alias=com.sbt.bgp.task.AffinityApplicationTaskCallable, 
clsName=com.sbt.bgp.task.AffinityApplicationTaskCallable, userVer=0, 
sndNodeId=4457016c-5f93-450f-b2a7-86bd25f536cf, 
clsLdrId=898962c4f51-4457016c-5f93-450f-b2a7-86bd25f536cf, clsLdr=null, 
participants=null, 

[jira] [Created] (IGNITE-6737) GridDeploymentPerVersionStore retries loading class infinitely

[Vladislav Pyatkov (JIRA)]

Vladislav Pyatkov created IGNITE-6737:
-

 Summary: GridDeploymentPerVersionStore retries loading class 
infinitely
 Key: IGNITE-6737
 URL: https://issues.apache.org/jira/browse/IGNITE-6737
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Vladislav Pyatkov


{noformat}
2017-10-24 14:34:06 [DEBUG] 
[org.apache.ignite.internal.managers.deployment.GridDeploymentLocalStore] 
[pub-#5258%DPL_GRID%DplGridNodeName%] - Deployment meta for local deployment: 
GridDeploymentMetadata [depMode=SHARED, 
alias=com.sbt.bgp.task.AffinityApplicationTaskCallable, 
clsName=com.sbt.bgp.task.AffinityApplicationTaskCallable, userVer=null, 
sndNodeId=1b852edd-1f41-4489-af78-dbe8226a9b16, clsLdrId=null, clsLdr=null, 
participants=null, parentLdr=null, record=true, nodeFilter=null, seqNum=n/a]

2017-10-24 14:34:06 [DEBUG] 
[org.apache.ignite.internal.managers.deployment.GridDeploymentLocalStore] 
[pub-#5258%DPL_GRID%DplGridNodeName%] - Failed to load class for local 
auto-deployment [ldr=grid:com.sbt.core.envelope.container.FileCl
assLoader@3e4327dc, meta=GridDeploymentMetadata [depMode=SHARED, 
alias=com.sbt.bgp.task.AffinityApplicationTaskCallable, 
clsName=com.sbt.bgp.task.AffinityApplicationTaskCallable, userVer=null, 
sndNodeId=1b852edd-1f41-4489-af78-dbe8226a9b
16, clsLdrId=null, clsLdr=null, participants=null, parentLdr=null, record=true, 
nodeFilter=null, seqNum=n/a]]

2017-10-24 14:34:06 [DEBUG] 
[org.apache.ignite.internal.managers.deployment.GridDeploymentPerVersionStore] 
[pub-#5258%DPL_GRID%DplGridNodeName%] - Deployment cannot be reused (class does 
not exist on participating nodes) [dep=SharedDeployment [rmv=false, 
super=GridDeployment [ts=1508810401226, depMode=SHARED, 
clsLdr=GridDeploymentClassLoader 
[id=7953e0c4f51-1b852edd-1f41-4489-af78-dbe8226a9b16, singleNode=false, 
nodeLdrMap={bc5a1eaa-e056-4bd8-b7d3-684e75522b81=373cd8c4f51-bc5a1eaa-e056-4bd8-b7d3-684e75522b81,
 
3018f0bb-7c94-410e-9a0f-028c3fbc8aab=a5b822c4f51-3018f0bb-7c94-410e-9a0f-028c3fbc8aab,
 
f1774f8d-84e9-43c3-86a3-d7a47c291f45=afd441c4f51-f1774f8d-84e9-43c3-86a3-d7a47c291f45,
 
5a0b56e8-a8ae-4742-834c-d688592866c4=a6e985c4f51-5a0b56e8-a8ae-4742-834c-d688592866c4,
 
65fdae9e-78c7-49a2-b9ee-a8e99dbb87ea=bcd257c4f51-65fdae9e-78c7-49a2-b9ee-a8e99dbb87ea,
 
045ddd4d-3e39-4b25-bf52-c264f59efbc6=e6ec81c4f51-045ddd4d-3e39-4b25-bf52-c264f59efbc6,
 
afadbbce-542d-435c-b85a-78d395b463a5=967664c4f51-afadbbce-542d-435c-b85a-78d395b463a5,
 
4b2662e9-d525-4d96-936c-8cc645464e65=591541c4f51-4b2662e9-d525-4d96-936c-8cc645464e65},
 p2pTimeout=5000, usrVer=0, depMode=SHARED, quiet=false], 
clsLdrId=7953e0c4f51-1b852edd-1f41-4489-af78-dbe8226a9b16, userVer=0, 
loc=false, 
sampleClsName=com.sbt.fea_cc.services.business.autoStopTurnkeySettings.AutoStopTurnkeySettingsService$FindOrderTurnkeyForSuspend,
 pendingUndeploy=false, undeployed=false, usage=0]], 
meta=GridDeploymentMetadata [depMode=SHARED, 
alias=com.sbt.bgp.task.AffinityApplicationTaskCallable, 
clsName=com.sbt.bgp.task.AffinityApplicationTaskCallable, userVer=0, 
sndNodeId=4457016c-5f93-450f-b2a7-86bd25f536cf, 
clsLdrId=898962c4f51-4457016c-5f93-450f-b2a7-86bd25f536cf, clsLdr=null, 
participants=null, parentLdr=null, record=true, nodeFilter=null, 
seqNum=150888744]]


2017-10-24 14:34:06 [DEBUG] 
[org.apache.ignite.internal.managers.deployment.GridDeploymentPerVersionStore] 
[pub-#5258%DPL_GRID%DplGridNodeName%] - Deployment cannot be reused (random 
class could not be loaded from sender node) [dep=SharedDeployment [rmv=false, 
super=GridDeployment [ts=1508810401226, depMode=SHARED, 
clsLdr=GridDeploymentClassLoader 
[id=7953e0c4f51-1b852edd-1f41-4489-af78-dbe8226a9b16, singleNode=false, 
nodeLdrMap={bc5a1eaa-e056-4bd8-b7d3-684e75522b81=373cd8c4f51-bc5a1eaa-e056-4bd8-b7d3-684e75522b81,
 
3018f0bb-7c94-410e-9a0f-028c3fbc8aab=a5b822c4f51-3018f0bb-7c94-410e-9a0f-028c3fbc8aab,
 
f1774f8d-84e9-43c3-86a3-d7a47c291f45=afd441c4f51-f1774f8d-84e9-43c3-86a3-d7a47c291f45,
 
5a0b56e8-a8ae-4742-834c-d688592866c4=a6e985c4f51-5a0b56e8-a8ae-4742-834c-d688592866c4,
 
65fdae9e-78c7-49a2-b9ee-a8e99dbb87ea=bcd257c4f51-65fdae9e-78c7-49a2-b9ee-a8e99dbb87ea,
 
045ddd4d-3e39-4b25-bf52-c264f59efbc6=e6ec81c4f51-045ddd4d-3e39-4b25-bf52-c264f59efbc6,
 
afadbbce-542d-435c-b85a-78d395b463a5=967664c4f51-afadbbce-542d-435c-b85a-78d395b463a5,
 
4b2662e9-d525-4d96-936c-8cc645464e65=591541c4f51-4b2662e9-d525-4d96-936c-8cc645464e65},
 p2pTimeout=5000, usrVer=0, depMode=SHARED, quiet=false], 
clsLdrId=7953e0c4f51-1b852edd-1f41-4489-af78-dbe8226a9b16, userVer=0, 
loc=false, 
sampleClsName=com.sbt.fea_cc.services.business.autoStopTurnkeySettings.AutoStopTurnkeySettingsService$FindOrderTurnkeyForSuspend,
 pendingUndeploy=false, undeployed=false, usage=0]], 
meta=GridDeploymentMetadata [depMode=SHARED, 
alias=com.sbt.bgp.task.AffinityApplicationTaskCallable, 

[jira] [Updated] (IGNITE-6736) Java 9: rework GridCacheMapEntry synchronization logic to avoid Unsafe.monitor* methods

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6736:

Component/s: cache

> Java 9: rework GridCacheMapEntry synchronization logic to avoid 
> Unsafe.monitor* methods
> ---
>
> Key: IGNITE-6736
> URL: https://issues.apache.org/jira/browse/IGNITE-6736
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: cache
>Reporter: Vladimir Ozerov
> Fix For: 2.4
>
>
> {{GridCacheMapEntry}} class rely on {{synchronized}} on itself heavily. In 
> {{ATOMIC}} caches we lock multiple entries at once using 
> {{Unsafe.monitorEnter/Exit}} methods. Unfortunately these methods were 
> removed in Java 9. Recursion is not an option, as it would cause stack 
> overflow for {{putAll}} operations with multiple entries.
> Possible fixes:
> 1) Rework {{synchronized}} to {{ReentrantLock}}. Easy, but may cause 
> additional memory pressure.
> 2) Have different implementations for Java 8 ({{synchronzied}}) and Java 9 
> ({{ReentrantLock}}) - much more complex solution, because we will require 
> separate module for Java 8 and Java 9.
> 3) Rework {{ATOMIC}} caches, so that {{putAll}} operation updates entries 
> one-by-one. As a side effect it will eliminate deadlocks.



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

[jira] [Comment Edited] (IGNITE-6667) Allow discovery cache instance reuse if only minor topology change has occured.

[Alexei Scherbakov (JIRA)]

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

Alexei Scherbakov edited comment on IGNITE-6667 at 10/24/17 1:57 PM:
-

[~sboikov]

I've implemented flexible strategy for disco cache reuse, please take a look.

TC: https://ci.ignite.apache.org/viewQueued.html?itemId=909093 (still in queue)


was (Author: ascherbakov):
[~sboikov]

I've implemented flexible strategy for disco cache reuse, please take a look.

TC: https://ci.ignite.apache.org/viewQueued.html?itemId=906993 (still in queue)

> Allow discovery cache instance reuse if only minor topology change has 
> occured.
> ---
>
> Key: IGNITE-6667
> URL: https://issues.apache.org/jira/browse/IGNITE-6667
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>Affects Versions: 2.2
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
> Fix For: 2.4
>
>
> Currently we always recreating DiscoCache instance even if only minor 
> topology change has occured and cache may be reused.
> Profiling shows what initialization of such object tooks up tens of millis 
> which adds to ring latency delay and especially sensitive for large 
> topologies.
> Solution: reuse current discovery cache instance whenever possible.



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

[jira] [Created] (IGNITE-6736) Java 9: rework GridCacheMapEntry synchronization logic to avoid Unsafe.monitor* methods

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6736:
---

 Summary: Java 9: rework GridCacheMapEntry synchronization logic to 
avoid Unsafe.monitor* methods
 Key: IGNITE-6736
 URL: https://issues.apache.org/jira/browse/IGNITE-6736
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
Reporter: Vladimir Ozerov
 Fix For: 2.4


{{GridCacheMapEntry}} class rely on {{synchronized}} on itself heavily. In 
{{ATOMIC}} caches we lock multiple entries at once using 
{{Unsafe.monitorEnter/Exit}} methods. Unfortunately these methods were removed 
in Java 9. Recursion is not an option, as it would cause stack overflow for 
{{putAll}} operations with multiple entries.

Possible fixes:
1) Rework {{synchronized}} to {{ReentrantLock}}. Easy, but may cause additional 
memory pressure.
2) Have different implementations for Java 8 ({{synchronzied}}) and Java 9 
({{ReentrantLock}}) - much more complex solution, because we will require 
separate module for Java 8 and Java 9.
3) Rework {{ATOMIC}} caches, so that {{putAll}} operation updates entries 
one-by-one. As a side effect it will eliminate deadlocks.



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

[jira] [Commented] (IGNITE-6690) DiscoverySpi: Clientmode Ignite should not fail on handshake errors

[Alexey Popov (JIRA)]

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

Alexey Popov commented on IGNITE-6690:
--

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

The fix is ready.
1. It includes changes in ServerImpl and ClientImpl of SpiDiscovery with 
StreamCorruptedException
2. Unit tests are added
3. The special case when non-SSL client/server connects to SSL-enabled server 
is handled as before. It is done by looking at StreamCorruptedException message 
to check for SSL Alarm message pattern

> DiscoverySpi: Clientmode Ignite should not fail on handshake errors
> ---
>
> Key: IGNITE-6690
> URL: https://issues.apache.org/jira/browse/IGNITE-6690
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: general
>Affects Versions: 2.2
>Reporter: Alexey Popov
>Assignee: Alexey Popov
>  Labels: discovery
> Fix For: 2.4
>
>
> Ignite in Client mode should not fail on handshake unmarshalling errors. It 
> should go to the next IP/port from ipFinder list
> http://apache-ignite-developers.2346864.n4.nabble.com/DiscoverySpi-Handshake-unmarshalling-errors-at-Client-client-mode-td23467.html



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

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

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6735:
---

 Summary: Java 9: fix Java version resolution/check logic
 Key: IGNITE-6735
 URL: https://issues.apache.org/jira/browse/IGNITE-6735
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: general
Reporter: Vladimir Ozerov
 Fix For: 2.4


We have several places in the code where Java version is validated. First, 
sometimes we do not take in count Java 9 at all. Second, sometimes we rely on 
old version pattern {{1.x}}, while as of Java 9 it is just {{x}}. 

Places to fix:
1) {{GridDiscoveryManager.nodeJavaMajorVersion}} - add support for new Java 
version format without {{1.}} prefix.
2) {{IgnitionEx.}} - add Java 9 to the list of supported versions.



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

[jira] [Assigned] (IGNITE-6607) Thin client: protocol documentation

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-6607:
--

Assignee: (was: Pavel Tupitsyn)

> Thin client: protocol documentation
> ---
>
> Key: IGNITE-6607
> URL: https://issues.apache.org/jira/browse/IGNITE-6607
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
> Fix For: 2.3
>
>
> Document thin client protocol on Ignite wiki: 
> https://cwiki.apache.org/confluence/display/IGNITE/Design+Documents
> * Common message format (length, flags)
> * Data types (endianness, strings, etc)
> * Request/Response format for each message type
> * How to connect



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

[jira] [Commented] (IGNITE-6704) .NET: CacheConfiguration.KeyConfiguration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6704:


Github user asfgit closed the pull request at:

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


> .NET: CacheConfiguration.KeyConfiguration
> -
>
> Key: IGNITE-6704
> URL: https://issues.apache.org/jira/browse/IGNITE-6704
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Propagate {{CacheCofiguration.KeyConfiguration}} to .NET, see IGNITE-5458



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

[jira] [Updated] (IGNITE-6734) Java 9: do not use sun.misc.BASE64Encoder

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6734:

Description: 
For some reason we use {{sun.misc.BASE64Encoder}} in several places:
1) {{jiraslurp.groovy}}
2) Several REST-related classes in {{ignite-clients}} module.

Need to remove this usages and use {{Base64}}. Note that this class is 
available since Java 8. Hopefully we will move to Java 8 in the same release. 
Otherwise we will have to apply some reflection-based hacks, I think.

  was:
For some reason we use {{sun.misc.BASE64Encoder}} in several places:
1) {{jiraslurp.groovy}}
2) Several REST-related classes in {{ignite-clients}} module.

Need to remove this usages and use {{Base64}}. Note that this class is 
available since Java 8. Hopefully we will move to Java 8 in the same release. 
Otherwise we will should think of using some 3-rd party dependency in 
{{clients}} module.


> Java 9: do not use sun.misc.BASE64Encoder
> -
>
> Key: IGNITE-6734
> URL: https://issues.apache.org/jira/browse/IGNITE-6734
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: general, rest
>Reporter: Vladimir Ozerov
> Fix For: 2.4
>
>
> For some reason we use {{sun.misc.BASE64Encoder}} in several places:
> 1) {{jiraslurp.groovy}}
> 2) Several REST-related classes in {{ignite-clients}} module.
> Need to remove this usages and use {{Base64}}. Note that this class is 
> available since Java 8. Hopefully we will move to Java 8 in the same release. 
> Otherwise we will have to apply some reflection-based hacks, I think.



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

[jira] [Commented] (IGNITE-6704) .NET: CacheConfiguration.KeyConfiguration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6704:


TC is fine, merged to master: {{5b3ad97b939bee6f3e272f93c75e920208cb7491}}.

> .NET: CacheConfiguration.KeyConfiguration
> -
>
> Key: IGNITE-6704
> URL: https://issues.apache.org/jira/browse/IGNITE-6704
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Propagate {{CacheCofiguration.KeyConfiguration}} to .NET, see IGNITE-5458



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

[jira] [Resolved] (IGNITE-6704) .NET: CacheConfiguration.KeyConfiguration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-6704.

Resolution: Fixed

> .NET: CacheConfiguration.KeyConfiguration
> -
>
> Key: IGNITE-6704
> URL: https://issues.apache.org/jira/browse/IGNITE-6704
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Propagate {{CacheCofiguration.KeyConfiguration}} to .NET, see IGNITE-5458



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

[jira] [Updated] (IGNITE-6734) Java 9: do not use sun.misc.BASE64Encoder

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6734:

Description: 
For some reason we use {{sun.misc.BASE64Encoder}} in several places:
1) {{jiraslurp.groovy}}
2) Several REST-related classes in {{ignite-clients}} module.

Need to remove this usages and use {{Base64}}. Note that this class is 
available since Java 8. Hopefully we will move to Java 8 in the same release. 
Otherwise we will should think of using some 3-rd party dependency in 
{{clients}} module.

  was:
For some reason we use {{sun.misc.BASE64Encoder}} in several places:
1) {{jiraslurp.groovy}}
2) Several REST-related classes in {{ignite-clients}} module.

Need to remove this usages and use {{Base64}}. Note that this class is 
available since Java 8. Hopefully we will move to Java 8 in the same release.


> Java 9: do not use sun.misc.BASE64Encoder
> -
>
> Key: IGNITE-6734
> URL: https://issues.apache.org/jira/browse/IGNITE-6734
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: general, rest
>Reporter: Vladimir Ozerov
> Fix For: 2.4
>
>
> For some reason we use {{sun.misc.BASE64Encoder}} in several places:
> 1) {{jiraslurp.groovy}}
> 2) Several REST-related classes in {{ignite-clients}} module.
> Need to remove this usages and use {{Base64}}. Note that this class is 
> available since Java 8. Hopefully we will move to Java 8 in the same release. 
> Otherwise we will should think of using some 3-rd party dependency in 
> {{clients}} module.



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

[jira] [Created] (IGNITE-6734) Java 9: do not use sun.misc.BASE64Encoder

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6734:
---

 Summary: Java 9: do not use sun.misc.BASE64Encoder
 Key: IGNITE-6734
 URL: https://issues.apache.org/jira/browse/IGNITE-6734
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: general, rest
Reporter: Vladimir Ozerov
 Fix For: 2.4


For some reason we use {{sun.misc.BASE64Encoder}} in several places:
1) {{jiraslurp.groovy}}
2) Several REST-related classes in {{ignite-clients}} module.

Need to remove this usages and use {{Base64}}. Note that this class is 
available since Java 8. Hopefully we will move to Java 8 in the same release.



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

[jira] [Commented] (IGNITE-6692) Select query on a client with unused field throws an exception.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6692:


GitHub user NSAmelchev opened a pull request:

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

IGNITE-6692



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

$ git pull https://github.com/NSAmelchev/ignite ignite-6692

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

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


commit cec27198db24c1f02152296ac1a74d60cfd899d2
Author: NSAmelchev 
Date:   2017-10-24T11:53:53Z

add test and fix




> Select query on a client with unused field throws an exception.
> ---
>
> Key: IGNITE-6692
> URL: https://issues.apache.org/jira/browse/IGNITE-6692
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
> Attachments: IgniteClientQueryTest.java
>
>
> Steps to reproduce:
> 1. Run one server, one client.
> 2. Execute next queries on a client:
> {{CREATE TABLE t1 (name VARCHAR(1), unused LONG, PRIMARY KEY(name))}}
> {{INSERT INTO t1 (name) values ('A')}}
> 3. Run select that throws an exception: 
> {{SELECT name FROM t1 ORDER BY name, unused}}
> Test is in attachment. 



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

[jira] [Created] (IGNITE-6733) Hadoop: support Java 9 distrbution

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6733:
---

 Summary: Hadoop: support Java 9 distrbution
 Key: IGNITE-6733
 URL: https://issues.apache.org/jira/browse/IGNITE-6733
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: hadoop
Affects Versions: 2.4
Reporter: Vladimir Ozerov


See IGNITE-6732 for more information. Now it is time to add full Java 9 support.



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

[jira] [Created] (IGNITE-6732) Java 9: Hadoop module should not start on Java 9

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6732:
---

 Summary: Java 9: Hadoop module should not start on Java 9
 Key: IGNITE-6732
 URL: https://issues.apache.org/jira/browse/IGNITE-6732
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: hadoop
Affects Versions: 2.3
Reporter: Vladimir Ozerov
 Fix For: 2.4


Hadoop module heavily relies on the fact that application class loader is 
{{URLClassLoader}}. It is used to inspect class path and hack it in various 
ways. But in Java 9 another class loader type is used. 

Looks like there is no simple solution at the moment. Let's check for Java 
version during startup and throw an exception if it Java 9 or later.



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

[jira] [Commented] (IGNITE-6729) Java 9: fix IgniteUtils#close(URLClassLoader, IgniteLogger)

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6729:
-

According to bug description [1], it would be enough to simply call 
{{URLClassLoader.close()}} method.

[1] http://bugs.java.com/bugdatabase/view_bug.do?bug_id=5041014

> Java 9: fix IgniteUtils#close(URLClassLoader, IgniteLogger)
> ---
>
> Key: IGNITE-6729
> URL: https://issues.apache.org/jira/browse/IGNITE-6729
> Project: Ignite
>  Issue Type: Task
>  Security Level: Public(Viewable by anyone) 
>  Components: general
>Affects Versions: 2.3
>Reporter: Vladimir Ozerov
> Fix For: 2.4
>
>
> This method use some internal API which is no longer accessible to cleanup 
> {{URLCLassLoader}} properly. The only usage of this method is in 
> {{GridUriDeploymentFileProcessor}} class.



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

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

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6731:
---

 Summary: Java 9: remove sun.misc.PerfCounter usages
 Key: IGNITE-6731
 URL: https://issues.apache.org/jira/browse/IGNITE-6731
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: hadoop
Affects Versions: 2.3
Reporter: Vladimir Ozerov
 Fix For: 2.4


This class is used in Hadoop module only:
1) {{HadoopClassLoader}}
2) {{HadoopTestClassLoader}}

Need to understand whether it is safe to simply remove this calls. Most 
probably - yes.



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

[jira] [Created] (IGNITE-6730) Java 9: fix project build procedure

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6730:
---

 Summary: Java 9: fix project build procedure
 Key: IGNITE-6730
 URL: https://issues.apache.org/jira/browse/IGNITE-6730
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: build
Affects Versions: 2.3
Reporter: Vladimir Ozerov
 Fix For: 2.4


1) In most modules compiler level is set to 1.7 explicitly. Should we fix it 
somehow? See commit {{a450452e}} for reference.
2) Most probably we will have separate code flows for Java 7/8 and Java 9. Need 
to understand how to organize this. Most probably we will have two pluggable 
modules producing separate JARs, which will be linked in runtime. Any other 
ideas?



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

[jira] [Created] (IGNITE-6729) Java 9: fix IgniteUtils#close(URLClassLoader, IgniteLogger)

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6729:
---

 Summary: Java 9: fix IgniteUtils#close(URLClassLoader, 
IgniteLogger)
 Key: IGNITE-6729
 URL: https://issues.apache.org/jira/browse/IGNITE-6729
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
  Components: general
Affects Versions: 2.3
Reporter: Vladimir Ozerov
 Fix For: 2.4


This method use some internal API which is no longer accessible to cleanup 
{{URLCLassLoader}} properly. The only usage of this method is in 
{{GridUriDeploymentFileProcessor}} class.



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

[jira] [Commented] (IGNITE-5553) Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov commented on IGNITE-5553:
--

Indeed, we can put current set size into set header cache entry. This will fix 
size(), but we have broken iterator() implementation as well.

Currently, set implementation maintains plain Java sets on every node, see 
CacheDataStructuresManager.setDataMap. These sets duplicate backing-cache 
entries, both primary and backup. size() and iterator() calls issue distributed 
queries to collect/filter data from all setDataMap's. And setDataMaps remain 
empty after cluster is recovered from checkpoint.

Now I see the following options to fix the issue.

#1 - Naive. Iterate over all datastructure-backing caches entries during 
recover from checkpoint procedure, filter set-related entries and refill 
setDataMap's.
Pros: easy to implement
Cons: inpredictable time/memory overhead.

#2 - More realistic. Avoid node-local copies of cache data. Maintain linked 
list in datastructure-backing cache: key is set item, value is next set item. 
List head is stored in set header cache entry (this set item is youngest one). 
Iterators build on top of this structure are fail-fast.
Pros: less memory overhead, no need to maintain node-local mirrors of cache data
Cons: iterators are not fail-safe.

#3 - Option #2 modified. We can store reference counter and 'removed' flag 
along with next item reference. This allows to make iterators fail safe.
Pros: iterators are fail-safe
Cons: slightly more complicated implementation, may affect performance, also I 
see no way to handle active iterators on remote nodes failures.

[~sergey-chugunov], any thoughts? Or maybe we should discuss this on devlist?

> Ignite PDS 2: IgnitePersistentStoreDataStructuresTest testSet assertion error
> -
>
> Key: IGNITE-5553
> URL: https://issues.apache.org/jira/browse/IGNITE-5553
> Project: Ignite
>  Issue Type: Bug
>  Components: data structures, persistence
>Affects Versions: 2.1
>Reporter: Dmitriy Pavlov
>Assignee: Andrey Kuznetsov
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-fail
>
> h2. Notes-4435
> When IgniteSet is restored from persistence, size of set is always 0, [link 
> to test 
> history|http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-7043871603266099589=testDetails].
> h2. Detailed description
> Unlike *IgniteQueue* which uses separate cache key to store its size 
> *IgniteSet* stores it in a field of some class.
> Test from the link above shows very clearly that after restoring memory state 
> from PDS all set values are restored correctly but size is lost.
> h2. Proposed solution
> One possible solution might be to do the same thing as *IgniteQueue* does: 
> size of *IgniteSet* must be stored is cache instead of volatile in-memory 
> fields of random classes.



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

[jira] [Assigned] (IGNITE-6724) PersistentStoreExample is broken

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk reassigned IGNITE-6724:


Assignee: Alexey Goncharuk

> PersistentStoreExample is broken
> 
>
> Key: IGNITE-6724
> URL: https://issues.apache.org/jira/browse/IGNITE-6724
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: examples
>Affects Versions: 2.3
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.3
>
>
> 1. Open in IDEA {{ignite-examples}} project
> 2. Start {{PersistentStoreExampleNodeStartup}}
> 3. Run {{PersistentStoreExample}}. Looks like it does nothing for now:
> {noformat}
> 14:50:46] Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=7.1GB]
> SQL Result: []
> GET Result: null
> [14:50:47] Ignite node stopped OK [uptime=00:00:01.181]
> {noformat}



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

[jira] [Resolved] (IGNITE-6724) PersistentStoreExample is broken

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk resolved IGNITE-6724.
--
Resolution: Fixed

Fixed in master and ignite-2.3

> PersistentStoreExample is broken
> 
>
> Key: IGNITE-6724
> URL: https://issues.apache.org/jira/browse/IGNITE-6724
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: examples
>Affects Versions: 2.3
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.3
>
>
> 1. Open in IDEA {{ignite-examples}} project
> 2. Start {{PersistentStoreExampleNodeStartup}}
> 3. Run {{PersistentStoreExample}}. Looks like it does nothing for now:
> {noformat}
> 14:50:46] Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=7.1GB]
> SQL Result: []
> GET Result: null
> [14:50:47] Ignite node stopped OK [uptime=00:00:01.181]
> {noformat}



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

[jira] [Commented] (IGNITE-6724) PersistentStoreExample is broken

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-6724:
--

The reason is wrong UPDATE flag value.

> PersistentStoreExample is broken
> 
>
> Key: IGNITE-6724
> URL: https://issues.apache.org/jira/browse/IGNITE-6724
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: examples
>Affects Versions: 2.3
>Reporter: Sergey Kozlov
>Assignee: Alexey Goncharuk
>Priority: Critical
> Fix For: 2.3
>
>
> 1. Open in IDEA {{ignite-examples}} project
> 2. Start {{PersistentStoreExampleNodeStartup}}
> 3. Run {{PersistentStoreExample}}. Looks like it does nothing for now:
> {noformat}
> 14:50:46] Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=7.1GB]
> SQL Result: []
> GET Result: null
> [14:50:47] Ignite node stopped OK [uptime=00:00:01.181]
> {noformat}



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

[jira] [Created] (IGNITE-6728) Support Java 9

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-6728:
---

 Summary: Support Java 9
 Key: IGNITE-6728
 URL: https://issues.apache.org/jira/browse/IGNITE-6728
 Project: Ignite
  Issue Type: Task
  Security Level: Public (Viewable by anyone)
Affects Versions: 2.3
Reporter: Vladimir Ozerov
 Fix For: 2.4


Currently Ignite cannot be used with Java 9 because it relies on some JDK 
internal API which is no longer accessible. We need to make sure that Ignite 
can be used with Java 9. 

This is an umbrella ticket for this activity.



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

[jira] [Commented] (IGNITE-6720) Move operation with file system outside checkpoint write lock

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov commented on IGNITE-6720:
-

[~EdShangGG], [~agoncharuk],
I reviewed the PR, it looks good. If TC results don't show any degradation 
please proceed with merging the change.

> Move operation with file system outside checkpoint write lock
> -
>
> Key: IGNITE-6720
> URL: https://issues.apache.org/jira/browse/IGNITE-6720
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>
> There could be long-running operation in onMarkCheckPointBegin call.
> So, to move them outside write lock holding block make possible make some 
> operations possible to async (for example, making onMarkCheckPointBegin 
> return Future).
> During this block is in progress no caches updated are allowed.



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

[jira] [Commented] (IGNITE-6704) .NET: CacheConfiguration.KeyConfiguration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6704:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-6704 .NET: CacheConfiguration.KeyConfiguration



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

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

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

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


commit ad197eea4c74641e5a70f5b0080213e8a9dbaead
Author: Pavel Tupitsyn 
Date:   2017-10-23T15:28:33Z

IGNITE-6704 .NET: CacheConfiguration.KeyConfiguration

commit 8b8632f8429a9f9e2e112b482ed8513fe3b0512b
Author: Pavel Tupitsyn 
Date:   2017-10-23T15:30:02Z

wip tests

commit 0f4084d92f95683875b40edf4f42547d4801d041
Author: Pavel Tupitsyn 
Date:   2017-10-23T16:10:18Z

wip

commit d9dccc5e29bb7a09a889819b38d51c6a270022af
Author: Pavel Tupitsyn 
Date:   2017-10-23T16:21:33Z

wip tests

commit ad2e19a48c07278efbfe6648e7e2c8078ce27f87
Author: Pavel Tupitsyn 
Date:   2017-10-24T10:12:20Z

wip affinity tests

commit 4b9ab1e63636aeaae732607a90ef0a816428aef4
Author: Pavel Tupitsyn 
Date:   2017-10-24T10:16:29Z

wip aff tests

commit 7439681cd28dd6b5753bab6482a8dd8f2139677e
Author: Pavel Tupitsyn 
Date:   2017-10-24T10:28:08Z

wip tests

commit 90623ca2128fe89ec691e4b63e62cfbb493108cb
Author: Pavel Tupitsyn 
Date:   2017-10-24T10:33:48Z

Refactor reflection utils

commit 8a97d7061194edf76f81dd9e19b99ac348d647c7
Author: Pavel Tupitsyn 
Date:   2017-10-24T10:48:56Z

wip tests

commit 0b83b3f9fcc4db13e17d5416f66518e205c4fffe
Author: Pavel Tupitsyn 
Date:   2017-10-24T10:49:16Z

wip tests

commit d784a5f008a1fdf92f5c6ea56480040ab1566f77
Author: Pavel Tupitsyn 
Date:   2017-10-24T10:51:24Z

wip tests

commit dda092aedc452848b2ac8dc9bcf8f01d012e8b57
Author: Pavel Tupitsyn 
Date:   2017-10-24T11:15:24Z

wip configs

commit 76cf2432435c6ed940c1a5d9afa29a5935c87628
Author: Pavel Tupitsyn 
Date:   2017-10-24T11:49:09Z

wip configs

commit 6164fcde7713e8f1c1e7de71994842939b105a67
Author: Pavel Tupitsyn 
Date:   2017-10-24T11:52:25Z

wip

commit e4f48640fc2d8f3fc718adb86f700293438aaa8b
Author: Pavel Tupitsyn 
Date:   2017-10-24T11:54:00Z

java part done

commit 719a65b41dfed7426ac7c4cd94429c41207aafaa
Author: Pavel Tupitsyn 
Date:   2017-10-24T11:55:55Z

wip tests

commit 21f5172ba47d8b503e6445f71bef13114896a3f5
Author: Pavel Tupitsyn 
Date:   2017-10-24T12:15:45Z

Fix stackoverflow in AssertReflectionEqual

commit eee1060b3b09c66f0482b36dc2bbdbe355835d31
Author: Pavel Tupitsyn 
Date:   2017-10-24T12:18:01Z

wip

commit 1613648c62559f83780609fe933a388be793fc1f
Author: Pavel Tupitsyn 
Date:   2017-10-24T12:31:05Z

fix java part

commit 777af9a0d0a2bbefb3f20a247dbc7144b990786c
Author: Pavel Tupitsyn 
Date:   2017-10-24T12:34:50Z

wip

commit 961bfe03a8026874d5c1289b8fdd04f172b51be2
Author: Pavel Tupitsyn 
Date:   2017-10-24T12:39:47Z

wip write refactoring

commit ea0a5cee5e606560d25512655f165524ce1fe866
Author: Pavel Tupitsyn 
Date:   2017-10-24T12:40:33Z

wip configs




> .NET: CacheConfiguration.KeyConfiguration
> -
>
> Key: IGNITE-6704
> URL: https://issues.apache.org/jira/browse/IGNITE-6704
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.4
>
>
> Propagate {{CacheCofiguration.KeyConfiguration}} to .NET, see IGNITE-5458



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

[jira] [Resolved] (IGNITE-6660) Python Redis example fails for python 3 run

[Nikolay Tikhonov (JIRA)]

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

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

[~oleg-ostanin],
Thank you for your contribution! I've merged your changes to master.

> Python Redis example fails for python 3 run
> ---
>
> Key: IGNITE-6660
> URL: https://issues.apache.org/jira/browse/IGNITE-6660
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: examples
>Affects Versions: 1.8, 1.9, 2.0, 2.1, 2.2
>Reporter: Sergey Kozlov
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> Looks like python redis example fails due to design python 2. But for python 
> 3 run raised the following error:
> {noformat}
>   File 
> "/var/lib/teamcity/data/work/17028f058b6ef75f/i2test/var/suite-examples/gg-pro-fab/examples/redis/redis-example.py",
>  line 32
> print 'Value for "k1": %s' % r.get('k1')
>  ^
> SyntaxError: invalid syntax
> {noformat}
> The suggested fix is to put brackets for print calls: 
> -{{print 'Value for "k1": %s' % r.get('k1')}}-
> {{print('Value for "k1": %s' % r.get('k1'))}}



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

[jira] [Updated] (IGNITE-6726) Licenses for Sqlline are missing

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6726:

Affects Version/s: 2.3

> Licenses for Sqlline are missing
> 
>
> Key: IGNITE-6726
> URL: https://issues.apache.org/jira/browse/IGNITE-6726
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: build
>Affects Versions: 2.3
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> Licenses for Sqlline are missing



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

[jira] [Updated] (IGNITE-6726) Licenses for Sqlline are missing

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6726:

Component/s: build

> Licenses for Sqlline are missing
> 
>
> Key: IGNITE-6726
> URL: https://issues.apache.org/jira/browse/IGNITE-6726
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: build
>Affects Versions: 2.3
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> Licenses for Sqlline are missing



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

[jira] [Updated] (IGNITE-6726) Licenses for Sqlline are missing

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6726:

Fix Version/s: 2.3

> Licenses for Sqlline are missing
> 
>
> Key: IGNITE-6726
> URL: https://issues.apache.org/jira/browse/IGNITE-6726
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Reporter: Oleg Ostanin
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> Licenses for Sqlline are missing



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

[jira] [Created] (IGNITE-6727) Ignite assembly should not require ignite-tools installation

[Anton Vinogradov (JIRA)]

Anton Vinogradov created IGNITE-6727:


 Summary: Ignite assembly should not require ignite-tools 
installation
 Key: IGNITE-6727
 URL: https://issues.apache.org/jira/browse/IGNITE-6727
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
Reporter: Anton Vinogradov
Assignee: Oleg Ostanin


Need to research how to solve this.



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

[jira] [Created] (IGNITE-6726) Licenses for Sqlline are missing

[Oleg Ostanin (JIRA)]

Oleg Ostanin created IGNITE-6726:


 Summary: Licenses for Sqlline are missing
 Key: IGNITE-6726
 URL: https://issues.apache.org/jira/browse/IGNITE-6726
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Oleg Ostanin
Assignee: Oleg Ostanin


Licenses for Sqlline are missing



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

[jira] [Updated] (IGNITE-6727) Ignite assembly should not require ignite-tools installation

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-6727:
-
Fix Version/s: 2.4

> Ignite assembly should not require ignite-tools installation
> 
>
> Key: IGNITE-6727
> URL: https://issues.apache.org/jira/browse/IGNITE-6727
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>Reporter: Anton Vinogradov
>Assignee: Oleg Ostanin
> Fix For: 2.4
>
>
> Need to research how to solve this.



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

[jira] [Commented] (IGNITE-6660) Python Redis example fails for python 3 run

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6660:


Github user asfgit closed the pull request at:

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


> Python Redis example fails for python 3 run
> ---
>
> Key: IGNITE-6660
> URL: https://issues.apache.org/jira/browse/IGNITE-6660
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: examples
>Affects Versions: 1.8, 1.9, 2.0, 2.1, 2.2
>Reporter: Sergey Kozlov
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> Looks like python redis example fails due to design python 2. But for python 
> 3 run raised the following error:
> {noformat}
>   File 
> "/var/lib/teamcity/data/work/17028f058b6ef75f/i2test/var/suite-examples/gg-pro-fab/examples/redis/redis-example.py",
>  line 32
> print 'Value for "k1": %s' % r.get('k1')
>  ^
> SyntaxError: invalid syntax
> {noformat}
> The suggested fix is to put brackets for print calls: 
> -{{print 'Value for "k1": %s' % r.get('k1')}}-
> {{print('Value for "k1": %s' % r.get('k1'))}}



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

[jira] [Created] (IGNITE-6725) Source release should be fixed

[Anton Vinogradov (JIRA)]

Anton Vinogradov created IGNITE-6725:


 Summary: Source release should be fixed
 Key: IGNITE-6725
 URL: https://issues.apache.org/jira/browse/IGNITE-6725
 Project: Ignite
  Issue Type: Improvement
  Security Level: Public (Viewable by anyone)
Reporter: Anton Vinogradov
Assignee: Oleg Ostanin
Priority: Critical
 Fix For: 2.4


I see a lot of garbage at source release.

Now source releasing using maven magic. 
Sources generation logic should be replaced with "git, give me source and I'll 
zip what you provide".  



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

[jira] [Created] (IGNITE-6724) PersistentStoreExample is broken

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-6724:
-

 Summary: PersistentStoreExample is broken
 Key: IGNITE-6724
 URL: https://issues.apache.org/jira/browse/IGNITE-6724
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: examples
Affects Versions: 2.3
Reporter: Sergey Kozlov
Priority: Critical
 Fix For: 2.3


1. Open in IDEA {{ignite-examples}} project
2. Start {{PersistentStoreExampleNodeStartup}}
3. Run {{PersistentStoreExample}}. Looks like it does nothing for now:
{noformat}
14:50:46] Topology snapshot [ver=2, servers=1, clients=1, CPUs=8, heap=7.1GB]
SQL Result: []
GET Result: null
[14:50:47] Ignite node stopped OK [uptime=00:00:01.181]
{noformat}



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

[jira] [Created] (IGNITE-6723) ScalarCreditRiskExample failed with StackOverflowError

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-6723:
-

 Summary: ScalarCreditRiskExample failed with StackOverflowError
 Key: IGNITE-6723
 URL: https://issues.apache.org/jira/browse/IGNITE-6723
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: examples
Affects Versions: 2.3
Reporter: Sergey Kozlov
Priority: Critical
 Fix For: 2.3


1. Open in IDEA {{ignite-examples}} project
2. Start {{ExampleNodeStartup}}
3. Run {{ScalarCreditRiskExample}}. It fails:
{noformat}
java.lang.StackOverflowError
at java.util.IdentityHashMap.maskNull(IdentityHashMap.java:192)
at java.util.IdentityHashMap.put(IdentityHashMap.java:426)
at 
org.apache.ignite.internal.binary.BinaryWriterHandles.put(BinaryWriterHandles.java:88)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.tryWriteAsHandle(BinaryWriterExImpl.java:1879)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.preWrite(BinaryClassDescriptor.java:888)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:790)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
at 
org.apache.ignite.internal.binary.BinaryClassDescriptor.write(BinaryClassDescriptor.java:793)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal0(BinaryWriterExImpl.java:206)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:147)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.marshal(BinaryWriterExImpl.java:134)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.doWriteObject(BinaryWriterExImpl.java:496)
at 
org.apache.ignite.internal.binary.BinaryWriterExImpl.writeObjectField(BinaryWriterExImpl.java:1160)
at 
org.apache.ignite.internal.binary.BinaryFieldAccessor$DefaultFinalClassAccessor.write(BinaryFieldAccessor.java:663)
at 

[jira] [Assigned] (IGNITE-6692) Select query on a client with unused field throws an exception.

[Amelchev Nikita (JIRA)]

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

Amelchev Nikita reassigned IGNITE-6692:
---

Assignee: Amelchev Nikita

> Select query on a client with unused field throws an exception.
> ---
>
> Key: IGNITE-6692
> URL: https://issues.apache.org/jira/browse/IGNITE-6692
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
> Attachments: IgniteClientQueryTest.java
>
>
> Steps to reproduce:
> 1. Run one server, one client.
> 2. Execute next queries on a client:
> {{CREATE TABLE t1 (name VARCHAR(1), unused LONG, PRIMARY KEY(name))}}
> {{INSERT INTO t1 (name) values ('A')}}
> 3. Run select that throws an exception: 
> {{SELECT name FROM t1 ORDER BY name, unused}}
> Test is in attachment. 



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

[jira] [Commented] (IGNITE-6713) Ignite Cache 5 flaky test CacheRebalancingSelfTest.testDisableRebalancing()

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6713:


GitHub user dspavlov opened a pull request:

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

IGNITE-6713: Ignite Cache 5 flaky test CacheRebalancingSelfTest.testD…

…isableRebalancing()

Full sync added, standalone suite for mass test startup

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

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

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

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


commit 6330ba221251f3d8d24868f38ea1fed18b5dd41b
Author: dpavlov 
Date:   2017-10-24T11:40:43Z

IGNITE-6713: Ignite Cache 5 flaky test 
CacheRebalancingSelfTest.testDisableRebalancing()
Full sync added, standalone suite for mass test startup




> Ignite Cache 5 flaky test CacheRebalancingSelfTest.testDisableRebalancing()
> ---
>
> Key: IGNITE-6713
> URL: https://issues.apache.org/jira/browse/IGNITE-6713
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Affects Versions: 2.3
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.4
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=904771=buildResultsDiv=Ignite20Tests_IgniteCache5
> CacheRebalancingSelfTest.testDisableRebalancing().
> has flaky failures on TC
> Success rate: 87,9%
> https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=-2095494394421107338=testDetails_Ignite20Tests=%3Cdefault%3E
> Reproducible locally (30 runs)



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

[jira] [Resolved] (IGNITE-6721) Data page evictions do not work in mixed persistence mode

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk resolved IGNITE-6721.
--
Resolution: Fixed

Merged to master and to ignite-2.3

> Data page evictions do not work in mixed persistence mode
> -
>
> Key: IGNITE-6721
> URL: https://issues.apache.org/jira/browse/IGNITE-6721
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Affects Versions: 2.3
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.3
>
>
> After IGNITE-6030 data page evictions are broken if in-memory caches are 
> mixed with persistence-enabled caches.
> The problem is in page eviction tracker creation code:
> {code}
> if (plc.getPageEvictionMode() == DataPageEvictionMode.DISABLED || 
> CU.isPersistenceEnabled(cctx.gridConfig()))
> return new NoOpPageEvictionTracker();
> {code}
> We should check not the global configuration, but the data region 
> configuration.



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

[jira] [Assigned] (IGNITE-6560) Web console: New api for memory and persistence configuration

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-6560:
-

Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> Web console: New api for memory and persistence configuration
> -
>
> Key: IGNITE-6560
> URL: https://issues.apache.org/jira/browse/IGNITE-6560
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.2
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.3
>
>




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

[jira] [Commented] (IGNITE-6560) Web console: New api for memory and persistence configuration

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-6560:
---

Fixed default page size.
Fixed data region configuration for cache.


> Web console: New api for memory and persistence configuration
> -
>
> Key: IGNITE-6560
> URL: https://issues.apache.org/jira/browse/IGNITE-6560
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.2
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 2.3
>
>




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

[jira] [Created] (IGNITE-6722) Marshaller mappings and binary metadata must be merged and written to disk on registerLocally

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-6722:
---

 Summary: Marshaller mappings and binary metadata must be merged 
and written to disk on registerLocally
 Key: IGNITE-6722
 URL: https://issues.apache.org/jira/browse/IGNITE-6722
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
 Fix For: 2.4


Each mapping/metadata register operation must result in creating/updating 
corresponding file in file system.

Methods for local register ({{MarshallerContext::registerClassNameLocally}} and 
{{CacheObjectBinaryProcessor::addMetaLocally}}) lack this part.



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

[jira] [Commented] (IGNITE-6512) Add an option to start caches in inactive state

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev commented on IGNITE-6512:
---

Sorry, I found extra 2 paths to create a cache and they use wrong flag value.

Please, look and merge
https://github.com/apache/ignite/pull/2913

> Add an option to start caches in inactive state
> ---
>
> Key: IGNITE-6512
> URL: https://issues.apache.org/jira/browse/IGNITE-6512
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Eduard Shangareev
>Assignee: Alexey Goncharuk
> Fix For: 2.4
>
>
> Now we always discard restarting state on cache while it is starting.
> But sometimes we need extra steps before making caches available from public 
> API.
> So, I suggest adding a new method which would be called when we want to make 
> caches available for public API clients.



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

[jira] [Updated] (IGNITE-6666) BinaryObjectImpl.writeFieldByOrder method does not support TIME

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-:
---
Affects Version/s: 2.2

> BinaryObjectImpl.writeFieldByOrder method does not support TIME
> ---
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: binary
>Affects Versions: 2.2
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
> Fix For: 2.4
>
>
> The variable totalLen is not define for TIME in method 
> BinaryObjectImpl.writeFieldByOrder.



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

[jira] [Updated] (IGNITE-6666) BinaryObjectImpl.writeFieldByOrder method does not support TIME

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-:
---
Fix Version/s: 2.4

> BinaryObjectImpl.writeFieldByOrder method does not support TIME
> ---
>
> Key: IGNITE-
> URL: https://issues.apache.org/jira/browse/IGNITE-
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>  Components: binary
>Affects Versions: 2.2
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
> Fix For: 2.4
>
>
> The variable totalLen is not define for TIME in method 
> BinaryObjectImpl.writeFieldByOrder.



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

[jira] [Updated] (IGNITE-6135) java.sql.Date is serialized using OptimizedMarshaller

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-6135:
---
Fix Version/s: 2.4

> java.sql.Date is serialized using OptimizedMarshaller
> -
>
> Key: IGNITE-6135
> URL: https://issues.apache.org/jira/browse/IGNITE-6135
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.1
>Reporter: Valentin Kulichenko
>Assignee: Amelchev Nikita
> Fix For: 2.4
>
>
> For some reason, if an object has a field of {{java.sql.Date}}, it's 
> serialized with {{OptimizedMarshaller}}. It should be a first class citizen, 
> similar to {{java.util.Date}}.
> In addition, it's possible to write a field using builder like this:
> {code}
> builder.setField(name, val, java.util.Date.class)
> {code}
> where {{val}} is instance of {{java.sql.Date}}. This leads to an exception 
> during deserialization, because {{java.util.Date}} would be expected.
> More context and code reproducing the issue can be found here: 
> http://apache-ignite-users.70518.x6.nabble.com/JDBC-store-Date-deserialization-problem-td16276.html



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

[jira] [Comment Edited] (IGNITE-6720) Move operation with file system outside checkpoint write lock

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev edited comment on IGNITE-6720 at 10/24/17 10:18 AM:
--

PR
https://github.com/apache/ignite/pull/2912

TC RUN:
https://ci.ignite.apache.org/viewQueued.html?itemId=907931


was (Author: edshanggg):
PR
https://github.com/apache/ignite/pull/2912

TC RUN:

> Move operation with file system outside checkpoint write lock
> -
>
> Key: IGNITE-6720
> URL: https://issues.apache.org/jira/browse/IGNITE-6720
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>
> There could be long-running operation in onMarkCheckPointBegin call.
> So, to move them outside write lock holding block make possible make some 
> operations possible to async (for example, making onMarkCheckPointBegin 
> return Future).
> During this block is in progress no caches updated are allowed.



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

[jira] [Commented] (IGNITE-6720) Move operation with file system outside checkpoint write lock

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6720:


GitHub user EdShangGG opened a pull request:

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

IGNITE-6720 Move operation with file system outside checkpoint write …

…lock

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

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

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

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


commit fd58fb9e76b2f4888df6fe058be5531cc4ed91f0
Author: Eduard Shangareev 
Date:   2017-10-24T09:48:39Z

IGNITE-6720 Move operation with file system outside checkpoint write lock




> Move operation with file system outside checkpoint write lock
> -
>
> Key: IGNITE-6720
> URL: https://issues.apache.org/jira/browse/IGNITE-6720
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>
> There could be long-running operation in onMarkCheckPointBegin call.
> So, to move them outside write lock holding block make possible make some 
> operations possible to async (for example, making onMarkCheckPointBegin 
> return Future).
> During this block is in progress no caches updated are allowed.



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

[jira] [Commented] (IGNITE-6720) Move operation with file system outside checkpoint write lock

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev commented on IGNITE-6720:
---

PR
https://github.com/apache/ignite/pull/2912

TC RUN:

> Move operation with file system outside checkpoint write lock
> -
>
> Key: IGNITE-6720
> URL: https://issues.apache.org/jira/browse/IGNITE-6720
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>Reporter: Eduard Shangareev
>Assignee: Eduard Shangareev
>
> There could be long-running operation in onMarkCheckPointBegin call.
> So, to move them outside write lock holding block make possible make some 
> operations possible to async (for example, making onMarkCheckPointBegin 
> return Future).
> During this block is in progress no caches updated are allowed.



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

[jira] [Commented] (IGNITE-6667) Allow discovery cache instance reuse if only minor topology change has occured.

[Alexei Scherbakov (JIRA)]

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

Alexei Scherbakov commented on IGNITE-6667:
---

[~sboikov]

I've implemented flexible strategy for disco cache reuse, please take a look.

TC: https://ci.ignite.apache.org/viewQueued.html?itemId=906993 (still in queue)

> Allow discovery cache instance reuse if only minor topology change has 
> occured.
> ---
>
> Key: IGNITE-6667
> URL: https://issues.apache.org/jira/browse/IGNITE-6667
> Project: Ignite
>  Issue Type: Improvement
>  Security Level: Public(Viewable by anyone) 
>Affects Versions: 2.2
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
> Fix For: 2.4
>
>
> Currently we always recreating DiscoCache instance even if only minor 
> topology change has occured and cache may be reused.
> Profiling shows what initialization of such object tooks up tens of millis 
> which adds to ring latency delay and especially sensitive for large 
> topologies.
> Solution: reuse current discovery cache instance whenever possible.



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

[jira] [Reopened] (IGNITE-6560) Web console: New api for memory and persistence configuration

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reopened IGNITE-6560:
---

> Web console: New api for memory and persistence configuration
> -
>
> Key: IGNITE-6560
> URL: https://issues.apache.org/jira/browse/IGNITE-6560
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.2
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 2.3
>
>




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

[jira] [Assigned] (IGNITE-6560) Web console: New api for memory and persistence configuration

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-6560:
-

Assignee: Vasiliy Sisko  (was: Ivan Rakov)

> Web console: New api for memory and persistence configuration
> -
>
> Key: IGNITE-6560
> URL: https://issues.apache.org/jira/browse/IGNITE-6560
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.2
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 2.3
>
>




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

[jira] [Updated] (IGNITE-6721) Data page evictions do not work in mixed persistence mode

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk updated IGNITE-6721:
-
Priority: Blocker  (was: Major)

> Data page evictions do not work in mixed persistence mode
> -
>
> Key: IGNITE-6721
> URL: https://issues.apache.org/jira/browse/IGNITE-6721
> Project: Ignite
>  Issue Type: Bug
>  Security Level: Public(Viewable by anyone) 
>Affects Versions: 2.3
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Blocker
> Fix For: 2.3
>
>
> After IGNITE-6030 data page evictions are broken if in-memory caches are 
> mixed with persistence-enabled caches.
> The problem is in page eviction tracker creation code:
> {code}
> if (plc.getPageEvictionMode() == DataPageEvictionMode.DISABLED || 
> CU.isPersistenceEnabled(cctx.gridConfig()))
> return new NoOpPageEvictionTracker();
> {code}
> We should check not the global configuration, but the data region 
> configuration.



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

[jira] [Created] (IGNITE-6721) Data page evictions do not work in mixed persistence mode

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-6721:


 Summary: Data page evictions do not work in mixed persistence mode
 Key: IGNITE-6721
 URL: https://issues.apache.org/jira/browse/IGNITE-6721
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
Affects Versions: 2.3
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
 Fix For: 2.3


After IGNITE-6030 data page evictions are broken if in-memory caches are mixed 
with persistence-enabled caches.
The problem is in page eviction tracker creation code:
{code}
if (plc.getPageEvictionMode() == DataPageEvictionMode.DISABLED || 
CU.isPersistenceEnabled(cctx.gridConfig()))
return new NoOpPageEvictionTracker();
{code}

We should check not the global configuration, but the data region configuration.



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