[jira] [Updated] (IGNITE-5823) Need to remove CacheAtomicUpdateTimeoutException

[Sergey Dorozhkin (JIRA)]

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

Sergey Dorozhkin updated IGNITE-5823:
-
Fix Version/s: 2.2

> Need to remove CacheAtomicUpdateTimeoutException
> 
>
> Key: IGNITE-5823
> URL: https://issues.apache.org/jira/browse/IGNITE-5823
> Project: Ignite
>  Issue Type: Task
>Reporter: Yakov Zhdanov
>Assignee: Sergey Dorozhkin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.2
>
>
> And releated - CacheAtomicUpdateTimeoutCheckedException
> These exceptions are not used any more and can be removed.



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

[jira] [Commented] (IGNITE-3935) ClassLoaders are not switched during object deserialization

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3935:


Github user xtern closed the pull request at:

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


> ClassLoaders are not switched during object deserialization
> ---
>
> Key: IGNITE-3935
> URL: https://issues.apache.org/jira/browse/IGNITE-3935
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.6
>Reporter: Denis Magda
>
> If an object is being deserialized with ClassLoader A then this ClassLoader A 
> will be used for the deserialization of the whole object's state, i.e., 
> including all its fields that can be custom objects loaded by ClassLoader B. 
> In a basic scenario we can have an object of some Ignite class that is 
> presented in the classpath. That Ignite class may enclose an object that is 
> loaded by peer-class-loading class loader. The deserialization will fail 
> because Ignite won't switch to the peer-class-loading loader when it's needed.
> To reproduce the issue do the following:
> 1. Start a remote ignite node using {{./ignite.sh 
> ../examples/config/example-ignite.xml}}
> 2. Run the code below
> {code}
> public class StreamingExample {`
> public static class StreamingExampleCacheEntryProcessor implements 
> CacheEntryProcessor {
> @Override
> public Object process(MutableEntry e, Object... arg) throws 
> EntryProcessorException {
> Long val = e.getValue();
> e.setValue(val == null ? 1L : val + 1);
> return null;
> }
> }
> public static void main(String[] args) throws IgniteException, IOException {
> Ignition.setClientMode(true);
> try (Ignite ignite = 
> Ignition.start("examples/config/example-ignite.xml")) {
> IgniteCache stmCache = 
> ignite.getOrCreateCache("mycache");
> try (IgniteDataStreamer stmr = 
> ignite.dataStreamer(stmCache.getName())) {
> stmr.allowOverwrite(true);
> stmr.receiver(StreamTransformer.from(new 
> StreamingExampleCacheEntryProcessor()));
> stmr.addData("word", 1L);
> System.out.println("Finished");
> }
> }
> }
> {code}
> However if to modify this code to the following everything will work fine 
> {code}
> public class StreamingExample {
> public static class StreamingExampleCacheEntryProcessor extends 
> StreamTransformer {
> @Override
> public Object process(MutableEntry e, Object... arg) 
> throws EntryProcessorException {
> System.out.println("Executed!");
> Long val = e.getValue();
> e.setValue(val == null ? 1L : val + 1);
> return null;
> }
> }
> public static void main(String[] args) throws IgniteException, 
> IOException {
> Ignition.setClientMode(true);
> try (Ignite ignite = 
> Ignition.start("examples/config/example-ignite.xml")) {
> IgniteCache stmCache = 
> ignite.getOrCreateCache("mycache");
> try (IgniteDataStreamer stmr = 
> ignite.dataStreamer(stmCache.getName())) {
> stmr.allowOverwrite(true);
> stmr.receiver(new StreamingExampleCacheEntryProcessor());
> stmr.addData("word", 1L);
> System.out.println("Finished");
> }
> }
> }
> }
> {code}



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

[jira] [Commented] (IGNITE-3935) ClassLoaders are not switched during object deserialization

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3935:


GitHub user xtern opened a pull request:

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

IGNITE-3935 test



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

$ git pull https://github.com/xtern/ignite test/ignite-3935

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

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


commit 9aa2f6dcc6ee478c284b8b48d3a828bb9e473b85
Author: Pereslegin Pavel 
Date:   2017-07-31T20:14:21Z

IGNITE-3935 test




> ClassLoaders are not switched during object deserialization
> ---
>
> Key: IGNITE-3935
> URL: https://issues.apache.org/jira/browse/IGNITE-3935
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 1.6
>Reporter: Denis Magda
>
> If an object is being deserialized with ClassLoader A then this ClassLoader A 
> will be used for the deserialization of the whole object's state, i.e., 
> including all its fields that can be custom objects loaded by ClassLoader B. 
> In a basic scenario we can have an object of some Ignite class that is 
> presented in the classpath. That Ignite class may enclose an object that is 
> loaded by peer-class-loading class loader. The deserialization will fail 
> because Ignite won't switch to the peer-class-loading loader when it's needed.
> To reproduce the issue do the following:
> 1. Start a remote ignite node using {{./ignite.sh 
> ../examples/config/example-ignite.xml}}
> 2. Run the code below
> {code}
> public class StreamingExample {`
> public static class StreamingExampleCacheEntryProcessor implements 
> CacheEntryProcessor {
> @Override
> public Object process(MutableEntry e, Object... arg) throws 
> EntryProcessorException {
> Long val = e.getValue();
> e.setValue(val == null ? 1L : val + 1);
> return null;
> }
> }
> public static void main(String[] args) throws IgniteException, IOException {
> Ignition.setClientMode(true);
> try (Ignite ignite = 
> Ignition.start("examples/config/example-ignite.xml")) {
> IgniteCache stmCache = 
> ignite.getOrCreateCache("mycache");
> try (IgniteDataStreamer stmr = 
> ignite.dataStreamer(stmCache.getName())) {
> stmr.allowOverwrite(true);
> stmr.receiver(StreamTransformer.from(new 
> StreamingExampleCacheEntryProcessor()));
> stmr.addData("word", 1L);
> System.out.println("Finished");
> }
> }
> }
> {code}
> However if to modify this code to the following everything will work fine 
> {code}
> public class StreamingExample {
> public static class StreamingExampleCacheEntryProcessor extends 
> StreamTransformer {
> @Override
> public Object process(MutableEntry e, Object... arg) 
> throws EntryProcessorException {
> System.out.println("Executed!");
> Long val = e.getValue();
> e.setValue(val == null ? 1L : val + 1);
> return null;
> }
> }
> public static void main(String[] args) throws IgniteException, 
> IOException {
> Ignition.setClientMode(true);
> try (Ignite ignite = 
> Ignition.start("examples/config/example-ignite.xml")) {
> IgniteCache stmCache = 
> ignite.getOrCreateCache("mycache");
> try (IgniteDataStreamer stmr = 
> ignite.dataStreamer(stmCache.getName())) {
> stmr.allowOverwrite(true);
> stmr.receiver(new StreamingExampleCacheEntryProcessor());
> stmr.addData("word", 1L);
> System.out.println("Finished");
> }
> }
> }
> }
> {code}



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

[jira] [Created] (IGNITE-5887) Apache Ignite Site Redesign

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5887:
---

 Summary: Apache Ignite Site Redesign
 Key: IGNITE-5887
 URL: https://issues.apache.org/jira/browse/IGNITE-5887
 Project: Ignite
  Issue Type: Task
Reporter: Denis Magda
Assignee: Prachi Garg


Apache Ignite site designed has to be revisited and reworked in the following 
way:
* The layout has to be optimized for all kind of screen resolutions 
(high-resolution, mobile, tablet, desktop).
* The header should be optimized for mobile and tablets screens - there has to 
be only one header menu and redundant items should be removed from it (like the 
download button).
*  The front page design is different from the design of the rest of the pages. 
The UI of the rest of the pages has to be improved (background, fonts, etc.)
* Make sure everything looks and behaves similarly in all the mainstream 
browsers (Safari, Chrome, Edge, Firefox).



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

[jira] [Updated] (IGNITE-5886) Ignite SQL Getting Started

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-5886:

Description: 
The goal of the task is to create an Ignite SQL Getting Started with the 
following sections:
* Connection to the cluster using JDBC and ODBC drivers. The 
content/description for both drivers will be the same. The only difference will 
be in the source code that can be shown in different tabs of "Code Sample" 
readme.io element. Take a look at the DDL doc [1] that incorporates the source 
code for Java API and JDBC.
* SQL tables and indexes creation using DDL statements [1]. There should be at 
least two tables. Use the affinity collocation for them. {{CREATE TABLE}} 
command support {{AFFINITYKEY}} parameter that can be passed to {{WITH}} block.
* Preload data using {{INSERT}} statements.
* Show how to query data with {{SELECT}} statements including joins.
* Show to update the data sets with {{UPDATE}} and {{DELETE}} statements.

Here is the page to document (presently it's hidden and visible only for 
documentation contributors):
https://apacheignite.readme.io/v2.1/docs/getting-started-sql

Use JDBC thin driver [2] for the JDBC connectivity. The ODBC is well documented 
here [3] and we have a lot of examples for it in Ignite deliverables.  

Moreover, as a part of this activity, we will have the ready-to-use source code 
that should be shared on GitHub and mentioned in the documentation.

[1] https://apacheignite.readme.io/v2.1/docs/distributed-ddl
[2] https://apacheignite.readme.io/v2.1/docs/jdbc-driver#jdbc-thin-driver
[3] https://apacheignite.readme.io/v2.1/docs/odbc-driver

  was:
The goal of the task is to create an Ignite SQL Getting Started with the 
following sections:
* Connection to the cluster using JDBC and ODBC drivers. The 
content/description for both drivers will be the same. The only difference will 
be in the source code that can be shown in different tabs of "Code Sample" 
readme.io element. Take a look at the DDL doc [1] that incorporates the source 
code for Java API and JDBC.
* SQL tables and indexes creation using DDL statements [1]. There should be at 
least two tables. Use the affinity collocation for them. {{CREATE TABLE}} 
command support {{AFFINITYKEY}} parameter that can be passed to {{WITH}} block.
* Preload data using {{INSERT}} statements.
* Show how to query data with {{SELECT}} statements including joins.
* Show to update the data sets with {{UPDATE}} and {{DELETE}} statements.

Here is the page to document (presently it's hidden and visible only for 
documentation contributors):
https://apacheignite.readme.io/v2.1/docs/getting-started-sql

Use JDBC thin driver [2] for the JDBC connectivity. The ODBC is well documented 
here [3] and we have a lot of examples for it in Ignite deliverables.  

[1] https://apacheignite.readme.io/v2.1/docs/distributed-ddl
[2] https://apacheignite.readme.io/v2.1/docs/jdbc-driver#jdbc-thin-driver
[3] https://apacheignite.readme.io/v2.1/docs/odbc-driver


> Ignite SQL Getting Started 
> ---
>
> Key: IGNITE-5886
> URL: https://issues.apache.org/jira/browse/IGNITE-5886
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Priority: Critical
> Fix For: 2.2
>
>
> The goal of the task is to create an Ignite SQL Getting Started with the 
> following sections:
> * Connection to the cluster using JDBC and ODBC drivers. The 
> content/description for both drivers will be the same. The only difference 
> will be in the source code that can be shown in different tabs of "Code 
> Sample" readme.io element. Take a look at the DDL doc [1] that incorporates 
> the source code for Java API and JDBC.
> * SQL tables and indexes creation using DDL statements [1]. There should be 
> at least two tables. Use the affinity collocation for them. {{CREATE TABLE}} 
> command support {{AFFINITYKEY}} parameter that can be passed to {{WITH}} 
> block.
> * Preload data using {{INSERT}} statements.
> * Show how to query data with {{SELECT}} statements including joins.
> * Show to update the data sets with {{UPDATE}} and {{DELETE}} statements.
> Here is the page to document (presently it's hidden and visible only for 
> documentation contributors):
> https://apacheignite.readme.io/v2.1/docs/getting-started-sql
> Use JDBC thin driver [2] for the JDBC connectivity. The ODBC is well 
> documented here [3] and we have a lot of examples for it in Ignite 
> deliverables.  
> Moreover, as a part of this activity, we will have the ready-to-use source 
> code that should be shared on GitHub and mentioned in the documentation.
> [1] https://apacheignite.readme.io/v2.1/docs/distributed-ddl
> [2] https://apacheignite.readme.io/v2.1/docs/jdbc-driver#jdbc-thin-driver
> [3] https://apacheignite.readme.io/v2.1/docs/odbc-driver



--
This message was sent by 

[jira] [Created] (IGNITE-5886) Ignite SQL Getting Started

[Denis Magda (JIRA)]

Denis Magda created IGNITE-5886:
---

 Summary: Ignite SQL Getting Started 
 Key: IGNITE-5886
 URL: https://issues.apache.org/jira/browse/IGNITE-5886
 Project: Ignite
  Issue Type: Task
Reporter: Denis Magda
Priority: Critical
 Fix For: 2.2


The goal of the task is to create an Ignite SQL Getting Started with the 
following sections:
* Connection to the cluster using JDBC and ODBC drivers. The 
content/description for both drivers will be the same. The only difference will 
be in the source code that can be shown in different tabs of "Code Sample" 
readme.io element. Take a look at the DDL doc [1] that incorporates the source 
code for Java API and JDBC.
* SQL tables and indexes creation using DDL statements [1]. There should be at 
least two tables. Use the affinity collocation for them. {{CREATE TABLE}} 
command support {{AFFINITYKEY}} parameter that can be passed to {{WITH}} block.
* Preload data using {{INSERT}} statements.
* Show how to query data with {{SELECT}} statements including joins.
* Show to update the data sets with {{UPDATE}} and {{DELETE}} statements.

Here is the page to document (presently it's hidden and visible only for 
documentation contributors):
https://apacheignite.readme.io/v2.1/docs/getting-started-sql

Use JDBC thin driver [2] for the JDBC connectivity. The ODBC is well documented 
here [3] and we have a lot of examples for it in Ignite deliverables.  

[1] https://apacheignite.readme.io/v2.1/docs/distributed-ddl
[2] https://apacheignite.readme.io/v2.1/docs/jdbc-driver#jdbc-thin-driver
[3] https://apacheignite.readme.io/v2.1/docs/odbc-driver



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

[jira] [Created] (IGNITE-5885) .NET: Add x86 tests on TeamCity

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5885:
--

 Summary: .NET: Add x86 tests on TeamCity
 Key: IGNITE-5885
 URL: https://issues.apache.org/jira/browse/IGNITE-5885
 Project: Ignite
  Issue Type: Task
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.2


Just copy a configuration and change NUnit bitness.



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

[jira] [Assigned] (IGNITE-5849) Introduce ignite node persistent meta-store

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov reassigned IGNITE-5849:
-

Assignee: Konstantin Dudkov

> Introduce ignite node persistent meta-store
> ---
>
> Key: IGNITE-5849
> URL: https://issues.apache.org/jira/browse/IGNITE-5849
> Project: Ignite
>  Issue Type: New Feature
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Konstantin Dudkov
> Fix For: 2.2
>
>
> As persistence feature is being developed, we will have a need for a 
> component, which reliably stores arbitrary metadata about node and cluster.
> We already have reserved partition IDs for this purpose, all we need to do is 
> to extend the partition store abstraction to store non-cache objects and make 
> sure this new store participates in all common recovery procedures.



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

[jira] [Commented] (IGNITE-5750) Format of uptime for metrics

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik commented on IGNITE-5750:


I am going to commit this today - the patch has fallen through the cracks.

> Format of uptime for metrics
> 
>
> Key: IGNITE-5750
> URL: https://issues.apache.org/jira/browse/IGNITE-5750
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Alexandr Kuramshin
>Assignee: Yevgeniy Ignatyev
>Priority: Trivial
>  Labels: newbie
> Fix For: 2.2
>
>
> Metrics for local node shows uptime formatted as 00:00:00:000
> But the last colon should be changed to the dot.
> Right format is 00:00:00.000



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

[jira] [Commented] (IGNITE-5618) .NET: Ignite fails with OOM on startup under x86 (32 bit) with default configuration

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-5618:


Issue fails tests on TC with exit code 
http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgnitePlatformCppWin32=%3Cdefault%3E=buildTypeStatusDiv
(no tests results for case bug is reproduced).

> .NET: Ignite fails with OOM on startup under x86 (32 bit) with default 
> configuration
> 
>
> Key: IGNITE-5618
> URL: https://issues.apache.org/jira/browse/IGNITE-5618
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Priority: Blocker
>  Labels: .NET, MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Default MemoryPolicyConfiguration settings do not take process bitness into 
> account. We can't use 80% of RAM under 32-bit mode.
> * Add a suite on TC which runs .NET tests on 32 bits



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

[jira] [Updated] (IGNITE-5618) .NET: Ignite fails with OOM on startup under x86 (32 bit) with default configuration

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-5618:
---
Labels: .NET MakeTeamcityGreenAgain  (was: .NET)

> .NET: Ignite fails with OOM on startup under x86 (32 bit) with default 
> configuration
> 
>
> Key: IGNITE-5618
> URL: https://issues.apache.org/jira/browse/IGNITE-5618
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Priority: Blocker
>  Labels: .NET, MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> Default MemoryPolicyConfiguration settings do not take process bitness into 
> account. We can't use 80% of RAM under 32-bit mode.
> * Add a suite on TC which runs .NET tests on 32 bits



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

[jira] [Updated] (IGNITE-5884) Change default pageSize of page memory to 4KB

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-5884:
---
Description: 
Checkpoint write speed is suboptimal with default 2K page on most UNIX-driven 
enviroments with SSD disk. There are several reasons for this:
1) Page size of linux page cache is 4k by default on most kernels (you can 
check yours by "getconf PAGE_SIZE" command). With 2k random writes 
vm.dirty_ratio threshold is reached two times faster than with 4k random writes.
2) Most SSD manufacturers don't reveal actual disk page size, but they 
recommend to write at least 4k at once. Also, 4k blocks are used during 
benchmarking SSD random writes. 
Related question: 
https://superuser.com/questions/1168014/nvme-ssd-why-is-4k-writing-faster-than-reading
Article by Emmanuel Goossaert describing why writing less than a page is 
сounterproductive: 
http://codecapsule.com/2014/02/12/coding-for-ssds-part-3-pages-blocks-and-the-flash-translation-layer/
I've prepared a checkpoint emulation benchmark (code and results attached). Run 
on production-level hardware (CentOS, 100 GB RAM, total LFS size is 100GB, 
vm.dirty_ratio=10) showed that checkpointing with 4k pages is much more 
efficient than with 2k.
*Important: backwards compatibility must be ensured with LFS files created with 
old 2k default page size.*

  was:
Checkpoint write speed is suboptimal with default 2K page on most UNIX-driven 
enviroments with SSD disk. There are several reasons for this:
1) Page size of linux page cache is 4k by default on most kernels (you can 
check yours by "getconf PAGE_SIZE" command). With 2k random writes 
vm.dirty_ratio threshold is reached two times faster than with 4k random writes.
2) Most SSD manufacturers don't reveal actual disk page size, but they 
recommend to write at least 4k at once. Also, 4k blocks are used during 
benchmarking SSD random writes. 
Related question: 
https://superuser.com/questions/1168014/nvme-ssd-why-is-4k-writing-faster-than-reading
Article by Emmanuel Goossaert describing why writeing less than a page is 
сounterproductive: 
http://codecapsule.com/2014/02/12/coding-for-ssds-part-3-pages-blocks-and-the-flash-translation-layer/
I've prepared a checkpoint emulation benchmark (code and results attached). Run 
on production-level hardware (CentOS, 100 GB RAM, total LFS size is 100GB, 
vm.dirty_ratio=10) showed that checkpointing with 4k pages is much more 
efficient than with 2k.
*Important: backwards compatibility must be ensured with LFS files created with 
old 2k default page size.*


> Change default pageSize of page memory to 4KB
> -
>
> Key: IGNITE-5884
> URL: https://issues.apache.org/jira/browse/IGNITE-5884
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Ivan Rakov
> Fix For: 2.2
>
> Attachments: CpBenchmark.java, iostat.log, ssdlab.log
>
>
> Checkpoint write speed is suboptimal with default 2K page on most UNIX-driven 
> enviroments with SSD disk. There are several reasons for this:
> 1) Page size of linux page cache is 4k by default on most kernels (you can 
> check yours by "getconf PAGE_SIZE" command). With 2k random writes 
> vm.dirty_ratio threshold is reached two times faster than with 4k random 
> writes.
> 2) Most SSD manufacturers don't reveal actual disk page size, but they 
> recommend to write at least 4k at once. Also, 4k blocks are used during 
> benchmarking SSD random writes. 
> Related question: 
> https://superuser.com/questions/1168014/nvme-ssd-why-is-4k-writing-faster-than-reading
> Article by Emmanuel Goossaert describing why writing less than a page is 
> сounterproductive: 
> http://codecapsule.com/2014/02/12/coding-for-ssds-part-3-pages-blocks-and-the-flash-translation-layer/
> I've prepared a checkpoint emulation benchmark (code and results attached). 
> Run on production-level hardware (CentOS, 100 GB RAM, total LFS size is 
> 100GB, vm.dirty_ratio=10) showed that checkpointing with 4k pages is much 
> more efficient than with 2k.
> *Important: backwards compatibility must be ensured with LFS files created 
> with old 2k default page size.*



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

[jira] [Updated] (IGNITE-5884) Change default pageSize of page memory to 4KB

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-5884:
---
Description: 
Checkpoint write speed is suboptimal with default 2K page on most UNIX-driven 
enviroments with SSD disk. There are several reasons for this:
1) Page size of linux page cache is 4k by default on most kernels (you can 
check yours by "getconf PAGE_SIZE" command). With 2k random writes 
vm.dirty_ratio threshold is reached two times faster than with 4k random writes.
2) Most SSD manufacturers don't reveal actual disk page size, but they 
recommend to write at least 4k at once. Also, 4k blocks are used during 
benchmarking SSD random writes. 
Related question: 
https://superuser.com/questions/1168014/nvme-ssd-why-is-4k-writing-faster-than-reading
Article by Emmanuel Goossaert describing why writeing less than a page is 
сounterproductive: 
http://codecapsule.com/2014/02/12/coding-for-ssds-part-3-pages-blocks-and-the-flash-translation-layer/
I've prepared a checkpoint emulation benchmark (code and results attached). Run 
on production-level hardware (CentOS, 100 GB RAM, total LFS size is 100GB, 
vm.dirty_ratio=10) showed that checkpointing with 4k pages is much more 
efficient than with 2k.
*Important: backwards compatibility must be ensured with LFS files created with 
old 2k default page size.*

  was:
Checkpoint write speed is suboptimal with default 2K page on most UNIX-driven 
enviroments with SSD disk. There are several reasons for this:
1) Page size of linux page cache is 4k by default on most kernels (you can 
check yours by "getconf PAGE_SIZE" command). With 2k random writes 
vm.dirty_ratio threshold is reached two times faster than with 4k random writes.
2) Most SSD manufacturers don't reveal actual disk page size, but they 
recommend to write at least 4k at once. Also, 4k blocks are used during 
benchmarking SSD random writes. Related question: 
https://superuser.com/questions/1168014/nvme-ssd-why-is-4k-writing-faster-than-reading
I've prepared a checkpoint emulation benchmark (code and results attached). Run 
on production-level hardware (CentOS, 100 GB RAM, total LFS size is 100GB, 
vm.dirty_ratio=10) showed that checkpointing with 4k pages is much more 
efficient than with 2k.
*Important: backwards compatibility must be ensured with LFS files created with 
old 2k default page size.*


> Change default pageSize of page memory to 4KB
> -
>
> Key: IGNITE-5884
> URL: https://issues.apache.org/jira/browse/IGNITE-5884
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Ivan Rakov
> Fix For: 2.2
>
> Attachments: CpBenchmark.java, iostat.log, ssdlab.log
>
>
> Checkpoint write speed is suboptimal with default 2K page on most UNIX-driven 
> enviroments with SSD disk. There are several reasons for this:
> 1) Page size of linux page cache is 4k by default on most kernels (you can 
> check yours by "getconf PAGE_SIZE" command). With 2k random writes 
> vm.dirty_ratio threshold is reached two times faster than with 4k random 
> writes.
> 2) Most SSD manufacturers don't reveal actual disk page size, but they 
> recommend to write at least 4k at once. Also, 4k blocks are used during 
> benchmarking SSD random writes. 
> Related question: 
> https://superuser.com/questions/1168014/nvme-ssd-why-is-4k-writing-faster-than-reading
> Article by Emmanuel Goossaert describing why writeing less than a page is 
> сounterproductive: 
> http://codecapsule.com/2014/02/12/coding-for-ssds-part-3-pages-blocks-and-the-flash-translation-layer/
> I've prepared a checkpoint emulation benchmark (code and results attached). 
> Run on production-level hardware (CentOS, 100 GB RAM, total LFS size is 
> 100GB, vm.dirty_ratio=10) showed that checkpointing with 4k pages is much 
> more efficient than with 2k.
> *Important: backwards compatibility must be ensured with LFS files created 
> with old 2k default page size.*



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

[jira] [Created] (IGNITE-5884) Change default pageSize of page memory to 4KB

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-5884:
--

 Summary: Change default pageSize of page memory to 4KB
 Key: IGNITE-5884
 URL: https://issues.apache.org/jira/browse/IGNITE-5884
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Reporter: Ivan Rakov
 Fix For: 2.2


Checkpoint write speed is suboptimal with default 2K page on most UNIX-driven 
enviroments with SSD disk. There are several reasons for this:
1) Page size of linux page cache is 4k by default on most kernels (you can 
check yours by "getconf PAGE_SIZE" command). With 2k random writes 
vm.dirty_ratio threshold is reached two times faster than with 4k random writes.
2) Most SSD manufacturers don't reveal actual disk page size, but they 
recommend to write at least 4k at once. Also, 4k blocks are used during 
benchmarking SSD random writes. Related question: 
https://superuser.com/questions/1168014/nvme-ssd-why-is-4k-writing-faster-than-reading
I've prepared a checkpoint emulation benchmark (code and results attached). Run 
on production-level hardware (CentOS, 100 GB RAM, total LFS size is 100GB, 
vm.dirty_ratio=10) showed that checkpointing with 4k pages is much more 
efficient than with 2k.
*Important: backwards compatibility must be ensured with LFS files created with 
old 2k default page size.*



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

[jira] [Updated] (IGNITE-5884) Change default pageSize of page memory to 4KB

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-5884:
---
Attachment: iostat.log
ssdlab.log
CpBenchmark.java

> Change default pageSize of page memory to 4KB
> -
>
> Key: IGNITE-5884
> URL: https://issues.apache.org/jira/browse/IGNITE-5884
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Reporter: Ivan Rakov
> Fix For: 2.2
>
> Attachments: CpBenchmark.java, iostat.log, ssdlab.log
>
>
> Checkpoint write speed is suboptimal with default 2K page on most UNIX-driven 
> enviroments with SSD disk. There are several reasons for this:
> 1) Page size of linux page cache is 4k by default on most kernels (you can 
> check yours by "getconf PAGE_SIZE" command). With 2k random writes 
> vm.dirty_ratio threshold is reached two times faster than with 4k random 
> writes.
> 2) Most SSD manufacturers don't reveal actual disk page size, but they 
> recommend to write at least 4k at once. Also, 4k blocks are used during 
> benchmarking SSD random writes. Related question: 
> https://superuser.com/questions/1168014/nvme-ssd-why-is-4k-writing-faster-than-reading
> I've prepared a checkpoint emulation benchmark (code and results attached). 
> Run on production-level hardware (CentOS, 100 GB RAM, total LFS size is 
> 100GB, vm.dirty_ratio=10) showed that checkpointing with 4k pages is much 
> more efficient than with 2k.
> *Important: backwards compatibility must be ensured with LFS files created 
> with old 2k default page size.*



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

[jira] [Updated] (IGNITE-5883) Ignite Start Nodes test suite is flaky

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-5883:
---
Affects Version/s: 2.1

> Ignite Start Nodes test suite is flaky
> --
>
> Key: IGNITE-5883
> URL: https://issues.apache.org/jira/browse/IGNITE-5883
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
>
> Ignite Start Nodes suite contains several flaky tests.
> Example runs with sporadic fails: 
> 1) 
> http://ci.ignite.apache.org/viewLog.html?buildId=746188=buildResultsDiv=Ignite20Tests_IgniteStartNodes
> 2) 
> http://ci.ignite.apache.org/viewLog.html?buildId=747364=buildResultsDiv=Ignite20Tests_IgniteStartNodes
> The ticket is for investigation and making tests stable.



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

[jira] [Updated] (IGNITE-5883) Ignite Start Nodes test suite is flaky

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-5883:
---
Affects Version/s: (was: 2.1)

> Ignite Start Nodes test suite is flaky
> --
>
> Key: IGNITE-5883
> URL: https://issues.apache.org/jira/browse/IGNITE-5883
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
>
> Ignite Start Nodes suite contains several flaky tests.
> Example runs with sporadic fails: 
> 1) 
> http://ci.ignite.apache.org/viewLog.html?buildId=746188=buildResultsDiv=Ignite20Tests_IgniteStartNodes
> 2) 
> http://ci.ignite.apache.org/viewLog.html?buildId=747364=buildResultsDiv=Ignite20Tests_IgniteStartNodes
> The ticket is for investigation and making tests stable.



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

[jira] [Updated] (IGNITE-5883) Ignite Start Nodes test suite is flaky

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-5883:
---
Description: 
Ignite Start Nodes suite contains several flaky tests.
Example runs with sporadic fails: 
1) 
http://ci.ignite.apache.org/viewLog.html?buildId=746188=buildResultsDiv=Ignite20Tests_IgniteStartNodes
2) 
http://ci.ignite.apache.org/viewLog.html?buildId=747364=buildResultsDiv=Ignite20Tests_IgniteStartNodes
The ticket is for investigation and making tests stable.

  was:
Ignite Start Nodes suite contains several flaky tests.
Example runs with flaky fails: 
1) 
http://ci.ignite.apache.org/viewLog.html?buildId=746188=buildResultsDiv=Ignite20Tests_IgniteStartNodes
2) 
http://ci.ignite.apache.org/viewLog.html?buildId=747364=buildResultsDiv=Ignite20Tests_IgniteStartNodes
The ticket is for investigation and making tests stable.


> Ignite Start Nodes test suite is flaky
> --
>
> Key: IGNITE-5883
> URL: https://issues.apache.org/jira/browse/IGNITE-5883
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
>
> Ignite Start Nodes suite contains several flaky tests.
> Example runs with sporadic fails: 
> 1) 
> http://ci.ignite.apache.org/viewLog.html?buildId=746188=buildResultsDiv=Ignite20Tests_IgniteStartNodes
> 2) 
> http://ci.ignite.apache.org/viewLog.html?buildId=747364=buildResultsDiv=Ignite20Tests_IgniteStartNodes
> The ticket is for investigation and making tests stable.



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

[jira] [Updated] (IGNITE-5883) Ignite Start Nodes test suite is flaky

[Ivan Rakov (JIRA)]

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

Ivan Rakov updated IGNITE-5883:
---
Description: 
Ignite Start Nodes suite contains several flaky tests.
Example runs with flaky fails: 
1) 
http://ci.ignite.apache.org/viewLog.html?buildId=746188=buildResultsDiv=Ignite20Tests_IgniteStartNodes
2) 
http://ci.ignite.apache.org/viewLog.html?buildId=747364=buildResultsDiv=Ignite20Tests_IgniteStartNodes
The ticket is for investigation and making tests stable.

  was:
Ignite Start Nodes suite contains several flaky tests: 
http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteStartNodes
Example runs with flaky fails: 
1) 
http://ci.ignite.apache.org/viewLog.html?buildId=746188=buildResultsDiv=Ignite20Tests_IgniteStartNodes
2) 
http://ci.ignite.apache.org/viewLog.html?buildId=747364=buildResultsDiv=Ignite20Tests_IgniteStartNodes
The ticket is for investigation and making tests stable.


> Ignite Start Nodes test suite is flaky
> --
>
> Key: IGNITE-5883
> URL: https://issues.apache.org/jira/browse/IGNITE-5883
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ivan Rakov
>  Labels: MakeTeamcityGreenAgain
>
> Ignite Start Nodes suite contains several flaky tests.
> Example runs with flaky fails: 
> 1) 
> http://ci.ignite.apache.org/viewLog.html?buildId=746188=buildResultsDiv=Ignite20Tests_IgniteStartNodes
> 2) 
> http://ci.ignite.apache.org/viewLog.html?buildId=747364=buildResultsDiv=Ignite20Tests_IgniteStartNodes
> The ticket is for investigation and making tests stable.



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

[jira] [Created] (IGNITE-5883) Ignite Start Nodes test suite is flaky

[Ivan Rakov (JIRA)]

Ivan Rakov created IGNITE-5883:
--

 Summary: Ignite Start Nodes test suite is flaky
 Key: IGNITE-5883
 URL: https://issues.apache.org/jira/browse/IGNITE-5883
 Project: Ignite
  Issue Type: Bug
Reporter: Ivan Rakov


Ignite Start Nodes suite contains several flaky tests: 
http://ci.ignite.apache.org/viewType.html?buildTypeId=Ignite20Tests_IgniteStartNodes
Example runs with flaky fails: 
1) 
http://ci.ignite.apache.org/viewLog.html?buildId=746188=buildResultsDiv=Ignite20Tests_IgniteStartNodes
2) 
http://ci.ignite.apache.org/viewLog.html?buildId=747364=buildResultsDiv=Ignite20Tests_IgniteStartNodes
The ticket is for investigation and making tests stable.



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

[jira] [Updated] (IGNITE-5882) Duplicated dependency in pom.xml of core module

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-5882:
---
Affects Version/s: 2.1

> Duplicated dependency in pom.xml of core module
> ---
>
> Key: IGNITE-5882
> URL: https://issues.apache.org/jira/browse/IGNITE-5882
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Affects Versions: 2.1
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
> Fix For: 2.2
>
>
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.ignite:ignite-core:jar:2.2.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: com.google.guava:guava:jar -> version 14.0.1 vs ${guava.version} @ 
> line 215, column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> {code}



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

[jira] [Updated] (IGNITE-5882) Duplicated dependency in pom.xml of core module

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-5882:
---
Component/s: build

> Duplicated dependency in pom.xml of core module
> ---
>
> Key: IGNITE-5882
> URL: https://issues.apache.org/jira/browse/IGNITE-5882
> Project: Ignite
>  Issue Type: Bug
>  Components: build
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
> Fix For: 2.2
>
>
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.ignite:ignite-core:jar:2.2.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: com.google.guava:guava:jar -> version 14.0.1 vs ${guava.version} @ 
> line 215, column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> {code}



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

[jira] [Updated] (IGNITE-5882) Duplicated dependency in pom.xml of core module

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur updated IGNITE-5882:
---
Fix Version/s: 2.2

> Duplicated dependency in pom.xml of core module
> ---
>
> Key: IGNITE-5882
> URL: https://issues.apache.org/jira/browse/IGNITE-5882
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
> Fix For: 2.2
>
>
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.ignite:ignite-core:jar:2.2.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: com.google.guava:guava:jar -> version 14.0.1 vs ${guava.version} @ 
> line 215, column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> {code}



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

[jira] [Commented] (IGNITE-5866) JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails on master

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5866:


GitHub user nizhikov opened a pull request:

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

IGNITE-5866: Fix MetadataJob filter to exclude any of system caches



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

$ git pull https://github.com/nizhikov/ignite IGNITE-5866

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

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


commit 46683787e6cb913c981a42041380adeb077ff5f7
Author: Nikolay Izhikov 
Date:   2017-07-31T13:28:32Z

IGNITE-5866: Fix MetadataJob filter to exclude any of system caches




> JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails 
> on master
> ---
>
> Key: IGNITE-5866
> URL: https://issues.apache.org/jira/browse/IGNITE-5866
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.1
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> JettyRestProcessorSignedSelfTest and JettyRestProcessorUnsignedSelfTest fails 
> on master
> when run whole test class.
> If run single method both tests succeed.
> testMetadataLocal:
> {noformat}
> junit.framework.AssertionFailedError: expected:<5> but was:<6>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataLocal(JettyRestProcessorAbstractSelfTest.java:1127)
> {noformat}
> testMetadataRemote
> {noformat}
> junit.framework.AssertionFailedError: expected:<6> but was:<7>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataRemote(JettyRestProcessorAbstractSelfTest.java:1174)
> {noformat}



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

[jira] [Commented] (IGNITE-5882) Duplicated dependency in pom.xml of core module

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur commented on IGNITE-5882:


Sent to [ci.tests|http://ci.ignite.apache.org/viewQueued.html?itemId=748600].

> Duplicated dependency in pom.xml of core module
> ---
>
> Key: IGNITE-5882
> URL: https://issues.apache.org/jira/browse/IGNITE-5882
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.ignite:ignite-core:jar:2.2.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: com.google.guava:guava:jar -> version 14.0.1 vs ${guava.version} @ 
> line 215, column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> {code}



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

[jira] [Commented] (IGNITE-5882) Duplicated dependency in pom.xml of core module

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5882:


GitHub user daradurvs opened a pull request:

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

IGNITE-5882 Duplicated dependency in pom.xml of core module



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

$ git pull https://github.com/daradurvs/ignite ignite-5882

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

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


commit e53e26aa5e0ce0fb2bcea6b7963ac1e1907635d7
Author: daradurvs 
Date:   2017-07-31T13:19:50Z

ignite-5882: duplicated property was removed




> Duplicated dependency in pom.xml of core module
> ---
>
> Key: IGNITE-5882
> URL: https://issues.apache.org/jira/browse/IGNITE-5882
> Project: Ignite
>  Issue Type: Bug
>Reporter: Vyacheslav Daradur
>Assignee: Vyacheslav Daradur
>
> {code}
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model 
> for org.apache.ignite:ignite-core:jar:2.2.0-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
> be unique: com.google.guava:guava:jar -> version 14.0.1 vs ${guava.version} @ 
> line 215, column 21
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they 
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support 
> building such malformed projects.
> [WARNING]
> {code}



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

[jira] [Created] (IGNITE-5882) Duplicated dependency in pom.xml of core module

[Vyacheslav Daradur (JIRA)]

Vyacheslav Daradur created IGNITE-5882:
--

 Summary: Duplicated dependency in pom.xml of core module
 Key: IGNITE-5882
 URL: https://issues.apache.org/jira/browse/IGNITE-5882
 Project: Ignite
  Issue Type: Bug
Reporter: Vyacheslav Daradur
Assignee: Vyacheslav Daradur


{code}
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model for 
org.apache.ignite:ignite-core:jar:2.2.0-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must 
be unique: com.google.guava:guava:jar -> version 14.0.1 vs ${guava.version} @ 
line 215, column 21
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING]
{code}



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

[jira] [Commented] (IGNITE-5866) JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails on master

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-5866:
--

[~NIzhikov],

If I understand correctly, the result contains information about Ignite system 
cache. In this case, I think you should fix the MetadataJobFilter to exclude 
any system caches. 

> JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails 
> on master
> ---
>
> Key: IGNITE-5866
> URL: https://issues.apache.org/jira/browse/IGNITE-5866
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.1
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> JettyRestProcessorSignedSelfTest and JettyRestProcessorUnsignedSelfTest fails 
> on master
> when run whole test class.
> If run single method both tests succeed.
> testMetadataLocal:
> {noformat}
> junit.framework.AssertionFailedError: expected:<5> but was:<6>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataLocal(JettyRestProcessorAbstractSelfTest.java:1127)
> {noformat}
> testMetadataRemote
> {noformat}
> junit.framework.AssertionFailedError: expected:<6> but was:<7>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataRemote(JettyRestProcessorAbstractSelfTest.java:1174)
> {noformat}



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

[jira] [Comment Edited] (IGNITE-5866) JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails on master

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov edited comment on IGNITE-5866 at 7/31/17 1:07 PM:
--

Results of investigation of this issue.

Problem for both test-cases the same.
{{cache.context().queries().sqlMetadata()}} returns information about cache for 
storing atomic data structures - "ignite-sys-atomic-cache@default-ds-group". 
Cache for atomic created in {{testIncrement}} or {{testDecrement}} test-case.

ignite-sys-atomic-cache@default-ds-group created in

{code:java}
//DataStructuresProcessor.java:494

if (type.isVolatile())
grpName = DEFAULT_VOLATILE_DS_GROUP_NAME;
else if (cfg.getGroupName() != null)
grpName = cfg.getGroupName();
else
grpName = DEFAULT_DS_GROUP_NAME;

String cacheName = ATOMICS_CACHE_NAME + "@" + grpName;

IgniteInternalCache 
cache0 = ctx.cache().cache(cacheName);
{code}

List of cache collected by sqlMetadata method is filtered in 
GridCacheQueryManager$MetadataJob#call

{code:java}
// GridCacheQueryManager.java:2068
new P1() {
@Override public boolean apply(IgniteInternalCache c) 
{
return !CU.UTILITY_CACHE_NAME.equals(c.name());
}
}

/** System cache name. */
public static final String UTILITY_CACHE_NAME = "ignite-sys-cache";
{code}

As far as I can see MetadataJob filter was modified by commit 
804ce8243a8d19c3d5b4ca96b905ec18ee0139cf by Ilya Lantukh.

Should I fix MetadataJob filter? Or I just need to fix asserts in test-cases?


was (Author: nizhikov):
Results of investigation of this issue.

Problem with test-cases the same - {{cache.context().queries().sqlMetadata()}} 
returns information about cache for storing atomic data structures - 
"ignite-sys-atomic-cache@default-ds-group". Cache for atomic created in 
{{testIncrement}} or {{testDecrement}} test-case.

ignite-sys-atomic-cache@default-ds-group created in

{code:java}
//DataStructuresProcessor.java:494

if (type.isVolatile())
grpName = DEFAULT_VOLATILE_DS_GROUP_NAME;
else if (cfg.getGroupName() != null)
grpName = cfg.getGroupName();
else
grpName = DEFAULT_DS_GROUP_NAME;

String cacheName = ATOMICS_CACHE_NAME + "@" + grpName;

IgniteInternalCache 
cache0 = ctx.cache().cache(cacheName);
{code}

List of cache collected by sqlMetadata method is filtered in 
GridCacheQueryManager$MetadataJob#call

{code:java}
// GridCacheQueryManager.java:2068
new P1() {
@Override public boolean apply(IgniteInternalCache c) 
{
return !CU.UTILITY_CACHE_NAME.equals(c.name());
}
}

/** System cache name. */
public static final String UTILITY_CACHE_NAME = "ignite-sys-cache";
{code}

As far as I can see MetadataJob filter was modified by commit 
804ce8243a8d19c3d5b4ca96b905ec18ee0139cf by Ilya Lantukh.

Should I fix MetadataJob filter? Or I just need to fix asserts in test-cases?

> JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails 
> on master
> ---
>
> Key: IGNITE-5866
> URL: https://issues.apache.org/jira/browse/IGNITE-5866
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.1
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> JettyRestProcessorSignedSelfTest and JettyRestProcessorUnsignedSelfTest fails 
> on master
> when run whole test class.
> If run single method both tests succeed.
> testMetadataLocal:
> {noformat}
> junit.framework.AssertionFailedError: expected:<5> but was:<6>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataLocal(JettyRestProcessorAbstractSelfTest.java:1127)
> {noformat}
> testMetadataRemote
> {noformat}
> junit.framework.AssertionFailedError: expected:<6> but was:<7>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at 

[jira] [Commented] (IGNITE-5866) JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails on master

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-5866:


Hi [~ilantukh], [~agoncharuk],

Could you please advice us about next steps to fix?

> JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails 
> on master
> ---
>
> Key: IGNITE-5866
> URL: https://issues.apache.org/jira/browse/IGNITE-5866
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.1
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> JettyRestProcessorSignedSelfTest and JettyRestProcessorUnsignedSelfTest fails 
> on master
> when run whole test class.
> If run single method both tests succeed.
> testMetadataLocal:
> {noformat}
> junit.framework.AssertionFailedError: expected:<5> but was:<6>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataLocal(JettyRestProcessorAbstractSelfTest.java:1127)
> {noformat}
> testMetadataRemote
> {noformat}
> junit.framework.AssertionFailedError: expected:<6> but was:<7>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataRemote(JettyRestProcessorAbstractSelfTest.java:1174)
> {noformat}



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

[jira] [Comment Edited] (IGNITE-5766) Folder platform/cpp/bin and files inside this folder are missing in 2.1

[Igor Sapego (JIRA)]

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

Igor Sapego edited comment on IGNITE-5766 at 7/31/17 12:45 PM:
---

Cannot reproduce.


was (Author: isapego):
Can't reproduce.

> Folder platform/cpp/bin and files inside this folder are missing in 2.1
> ---
>
> Key: IGNITE-5766
> URL: https://issues.apache.org/jira/browse/IGNITE-5766
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Alex Volkov
> Fix For: 2.1
>
>
> I can't find folder platform/cpp/bin and files 
> bin/odbc/ignite-odbc-amd64.msi, bin/odbc/ignite-odbc-x86.msi inside this 
> folder for 2.1. They were there for 2.0. 
> Could you please check were they move or just missing and fix it.



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

[jira] [Resolved] (IGNITE-5766) Folder platform/cpp/bin and files inside this folder are missing in 2.1

[Igor Sapego (JIRA)]

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

Igor Sapego resolved IGNITE-5766.
-
   Resolution: Cannot Reproduce
Fix Version/s: (was: 2.2)
   2.1

Can't reproduce.

> Folder platform/cpp/bin and files inside this folder are missing in 2.1
> ---
>
> Key: IGNITE-5766
> URL: https://issues.apache.org/jira/browse/IGNITE-5766
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Alex Volkov
> Fix For: 2.1
>
>
> I can't find folder platform/cpp/bin and files 
> bin/odbc/ignite-odbc-amd64.msi, bin/odbc/ignite-odbc-x86.msi inside this 
> folder for 2.1. They were there for 2.0. 
> Could you please check were they move or just missing and fix it.



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

[jira] [Updated] (IGNITE-5655) Introduce pluggable string encoder/decoder

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-5655:
-
Fix Version/s: 2.2

> Introduce pluggable string encoder/decoder
> --
>
> Key: IGNITE-5655
> URL: https://issues.apache.org/jira/browse/IGNITE-5655
> Project: Ignite
>  Issue Type: New Feature
>  Components: binary
>Affects Versions: 2.0
>Reporter: Valentin Kulichenko
>Assignee: Andrey Kuznetsov
> Fix For: 2.2
>
>
> Currently binary marshaller encodes strings in UTF-8. However, sometimes it 
> makes sense to serialize strings with different encodings to save space. 
> Let's add global property to control String encoding and customize our binary 
> protocol to support it. For instance, we can add another flag 
> {{ENCODED_STRING}}, which will write strings as follows:
> [flag][encoding_flag][str_len][str_bytes]



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

[jira] [Commented] (IGNITE-5866) JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails on master

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-5866:
-

Results of investigation of this issue.

Problem with test-cases the same - {{cache.context().queries().sqlMetadata()}} 
returns information about cache for storing atomic data structures - 
"ignite-sys-atomic-cache@default-ds-group". Cache for atomic created in 
{{testIncrement}} or {{testDecrement}} test-case.

ignite-sys-atomic-cache@default-ds-group created in

{code:java}
//DataStructuresProcessor.java:494

if (type.isVolatile())
grpName = DEFAULT_VOLATILE_DS_GROUP_NAME;
else if (cfg.getGroupName() != null)
grpName = cfg.getGroupName();
else
grpName = DEFAULT_DS_GROUP_NAME;

String cacheName = ATOMICS_CACHE_NAME + "@" + grpName;

IgniteInternalCache 
cache0 = ctx.cache().cache(cacheName);
{code}

List of cache collected by sqlMetadata method is filtered in 
GridCacheQueryManager$MetadataJob#call

{code:java}
// GridCacheQueryManager.java:2068
new P1() {
@Override public boolean apply(IgniteInternalCache c) 
{
return !CU.UTILITY_CACHE_NAME.equals(c.name());
}
}

/** System cache name. */
public static final String UTILITY_CACHE_NAME = "ignite-sys-cache";
{code}

As far as I can see MetadataJob filter was modified by commit 
804ce8243a8d19c3d5b4ca96b905ec18ee0139cf by Ilya Lantukh.

Should I fix MetadataJob filter? Or I just need to fix asserts in test-cases?

> JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails 
> on master
> ---
>
> Key: IGNITE-5866
> URL: https://issues.apache.org/jira/browse/IGNITE-5866
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.1
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> JettyRestProcessorSignedSelfTest and JettyRestProcessorUnsignedSelfTest fails 
> on master
> when run whole test class.
> If run single method both tests succeed.
> testMetadataLocal:
> {noformat}
> junit.framework.AssertionFailedError: expected:<5> but was:<6>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataLocal(JettyRestProcessorAbstractSelfTest.java:1127)
> {noformat}
> testMetadataRemote
> {noformat}
> junit.framework.AssertionFailedError: expected:<6> but was:<7>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataRemote(JettyRestProcessorAbstractSelfTest.java:1174)
> {noformat}



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

[jira] [Assigned] (IGNITE-5881) Web Console: Improve the Сluster active/inactive states control

[Vica Abramova (JIRA)]

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

Vica Abramova reassigned IGNITE-5881:
-

Assignee: Alexey Kuznetsov

> Web Console: Improve the Сluster active/inactive states control
> ---
>
> Key: IGNITE-5881
> URL: https://issues.apache.org/jira/browse/IGNITE-5881
> Project: Ignite
>  Issue Type: Improvement
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Alexey Kuznetsov
>Priority: Minor
> Attachments: Clusters inactive.png
>
>




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

[jira] [Updated] (IGNITE-5881) Web Console: Improve the Сluster active/inactive states control

[Vica Abramova (JIRA)]

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

Vica Abramova updated IGNITE-5881:
--
Priority: Minor  (was: Major)

> Web Console: Improve the Сluster active/inactive states control
> ---
>
> Key: IGNITE-5881
> URL: https://issues.apache.org/jira/browse/IGNITE-5881
> Project: Ignite
>  Issue Type: Improvement
>  Components: UI, wizards
>Reporter: Vica Abramova
>Priority: Minor
> Attachments: Clusters inactive.png
>
>




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

[jira] [Updated] (IGNITE-5881) Web Console: Improve the Сluster active/inactive states control

[Vica Abramova (JIRA)]

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

Vica Abramova updated IGNITE-5881:
--
Attachment: Clusters inactive.png

> Web Console: Improve the Сluster active/inactive states control
> ---
>
> Key: IGNITE-5881
> URL: https://issues.apache.org/jira/browse/IGNITE-5881
> Project: Ignite
>  Issue Type: Improvement
>  Components: UI, wizards
>Reporter: Vica Abramova
> Attachments: Clusters inactive.png
>
>




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

[jira] [Created] (IGNITE-5881) Web Console: Improve the Сluster active/inactive states control

[Vica Abramova (JIRA)]

Vica Abramova created IGNITE-5881:
-

 Summary: Web Console: Improve the Сluster active/inactive states 
control
 Key: IGNITE-5881
 URL: https://issues.apache.org/jira/browse/IGNITE-5881
 Project: Ignite
  Issue Type: Improvement
  Components: UI, wizards
Reporter: Vica Abramova






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

[jira] [Updated] (IGNITE-5336) Add documentation for JDBC thick driver BLOB support

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-5336:
-
Fix Version/s: (was: 2.1)
   2.2

> Add documentation for JDBC thick driver BLOB support
> 
>
> Key: IGNITE-5336
> URL: https://issues.apache.org/jira/browse/IGNITE-5336
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Andrey Gura
> Fix For: 2.2
>
>
> Need to add documentation to readme.io about IGNITE-5203.



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

[jira] [Updated] (IGNITE-5750) Format of uptime for metrics

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-5750:
-
Fix Version/s: (was: 2.1)
   2.2

> Format of uptime for metrics
> 
>
> Key: IGNITE-5750
> URL: https://issues.apache.org/jira/browse/IGNITE-5750
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Alexandr Kuramshin
>Assignee: Yevgeniy Ignatyev
>Priority: Trivial
>  Labels: newbie
> Fix For: 2.2
>
>
> Metrics for local node shows uptime formatted as 00:00:00:000
> But the last colon should be changed to the dot.
> Right format is 00:00:00.000



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

[jira] [Updated] (IGNITE-5330) .NET: Peer assembly loading documentation

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-5330:
-
Fix Version/s: (was: 2.1)
   2.2

> .NET: Peer assembly loading documentation
> -
>
> Key: IGNITE-5330
> URL: https://issues.apache.org/jira/browse/IGNITE-5330
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Affects Versions: 2.1
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.2
>
>
> Document peer assembly loading on https://apacheignite-net.readme.io/
> Update existing docs about {{-assembly}} switch, etc.



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

[jira] [Updated] (IGNITE-5798) Logging Ignite configuration at startup

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-5798:
-
Fix Version/s: (was: 2.1)
   2.2

> Logging Ignite configuration at startup
> ---
>
> Key: IGNITE-5798
> URL: https://issues.apache.org/jira/browse/IGNITE-5798
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexandr Kuramshin
>  Labels: easyfix, newbie
> Fix For: 2.2
>
>
> I've found that IgniteConfiguration is not logged even when 
> -DIGNITE_QUIET=false
> When we starting Ignite with path to the xml, or InputStream, we have to 
> ensure, that all configuration options were properly read. And also we would 
> like to know actual values of uninitialized configuration properties (default 
> values), which will be set only after Ignite get started.
> Monitoring tools, like Visor or WebConsole, do not show all configuration 
> options. And even though they will be updated to show all properties, when 
> new configuration options appear, then tools update will be needed.
> Logging IgniteConfiguration at startup gives a possibility to ensure that the 
> right grid configuration has been applied and leads to better user support 
> based on log analyzing.



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

[jira] [Updated] (IGNITE-4718) Add section in documentation on what actions may cause deadlock

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-4718:
-
Fix Version/s: (was: 2.1)
   2.2

> Add section in documentation on what actions may cause deadlock
> ---
>
> Key: IGNITE-4718
> URL: https://issues.apache.org/jira/browse/IGNITE-4718
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Affects Versions: 1.8
>Reporter: Dmitry Karachentsev
>Assignee: Denis Magda
> Fix For: 2.2
>
>
> Ignite has number of common cases, where wrong usage of API may lead to 
> deadlocks, starvations, cluster hangs, and they should be properly 
> documented. 
> For example, cache operations is not allowed in CacheEntryProcessor, 
> ContinuousQuery's remote filter, etc. And in some callbacks it's possible to 
> use cache API if they annotated with @IgniteAsyncCallback.



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

[jira] [Updated] (IGNITE-5508) Document Web Console Installation from Docker Image

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-5508:
-
Fix Version/s: (was: 2.1)
   2.2

> Document Web Console Installation from Docker Image
> ---
>
> Key: IGNITE-5508
> URL: https://issues.apache.org/jira/browse/IGNITE-5508
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 2.2
>
>
> We need to add a section to the very beginning of the doc below explaining 
> how to install and set up the console from the Docker image:
> https://apacheignite-tools.readme.io/docs/build-and-deploy



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

[jira] [Updated] (IGNITE-5766) Folder platform/cpp/bin and files inside this folder are missing in 2.1

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-5766:
-
Fix Version/s: (was: 2.1)
   2.2

> Folder platform/cpp/bin and files inside this folder are missing in 2.1
> ---
>
> Key: IGNITE-5766
> URL: https://issues.apache.org/jira/browse/IGNITE-5766
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Alex Volkov
> Fix For: 2.2
>
>
> I can't find folder platform/cpp/bin and files 
> bin/odbc/ignite-odbc-amd64.msi, bin/odbc/ignite-odbc-x86.msi inside this 
> folder for 2.1. They were there for 2.0. 
> Could you please check were they move or just missing and fix it.



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

[jira] [Issue Comment Deleted] (IGNITE-5866) JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails on master

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov updated IGNITE-5866:

Comment: was deleted

(was: US - http://reviews.ignite.apache.org/ignite/review/IGNT-CR-247
PR - https://github.com/apache/ignite/pull/2359)

> JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails 
> on master
> ---
>
> Key: IGNITE-5866
> URL: https://issues.apache.org/jira/browse/IGNITE-5866
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.1
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> JettyRestProcessorSignedSelfTest and JettyRestProcessorUnsignedSelfTest fails 
> on master
> when run whole test class.
> If run single method both tests succeed.
> testMetadataLocal:
> {noformat}
> junit.framework.AssertionFailedError: expected:<5> but was:<6>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataLocal(JettyRestProcessorAbstractSelfTest.java:1127)
> {noformat}
> testMetadataRemote
> {noformat}
> junit.framework.AssertionFailedError: expected:<6> but was:<7>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataRemote(JettyRestProcessorAbstractSelfTest.java:1174)
> {noformat}



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

[jira] [Commented] (IGNITE-5866) JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails on master

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5866:


Github user nizhikov closed the pull request at:

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


> JettyRestProcessorUnsignedSelfTest and JettyRestProcessorSignedSelfTest fails 
> on master
> ---
>
> Key: IGNITE-5866
> URL: https://issues.apache.org/jira/browse/IGNITE-5866
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.1
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Minor
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.2
>
>
> JettyRestProcessorSignedSelfTest and JettyRestProcessorUnsignedSelfTest fails 
> on master
> when run whole test class.
> If run single method both tests succeed.
> testMetadataLocal:
> {noformat}
> junit.framework.AssertionFailedError: expected:<5> but was:<6>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataLocal(JettyRestProcessorAbstractSelfTest.java:1127)
> {noformat}
> testMetadataRemote
> {noformat}
> junit.framework.AssertionFailedError: expected:<6> but was:<7>
>   at junit.framework.Assert.fail(Assert.java:57)
>   at junit.framework.Assert.failNotEquals(Assert.java:329)
>   at junit.framework.Assert.assertEquals(Assert.java:78)
>   at junit.framework.Assert.assertEquals(Assert.java:234)
>   at junit.framework.Assert.assertEquals(Assert.java:241)
>   at junit.framework.TestCase.assertEquals(TestCase.java:409)
>   at 
> org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testMetadataRemote(JettyRestProcessorAbstractSelfTest.java:1174)
> {noformat}



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

[jira] [Assigned] (IGNITE-5880) BLAS integration phase 2

[Yury Babak (JIRA)]

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

Yury Babak reassigned IGNITE-5880:
--

Assignee: Yury Babak

> BLAS integration phase 2
> 
>
> Key: IGNITE-5880
> URL: https://issues.apache.org/jira/browse/IGNITE-5880
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.2
>
>
> The second phase of BLAS integration.



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

[jira] [Created] (IGNITE-5880) BLAS integration phase 2

[Yury Babak (JIRA)]

Yury Babak created IGNITE-5880:
--

 Summary: BLAS integration phase 2
 Key: IGNITE-5880
 URL: https://issues.apache.org/jira/browse/IGNITE-5880
 Project: Ignite
  Issue Type: Sub-task
  Components: ml
Reporter: Yury Babak
 Fix For: 2.2


The second phase of BLAS integration.



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

[jira] [Commented] (IGNITE-5856) BLAS integration phase 1

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5856:


Github user ybabak closed the pull request at:

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


> BLAS integration phase 1
> 
>
> Key: IGNITE-5856
> URL: https://issues.apache.org/jira/browse/IGNITE-5856
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
> Fix For: 2.2
>
>
> (i) BLAS multiplication for dense and sparse local matrices.



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

[jira] [Commented] (IGNITE-5869) Unexpected timeout exception while client connected with different BinaryConfiguration compactFooter param.

[Stanilovsky Evgeny (JIRA)]

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

Stanilovsky Evgeny commented on IGNITE-5869:


Dmitry, no, different config must lead into: "configuration is not equal to 
remote node's binary configuration" Exception, but sometimes we got timeout 
exception.

> Unexpected timeout exception while client connected with different 
> BinaryConfiguration compactFooter param.
> ---
>
> Key: IGNITE-5869
> URL: https://issues.apache.org/jira/browse/IGNITE-5869
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.0
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
> Attachments: TcpClientDiscoveryMarshallerCheckSelfTest.java
>
>
> While client connecting with different from cluster 
> BinaryConfiguration::setCompactFooter param, instead of expecting: 
> "configuration is not equal" exception catch: Join process timed out 
> exception.



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

[jira] [Closed] (IGNITE-4697) Web Console: The Main menu looks disabled in demo mode

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov closed IGNITE-4697.


> Web Console: The Main menu looks disabled in demo mode
> --
>
> Key: IGNITE-4697
> URL: https://issues.apache.org/jira/browse/IGNITE-4697
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
>




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

[jira] [Resolved] (IGNITE-4697) Web Console: The Main menu looks disabled in demo mode

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-4697.
--
Resolution: Fixed

Menu reworked.

> Web Console: The Main menu looks disabled in demo mode
> --
>
> Key: IGNITE-4697
> URL: https://issues.apache.org/jira/browse/IGNITE-4697
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
>




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

[jira] [Assigned] (IGNITE-4697) Web Console: The Main menu looks disabled in demo mode

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-4697:


Assignee: Alexey Kuznetsov  (was: Vica Abramova)

> Web Console: The Main menu looks disabled in demo mode
> --
>
> Key: IGNITE-4697
> URL: https://issues.apache.org/jira/browse/IGNITE-4697
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
>




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

[jira] [Assigned] (IGNITE-5865) TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing

[Vitaliy Biryukov (JIRA)]

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

Vitaliy Biryukov  reassigned IGNITE-5865:
-

Assignee: Vitaliy Biryukov 

> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitioned is failing
> -
>
> Key: IGNITE-5865
> URL: https://issues.apache.org/jira/browse/IGNITE-5865
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.1
>Reporter: Pavel Kovalenko
>Assignee: Vitaliy Biryukov 
>  Labels: MakeTeamcityGreenAgain, Muted_test, test-failure
> Fix For: 2.2
>
>
> Test is flaky.
> Also there is always failing test in suite: 
> TxOptimisticDeadlockDetectionTest.testDeadlocksPartitionedNear
> TC build result: 
> http://ci.ignite.apache.org/viewLog.html?buildId=744109=buildResultsDiv=Ignite20Tests_IgniteCacheDeadlockDetection
> Stacktrace: 
> {noformat}
> [2017-07-28 
> 03:31:52,827][ERROR][grid-timeout-worker-#31%transactions.TxOptimisticDeadlockDetectionTest0%][IgniteTxHandler]
>  Failed to prepare DHT transaction: GridDhtTxLocal 
> [nearNodeId=d005de76-4378-4cd5-ad7e-f00593a2, 
> nearFutId=aab9f378d51-37ca90c9-03f5-417c-9731-2c29810e3cc0, nearMiniId=1, 
> nearFinFutId=null, nearFinMiniId=0, nearXidVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], 
> super=GridDhtTxLocalAdapter [nearOnOriginatingNode=false, nearNodes=[], 
> dhtNodes=[], explicitLock=false, super=IgniteTxLocalAdapter 
> [completedBase=null, sndTransformedVals=false, depEnabled=false, 
> txState=IgniteTxStateImpl [activeCacheIds=GridIntList [idx=1, 
> arr=[94416770]], recovery=false, txMap=[IgniteTxEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770, txKey=IgniteTxKey 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=424974513, hash=-1228408719, id=1, name=KeyObject1], 
> cacheId=94416770], val=[op=CREATE, val=CacheObjectImpl [val=null, 
> hasValBytes=true]], prevVal=[op=NOOP, val=null], oldVal=[op=NOOP, val=null], 
> entryProcessorsCol=null, ttl=-1, conflictExpireTime=-1, conflictVer=null, 
> explicitVer=null, dhtVer=null, filters=[], filtersPassed=false, 
> filtersSet=false, entry=GridDhtCacheEntry [rdrs=[], part=694, 
> super=GridDistributedCacheEntry [super=GridCacheMapEntry 
> [key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], val=null, 
> startVer=1501212673290, ver=GridCacheVersion [topVer=112692678, 
> order=1501212673290, nodeOrder=1], hash=-1228408719, 
> extras=GridCacheMvccEntryExtras [mvcc=GridCacheMvcc 
> [locs=[GridCacheMvccCandidate [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, 
> ver=GridCacheVersion [topVer=112692678, order=1501212673287, nodeOrder=1], 
> threadId=846, id=520, topVer=AffinityTopologyVersion [topVer=8, 
> minorTopVer=8], reentry=null, 
> otherNodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673287, nodeOrder=1], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=null, serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=1|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null], GridCacheMvccCandidate 
> [nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, ver=GridCacheVersion 
> [topVer=112692678, order=1501212673314, nodeOrder=1], threadId=847, id=521, 
> topVer=AffinityTopologyVersion [topVer=8, minorTopVer=8], reentry=null, 
> otherNodeId=d005de76-4378-4cd5-ad7e-f00593a2, otherVer=GridCacheVersion 
> [topVer=112692678, order=1501212673293, nodeOrder=3], mappedDhtNodes=null, 
> mappedNearNodes=null, ownerVer=GridCacheVersion [topVer=112692678, 
> order=1501212673287, nodeOrder=1], serOrder=null, 
> key=o.a.i.i.processors.cache.transactions.TxOptimisticDeadlockDetectionTest$KeyObject
>  [idHash=16030069, hash=-1228408719, id=1, name=KeyObject1], 
> masks=local=1|owner=0|ready=1|reentry=0|used=0|tx=1|single_implicit=0|dht_local=1|near_local=0|removed=0|read=0,
>  prevVer=null, nextVer=null]], rmts=null]], flags=2]]], prepared=1, 
> locked=false, nodeId=null, locMapped=false, expiryPlc=null, 
> transferExpiryPlc=false, flags=0, partUpdateCntr=0, serReadVer=null, 
> xidVer=null]]], super=IgniteTxAdapter [xidVer=GridCacheVersion 
> [topVer=112692678, order=1501212673314, nodeOrder=1], writeVer=null, 
> implicit=false, loc=true, threadId=847, startTime=1501212712015, 
> nodeId=5d1c593f-e7b8-4672-9a3f-ff75dfe0, 

[jira] [Updated] (IGNITE-4697) Web Console: The Main menu looks disabled in demo mode

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4697:
-
Fix Version/s: 2.2

> Web Console: The Main menu looks disabled in demo mode
> --
>
> Key: IGNITE-4697
> URL: https://issues.apache.org/jira/browse/IGNITE-4697
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Vica Abramova
> Fix For: 2.2
>
>




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

[jira] [Assigned] (IGNITE-5773) Scheduler throwing NullPointerException

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin reassigned IGNITE-5773:
--

Assignee: Dmitriy Govorukhin  (was: Dmitriy Pavlov)

> Scheduler throwing NullPointerException
> ---
>
> Key: IGNITE-5773
> URL: https://issues.apache.org/jira/browse/IGNITE-5773
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.0
> Environment: Oracle Hotspot 1.8_121
> Ignite 2.0.0
> Springmix 4.3.7
>Reporter: Mikhail Cherkasov
>Assignee: Dmitriy Govorukhin
>Priority: Critical
> Fix For: 2.2
>
>
> NPE occurs during deploying a service as cluster singleton. Ignite scheduler 
> is used as a cron for this purpose, however NPE occurs for ignite version 
> 2.0.0.
> Below is the log information for the exception:
> {noformat}
> 2017-06-06 13:21:08 ERROR GridServiceProcessor:495 - Failed to initialize 
> service (service will not be deployed): AVxezSbWNphcxa1CYjfP
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.schedule.ScheduleFutureImpl.schedule(ScheduleFutureImpl.java:299)
> at 
> org.apache.ignite.internal.processors.schedule.IgniteScheduleProcessor.schedule(IgniteScheduleProcessor.java:56)
> at 
> org.apache.ignite.internal.IgniteSchedulerImpl.scheduleLocal(IgniteSchedulerImpl.java:109)
> at 
> com.mypackage.state.services.MyService.startScheduler(MyService.scala:172)
> at com.mypackage.state.services.MyService.init(MyService.scala:149)
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.redeploy(GridServiceProcessor.java:1097)
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.processAssignment(GridServiceProcessor.java:1698)
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.onSystemCacheUpdated(GridServiceProcessor.java:1372)
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.access$300(GridServiceProcessor.java:117)
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor$ServiceEntriesListener$1.run0(GridServiceProcessor.java:1339)
> at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor$DepRunnable.run(GridServiceProcessor.java:1753)
> 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)
> 2017-06-06 13:21:08:868 ERROR application - Unable to initialise GRID:
> class org.apache.ignite.IgniteException: null
> at 
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:949)
> at 
> org.apache.ignite.internal.IgniteServicesImpl.deployClusterSingleton(IgniteServicesImpl.java:122)
> at 
> com.mypackage.state.mypackage1.InitialiseGrid$$anonfun$apply$1.apply(InitialiseGrid.scala:22)
> at 
> com.mypackage.state.mypackage1.InitialiseGrid$$anonfun$apply$1.apply(InitialiseGrid.scala:19)
> at 
> scala.collection.mutable.ResizableArray$class.foreach(ResizableArray.scala:59)
> at scala.collection.mutable.ArrayBuffer.foreach(ArrayBuffer.scala:48)
> at 
> com.mypackage.state.mypackage1.InitialiseGrid$.apply(InitialiseGrid.scala:19)
> at com.mypackage.state.Application$.main(Application.scala:54)
> at com.mypackage.state.Application.main(Application.scala)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at sbt.Run.invokeMain(Run.scala:67)
> at sbt.Run.run0(Run.scala:61)
> at sbt.Run.sbt$Run$$execute$1(Run.scala:51)
> at sbt.Run$$anonfun$run$1.apply$mcV$sp(Run.scala:55)
> at sbt.Run$$anonfun$run$1.apply(Run.scala:55)
> at sbt.Run$$anonfun$run$1.apply(Run.scala:55)
> at sbt.Logger$$anon$4.apply(Logger.scala:85)
> at sbt.TrapExit$App.run(TrapExit.scala:248)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: class org.apache.ignite.IgniteCheckedException: null
> at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7242)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:258)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:189)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
> at 

[jira] [Commented] (IGNITE-5823) Need to remove CacheAtomicUpdateTimeoutException

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5823:


GitHub user StalkXT opened a pull request:

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

IGNITE-5823 Removed unused exceptions



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

$ git pull https://github.com/StalkXT/ignite IGNITE-5823

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

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


commit 6f2f5244b1ffbdc0dcd19a6239359c7665fbb4aa
Author: StalkXT 
Date:   2017-07-31T10:17:43Z

IGNITE-5823 Removed unused exceptions




> Need to remove CacheAtomicUpdateTimeoutException
> 
>
> Key: IGNITE-5823
> URL: https://issues.apache.org/jira/browse/IGNITE-5823
> Project: Ignite
>  Issue Type: Task
>Reporter: Yakov Zhdanov
>Assignee: Sergey Dorozhkin
>Priority: Minor
>  Labels: newbie
>
> And releated - CacheAtomicUpdateTimeoutCheckedException
> These exceptions are not used any more and can be removed.



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

[jira] [Updated] (IGNITE-5658) Optimizations for data streamer

[Yakov Zhdanov (JIRA)]

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

Yakov Zhdanov updated IGNITE-5658:
--
Attachment: benchmark-full.properties

> Optimizations for data streamer
> ---
>
> Key: IGNITE-5658
> URL: https://issues.apache.org/jira/browse/IGNITE-5658
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Yakov Zhdanov
>Assignee: Yakov Zhdanov
>  Labels: performance
> Fix For: 2.2
>
> Attachments: benchmark-full.properties
>
>
> Data streamer can be improved with this:
> -batch on per-partition basis and send batches to striped pool (for 
> allowOverwirte=false)
> -New default - perNodeParallelOps should be twice CPU count of a remote node 
> (if not set by user, if set then parallelOps for every node is the value 
> provided by user)
> -wait stable topology error should be output as warn



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

[jira] [Commented] (IGNITE-5061) Add ability to enable and disable rebalancing per-node

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-5061:
--

[~ainozemtsev],
Could you please check priority of thew issue?

> Add ability to enable and disable rebalancing per-node
> --
>
> Key: IGNITE-5061
> URL: https://issues.apache.org/jira/browse/IGNITE-5061
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexander Belyak
> Fix For: 2.2
>
>
> It would be nice to have an ability to enable and disable rebalancing per 
> node. 
> First of all, we need to come up with a simple API to allow this. 
> Corresponding methods most likely should be also added to Ignite MBean.
> We need to discuss on the dev-list whether it is enough to have this setting 
> per-node, or this needs to be done on a per-cache basis.



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

[jira] [Updated] (IGNITE-5867) Web console: Add parameter for adding primary key columns to generated POJO class

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-5867:
-
Fix Version/s: 2.2

> Web console: Add parameter for adding primary key columns to generated POJO 
> class
> -
>
> Key: IGNITE-5867
> URL: https://issues.apache.org/jira/browse/IGNITE-5867
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Evgenii Zhuravlev
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
>




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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-4377.

Resolution: Fixed

> Cannot find schema for object with compact footer
> -
>
> Key: IGNITE-4377
> URL: https://issues.apache.org/jira/browse/IGNITE-4377
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, compute
>Affects Versions: 1.7, 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.2
>
>
> When invoking a computation which returns an object from *client* node, 
> "Cannot find schema for object with compact footer" exception occurs some 
> times (only during first invocation)
> {code}
> class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for 
> object with compact footer [typeId=2005649068, schemaId=-1206298342]
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {code}
> Reproducer:
> {code}
> package org.apache.ignite;
> import org.apache.ignite.platform.PlatformComputeBinarizable;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> public class ClientModeCompactFooterTest extends GridCommonAbstractTest {
> public ClientModeCompactFooterTest() {
> super(false);
> }
> public void test() throws Exception {
> for (int i =0; i < 100; i++) {
> startGrid("server", 
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid1.xml");
> Ignite client = startGrid("client", 
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid3.xml");
> PlatformComputeBinarizable res = 
> client.compute().execute("org.apache.ignite.platform.PlatformComputeEchoTask",
>  12);
> assertEquals(1, res.field);
> stopAllGrids();
> }
> }
> }
> {code}



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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4377:


Checked in master, problem seems to be gone. Updated .NET tests: 
{{d758a3f1b09def177b11d85c782ff11e274cfdec}}.

> Cannot find schema for object with compact footer
> -
>
> Key: IGNITE-4377
> URL: https://issues.apache.org/jira/browse/IGNITE-4377
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, compute
>Affects Versions: 1.7, 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.2
>
>
> When invoking a computation which returns an object from *client* node, 
> "Cannot find schema for object with compact footer" exception occurs some 
> times (only during first invocation)
> {code}
> class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for 
> object with compact footer [typeId=2005649068, schemaId=-1206298342]
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {code}
> Reproducer:
> {code}
> package org.apache.ignite;
> import org.apache.ignite.platform.PlatformComputeBinarizable;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> public class ClientModeCompactFooterTest extends GridCommonAbstractTest {
> public ClientModeCompactFooterTest() {
> super(false);
> }
> public void test() throws Exception {
> for (int i =0; i < 100; i++) {
> startGrid("server", 
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid1.xml");
> Ignite client = startGrid("client", 
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid3.xml");
> PlatformComputeBinarizable res = 
> client.compute().execute("org.apache.ignite.platform.PlatformComputeEchoTask",
>  12);
> assertEquals(1, res.field);
> stopAllGrids();
> }
> }
> }
> {code}



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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn updated IGNITE-4377:
---
Fix Version/s: 2.2

> Cannot find schema for object with compact footer
> -
>
> Key: IGNITE-4377
> URL: https://issues.apache.org/jira/browse/IGNITE-4377
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, compute
>Affects Versions: 1.7, 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
> Fix For: 2.2
>
>
> When invoking a computation which returns an object from *client* node, 
> "Cannot find schema for object with compact footer" exception occurs some 
> times (only during first invocation)
> {code}
> class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for 
> object with compact footer [typeId=2005649068, schemaId=-1206298342]
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {code}
> Reproducer:
> {code}
> package org.apache.ignite;
> import org.apache.ignite.platform.PlatformComputeBinarizable;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> public class ClientModeCompactFooterTest extends GridCommonAbstractTest {
> public ClientModeCompactFooterTest() {
> super(false);
> }
> public void test() throws Exception {
> for (int i =0; i < 100; i++) {
> startGrid("server", 
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid1.xml");
> Ignite client = startGrid("client", 
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid3.xml");
> PlatformComputeBinarizable res = 
> client.compute().execute("org.apache.ignite.platform.PlatformComputeEchoTask",
>  12);
> assertEquals(1, res.field);
> stopAllGrids();
> }
> }
> }
> {code}



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

[jira] [Updated] (IGNITE-5876) Web console: error on opening Hadoop Configuration

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-5876:
-
Fix Version/s: 2.2

> Web console: error on opening Hadoop Configuration
> --
>
> Key: IGNITE-5876
> URL: https://issues.apache.org/jira/browse/IGNITE-5876
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
> Attachments: hadoop.patch
>
>
> Just open Configuration - Cluster - Hadoop Configuration
> {code}
> "Error: [$parse:syntax] Syntax Error: Token 'Object' is unexpected, expecting 
> []] at column 9 of the expression [[object Object]] starting at [Object]].
> http://errors.angularjs.org/1.5.11/$parse/syntax?p0=Object=is%20unexpected%2C%20expecting%20%5B%5D%5D=9=%5Bobject%20Object%5D=Object%5D
> minErr/<@https://staging-console.my.com/vendor.ba700f32d508b24fa354.js:1:761642
> throwError@https://staging-console.my.com
> {code}



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

[jira] [Closed] (IGNITE-5734) Web Console: update npm dependensies

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov closed IGNITE-5734.


> Web Console: update npm dependensies
> 
>
> Key: IGNITE-5734
> URL: https://issues.apache.org/jira/browse/IGNITE-5734
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
> Fix For: 2.2
>
>
> Before major release we can update npm dependencies.



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

[jira] [Updated] (IGNITE-4944) Web Console: Highlight hovered line in table

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-4944:
-
Fix Version/s: 2.2

> Web Console: Highlight hovered line in table
> 
>
> Key: IGNITE-4944
> URL: https://issues.apache.org/jira/browse/IGNITE-4944
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI, wizards
>Reporter: Andrey Novikov
>Assignee: Alexey Kuznetsov
> Fix For: 2.2
>
>
> Should work for tables with grouping and pinned columns.
> Hovered line should have color: #ededed



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

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

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-4377:
--

Assignee: Pavel Tupitsyn

> Cannot find schema for object with compact footer
> -
>
> Key: IGNITE-4377
> URL: https://issues.apache.org/jira/browse/IGNITE-4377
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, compute
>Affects Versions: 1.7, 1.8
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Critical
>
> When invoking a computation which returns an object from *client* node, 
> "Cannot find schema for object with compact footer" exception occurs some 
> times (only during first invocation)
> {code}
> class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for 
> object with compact footer [typeId=2005649068, schemaId=-1206298342]
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {code}
> Reproducer:
> {code}
> package org.apache.ignite;
> import org.apache.ignite.platform.PlatformComputeBinarizable;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> public class ClientModeCompactFooterTest extends GridCommonAbstractTest {
> public ClientModeCompactFooterTest() {
> super(false);
> }
> public void test() throws Exception {
> for (int i =0; i < 100; i++) {
> startGrid("server", 
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid1.xml");
> Ignite client = startGrid("client", 
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid3.xml");
> PlatformComputeBinarizable res = 
> client.compute().execute("org.apache.ignite.platform.PlatformComputeEchoTask",
>  12);
> assertEquals(1, res.field);
> stopAllGrids();
> }
> }
> }
> {code}



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

[jira] [Assigned] (IGNITE-5879) .NET: Move TestPlatformPlugin to a separate module

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-5879:
--

Assignee: (was: Pavel Tupitsyn)

> .NET: Move TestPlatformPlugin to a separate module
> --
>
> Key: IGNITE-5879
> URL: https://issues.apache.org/jira/browse/IGNITE-5879
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>  Labels: .NET
>
> Move test plugin to a separate module and load it only for .NET tests so we 
> don't interfere with other tests.
> Dev list discussion: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Plugins-in-tests-td20167.html



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

[jira] [Assigned] (IGNITE-5879) .NET: Move TestPlatformPlugin to a separate module

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn reassigned IGNITE-5879:
--

Assignee: Pavel Tupitsyn

> .NET: Move TestPlatformPlugin to a separate module
> --
>
> Key: IGNITE-5879
> URL: https://issues.apache.org/jira/browse/IGNITE-5879
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
>
> Move test plugin to a separate module and load it only for .NET tests so we 
> don't interfere with other tests.
> Dev list discussion: 
> http://apache-ignite-developers.2346864.n4.nabble.com/Plugins-in-tests-td20167.html



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

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

[Alex Volkov (JIRA)]

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

Alex Volkov edited comment on IGNITE-4377 at 7/31/17 8:33 AM:
--

Retested for master. No exceptions during reproducer runs.
[~ptupitsyn], could you please recheck from your side?


was (Author: avolkov):
Retested for 1.8.9. No exceptions during reproducer runs.
[~ptupitsyn], could you please recheck from your side?

> Cannot find schema for object with compact footer
> -
>
> Key: IGNITE-4377
> URL: https://issues.apache.org/jira/browse/IGNITE-4377
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, compute
>Affects Versions: 1.7, 1.8
>Reporter: Pavel Tupitsyn
>Priority: Critical
>
> When invoking a computation which returns an object from *client* node, 
> "Cannot find schema for object with compact footer" exception occurs some 
> times (only during first invocation)
> {code}
> class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for 
> object with compact footer [typeId=2005649068, schemaId=-1206298342]
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {code}
> Reproducer:
> {code}
> package org.apache.ignite;
> import org.apache.ignite.platform.PlatformComputeBinarizable;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> public class ClientModeCompactFooterTest extends GridCommonAbstractTest {
> public ClientModeCompactFooterTest() {
> super(false);
> }
> public void test() throws Exception {
> for (int i =0; i < 100; i++) {
> startGrid("server", 
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid1.xml");
> Ignite client = startGrid("client", 
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid3.xml");
> PlatformComputeBinarizable res = 
> client.compute().execute("org.apache.ignite.platform.PlatformComputeEchoTask",
>  12);
> assertEquals(1, res.field);
> stopAllGrids();
> }
> }
> }
> {code}



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

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

[Alex Volkov (JIRA)]

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

Alex Volkov commented on IGNITE-4377:
-

Retested for 1.8.9. No exceptions during reproducer runs.
[~ptupitsyn], could you please recheck from your side?

> Cannot find schema for object with compact footer
> -
>
> Key: IGNITE-4377
> URL: https://issues.apache.org/jira/browse/IGNITE-4377
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, compute
>Affects Versions: 1.7, 1.8
>Reporter: Pavel Tupitsyn
>Priority: Critical
>
> When invoking a computation which returns an object from *client* node, 
> "Cannot find schema for object with compact footer" exception occurs some 
> times (only during first invocation)
> {code}
> class org.apache.ignite.binary.BinaryObjectException: Cannot find schema for 
> object with compact footer [typeId=2005649068, schemaId=-1206298342]
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:1738)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:279)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:178)
>   at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:157)
>   at 
> org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
>   at 
> org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal0(BinaryMarshaller.java:100)
>   at 
> org.apache.ignite.marshaller.AbstractNodeNameAwareMarshaller.unmarshal(AbstractNodeNameAwareMarshaller.java:82)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.unmarshal(IgniteUtils.java:9751)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:808)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:996)
>   at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1221)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {code}
> Reproducer:
> {code}
> package org.apache.ignite;
> import org.apache.ignite.platform.PlatformComputeBinarizable;
> import org.apache.ignite.testframework.junits.common.GridCommonAbstractTest;
> public class ClientModeCompactFooterTest extends GridCommonAbstractTest {
> public ClientModeCompactFooterTest() {
> super(false);
> }
> public void test() throws Exception {
> for (int i =0; i < 100; i++) {
> startGrid("server", 
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid1.xml");
> Ignite client = startGrid("client", 
> "modules\\platforms\\dotnet\\Apache.Ignite.Core.Tests\\Config\\Compute\\compute-grid3.xml");
> PlatformComputeBinarizable res = 
> client.compute().execute("org.apache.ignite.platform.PlatformComputeEchoTask",
>  12);
> assertEquals(1, res.field);
> stopAllGrids();
> }
> }
> }
> {code}



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

[jira] [Commented] (IGNITE-4944) Web Console: Highlight hovered line in table

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-4944:


Reviewed. Merged.

> Web Console: Highlight hovered line in table
> 
>
> Key: IGNITE-4944
> URL: https://issues.apache.org/jira/browse/IGNITE-4944
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI, wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
>
> Should work for tables with grouping and pinned columns.
> Hovered line should have color: #ededed



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

[jira] [Closed] (IGNITE-4944) Web Console: Highlight hovered line in table

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-4944.
--
Assignee: Alexey Kuznetsov  (was: Andrey Novikov)

> Web Console: Highlight hovered line in table
> 
>
> Key: IGNITE-4944
> URL: https://issues.apache.org/jira/browse/IGNITE-4944
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI, wizards
>Reporter: Andrey Novikov
>Assignee: Alexey Kuznetsov
>
> Should work for tables with grouping and pinned columns.
> Hovered line should have color: #ededed



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

[jira] [Commented] (IGNITE-5856) BLAS integration phase 1

[Artem Malykh (JIRA)]

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

Artem Malykh commented on IGNITE-5856:
--

[~chief] Looks ok to me.

> BLAS integration phase 1
> 
>
> Key: IGNITE-5856
> URL: https://issues.apache.org/jira/browse/IGNITE-5856
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
>
> (i) BLAS multiplication for dense and sparse local matrices.



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

[jira] [Created] (IGNITE-5879) .NET: Move TestPlatformPlugin to a separate module

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-5879:
--

 Summary: .NET: Move TestPlatformPlugin to a separate module
 Key: IGNITE-5879
 URL: https://issues.apache.org/jira/browse/IGNITE-5879
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn


Move test plugin to a separate module and load it only for .NET tests so we 
don't interfere with other tests.

Dev list discussion: 
http://apache-ignite-developers.2346864.n4.nabble.com/Plugins-in-tests-td20167.html



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

[jira] [Commented] (IGNITE-5734) Web Console: update npm dependensies

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-5734:


Tested

> Web Console: update npm dependensies
> 
>
> Key: IGNITE-5734
> URL: https://issues.apache.org/jira/browse/IGNITE-5734
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Andrey Novikov
> Fix For: 2.2
>
>
> Before major release we can update npm dependencies.



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

[jira] [Assigned] (IGNITE-5876) Web console: error on opening Hadoop Configuration

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-5876:


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

Fixed, please retest.

> Web console: error on opening Hadoop Configuration
> --
>
> Key: IGNITE-5876
> URL: https://issues.apache.org/jira/browse/IGNITE-5876
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Attachments: hadoop.patch
>
>
> Just open Configuration - Cluster - Hadoop Configuration
> {code}
> "Error: [$parse:syntax] Syntax Error: Token 'Object' is unexpected, expecting 
> []] at column 9 of the expression [[object Object]] starting at [Object]].
> http://errors.angularjs.org/1.5.11/$parse/syntax?p0=Object=is%20unexpected%2C%20expecting%20%5B%5D%5D=9=%5Bobject%20Object%5D=Object%5D
> minErr/<@https://staging-console.my.com/vendor.ba700f32d508b24fa354.js:1:761642
> throwError@https://staging-console.my.com
> {code}



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

[jira] [Resolved] (IGNITE-5877) Web console: 'Execute query' doesn't work

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov resolved IGNITE-5877.
--
Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Fixed, please retest. You will need to rebuild ignite binaries.

> Web console: 'Execute query' doesn't work
> -
>
> Key: IGNITE-5877
> URL: https://issues.apache.org/jira/browse/IGNITE-5877
> Project: Ignite
>  Issue Type: Bug
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 2.2
>
>
> For example just start Demo and try to execute its query.
> Query result panel doesn't appear after clicking Execute or Explain button.
> Query history is empty as well.



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

[jira] [Commented] (IGNITE-5706) Redis FLUSHDB command support

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-5706:
--

ok

> Redis FLUSHDB command support
> -
>
> Key: IGNITE-5706
> URL: https://issues.apache.org/jira/browse/IGNITE-5706
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
> Fix For: 2.2
>
>
> https://redis.io/commands/flushdb



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

[jira] [Updated] (IGNITE-5878) Add memory policy name into IgniteOOM exception

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5878:
---
Fix Version/s: (was: 2.1)
   2.2

> Add memory policy name into IgniteOOM exception
> ---
>
> Key: IGNITE-5878
> URL: https://issues.apache.org/jira/browse/IGNITE-5878
> Project: Ignite
>  Issue Type: Wish
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.2
>
>
> I got OOM exception but I was not able to understand what policy exactly I 
> need to tune
> It will be more informative to add memory policy name into exception text
> {code}
> [14:25:23,127][SEVERE][db-checkpoint-thread-#41%tester%][GridCacheDatabaseSharedManager]
>  Runtime error caught during grid runnable execution: GridWorker 
> [name=db-checkpoint-thread, igniteInstanceName=tester, finished=false, 
> hashCode=392861026, interrupted=false, 
> runner=db-checkpoint-thread-#41%tester%]
> class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to 
> find a page for eviction [segmentCapacity=1580, loaded=622, 
> maxDirtyPages=415, dirtyPages=622, cpPages=0, pinnedInSegment=0, 
> failedToPrepare=623]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:1883)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.evictPage(PageMemoryImpl.java:1807)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.access$600(PageMemoryImpl.java:1540)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:540)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:487)
>   at 
> org.gridgain.grid.internal.processors.cache.database.GridCacheSnapshotManager.onChangeTrackerPage(GridCacheSnapshotManager.java:1499)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:648)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:642)
>   at 
> org.apache.ignite.internal.util.lang.GridInClosure3X.apply(GridInClosure3X.java:34)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1197)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:380)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:374)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeUnlock(PageHandler.java:377)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.writeUnlock(DataStructure.java:197)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.releaseAndClose(PagesList.java:362)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.saveMetadata(PagesList.java:320)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.saveStoreMetadata(GridCacheOffheapManager.java:178)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.onCheckpointBegin(GridCacheOffheapManager.java:159)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2134)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:1917)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:1842)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> [14:25:24,964][WARNING][visor-tester-populate-cache-task-0][]  Populating 
> cache: c_partitioned
> [14:25:24,994][WARNING][visor-tester-populate-cache-task-0][DataStreamerImpl] 
> Data streamer will not overwrite existing cache entries for better 
> performance (to change, set allowOverwrite to true)
> [14:25:37,966][WARNING][visor-tester-cache-query-load-task-0][]  Query 
> execution (Query): c_partitioned
> [14:25:37,990][SEVERE][visor-tester-cache-query-load-task-1][] Query 
> execution task error
> class 

[jira] [Updated] (IGNITE-5878) Add memory policy name into IgniteOOM exception

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5878:
---
Affects Version/s: (was: 2.0)
   2.1

> Add memory policy name into IgniteOOM exception
> ---
>
> Key: IGNITE-5878
> URL: https://issues.apache.org/jira/browse/IGNITE-5878
> Project: Ignite
>  Issue Type: Wish
>Affects Versions: 2.1
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.1
>
>
> I got OOM exception but I was not able to understand what policy exactly I 
> need to tune
> It will be more informative to add memory policy name into exception text
> {code}
> [14:25:23,127][SEVERE][db-checkpoint-thread-#41%tester%][GridCacheDatabaseSharedManager]
>  Runtime error caught during grid runnable execution: GridWorker 
> [name=db-checkpoint-thread, igniteInstanceName=tester, finished=false, 
> hashCode=392861026, interrupted=false, 
> runner=db-checkpoint-thread-#41%tester%]
> class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to 
> find a page for eviction [segmentCapacity=1580, loaded=622, 
> maxDirtyPages=415, dirtyPages=622, cpPages=0, pinnedInSegment=0, 
> failedToPrepare=623]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:1883)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.evictPage(PageMemoryImpl.java:1807)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.access$600(PageMemoryImpl.java:1540)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:540)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:487)
>   at 
> org.gridgain.grid.internal.processors.cache.database.GridCacheSnapshotManager.onChangeTrackerPage(GridCacheSnapshotManager.java:1499)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:648)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:642)
>   at 
> org.apache.ignite.internal.util.lang.GridInClosure3X.apply(GridInClosure3X.java:34)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1197)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:380)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:374)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeUnlock(PageHandler.java:377)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.writeUnlock(DataStructure.java:197)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.releaseAndClose(PagesList.java:362)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.saveMetadata(PagesList.java:320)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.saveStoreMetadata(GridCacheOffheapManager.java:178)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.onCheckpointBegin(GridCacheOffheapManager.java:159)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2134)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:1917)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:1842)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> [14:25:24,964][WARNING][visor-tester-populate-cache-task-0][]  Populating 
> cache: c_partitioned
> [14:25:24,994][WARNING][visor-tester-populate-cache-task-0][DataStreamerImpl] 
> Data streamer will not overwrite existing cache entries for better 
> performance (to change, set allowOverwrite to true)
> [14:25:37,966][WARNING][visor-tester-cache-query-load-task-0][]  Query 
> execution (Query): c_partitioned
> [14:25:37,990][SEVERE][visor-tester-cache-query-load-task-1][] Query 
> execution task error
> class 

[jira] [Updated] (IGNITE-5878) Add memory policy name into IgniteOOM exception

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5878:
---
Affects Version/s: 2.0

> Add memory policy name into IgniteOOM exception
> ---
>
> Key: IGNITE-5878
> URL: https://issues.apache.org/jira/browse/IGNITE-5878
> Project: Ignite
>  Issue Type: Wish
>Affects Versions: 2.0
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.1
>
>
> I got OOM exception but I was not able to understand what policy exactly I 
> need to tune
> It will be more informative to add memory policy name into exception text
> {code}
> [14:25:23,127][SEVERE][db-checkpoint-thread-#41%tester%][GridCacheDatabaseSharedManager]
>  Runtime error caught during grid runnable execution: GridWorker 
> [name=db-checkpoint-thread, igniteInstanceName=tester, finished=false, 
> hashCode=392861026, interrupted=false, 
> runner=db-checkpoint-thread-#41%tester%]
> class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to 
> find a page for eviction [segmentCapacity=1580, loaded=622, 
> maxDirtyPages=415, dirtyPages=622, cpPages=0, pinnedInSegment=0, 
> failedToPrepare=623]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:1883)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.evictPage(PageMemoryImpl.java:1807)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.access$600(PageMemoryImpl.java:1540)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:540)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:487)
>   at 
> org.gridgain.grid.internal.processors.cache.database.GridCacheSnapshotManager.onChangeTrackerPage(GridCacheSnapshotManager.java:1499)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:648)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:642)
>   at 
> org.apache.ignite.internal.util.lang.GridInClosure3X.apply(GridInClosure3X.java:34)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1197)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:380)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:374)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeUnlock(PageHandler.java:377)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.writeUnlock(DataStructure.java:197)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.releaseAndClose(PagesList.java:362)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.saveMetadata(PagesList.java:320)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.saveStoreMetadata(GridCacheOffheapManager.java:178)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.onCheckpointBegin(GridCacheOffheapManager.java:159)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2134)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:1917)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:1842)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> [14:25:24,964][WARNING][visor-tester-populate-cache-task-0][]  Populating 
> cache: c_partitioned
> [14:25:24,994][WARNING][visor-tester-populate-cache-task-0][DataStreamerImpl] 
> Data streamer will not overwrite existing cache entries for better 
> performance (to change, set allowOverwrite to true)
> [14:25:37,966][WARNING][visor-tester-cache-query-load-task-0][]  Query 
> execution (Query): c_partitioned
> [14:25:37,990][SEVERE][visor-tester-cache-query-load-task-1][] Query 
> execution task error
> class org.apache.ignite.IgniteException: Runtime failure on bounds: 

[jira] [Updated] (IGNITE-5878) Add memory policy name into IgniteOOM exception

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-5878:
---
Fix Version/s: 2.1

> Add memory policy name into IgniteOOM exception
> ---
>
> Key: IGNITE-5878
> URL: https://issues.apache.org/jira/browse/IGNITE-5878
> Project: Ignite
>  Issue Type: Wish
>Affects Versions: 2.0
>Reporter: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.1
>
>
> I got OOM exception but I was not able to understand what policy exactly I 
> need to tune
> It will be more informative to add memory policy name into exception text
> {code}
> [14:25:23,127][SEVERE][db-checkpoint-thread-#41%tester%][GridCacheDatabaseSharedManager]
>  Runtime error caught during grid runnable execution: GridWorker 
> [name=db-checkpoint-thread, igniteInstanceName=tester, finished=false, 
> hashCode=392861026, interrupted=false, 
> runner=db-checkpoint-thread-#41%tester%]
> class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to 
> find a page for eviction [segmentCapacity=1580, loaded=622, 
> maxDirtyPages=415, dirtyPages=622, cpPages=0, pinnedInSegment=0, 
> failedToPrepare=623]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:1883)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.evictPage(PageMemoryImpl.java:1807)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.access$600(PageMemoryImpl.java:1540)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:540)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:487)
>   at 
> org.gridgain.grid.internal.processors.cache.database.GridCacheSnapshotManager.onChangeTrackerPage(GridCacheSnapshotManager.java:1499)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:648)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:642)
>   at 
> org.apache.ignite.internal.util.lang.GridInClosure3X.apply(GridInClosure3X.java:34)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1197)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:380)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:374)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeUnlock(PageHandler.java:377)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.writeUnlock(DataStructure.java:197)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.releaseAndClose(PagesList.java:362)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.saveMetadata(PagesList.java:320)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.saveStoreMetadata(GridCacheOffheapManager.java:178)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.onCheckpointBegin(GridCacheOffheapManager.java:159)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2134)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:1917)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:1842)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> [14:25:24,964][WARNING][visor-tester-populate-cache-task-0][]  Populating 
> cache: c_partitioned
> [14:25:24,994][WARNING][visor-tester-populate-cache-task-0][DataStreamerImpl] 
> Data streamer will not overwrite existing cache entries for better 
> performance (to change, set allowOverwrite to true)
> [14:25:37,966][WARNING][visor-tester-cache-query-load-task-0][]  Query 
> execution (Query): c_partitioned
> [14:25:37,990][SEVERE][visor-tester-cache-query-load-task-1][] Query 
> execution task error
> class org.apache.ignite.IgniteException: Runtime failure on bounds: 
> 

[jira] [Assigned] (IGNITE-4944) Web Console: Highlight hovered line in table

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin reassigned IGNITE-4944:


Assignee: Andrey Novikov  (was: Dmitriy Shabalin)

added solution, pls review it

> Web Console: Highlight hovered line in table
> 
>
> Key: IGNITE-4944
> URL: https://issues.apache.org/jira/browse/IGNITE-4944
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI, wizards
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
>
> Should work for tables with grouping and pinned columns.
> Hovered line should have color: #ededed



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

[jira] [Created] (IGNITE-5878) Add memory policy name into IgniteOOM exception

[Pavel Konstantinov (JIRA)]

Pavel Konstantinov created IGNITE-5878:
--

 Summary: Add memory policy name into IgniteOOM exception
 Key: IGNITE-5878
 URL: https://issues.apache.org/jira/browse/IGNITE-5878
 Project: Ignite
  Issue Type: Wish
Reporter: Pavel Konstantinov
Priority: Minor


I got OOM exception but I was not able to understand what policy exactly I need 
to tune
It will be more informative to add memory policy name into exception text
{code}
[14:25:23,127][SEVERE][db-checkpoint-thread-#41%tester%][GridCacheDatabaseSharedManager]
 Runtime error caught during grid runnable execution: GridWorker 
[name=db-checkpoint-thread, igniteInstanceName=tester, finished=false, 
hashCode=392861026, interrupted=false, runner=db-checkpoint-thread-#41%tester%]
class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Failed to find 
a page for eviction [segmentCapacity=1580, loaded=622, maxDirtyPages=415, 
dirtyPages=622, cpPages=0, pinnedInSegment=0, failedToPrepare=623]
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.tryToFindSequentially(PageMemoryImpl.java:1883)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.evictPage(PageMemoryImpl.java:1807)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl$Segment.access$600(PageMemoryImpl.java:1540)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:540)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:487)
at 
org.gridgain.grid.internal.processors.cache.database.GridCacheSnapshotManager.onChangeTrackerPage(GridCacheSnapshotManager.java:1499)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:648)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$7.applyx(GridCacheDatabaseSharedManager.java:642)
at 
org.apache.ignite.internal.util.lang.GridInClosure3X.apply(GridInClosure3X.java:34)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1197)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:380)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:374)
at 
org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeUnlock(PageHandler.java:377)
at 
org.apache.ignite.internal.processors.cache.persistence.DataStructure.writeUnlock(DataStructure.java:197)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.releaseAndClose(PagesList.java:362)
at 
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.saveMetadata(PagesList.java:320)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.saveStoreMetadata(GridCacheOffheapManager.java:178)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.onCheckpointBegin(GridCacheOffheapManager.java:159)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2134)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:1917)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:1842)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
[14:25:24,964][WARNING][visor-tester-populate-cache-task-0][]  Populating 
cache: c_partitioned
[14:25:24,994][WARNING][visor-tester-populate-cache-task-0][DataStreamerImpl] 
Data streamer will not overwrite existing cache entries for better performance 
(to change, set allowOverwrite to true)
[14:25:37,966][WARNING][visor-tester-cache-query-load-task-0][]  Query 
execution (Query): c_partitioned
[14:25:37,990][SEVERE][visor-tester-cache-query-load-task-1][] Query execution 
task error
class org.apache.ignite.IgniteException: Runtime failure on bounds: 
[lower=null, upper=null]
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.find(BPlusTree.java:965)
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.cursor(IgniteCacheOffheapManagerImpl.java:1515)
at 

[jira] [Assigned] (IGNITE-5793) Cache with constant time TTL for entries and enabled persistence hangs for a long time when TTL expirations start

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk reassigned IGNITE-5793:


Assignee: Alexey Goncharuk

> Cache with constant time TTL for entries and enabled persistence hangs for a 
> long time when TTL expirations start
> -
>
> Key: IGNITE-5793
> URL: https://issues.apache.org/jira/browse/IGNITE-5793
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.0
>Reporter: Ivan Rakov
>Assignee: Alexey Goncharuk
> Fix For: 2.2
>
> Attachments: ttl_hang.patch
>
>
> Right after expiration time, all threads from sys-stripe pool are busy with 
> removing expired entries, example stacktrace:
> {noformat}
> Thread 
> [name="sys-stripe-3-#35%database.IgniteDbSnapshotWithEvictionsSelfTest1%", 
> id=60, state=RUNNABLE, blockCnt=0, waitCnt=101794]
> at o.a.i.i.binary.BinaryObjectImpl.typeId(BinaryObjectImpl.java:278)
> at 
> o.a.i.i.processors.cache.binary.CacheObjectBinaryProcessorImpl.typeId(CacheObjectBinaryProcessorImpl.java:672)
> at 
> o.a.i.i.processors.query.GridQueryProcessor.typeByValue(GridQueryProcessor.java:1688)
> at 
> o.a.i.i.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:2177)
> at 
> o.a.i.i.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:451)
> at 
> o.a.i.i.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishRemove(IgniteCacheOffheapManagerImpl.java:1456)
> at 
> o.a.i.i.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1419)
> at 
> o.a.i.i.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.remove(GridCacheOffheapManager.java:1241)
> at 
> o.a.i.i.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:383)
> at 
> o.a.i.i.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3221)
> at 
> o.a.i.i.processors.cache.GridCacheMapEntry.onExpired(GridCacheMapEntry.java:3028)
> at 
> o.a.i.i.processors.cache.GridCacheMapEntry.onTtlExpired(GridCacheMapEntry.java:2961)
> at 
> o.a.i.i.processors.cache.GridCacheTtlManager$1.applyx(GridCacheTtlManager.java:61)
> at 
> o.a.i.i.processors.cache.GridCacheTtlManager$1.applyx(GridCacheTtlManager.java:52)
> at 
> o.a.i.i.util.lang.IgniteInClosure2X.apply(IgniteInClosure2X.java:38)
> at 
> o.a.i.i.processors.cache.IgniteCacheOffheapManagerImpl.expire(IgniteCacheOffheapManagerImpl.java:1007)
> at 
> o.a.i.i.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:198)
> at 
> o.a.i.i.processors.cache.GridCacheTtlManager.expire(GridCacheTtlManager.java:160)
> at 
> o.a.i.i.processors.cache.GridCacheUtils.unwindEvicts(GridCacheUtils.java:854)
> at 
> o.a.i.i.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1073)
> at 
> o.a.i.i.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:561)
> at 
> o.a.i.i.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:378)
> at 
> o.a.i.i.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:304)
> at 
> o.a.i.i.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:99)
> at 
> o.a.i.i.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:293)
> at 
> o.a.i.i.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at 
> o.a.i.i.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at 
> o.a.i.i.managers.communication.GridIoManager.access$4200(GridIoManager.java:126)
> at 
> o.a.i.i.managers.communication.GridIoManager$9.run(GridIoManager.java:1097)
> at o.a.i.i.util.StripedExecutor$Stripe.run(StripedExecutor.java:483)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}
> Patch with reproducer test and expire metrics attached. Put/Get/Expire 
> metrics when expirations start looks like that:
> {noformat}
> [17:21:26,908][INFO 
> ][db-checkpoint-thread-#62%database.TtlHangReproducerTest1%][GridCacheDatabaseSharedManager]
>  Checkpoint started [checkpointId=9e564ba2-8c41-4cf9-bfa8-75e3d50c00dc, 
> startPtr=FileWALPointer [idx=64, fileOffset=45383475, len=4459, 
> forceFlush=true], checkpointLockWait=0ms, checkpointLockHoldTime=16ms, 
> pages=259801, reason='timeout']
> @@@ putsPerSec=5459  getsPerSec=3063 expiresPerSec=0 
> MemoryMetricsSnapshot{name='dfltMemPlc', totalAllocatedPages=0, 
> allocationRate=0.0, evictionRate=0.0, 

[jira] [Commented] (IGNITE-5706) Redis FLUSHDB command support

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-5706:


Hi, could you please check compilation on CI server?
It seems last merge failed to compile.
http://ci.ignite.apache.org/project.html?projectId=Ignite20Tests_Ignite20Tests=%3Cdefault%3E

> Redis FLUSHDB command support
> -
>
> Key: IGNITE-5706
> URL: https://issues.apache.org/jira/browse/IGNITE-5706
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
> Fix For: 2.2
>
>
> https://redis.io/commands/flushdb



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

[jira] [Comment Edited] (IGNITE-5869) Unexpected timeout exception while client connected with different BinaryConfiguration compactFooter param.

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan edited comment on IGNITE-5869 at 7/31/17 7:33 AM:


Is Ignite supposed to work with different compactFooter configurations in the 
cluster? If not, why do we even allow for such clients to connect?


was (Author: dsetrakyan):
Is Ignite supposed to work with different compactFooter configurations in the 
cluster? If not, why do we even allow for such client to connect?

> Unexpected timeout exception while client connected with different 
> BinaryConfiguration compactFooter param.
> ---
>
> Key: IGNITE-5869
> URL: https://issues.apache.org/jira/browse/IGNITE-5869
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.0
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
> Attachments: TcpClientDiscoveryMarshallerCheckSelfTest.java
>
>
> While client connecting with different from cluster 
> BinaryConfiguration::setCompactFooter param, instead of expecting: 
> "configuration is not equal" exception catch: Join process timed out 
> exception.



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

[jira] [Commented] (IGNITE-5869) Unexpected timeout exception while client connected with different BinaryConfiguration compactFooter param.

[Dmitriy Setrakyan (JIRA)]

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

Dmitriy Setrakyan commented on IGNITE-5869:
---

Is Ignite supposed to work with different compactFooter configurations in the 
cluster? If not, why do we even allow for such client to connect?

> Unexpected timeout exception while client connected with different 
> BinaryConfiguration compactFooter param.
> ---
>
> Key: IGNITE-5869
> URL: https://issues.apache.org/jira/browse/IGNITE-5869
> Project: Ignite
>  Issue Type: Bug
>  Components: clients
>Affects Versions: 2.0
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
> Attachments: TcpClientDiscoveryMarshallerCheckSelfTest.java
>
>
> While client connecting with different from cluster 
> BinaryConfiguration::setCompactFooter param, instead of expecting: 
> "configuration is not equal" exception catch: Join process timed out 
> exception.



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

[jira] [Updated] (IGNITE-5778) Update JobMetrics on each job add/start/finish methods and add possibility to turn off JobMetrics

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev updated IGNITE-5778:
--
Priority: Trivial  (was: Major)

> Update JobMetrics on each job add/start/finish methods and add possibility to 
> turn off JobMetrics
> -
>
> Key: IGNITE-5778
> URL: https://issues.apache.org/jira/browse/IGNITE-5778
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 1.9
>Reporter: Evgenii Zhuravlev
>Assignee: Evgenii Zhuravlev
>Priority: Trivial
> Fix For: 2.2
>
>




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

[jira] [Closed] (IGNITE-5706) Redis FLUSHDB command support

[Roman Shtykh (JIRA)]

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

Roman Shtykh closed IGNITE-5706.


> Redis FLUSHDB command support
> -
>
> Key: IGNITE-5706
> URL: https://issues.apache.org/jira/browse/IGNITE-5706
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
> Fix For: 2.2
>
>
> https://redis.io/commands/flushdb



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

[jira] [Commented] (IGNITE-5706) Redis FLUSHDB command support

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5706:


Github user asfgit closed the pull request at:

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


> Redis FLUSHDB command support
> -
>
> Key: IGNITE-5706
> URL: https://issues.apache.org/jira/browse/IGNITE-5706
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
> Fix For: 2.2
>
>
> https://redis.io/commands/flushdb



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

[jira] [Commented] (IGNITE-5706) Redis FLUSHDB command support

[Andrey Novikov (JIRA)]

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

Andrey Novikov commented on IGNITE-5706:


Hi [~roman_s],

If database count is not limited or big, your solution is correct. Looks good, 
please merge.

> Redis FLUSHDB command support
> -
>
> Key: IGNITE-5706
> URL: https://issues.apache.org/jira/browse/IGNITE-5706
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
> Fix For: 2.2
>
>
> https://redis.io/commands/flushdb



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