[jira] [Commented] (IGNITE-6802) NullPointerException when WAL store and WAL archive paths are same

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-6802:


Hi [~SomeFire], now under https://issues.apache.org/jira/browse/IGNITE-7017  
there was supported special WAL mode: 'no archiver'.
In case folders are equall then all files (both archive and work) are placed 
into this folder instead of placing files first in work and then copying file 
from work to archive.

> NullPointerException when WAL store and WAL archive paths are same 
> ---
>
> Key: IGNITE-6802
> URL: https://issues.apache.org/jira/browse/IGNITE-6802
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Alexey Kukushkin
>Assignee: Ryabov Dmitrii
>Priority: Major
>  Labels: newbie, usability
> Fix For: 2.5
>
>
> Configuring WAL store and WAL archive paths to be the same results in 
> NullPointerException. We should display a meaningful error about the 
> misconfiguration instead.
> See 
> http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-in-FileWriteAheadLogManager-java-1313-tc17860.html
> The thread includes the reproducer code and stack trace. I was able to 
> reproduce the issue with today's (31-Oct-2017) Apache master.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (IGNITE-7074) NPE when WAL path and WAL archive path are the same

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov resolved IGNITE-7074.

Resolution: Fixed

Under https://issues.apache.org/jira/browse/IGNITE-7017 there was supported 
special WAL mode: 'no archiver'.
In case folders are equall then all files (both archive and work) are placed 
into this folder instead of placing files first in work and then copying file 
from work to archive.

> NPE when WAL path and WAL archive path are the same
> ---
>
> Key: IGNITE-7074
> URL: https://issues.apache.org/jira/browse/IGNITE-7074
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.2, 2.3
>Reporter: Dan Ellis
>Assignee: Dmitriy Pavlov
>Priority: Minor
> Fix For: 2.5
>
>
> Log here: https://gist.github.com/danellis/660054b5a7f0e83ae4dcac8c1516d2ca
> It appears that the WAL path and the WAL archive path cannot be set to the 
> same directory. When they are, instead of the invalid configuration being 
> caught, a number of NPEs are thrown as shown in the above log.
> Additionally, this constraint does not appear to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7074) NPE when WAL path and WAL archive path are the same

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-7074:
---
Fix Version/s: 2.5

> NPE when WAL path and WAL archive path are the same
> ---
>
> Key: IGNITE-7074
> URL: https://issues.apache.org/jira/browse/IGNITE-7074
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.2, 2.3
>Reporter: Dan Ellis
>Assignee: Dmitriy Pavlov
>Priority: Minor
> Fix For: 2.5
>
>
> Log here: https://gist.github.com/danellis/660054b5a7f0e83ae4dcac8c1516d2ca
> It appears that the WAL path and the WAL archive path cannot be set to the 
> same directory. When they are, instead of the invalid configuration being 
> caught, a number of NPEs are thrown as shown in the above log.
> Additionally, this constraint does not appear to be documented.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7090) Semaphore Stuck when no acquirers to assign permit

[Tim Onyschak (JIRA)]

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

Tim Onyschak commented on IGNITE-7090:
--

I may be doing something wrong, but when i attempted both solution. Removing 
the closure and manually adjusting the SemaphoreState, neither seemed to work. 
The execution without the closure in same thread seems to hang/deadlock on 
initializeSemaphore() ( specifically cacheView.get(key); )

Then, manually setting SemaphoreState within the 
DataStructuresProcessor#semaphore() witha few iterations of the below code did 
not seem to work as well. I must be missing something within the onNodeRemoved. 
Guessing something around the GridCacheSemaphoreImpl.Sync

 
{code:java}
if(val!=null){
GridCacheSemaphoreState semState=(GridCacheSemaphoreState)val;
boolean updated=false;
Map waiters = semState.getWaiters();
for(UUID nodeId:waiters.keySet()){
ClusterNode node = ctx.cluster().get().node(nodeId);
if(node==null){
waiters.remove(nodeId);
updated=true;
}
}
if(updated) {
semState.setWaiters(waiters);
sem0.onUpdate(semState);
retVal=semState;
}
 }{code}
 

Any thoughts? 

 

> Semaphore Stuck when no acquirers to assign permit
> --
>
> Key: IGNITE-7090
> URL: https://issues.apache.org/jira/browse/IGNITE-7090
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, data structures
>Affects Versions: 2.1, 2.4
>Reporter: Tim Onyschak
>Priority: Major
> Fix For: 2.5
>
> Attachments: SemaphoreFailoverNoWaitingAcquirerTest.java
>
>
> If no acquirers are available to take permit of semaphore, the permit never 
> gets release and any further acquirerers will wait forever. 
> On node shut down DataStructuresProcessor.dsMap gets cleared out prior to 
> event listener being able to execute onNodeRemoved, hence owner is never 
> cleared out if it was unable to pass to a different acquirer. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7565) Remove IgniteSet from heap

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-7565:


 Summary: Remove IgniteSet from heap
 Key: IGNITE-7565
 URL: https://issues.apache.org/jira/browse/IGNITE-7565
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.2
Reporter: Alexander Belyak


IgniteSet store all data in durable memory and in java heap. It's not good for 
big clusters and big sets, so we need to remove values from heap.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7564) Document IgniteSet memory consumption

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-7564:


 Summary: Document IgniteSet memory consumption
 Key: IGNITE-7564
 URL: https://issues.apache.org/jira/browse/IGNITE-7564
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Affects Versions: 2.2
Reporter: Alexander Belyak


We need to document onheap memory consumption of IgniteSet collections (all 
values stored in durable memory AND in java heap).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-7357) Web Console: Add support for custom SMTP servers

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-7357.
--

> Web Console: Add support for custom SMTP servers
> 
>
> Key: IGNITE-7357
> URL: https://issues.apache.org/jira/browse/IGNITE-7357
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.4
>
>
> For now Web Console supports only "external" services like GMail.
> We should support custom SMTP servers also.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7357) Web Console: Add support for custom SMTP servers

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7357:


Tested

> Web Console: Add support for custom SMTP servers
> 
>
> Key: IGNITE-7357
> URL: https://issues.apache.org/jira/browse/IGNITE-7357
> Project: Ignite
>  Issue Type: Improvement
>  Components: wizards
>Reporter: Alexey Kuznetsov
>Assignee: Pavel Konstantinov
>Priority: Major
> Fix For: 2.4
>
>
> For now Web Console supports only "external" services like GMail.
> We should support custom SMTP servers also.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7323) Update Storm dependencies to 1.1.1

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7323:


Github user asfgit closed the pull request at:

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


> Update Storm dependencies to 1.1.1
> --
>
> Key: IGNITE-7323
> URL: https://issues.apache.org/jira/browse/IGNITE-7323
> Project: Ignite
>  Issue Type: Bug
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>Priority: Major
> Fix For: 2.5
>
>
> http://storm.apache.org/2017/08/01/storm111-released.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7556) Docs should feature specifying SQL key more prominently

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7556:
-

[~ilyak] , thanks for bringing this to our attention. Technically, this issue 
arises only when the annotations or QueryEntities are used for SQL level 
configuration. If a table is created with CREATE TABLE command then the INSERT 
doc is 100% correct. I'll think over on how to add information on "_key" to 
cover QueryEntity use cases.

> Docs should feature specifying SQL key more prominently
> ---
>
> Key: IGNITE-7556
> URL: https://issues.apache.org/jira/browse/IGNITE-7556
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Reporter: Ilya Kasnacheev
>Priority: Minor
> Fix For: 2.5
>
>
> Descriptions on [https://apacheignite-sql.readme.io/docs/schema-and-indexes] 
> are not DML-friendly
> After reading this page and [https://apacheignite-sql.readme.io/docs/insert], 
> one would likely still unable to write working INSERT because there won't be 
> primary key in it.
> Their only chance is to spot _key reference in infoblock, or infer usability 
> of setKeyFields() with single key type. Both are unlikely, leading to 
> questions such as 
> [https://stackoverflow.com/questions/48460214/how-do-i-read-data-from-ignite-kv-storage-using-jdbc]
>  see {{Key is missing from query}}
> Such problems are hard to debug. They can be avoided if all examples of 
> QueryEntities in docs will contain setKeyFields, and INSERT docs page will 
> refer to _key field.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7556) Docs should feature specifying SQL key more prominently

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-7556:
---

Assignee: Denis Magda

> Docs should feature specifying SQL key more prominently
> ---
>
> Key: IGNITE-7556
> URL: https://issues.apache.org/jira/browse/IGNITE-7556
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Reporter: Ilya Kasnacheev
>Assignee: Denis Magda
>Priority: Minor
> Fix For: 2.5
>
>
> Descriptions on [https://apacheignite-sql.readme.io/docs/schema-and-indexes] 
> are not DML-friendly
> After reading this page and [https://apacheignite-sql.readme.io/docs/insert], 
> one would likely still unable to write working INSERT because there won't be 
> primary key in it.
> Their only chance is to spot _key reference in infoblock, or infer usability 
> of setKeyFields() with single key type. Both are unlikely, leading to 
> questions such as 
> [https://stackoverflow.com/questions/48460214/how-do-i-read-data-from-ignite-kv-storage-using-jdbc]
>  see {{Key is missing from query}}
> Such problems are hard to debug. They can be avoided if all examples of 
> QueryEntities in docs will contain setKeyFields, and INSERT docs page will 
> refer to _key field.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7556) Docs should feature specifying SQL key more prominently

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-7556:

Fix Version/s: 2.5

> Docs should feature specifying SQL key more prominently
> ---
>
> Key: IGNITE-7556
> URL: https://issues.apache.org/jira/browse/IGNITE-7556
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Reporter: Ilya Kasnacheev
>Assignee: Denis Magda
>Priority: Minor
> Fix For: 2.5
>
>
> Descriptions on [https://apacheignite-sql.readme.io/docs/schema-and-indexes] 
> are not DML-friendly
> After reading this page and [https://apacheignite-sql.readme.io/docs/insert], 
> one would likely still unable to write working INSERT because there won't be 
> primary key in it.
> Their only chance is to spot _key reference in infoblock, or infer usability 
> of setKeyFields() with single key type. Both are unlikely, leading to 
> questions such as 
> [https://stackoverflow.com/questions/48460214/how-do-i-read-data-from-ignite-kv-storage-using-jdbc]
>  see {{Key is missing from query}}
> Such problems are hard to debug. They can be avoided if all examples of 
> QueryEntities in docs will contain setKeyFields, and INSERT docs page will 
> refer to _key field.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7469) Update Apache Ignite documentation about RPM-repository usage

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-7469:
-

[~pgarg], please:
 * do a final review of this section 
[https://apacheignite.readme.io/v2.3/docs/getting-started-24#section-rpm-package-installation]
 * prepare "Installing from RPM" section on Ignite download page 
([https://ignite.apache.org/download.cgi).] Put the section below "Download 
from NuGet". The site section should show how to add the Ignite repo to a Yum 
list and install Ignite afterward. Provide a link to the readme.io doc so that 
a user can see how to do the rest (starting a node, scavenging through the 
logs, etc.) .

 

> Update Apache Ignite documentation about RPM-repository usage
> -
>
> Key: IGNITE-7469
> URL: https://issues.apache.org/jira/browse/IGNITE-7469
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.4
>
>
> After IGNITE-7107 release in 2.4 version Apache Ignite will be available 
> through custom RPM repository packed in RPM package. Corresponding 
> documentation (how to add RPM-repository and install from it) should be 
> created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7469) Update Apache Ignite documentation about RPM-repository usage

[Denis Magda (JIRA)]

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

Denis Magda reassigned IGNITE-7469:
---

Assignee: Prachi Garg  (was: Peter Ivanov)

> Update Apache Ignite documentation about RPM-repository usage
> -
>
> Key: IGNITE-7469
> URL: https://issues.apache.org/jira/browse/IGNITE-7469
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Peter Ivanov
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.4
>
>
> After IGNITE-7107 release in 2.4 version Apache Ignite will be available 
> through custom RPM repository packed in RPM package. Corresponding 
> documentation (how to add RPM-repository and install from it) should be 
> created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-7403) Improve content on What's Ignite page

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-7403.
---

> Improve content on What's Ignite page
> -
>
> Key: IGNITE-7403
> URL: https://issues.apache.org/jira/browse/IGNITE-7403
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.4
>
> Attachments: What.png, What_v2.png, What_v3.png, What_v4.png, 
> What_v4_1.png, What_v5.png, ignite_architecture.png
>
>
> A proposed of a new draft for the What's Ignite page:
> https://ignite.apache.org/whatisignite-2.html
> The goal is to make the page more informative and tell about the main things 
> of Ignite or provide references to them. Overall, the structure should be as 
> follows:
> - Product name and definition.
> - Diagram.
> - Features and Benefits
> - Ignite facts



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7403) Improve content on What's Ignite page

[Prachi Garg (JIRA)]

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

Prachi Garg commented on IGNITE-7403:
-

All recommended changes are merged - 
[https://ignite.apache.org/whatisignite.html]

Old 'whatisignite' page is saved at - 
https://ignite.apache.org/whatisignite-bk.html

> Improve content on What's Ignite page
> -
>
> Key: IGNITE-7403
> URL: https://issues.apache.org/jira/browse/IGNITE-7403
> Project: Ignite
>  Issue Type: Task
>  Components: site
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Major
> Fix For: 2.4
>
> Attachments: What.png, What_v2.png, What_v3.png, What_v4.png, 
> What_v4_1.png, What_v5.png, ignite_architecture.png
>
>
> A proposed of a new draft for the What's Ignite page:
> https://ignite.apache.org/whatisignite-2.html
> The goal is to make the page more informative and tell about the main things 
> of Ignite or provide references to them. Overall, the structure should be as 
> follows:
> - Product name and definition.
> - Diagram.
> - Features and Benefits
> - Ignite facts



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7563) .NET: Binary object builder dynamic API

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7563:
--

 Summary: .NET: Binary object builder dynamic API
 Key: IGNITE-7563
 URL: https://issues.apache.org/jira/browse/IGNITE-7563
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn


Provide a way to build binary objects with C# {{dynamic}} API:

{code}
IBinary bin = ignite.GetBinary();
IBinaryObjectBuilder builder = bin.GetBuilder("myType");
builder.SetField("Name", "Jack");  // current API

IBinaryObjectBuilderDynamic dynBuilder = builder.AsDynamic();
dynBuilder.Name = "Jack";
IBinaryObject result = dynBuilder.Build();
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7562) .NET: Binary object as dynamic object

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7562:
--

 Summary: .NET: Binary object as dynamic object
 Key: IGNITE-7562
 URL: https://issues.apache.org/jira/browse/IGNITE-7562
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn


Provide a way to access {{IBinaryObject}} fields through C# {{dynamic}} API:

{code}
IBinaryObject obj = cache.Get(1);
var name = obj.GetField("Name");  // Current API

dynamic dynObj = obj.AsDynamic();
name = dynObj.Name;  // Proposed API
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7561) .NET: Service proxy as dynamic object

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-7561:
--

 Summary: .NET: Service proxy as dynamic object
 Key: IGNITE-7561
 URL: https://issues.apache.org/jira/browse/IGNITE-7561
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn


Currently we require user to provide an interface to interact with .NET and 
Java services.

We could also provide a dynamic API (based on {{dynamic}} keyword) like this:

{code}
IServices services = ignite.GetServices();
dynamic prx = services.GetDynamicServiceProxy("someService");
prx.Foo();
prx.Bar = 1;
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7534) ClusterGroupExample duplicate

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7534:


Github user asfgit closed the pull request at:

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


> ClusterGroupExample duplicate
> -
>
> Key: IGNITE-7534
> URL: https://issues.apache.org/jira/browse/IGNITE-7534
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Sergey Kozlov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.4
>
>
> The examples \{{org.apache.ignite.examples.cluster.ClusterGroupExample}} and 
> \{{org.apache.ignite.examples.computegrid.cluster.ClusterGroupExample}} are 
> same



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-7534) ClusterGroupExample duplicate

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko closed IGNITE-7534.
---

> ClusterGroupExample duplicate
> -
>
> Key: IGNITE-7534
> URL: https://issues.apache.org/jira/browse/IGNITE-7534
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Sergey Kozlov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.4
>
>
> The examples \{{org.apache.ignite.examples.cluster.ClusterGroupExample}} and 
> \{{org.apache.ignite.examples.computegrid.cluster.ClusterGroupExample}} are 
> same



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7560) Baseline topology documentation

[Denis Magda (JIRA)]

Denis Magda created IGNITE-7560:
---

 Summary: Baseline topology documentation
 Key: IGNITE-7560
 URL: https://issues.apache.org/jira/browse/IGNITE-7560
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Denis Magda
Assignee: Denis Magda
 Fix For: 2.4


Document baseline topology architecture, benefits, and usage:

https://cwiki.apache.org/confluence/display/IGNITE/IEP-4+Baseline+topology+for+caches



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7358) Document ELB based AWS IP Finder

[Prachi Garg (JIRA)]

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

Prachi Garg commented on IGNITE-7358:
-

[~dmagda], Please review - 
https://apacheignite-mix.readme.io/v2.3/docs/amazon-aws-24

> Document ELB based AWS IP Finder
> 
>
> Key: IGNITE-7358
> URL: https://issues.apache.org/jira/browse/IGNITE-7358
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Critical
> Fix For: 2.4
>
>
> Document the new IP finder that can be used for AWS deployments - IGNITE-7304.
> The main documentation should be hosted here:
> https://apacheignite-mix.readme.io/docs/amazon-aws
> and there we need to provide a reference to ELB IP finder:
> https://apacheignite.readme.io/docs/cluster-config



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7358) Document ELB based AWS IP Finder

[Prachi Garg (JIRA)]

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

Prachi Garg reassigned IGNITE-7358:
---

Assignee: Denis Magda  (was: Prachi Garg)

> Document ELB based AWS IP Finder
> 
>
> Key: IGNITE-7358
> URL: https://issues.apache.org/jira/browse/IGNITE-7358
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 2.4
>
>
> Document the new IP finder that can be used for AWS deployments - IGNITE-7304.
> The main documentation should be hosted here:
> https://apacheignite-mix.readme.io/docs/amazon-aws
> and there we need to provide a reference to ELB IP finder:
> https://apacheignite.readme.io/docs/cluster-config



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-6252) Cassandra Cache Store Session does not retry if prepare statement failed

[Denis Magda (JIRA)]

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

Denis Magda updated IGNITE-6252:

Fix Version/s: 2.4

> Cassandra Cache Store Session does not retry if prepare statement failed
> 
>
> Key: IGNITE-6252
> URL: https://issues.apache.org/jira/browse/IGNITE-6252
> Project: Ignite
>  Issue Type: Bug
>  Components: cassandra
>Affects Versions: 2.0, 2.1
>Reporter: Sunny Chan
>Assignee: Igor Rudyak
>Priority: Major
> Fix For: 2.4
>
>
> During our testing, we have found that certain warning about prepared 
> statement:
> 2017-08-31 11:27:19.479 
> org.apache.ignite.cache.store.cassandra.CassandraCacheStore 
> flusher-0-#265%% WARN CassandraCacheStore - Prepared statement cluster 
> error detected, refreshing Cassandra session
> com.datastax.driver.core.exceptions.InvalidQueryException: Tried to execute 
> unknown prepared query : 0xc7647611fd755386ef63478ee7de577b. You may have 
> used a PreparedStatement that was created with another Cluster instance.
> We notice that after this warning occurs some of the data didn't persist 
> properly in cassandra cache. After further examining the Ignite's 
> CassandraSessionImpl code in method 
> execute(BatchExecutionAssistance,Iterable), we found that at around [line 
> 283|https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L283],
>  if the prepare statement fails in the asnyc call, it will not retry the 
> operation as the error is stored in [line 
> 269|https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L269]
>  and cleared in [line 
> 277|https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L277]
>  but it was not checked again after going through the [ResultSetFuture 
> |https://github.com/apache/ignite/blob/86bd544a557663bce497134f7826be6b24d53330/modules/cassandra/store/src/main/java/org/apache/ignite/cache/store/cassandra/session/CassandraSessionImpl.java#L307].
> I believe in line 307 you should check for error != null such that any 
> failure will be retry.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-7000) .NET: Document .NET Core support and running on Linux / macOs

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-7000.
---

Looks good.

> .NET: Document .NET Core support and running on Linux / macOs
> -
>
> Key: IGNITE-7000
> URL: https://issues.apache.org/jira/browse/IGNITE-7000
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, platforms
>Reporter: Pavel Tupitsyn
>Assignee: Prachi Garg
>Priority: Minor
>  Labels: .NET, xplat
> Fix For: 2.4
>
> Attachments: Cross-Platform Support.md
>
>
> Create a documentation page about running Ignite.NET under .NET Core and/or 
> Linux. Things to mention:
> * Delegates can't be serialized under .NET Core: 
> https://github.com/dotnet/corefx/issues/24424
> * Build warning - suppress {{NU1701}} with 
> {{NU1701}}
> * Java home, dll paths, etc
> * Publish and deploy (copy libs folder to {{dotnet publish}} dir)
> * macOs: document {{No Java runtime present, requesting install.}} issue 
> https://bugs.openjdk.java.net/browse/JDK-7131356, 
> https://github.com/s-u/rJava/issues/37
> * VS Code and Rider
> * Mono is supported (useful for 32 bit and/or older distros): need to set 
> {{IgniteHome}}, need {{sudo apt-get install mono-reference-assemblies-4.0}} 
> to build
> * {{ Version="4.4.0" />}} may be required
> * Make sure examples in binary package can be run on Mono and .NET Core on 
> every OS.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-7345) Spark Data Frames and Ignite Documentation

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-7345.
---

> Spark Data Frames and Ignite Documentation
> --
>
> Key: IGNITE-7345
> URL: https://issues.apache.org/jira/browse/IGNITE-7345
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
>Priority: Critical
> Fix For: 2.4
>
>
> Spark Data frames integration [1] needs to be documented in this [2] domain.
> [1] 
> http://apache-ignite-developers.2346864.n4.nabble.com/Spark-data-frames-integration-merged-td25817.html
> [2] https://apacheignite-fs.readme.io/docs



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-6917) SQL: implement COPY command for efficient data loading

[Kirill Shirokov (JIRA)]

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

Kirill Shirokov updated IGNITE-6917:

Description: 
Inspired by Postgres [1]

Common use case - bulk data load through JDBC/ODBC interface. Currently it is 
only possible to execute single commands one by one. We already can batch them 
to improve performance, but there is still big room for improvement.

We should think of a completely new command - {{COPY}}. It will accept a file 
(or input stream in general case) on the client side, then transfer data to the 
cluster, and then execute update inside the cluster, e.g. through streamer.

First of all we need to create quick and dirty prototype to assess potential 
performance improvement. It speedup is confirmed, we should build base 
implementation which will accept only files. But at the same time we should 
understand how it will evolve in future: multiple file formats (probably 
including Hadoop formarts, e.g. Parquet), escape characters, input streams, 
etc..

[1] [https://www.postgresql.org/docs/9.6/static/sql-copy.html]
h1. Proposed syntax

Curent implementation:
{noformat}
COPY 
FROM "file.name"
INTO .
[(col-name, ...)]
FORMAT  -- Only CSV format is supported in the current 
release
[BATCH_SIZE ]
{noformat}
We may want to gradually add features to this command in future to have 
something like this:
{noformat}
COPY
FROM "file.name" [CHARSET ""]
INTO . [CREATE [IF NOT EXISTS]]
[(col-name [] [NULLABLE] [ESCAPES], ...) [MATCH HEADER]]
FORMAT (csv|tsv|...)

-- CSV format options:
[FIELDSEP='column-separators-regexp']
[LINESEP='row-separators-regexp']
[QUOTE='quote-chars']
[ESCAPE='escape-char']
[NULL='null-sequence']
[COMMENT='single-line-comment-start-char']
[TRIM_LINES]
[IMPORT_EMPTY_LINES]

[ROWS -]
--or--
[SKIP ROWS ] [MAX ROWS ]

[COLS -]
--or--
[SKIP COLS ] [MAX COLS ]

[(MATCH | SKIP) HEADER]
[(REPLACE|IGNORE|ABORT ON [])) DUPLICATE KEYS]
[BATCH SIZE ( ROWS | [K|M|G|T|P])]
[COMPRESS "codec-name" [codec options]]
[LOCK (TABLE|ROWS)]
[NOLOGGING]
[BACKEND (DIRECT | STREAMER)]
{noformat}

h1. Implementation decisions and notes

h2. Parsing

* We support CSV format described in RFC 4180.
* Custom row and column separators, quoting characters are currently hardcoded
* Escape sequences, line comment characters are currently not supported
* We may want to support fixed-length formats (via format descriptors) in future
* We may want to strip comments from lines (for example, starting with '#')
* We may want to allow user to either ignore empty lines or treat them as a 
special case of record having all default values
* We may allow user to enable whitespace trimming from beginning and end of a 
line

h2. File handling

* File character set to be supported in future
* Skipped/imported row number (or first/last line or skip header option), 
skipped/imported column number (or first/last column): to be supported in future
* Line start pattern (as in MySQL): no support planned
* We currently support only client-side import. No server-side file import.
* We may want to support client-side stdin import in future.
* We do not handle importing multiple files from single command
* We don't benefit from any kind of pre-sorting pre-partitioning data on client 
side.
* We don't include any any metadata, such as line number from client side.

h3. Transferring data

* We send file data via batches. In future we will support batch size 
(specified with rows per batch or data block size 
per batch).
* We may want to implement data compression in future.
* We connect to single node in JDBC driver (no multi-node connections).

h3. Cache/tables/column handling

* We don't create table in the bulk load command
* We may want to have and option for reading header row, which contains column 
names to match columns
* In future we may wish to support COLUMNS (col1, _, col2, _, col3) syntax, 
where '_' marker means a skipped column (MySQL uses '@dummy' for this)

h3. Data types

* Data types are converted as if they were supplied to INSERT SQL command.
* We may want type conversion (automatic, custom using sql function, custom via 
Java code, string auto-trimming) in future.
* We will support optional null sequence ("\N") later
* We may want to allow user to specify what to do if the same record exists 
(e.g., ignore record, replace it, report error with a max. error counter before 
failing the command)
* We don't currently support any generated/autoincremented row IDs or any 
custom generators.
* We don't support any filtering/conditional expressions
* We don't support any files/recordsets/tables with multiple conversion errors 
generated during import.

h3. Backend / Transactional / MVCC / other
* We may want an option to select how do we insert the data into cache: using 
cache.putAll(...), for 

[jira] [Updated] (IGNITE-6917) SQL: implement COPY command for efficient data loading

[Kirill Shirokov (JIRA)]

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

Kirill Shirokov updated IGNITE-6917:

Description: 
Inspired by Postgres [1]

Common use case - bulk data load through JDBC/ODBC interface. Currently it is 
only possible to execute single commands one by one. We already can batch them 
to improve performance, but there is still big room for improvement.

We should think of a completely new command - {{COPY}}. It will accept a file 
(or input stream in general case) on the client side, then transfer data to the 
cluster, and then execute update inside the cluster, e.g. through streamer.

First of all we need to create quick and dirty prototype to assess potential 
performance improvement. It speedup is confirmed, we should build base 
implementation which will accept only files. But at the same time we should 
understand how it will evolve in future: multiple file formats (probably 
including Hadoop formarts, e.g. Parquet), escape characters, input streams, 
etc..

[1] [https://www.postgresql.org/docs/9.6/static/sql-copy.html]
h1. Proposed syntax

Curent implementation:
{noformat}
COPY 
FROM "file.name"
INTO .
[(col-name, ...)]
FORMAT  -- Only CSV format is supported in the current 
release
[BATCH_SIZE ]
{noformat}
We may want to gradually add features to this command in future to have 
something like this:
{noformat}
COPY
FROM 'file.name' [CHARSET ""]
INTO . [CREATE [IF NOT EXISTS]]
[(col-name [] [NULLABLE] [ESCAPES], ...) [MATCH HEADER]]
FORMAT (csv|tsv|...)

-- CSV format options:
[FIELDSEP='column-separators-regexp']
[LINESEP='row-separators-regexp']
[QUOTE='quote-chars']
[ESCAPE='escape-char']
[NULL='null-sequence']
[COMMENT='single-line-comment-start-char']
[TRIM_LINES]
[IMPORT_EMPTY_LINES]

[ROWS -]
--or--
[SKIP ROWS ] [MAX ROWS ]

[COLS -]
--or--
[SKIP COLS ] [MAX COLS ]

[(MATCH | SKIP) HEADER]
[(REPLACE|IGNORE|ABORT ON [])) DUPLICATE KEYS]
[BATCH SIZE ( ROWS | [K|M|G|T|P])]
[COMPRESS "codec-name" [codec options]]
[LOCK (TABLE|ROWS)]
[NOLOGGING]
[BACKEND (DIRECT | STREAMER)]
{noformat}

h1. Implementation decisions and notes

h2. Parsing

* We support CSV format described in RFC 4180.
* Custom row and column separators, quoting characters are currently hardcoded
* Escape sequences, line comment characters are currently not supported
* We may want to support fixed-length formats (via format descriptors) in future
* We may want to strip comments from lines (for example, starting with '#')
* We may want to allow user to either ignore empty lines or treat them as a 
special case of record having all default values
* We may allow user to enable whitespace trimming from beginning and end of a 
line

h2. File handling

* File character set to be supported in future
* Skipped/imported row number (or first/last line or skip header option), 
skipped/imported column number (or first/last column): to be supported in future
* Line start pattern (as in MySQL): no support planned
* We currently support only client-side import. No server-side file import.
* We may want to support client-side stdin import in future.
* We do not handle importing multiple files from single command
* We don't benefit from any kind of pre-sorting pre-partitioning data on client 
side.
* We don't include any any metadata, such as line number from client side.

h3. Transferring data

* We send file data via batches. In future we will support batch size 
(specified with rows per batch or data block size 
per batch).
* We may want to implement data compression in future.
* We connect to single node in JDBC driver (no multi-node connections).

h3. Cache/tables/column handling

* We don't create table in the bulk load command
* We may want to have and option for reading header row, which contains column 
names to match columns
* In future we may wish to support COLUMNS (col1, _, col2, _, col3) syntax, 
where '_' marker means a skipped column (MySQL uses '@dummy' for this)

h3. Data types

* Data types are converted as if they were supplied to INSERT SQL command.
* We may want type conversion (automatic, custom using sql function, custom via 
Java code, string auto-trimming) in future.
* We will support optional null sequence ("\N") later
* We may want to allow user to specify what to do if the same record exists 
(e.g., ignore record, replace it, report error with a max. error counter before 
failing the command)
* We don't currently support any generated/autoincremented row IDs or any 
custom generators.
* We don't support any filtering/conditional expressions
* We don't support any files/recordsets/tables with multiple conversion errors 
generated during import.

h3. Backend / Transactional / MVCC / other
* We may want an option to select how do we insert the data into cache: using 
cache.putAll(...), for 

[jira] [Updated] (IGNITE-7535) SQL COPY command: implement encoding option

[Kirill Shirokov (JIRA)]

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

Kirill Shirokov updated IGNITE-7535:

Description: 
The syntax can be something like:

{noformat}
COPY 
FROM 'file' [CHARSET ""]
INTO ...
{noformat}

CHARSET is optional. By default the encoding is UTF-8.

  was:
The syntax can be something like:

{noformat}
COPY 
FROM 'file' [CHARSET ]
INTO ...
{noformat}

CHARSET is optional. By default the encoding is UTF-8.


> SQL COPY command: implement encoding option
> ---
>
> Key: IGNITE-7535
> URL: https://issues.apache.org/jira/browse/IGNITE-7535
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Kirill Shirokov
>Assignee: Kirill Shirokov
>Priority: Major
>
> The syntax can be something like:
> {noformat}
> COPY 
> FROM 'file' [CHARSET ""]
> INTO ...
> {noformat}
> CHARSET is optional. By default the encoding is UTF-8.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7535) SQL COPY command: implement encoding option

[Kirill Shirokov (JIRA)]

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

Kirill Shirokov reassigned IGNITE-7535:
---

Assignee: Kirill Shirokov

> SQL COPY command: implement encoding option
> ---
>
> Key: IGNITE-7535
> URL: https://issues.apache.org/jira/browse/IGNITE-7535
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Reporter: Kirill Shirokov
>Assignee: Kirill Shirokov
>Priority: Major
>
> The syntax can be something like:
> {noformat}
> COPY 
> FROM 'file' [CHARSET ]
> INTO ...
> {noformat}
> CHARSET is optional. By default the encoding is UTF-8.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7553) SQL COPY: provide support for the command in org.apache.ignite.internal.jdbc2 driver

[Kirill Shirokov (JIRA)]

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

Kirill Shirokov updated IGNITE-7553:

Priority: Minor  (was: Major)

> SQL COPY: provide support for the command in org.apache.ignite.internal.jdbc2 
> driver
> 
>
> Key: IGNITE-7553
> URL: https://issues.apache.org/jira/browse/IGNITE-7553
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 2.4
>Reporter: Kirill Shirokov
>Priority: Minor
>
> Currently COPY command is supported only in thin JDBC driver. It needs to be 
> supported in other JDBC driver implementations as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7509) Adjust "build" and "getting started" sections of documentation for ML module

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7509:


Github user asfgit closed the pull request at:

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


> Adjust "build" and "getting started" sections of documentation for ML module
> 
>
> Key: IGNITE-7509
> URL: https://issues.apache.org/jira/browse/IGNITE-7509
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, ml
>Reporter: Yury Babak
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-3999) Support case insensitive search in SQL

[Amir Akhmedov (JIRA)]

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

Amir Akhmedov commented on IGNITE-3999:
---

[~vkulichenko], [~sergi.vladykin], can you please review my PR.

> Support case insensitive search in SQL
> --
>
> Key: IGNITE-3999
> URL: https://issues.apache.org/jira/browse/IGNITE-3999
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Amir Akhmedov
>Priority: Critical
> Fix For: 2.4
>
>
> Currently case insensitive search is possible only with the help of 
> {{lower()}} function:
> {code}
> select name from MyValue where lower(name) = 'abc_5'
> {code}
> But this will always be a full scan, even if {{name}} field is indexed.
> We need to correctly support {{VARCHAR_IGNORECASE}} H2 type in Ignite and add 
> a respective property to {{@QuerySqlField}} annotation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7559) Adjust documentation for ML module at readme.io

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko edited comment on IGNITE-7559 at 1/29/18 4:29 PM:
-

Drafted update to readme.io doc for coming release 2.4: [Machine Learning - 
2.4|https://dash.readme.io/project/apacheignite/v2.3/docs/machine-learning-24].

[~dmagda] I would appreciate if you take a look at above. This is supposed to 
replace [current doc 
version|https://apacheignite.readme.io/docs/machine-learning] after 2.4 is 
released. Changes made to the doc are:
 # Build instructions adjusted to account for changes made per IGNITE-7203.
 # Word "beta" is removed from the sentence "Current beta version of Apache 
Ignite Machine Learning Grid..."


was (Author: oignatenko):
Drafted update to readme.io doc for coming release 2.4: [Machine Learning - 
2.4|https://dash.readme.io/project/apacheignite/v2.3/docs/machine-learning-24].

[~dmagda] I would appreciate if you take a look at above. This is supposed to 
replace [current doc 
version|https://apacheignite.readme.io/docs/machine-learning] after 2.4 is 
released. Changes made to the doc are:
 # Build instructions adjusted to account for changes made per -IGNITE-7203.-
 # Word "beta" is removed from the sentence "Current beta version of Apache 
Ignite Machine Learning Grid..."

> Adjust documentation for ML module at readme.io
> ---
>
> Key: IGNITE-7559
> URL: https://issues.apache.org/jira/browse/IGNITE-7559
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation, ml
>Affects Versions: 2.4
>Reporter: Oleg Ignatenko
>Assignee: Denis Magda
>Priority: Major
>
> Reflect changes made to github per IGNITE-7509 in respective docs at 
> readme.io.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7559) Adjust documentation for ML module at readme.io

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko edited comment on IGNITE-7559 at 1/29/18 4:28 PM:
-

Drafted update to readme.io doc for coming release 2.4: [Machine Learning - 
2.4|https://dash.readme.io/project/apacheignite/v2.3/docs/machine-learning-24].

[~dmagda] I would appreciate if you take a look at above. This is supposed to 
replace [current doc 
version|https://apacheignite.readme.io/docs/machine-learning] after 2.4 is 
released. Changes made to the doc are:
 # Build instructions adjusted to account for changes made per -IGNITE-7203.-
 # Word "beta" is removed from the sentence "Current beta version of Apache 
Ignite Machine Learning Grid..."


was (Author: oignatenko):
Drafted update to readme.io doc for coming release 2.4: [Machine Learning - 
2.4|https://dash.readme.io/project/apacheignite/v2.3/docs/machine-learning-24].

[~dmagda] I would appreciate if you take a look at above. This is supposed to 
replace [current doc 
version|https://apacheignite.readme.io/docs/machine-learning] after 2.4 is 
released. Changes made to the doc are:
 # Build instructions adjusted to account for changes made per IGNITE-7203
 # Word "beta" is removed from the sentence "Current beta version of Apache 
Ignite Machine Learning Grid..."

> Adjust documentation for ML module at readme.io
> ---
>
> Key: IGNITE-7559
> URL: https://issues.apache.org/jira/browse/IGNITE-7559
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation, ml
>Affects Versions: 2.4
>Reporter: Oleg Ignatenko
>Assignee: Denis Magda
>Priority: Major
>
> Reflect changes made to github per IGNITE-7509 in respective docs at 
> readme.io.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7559) Adjust documentation for ML module at readme.io

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko reassigned IGNITE-7559:
--

Assignee: Denis Magda  (was: Oleg Ignatenko)

> Adjust documentation for ML module at readme.io
> ---
>
> Key: IGNITE-7559
> URL: https://issues.apache.org/jira/browse/IGNITE-7559
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation, ml
>Affects Versions: 2.4
>Reporter: Oleg Ignatenko
>Assignee: Denis Magda
>Priority: Major
>
> Reflect changes made to github per IGNITE-7509 in respective docs at 
> readme.io.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7559) Adjust documentation for ML module at readme.io

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-7559:


Drafted update to readme.io doc for coming release 2.4: [Machine Learning - 
2.4|https://dash.readme.io/project/apacheignite/v2.3/docs/machine-learning-24].

[~dmagda] I would appreciate if you take a look. This is supposed to replace 
[current doc version|https://apacheignite.readme.io/docs/machine-learning] 
after 2.4 is released. Changes made to the doc are:

# Build instructions adjusted to account for changes made per IGNITE-7203
# Word "beta" is removed from the sentence "Current beta version of Apache 
Ignite Machine Learning Grid..."

> Adjust documentation for ML module at readme.io
> ---
>
> Key: IGNITE-7559
> URL: https://issues.apache.org/jira/browse/IGNITE-7559
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation, ml
>Affects Versions: 2.4
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
>
> Reflect changes made to github per IGNITE-7509 in respective docs at 
> readme.io.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7559) Adjust documentation for ML module at readme.io

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko edited comment on IGNITE-7559 at 1/29/18 4:28 PM:
-

Drafted update to readme.io doc for coming release 2.4: [Machine Learning - 
2.4|https://dash.readme.io/project/apacheignite/v2.3/docs/machine-learning-24].

[~dmagda] I would appreciate if you take a look at above. This is supposed to 
replace [current doc 
version|https://apacheignite.readme.io/docs/machine-learning] after 2.4 is 
released. Changes made to the doc are:
 # Build instructions adjusted to account for changes made per IGNITE-7203
 # Word "beta" is removed from the sentence "Current beta version of Apache 
Ignite Machine Learning Grid..."


was (Author: oignatenko):
Drafted update to readme.io doc for coming release 2.4: [Machine Learning - 
2.4|https://dash.readme.io/project/apacheignite/v2.3/docs/machine-learning-24].

[~dmagda] I would appreciate if you take a look. This is supposed to replace 
[current doc version|https://apacheignite.readme.io/docs/machine-learning] 
after 2.4 is released. Changes made to the doc are:

# Build instructions adjusted to account for changes made per IGNITE-7203
# Word "beta" is removed from the sentence "Current beta version of Apache 
Ignite Machine Learning Grid..."

> Adjust documentation for ML module at readme.io
> ---
>
> Key: IGNITE-7559
> URL: https://issues.apache.org/jira/browse/IGNITE-7559
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation, ml
>Affects Versions: 2.4
>Reporter: Oleg Ignatenko
>Assignee: Denis Magda
>Priority: Major
>
> Reflect changes made to github per IGNITE-7509 in respective docs at 
> readme.io.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-3999) Support case insensitive search in SQL

[Amir Akhmedov (JIRA)]

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

Amir Akhmedov reassigned IGNITE-3999:
-

Assignee: Amir Akhmedov

> Support case insensitive search in SQL
> --
>
> Key: IGNITE-3999
> URL: https://issues.apache.org/jira/browse/IGNITE-3999
> Project: Ignite
>  Issue Type: Improvement
>  Components: sql
>Affects Versions: 1.7
>Reporter: Valentin Kulichenko
>Assignee: Amir Akhmedov
>Priority: Critical
>
> Currently case insensitive search is possible only with the help of 
> {{lower()}} function:
> {code}
> select name from MyValue where lower(name) = 'abc_5'
> {code}
> But this will always be a full scan, even if {{name}} field is indexed.
> We need to correctly support {{VARCHAR_IGNORECASE}} H2 type in Ignite and add 
> a respective property to {{@QuerySqlField}} annotation.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7329) .NET: Thin client: SSL

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-7329:


All done, waiting for IGNITE-6810 merge.

> .NET: Thin client: SSL
> --
>
> Key: IGNITE-7329
> URL: https://issues.apache.org/jira/browse/IGNITE-7329
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms, thin client
>Affects Versions: 2.4
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.5
>
>
> Allow secure .NET thin client connection.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-898) Ignite does not starts from folder which name contains space

[ASF GitHub Bot (JIRA)]

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

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

GitHub user vveider opened a pull request:

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

IGNITE-898: Fixed error when path to Ignite folder contains whitespaces

 * Fixed error when path to ignite folder contains whitespaces
 * Fixed error when path to ignite folder contains whitespaces (for Windows 
batch files)
 * Fixed condition operator for paths with spaces
 * Returned full path to java.exe

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

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

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

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


commit 673868239558d7350c3bfbb8d9d95565772e371b
Author: alexzaitzev 
Date:   2018-01-29T15:36:41Z

IGNITE-898: Fixed error when path to Ignite folder contains whitespaces
 * Fixed error when path to ignite folder contains whitespaces
 * Fixed error when path to ignite folder contains whitespaces (for Windows 
batch files)
 * Fixed condition operator for paths with spaces
 * Returned full path to java.exe




> Ignite does not starts from folder which name contains space
> 
>
> Key: IGNITE-898
> URL: https://issues.apache.org/jira/browse/IGNITE-898
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Aleksei Zaitsev
>Priority: Trivial
> Fix For: 2.5
>
>
> Observed:
> In case folder name contains space character Ignite node cannot be started.
> Expected:
> Ingine node should be startable even when folder name contains space 
> character.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7559) Adjust documentation for ML module at readme.io

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko reassigned IGNITE-7559:
--

Assignee: Oleg Ignatenko

> Adjust documentation for ML module at readme.io
> ---
>
> Key: IGNITE-7559
> URL: https://issues.apache.org/jira/browse/IGNITE-7559
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation, ml
>Affects Versions: 2.4
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
>
> Reflect changes made to github per IGNITE-7509 in respective docs at 
> readme.io.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7509) Adjust "build" and "getting started" sections of documentation for ML module

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-7509:


Changes to be made at readme.io "extracted" to separate sub-task IGNITE-7559 as 
these are expected to be integrated differently that these done at github.

> Adjust "build" and "getting started" sections of documentation for ML module
> 
>
> Key: IGNITE-7509
> URL: https://issues.apache.org/jira/browse/IGNITE-7509
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, ml
>Reporter: Yury Babak
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7559) Adjust documentation for ML module at readme.io

[Oleg Ignatenko (JIRA)]

Oleg Ignatenko created IGNITE-7559:
--

 Summary: Adjust documentation for ML module at readme.io
 Key: IGNITE-7559
 URL: https://issues.apache.org/jira/browse/IGNITE-7559
 Project: Ignite
  Issue Type: Sub-task
  Components: documentation, ml
Affects Versions: 2.4
Reporter: Oleg Ignatenko


Reflect changes made to github per IGNITE-7509 in respective docs at readme.io.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7509) Adjust "build" and "getting started" sections of documentation for ML module

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7509:


GitHub user oignatenko opened a pull request:

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

IGNITE-7509 Adjust documentation for ML module

- updated docs
-- verified with diffs overview and rebuild per updated instructions

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

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

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

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


commit 88fc8e95fcfb6ead7379c1ecfaa861b286882695
Author: Oleg Ignatenko 
Date:   2018-01-29T15:21:51Z

IGNITE-7509 Adjust documentation for ML module
- updated docs
-- verified with diffs overview and rebuild per updated instructions




> Adjust "build" and "getting started" sections of documentation for ML module
> 
>
> Key: IGNITE-7509
> URL: https://issues.apache.org/jira/browse/IGNITE-7509
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, ml
>Reporter: Yury Babak
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7558) CLI AUTH: add user authentication to JDBC thin driver

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-7558:


 Summary: CLI AUTH: add user authentication to JDBC thin driver
 Key: IGNITE-7558
 URL: https://issues.apache.org/jira/browse/IGNITE-7558
 Project: Ignite
  Issue Type: Task
  Components: jdbc
Affects Versions: 2.3
Reporter: Taras Ledkov
Assignee: Taras Ledkov
 Fix For: 2.5


Add user authentication to JDBC thin driver.
- Authentication will be disabled by default to let users migrate from previous 
versions easily
- Clients will optionally pass username and password to the cluster during 
handshake phase.
- Password will be delivered in a *plain form*, because otherwise clients will 
have to implement complex hashing logic on their own. SSL will be used to 
protect passwords.

[Devlist 
discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Username-password-authentication-for-thin-clients-td26058.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7557) CLI AUTH: implement SQL commands to users management

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-7557:


 Summary: CLI AUTH: implement SQL commands to users management
 Key: IGNITE-7557
 URL: https://issues.apache.org/jira/browse/IGNITE-7557
 Project: Ignite
  Issue Type: Task
  Components: sql
Affects Versions: 2.3
Reporter: Taras Ledkov
Assignee: Taras Ledkov
 Fix For: 2.5


Create SQL commands for user management:
- CREATE USER
- ALTER USER
- DROP USER

[Devlist 
discussion|http://apache-ignite-developers.2346864.n4.nabble.com/Username-password-authentication-for-thin-clients-td26058.html]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7509) Adjust "build" and "getting started" sections of documentation for ML module

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-7509:


Need to make sure that docs take into account changes made per IGNITE-7203. 
This should be checked in ml, examples and yardstick modules.

> Adjust "build" and "getting started" sections of documentation for ML module
> 
>
> Key: IGNITE-7509
> URL: https://issues.apache.org/jira/browse/IGNITE-7509
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, ml
>Reporter: Yury Babak
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7509) Adjust "build" and "getting started" sections of documentation for ML module

[Yury Babak (JIRA)]

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

Yury Babak reassigned IGNITE-7509:
--

Assignee: Oleg Ignatenko  (was: Yury Babak)

> Adjust "build" and "getting started" sections of documentation for ML module
> 
>
> Key: IGNITE-7509
> URL: https://issues.apache.org/jira/browse/IGNITE-7509
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, ml
>Reporter: Yury Babak
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7348) Create MLP benchmarks

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko updated IGNITE-7348:
---
Issue Type: Task  (was: Sub-task)
Parent: (was: IGNITE-7129)

> Create MLP benchmarks
> -
>
> Key: IGNITE-7348
> URL: https://issues.apache.org/jira/browse/IGNITE-7348
> Project: Ignite
>  Issue Type: Task
>  Components: ml, yardstick
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Major
>
> We want to start tracking our performance to avoid performance degradation. 
> Also we need some performance comparison with other ml libs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7017) Reconsider WAL archive strategy

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7017:


Github user asfgit closed the pull request at:

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


> Reconsider WAL archive strategy
> ---
>
> Key: IGNITE-7017
> URL: https://issues.apache.org/jira/browse/IGNITE-7017
> Project: Ignite
>  Issue Type: Task
>Affects Versions: 2.3
>Reporter: Alexey Goncharuk
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.5
>
>
> Currently, we write WAL files in work directory and then copy them to the 
> archive after the segment is closed. 
> This was done to overcome XFS bug which leads to a double fsync cost 
> immediately after file creation. This approach leads to excessive disk usage 
> and can be optimized, especially for LOG_ONLY mode.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7511) FCM documentation

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko reassigned IGNITE-7511:
--

Assignee: Denis Magda  (was: Oleg Ignatenko)

> FCM documentation
> -
>
> Key: IGNITE-7511
> URL: https://issues.apache.org/jira/browse/IGNITE-7511
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, ml
>Reporter: Yury Babak
>Assignee: Denis Magda
>Priority: Major
> Fix For: 2.4
>
>
> We need to update documentation on readme.io and add section about FCM



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7511) FCM documentation

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-7511:


Drafted docs for version 2.4 at readme.io: [Fuzzy C-Means Clustering - 
2.4|https://dash.readme.io/project/apacheignite/v2.3/docs/fuzzy-c-means-clustering-24].

Also prepared draft update for related K-means docs page that needs to be 
published instead of [current 
version|https://apacheignite.readme.io/docs/k-means-clustering] after 2.4 is 
released: [K-Means Clustering - 
2.4|https://dash.readme.io/project/apacheignite/v2.3/docs/k-means-clustering-24].

[~dmagda] - I would appreciate if you take a look. If you have questions please 
feel free to ping me.

> FCM documentation
> -
>
> Key: IGNITE-7511
> URL: https://issues.apache.org/jira/browse/IGNITE-7511
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, ml
>Reporter: Yury Babak
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.4
>
>
> We need to update documentation on readme.io and add section about FCM



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7476) Server node will join with failure gathering metrics

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7476:


GitHub user alamar opened a pull request:

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

IGNITE-7476 IGNITE-7519 needed for reproducer of IGNITE-7540



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

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

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

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


commit 246239105c7ca5b835ed1767f4f6be667f374ccc
Author: Ilya Kasnacheev 
Date:   2018-01-29T13:18:21Z

IGNITE-7519 Avoid suppression of exceptions by IsolatedUpdater in data 
streamer.

commit 83ebbe5630cca6b40e96d61637ba4e5058b3c253
Author: Ilya Kasnacheev 
Date:   2018-01-29T13:20:01Z

IGNITE-7476 Avoid NPE during metrics gathering leading to discovery thread 
failure.




> Server node will join with failure gathering metrics
> 
>
> Key: IGNITE-7476
> URL: https://issues.apache.org/jira/browse/IGNITE-7476
> Project: Ignite
>  Issue Type: Bug
>Reporter: Ilya Kasnacheev
>Priority: Critical
>
> Sometimes server node will fail with the following trace:
> {code:java}
> SEVERE: TcpDiscoverSpi's message worker thread failed abnormally. Stopping 
> the node in order to prevent cluster wide instability.
> java.lang.NullPointerException
>     at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.cacheMetrics(GridDiscoveryManager.java:1149)
>     at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMetricsUpdateMessage(ServerImpl.java:5022)
>     at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2690)
>     at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2491)
>     at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6675)
>     at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2574)
>     at 
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62){code}
> Two problems here:
>  * Uncaught exception in cacheMetrics() leads to unconditional failure of 
> node, because it happens to be in discovery thread. Should probably wrap all 
> non-trivial code include try-catch.
>  * Lack of proper locking when destroying cache (see also IGNITE-6580, 
> IGNITE-7278 and IGNITE-7165)
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7540) Sequential checkpoints cause overwrite of already cleaned & freed offheap page

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev commented on IGNITE-7540:
-

Please consider applying [https://github.com/apache/ignite/pull/3448] before 
starting this fix

> Sequential checkpoints cause overwrite of already cleaned & freed offheap page
> --
>
> Key: IGNITE-7540
> URL: https://issues.apache.org/jira/browse/IGNITE-7540
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.4
>Reporter: Ilya Kasnacheev
>Assignee: Alexey Goncharuk
>Priority: Major
> Attachments: IgnitePdsDestroyCacheTest.java
>
>
> The sequence of events as follows:
> in GridCacheProcessor.onExchangeDone(), 
> {color:#660e7a}sharedCtx{color}.database().waitForCheckpoint({color:#008000}"caches
>  stop"{color}) is peformed and then cache is destroyed and all its pages are 
> freed and cleared asynchronously.
> However, it is entirely possible that after waitForCheckpoint(), next 
> checkpoint will start immediately. It is typical when a lot of data being 
> loaded into Ignite, leading to rapid checkpoint buffer depletion, as well as 
> with artificially increased checkpoint frequency, as used in reproducer.
> Then, checkpointer will save (overwrite) metadata page:
> {code:java}
>     at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1330)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:428)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.writeUnlock(PageMemoryImpl.java:422)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.saveStoreMetadata(GridCacheOffheapManager.java:375)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager.onCheckpointBegin(GridCacheOffheapManager.java:163)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:2309)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:2088)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:2013)
>     at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>     at java.lang.Thread.run(Thread.java:748){code}
> This will happen after cache is already destroyed and even after the page is 
> already zeroed by PageMemoryImpl$ClearSegmentRunnable.run().
> Then, some new cache is being created, and in 
> GridCacheOffheapManager$GridCacheDataStore.getOrAllocatePartitionMetas(), 
> pageMem.acquirePage() will return this page, expected zeroed, but actually 
> containing metadata for old cache's partition. Then, type == 
> PageIO.T_PART_META check will return true and the following exception is 
> issued, leading to cache state inconsistency and data loss:
> {code:java}
> Caused by: java.lang.IllegalStateException: Failed to get page IO instance 
> (page content is corrupted)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forVersion(IOVersions.java:83)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.IOVersions.forPage(IOVersions.java:95)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:175)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl.(FreeListImpl.java:370)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore$1.(GridCacheOffheapManager.java:932)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.init0(GridCacheOffheapManager.java:929)
>     at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.invoke(GridCacheOffheapManager.java:1295)
>     at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:344)
>     at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.storeValue(GridCacheMapEntry.java:3191)
>     at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.initialValue(GridCacheMapEntry.java:2571)
>     at 
> org.apache.ignite.internal.processors.datastreamer.DataStreamerImpl$IsolatedUpdater.receive(DataStreamerImpl.java:2096)
>     at 
> 

[jira] [Commented] (IGNITE-6565) Use long type for size and keySize in cache metrics

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev commented on IGNITE-6565:
-

[~sharpler] Looks OK by me.

> Use long type for size and keySize in cache metrics
> ---
>
> Key: IGNITE-6565
> URL: https://issues.apache.org/jira/browse/IGNITE-6565
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Ilya Kasnacheev
>Assignee: Alexander Menshikov
>Priority: Major
>  Labels: easyfix
>
> Currently it's int so for large caches there's no way to convey correct value.
> Should introduce getSizeLong() and getKeySizeLong()
> Also introduce the same in .Net and make sure that compatibility not broken 
> when passing OP_LOCAL_METRICS and OP_GLOBAL_METRICS.
> BTW do we need keySize at all? What's it for?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7329) .NET: Thin client: SSL

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-7329 at 1/29/18 12:55 PM:
--

GitHub user ptupitsyn opened a pull request:

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

IGNITE-7329 .NET: Thin client: SSL



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

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

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

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


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

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

IGNITE-7329 .NET: Thin client: SSL



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

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

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

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


commit 68d7154cb033ed69d48998f40ec3ed5da6a1392a
Author: Igor Sapego 
Date:   2017-12-04T16:14:04Z

IGNITE-6810: Implemented SecureSocketClient

commit 5cebaacb49a30dfba8ffc1f7f566a9fdd365a37a
Author: Igor Sapego 
Date:   2017-12-21T16:44:29Z

IGNITE-6810: Implemented SSL connection.

commit 955dd22930b35b3d54d98f4932229223537bcd53
Author: Igor Sapego 
Date:   2017-12-22T15:16:58Z

IGNITE-6810: Added saving SSL parameters to DSN

commit 8876df39efbf0061b611ee16479a3d032d7d2676
Author: Igor Sapego 
Date:   2017-12-25T16:24:24Z

IGNITE-6810: Changed UI layout

commit 089c81b9b971c1d8270987d5a6bcac94383212bc
Author: Igor Sapego 
Date:   2017-12-26T12:26:44Z

IGNITE-6810: Added values retrieval

commit 817584dc9de401d523af8c301ec5982d3ad8f249
Author: Igor Sapego 
Date:   2017-12-26T13:05:59Z

IGNITE-6810: Implmented disabling of SSL options on choosing "disable"
mode

commit a780fd1f36903549199cdcbef0d963b79f00b462
Author: Igor Sapego 
Date:   2017-12-26T13:40:42Z

IGNITE-6810: Merge-related fixes

commit 26a882eb5795b7b86e94dedc50c81791a7d04ddd
Author: Igor Sapego 
Date:   2017-12-27T12:26:25Z

IGNITE-6810: Fix for SecureSocketClient disconnect.

commit 64e3c89a8c626ab5c77da8aefe2106473cfcc078
Author: Igor Sapego 
Date:   2017-12-28T17:54:17Z

IGNITE-6810: Implemented OpenSSL dynamic loading.

commit 92e3febdd2d54dc0cfb16e6d8d9299dc571b6855
Author: Igor Sapego 
Date:   2018-01-10T15:54:49Z

IGNITE-6810: Minor fixes

commit 517ff46c5e3dff8ea0969c71963649aa0e709225
Author: Igor Sapego 
Date:   2018-01-11T15:37:26Z

IGNITE-6810: Fixes for Linux

commit 56b2d1046a85bed85e3e3955f974f507cdfa8e61
Author: Igor Sapego 
Date:   2018-01-11T15:41:06Z

IGNITE-6810: Fixed test

commit 9f719cd720e798a3f9e128a7eae7ae7adb855acb
Author: Igor Sapego 
Date:   2018-01-11T16:42:55Z

IGNITE-6810: Changes for Linux

commit cf4c716749b5b7b0f6d20bc48b0992a6233fbe3d
Author: Igor Sapego 
Date:   2018-01-12T09:08:33Z

IGNITE-6810: Merge-related fixes

commit a5aec9b62aedf24434d9ea12c9259ef04db74ed9
Author: Igor Sapego 
Date:   2018-01-16T15:46:38Z

IGNITE-6810: Improved Server-side

commit 09fe00532faa75e0148eafd67696efda73dca6ba
Author: Igor Sapego 
Date:   2018-01-18T12:43:28Z

IGNITE-6810: Implemented timeouts for SSL connections

commit db770a8537b28922f74b3984eef88285fe53508f
Author: Igor Sapego 
Date:   2018-01-18T15:11:02Z

IGNITE-6810: Fix for linux

commit 471d49cf33a8008dc100c33c9ac107f199f19f17
Author: Igor Sapego 
Date:   2018-01-18T15:49:03Z

IGNITE-6810: Fixes for linux

commit 77eb83cb2d249faea4c36050653ab9d1de24272b
Author: Igor Sapego 
Date:   2018-01-18T16:10:43Z

IGNITE-6810: Fixed linux errors

commit 97b1c80b078bbf984d4137f17f9ad6ddf6b3e1fc
Author: Igor Sapego 
Date:   2018-01-23T16:43:25Z

IGNITE-6810: Fix for x86

commit 79b5be4fe5c078c0d2fa28f9c9adbb29dadce491
Author: Igor Sapego 
Date:   2018-01-23T16:44:59Z

IGNITE-6810: Typo fixed

commit 90b74898ac84f158ce6dd76818ced6eb5aee4014
Author: Pavel Tupitsyn 
Date:   2018-01-24T07:54:25Z

Merge branch 'master' into ignite-7329

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/configuration/ClientConnectorConfiguration.java
#   

[jira] [Commented] (IGNITE-7329) .NET: Thin client: SSL

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7329:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-7329 .NET: Thin client: SSL



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

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

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

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


commit 68d7154cb033ed69d48998f40ec3ed5da6a1392a
Author: Igor Sapego 
Date:   2017-12-04T16:14:04Z

IGNITE-6810: Implemented SecureSocketClient

commit 5cebaacb49a30dfba8ffc1f7f566a9fdd365a37a
Author: Igor Sapego 
Date:   2017-12-21T16:44:29Z

IGNITE-6810: Implemented SSL connection.

commit 955dd22930b35b3d54d98f4932229223537bcd53
Author: Igor Sapego 
Date:   2017-12-22T15:16:58Z

IGNITE-6810: Added saving SSL parameters to DSN

commit 8876df39efbf0061b611ee16479a3d032d7d2676
Author: Igor Sapego 
Date:   2017-12-25T16:24:24Z

IGNITE-6810: Changed UI layout

commit 089c81b9b971c1d8270987d5a6bcac94383212bc
Author: Igor Sapego 
Date:   2017-12-26T12:26:44Z

IGNITE-6810: Added values retrieval

commit 817584dc9de401d523af8c301ec5982d3ad8f249
Author: Igor Sapego 
Date:   2017-12-26T13:05:59Z

IGNITE-6810: Implmented disabling of SSL options on choosing "disable"
mode

commit a780fd1f36903549199cdcbef0d963b79f00b462
Author: Igor Sapego 
Date:   2017-12-26T13:40:42Z

IGNITE-6810: Merge-related fixes

commit 26a882eb5795b7b86e94dedc50c81791a7d04ddd
Author: Igor Sapego 
Date:   2017-12-27T12:26:25Z

IGNITE-6810: Fix for SecureSocketClient disconnect.

commit 64e3c89a8c626ab5c77da8aefe2106473cfcc078
Author: Igor Sapego 
Date:   2017-12-28T17:54:17Z

IGNITE-6810: Implemented OpenSSL dynamic loading.

commit 92e3febdd2d54dc0cfb16e6d8d9299dc571b6855
Author: Igor Sapego 
Date:   2018-01-10T15:54:49Z

IGNITE-6810: Minor fixes

commit 517ff46c5e3dff8ea0969c71963649aa0e709225
Author: Igor Sapego 
Date:   2018-01-11T15:37:26Z

IGNITE-6810: Fixes for Linux

commit 56b2d1046a85bed85e3e3955f974f507cdfa8e61
Author: Igor Sapego 
Date:   2018-01-11T15:41:06Z

IGNITE-6810: Fixed test

commit 9f719cd720e798a3f9e128a7eae7ae7adb855acb
Author: Igor Sapego 
Date:   2018-01-11T16:42:55Z

IGNITE-6810: Changes for Linux

commit cf4c716749b5b7b0f6d20bc48b0992a6233fbe3d
Author: Igor Sapego 
Date:   2018-01-12T09:08:33Z

IGNITE-6810: Merge-related fixes

commit a5aec9b62aedf24434d9ea12c9259ef04db74ed9
Author: Igor Sapego 
Date:   2018-01-16T15:46:38Z

IGNITE-6810: Improved Server-side

commit 09fe00532faa75e0148eafd67696efda73dca6ba
Author: Igor Sapego 
Date:   2018-01-18T12:43:28Z

IGNITE-6810: Implemented timeouts for SSL connections

commit db770a8537b28922f74b3984eef88285fe53508f
Author: Igor Sapego 
Date:   2018-01-18T15:11:02Z

IGNITE-6810: Fix for linux

commit 471d49cf33a8008dc100c33c9ac107f199f19f17
Author: Igor Sapego 
Date:   2018-01-18T15:49:03Z

IGNITE-6810: Fixes for linux

commit 77eb83cb2d249faea4c36050653ab9d1de24272b
Author: Igor Sapego 
Date:   2018-01-18T16:10:43Z

IGNITE-6810: Fixed linux errors

commit 97b1c80b078bbf984d4137f17f9ad6ddf6b3e1fc
Author: Igor Sapego 
Date:   2018-01-23T16:43:25Z

IGNITE-6810: Fix for x86

commit 79b5be4fe5c078c0d2fa28f9c9adbb29dadce491
Author: Igor Sapego 
Date:   2018-01-23T16:44:59Z

IGNITE-6810: Typo fixed

commit 90b74898ac84f158ce6dd76818ced6eb5aee4014
Author: Pavel Tupitsyn 
Date:   2018-01-24T07:54:25Z

Merge branch 'master' into ignite-7329

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/configuration/ClientConnectorConfiguration.java
#   
modules/core/src/main/java/org/apache/ignite/internal/processors/odbc/ClientListenerProcessor.java

commit 18bf93161008cdf02b6e35d536a37baaf58753ec
Author: Pavel Tupitsyn 
Date:   2018-01-24T08:29:36Z

IGNITE-7329 .NET: Thin client: SSL

commit 78f22353add53bee60b341756dee41c5aed738a9
Author: Pavel Tupitsyn 
Date:   2018-01-24T12:16:34Z

wip raw tests

commit 80b399895a13686a231872fabb0f07a672219c85
Author: Pavel Tupitsyn 
Date:   2018-01-24T12:21:54Z

wip

commit 2b723d494f12c97989f1f24338d056e308a3b01f
Author: Pavel Tupitsyn 
Date:   2018-01-24T12:30:19Z

wip test

commit 

[jira] [Assigned] (IGNITE-7547) Failing to deploy service created by Proxy.newProxyInstance() on multiple nodes

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev reassigned IGNITE-7547:
---

Assignee: Ilya Kasnacheev

> Failing to deploy service created by Proxy.newProxyInstance() on multiple 
> nodes
> ---
>
> Key: IGNITE-7547
> URL: https://issues.apache.org/jira/browse/IGNITE-7547
> Project: Ignite
>  Issue Type: Bug
>  Components: compute
>Affects Versions: 2.4
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>Priority: Major
>
> When a new node comes with a service which is already defined in the cluster 
> (by name), the following check is made:
> deployed.configuration().equalsIgnoreNodeFilter(newCfg)
> It checks for several parameters, including Service's class.equals().
> If a normal class is used, it will work. However, sometimes Service 
> implementation is created with java.lang.reflect.Proxy.newProxyInstance().
> This method creates new classes on demand. They will have names like 
> $ProxyNN, where NN is ordinal which cannot be depended on. On different nodes 
> the ordering of proxies will be different. This means that equality for these 
> classes cannot be dependent on.
> And indeed it causes problems, as follows
> {code:java}
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to deploy 
> service (service already exists with different configuration) 
> [deployed=LazyServiceConfiguration [srvcClsName=com.sun.proxy.$Proxy0, 
> svcCls=, nodeFilterCls=], new=LazyServiceConfiguration 
> [srvcClsName=com.sun.proxy.$Proxy1, svcCls=$Proxy1, nodeFilterCls=]]
>     at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.writeServiceToCache(GridServiceProcessor.java:689)
>     at 
> org.apache.ignite.internal.processors.service.GridServiceProcessor.deployAll(GridServiceProcessor.java:590){code}
> My proposal follows: we should check that both classes respond to 
> Proxy.isProxyClass() before comparing classes. If they are, consider them 
> equal. I don't think we can check more.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-898) Ignite does not starts from folder which name contains space

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-898:
-

[~vveider], [~alexzaitzev]

I've tried to merge changes, but found conflicts. Could you please resolve them?

> Ignite does not starts from folder which name contains space
> 
>
> Key: IGNITE-898
> URL: https://issues.apache.org/jira/browse/IGNITE-898
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Vinogradov
>Assignee: Aleksei Zaitsev
>Priority: Trivial
> Fix For: 2.5
>
>
> Observed:
> In case folder name contains space character Ignite node cannot be started.
> Expected:
> Ingine node should be startable even when folder name contains space 
> character.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7090) Semaphore Stuck when no acquirers to assign permit

[Vladisav Jelisavcic (JIRA)]

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

Vladisav Jelisavcic commented on IGNITE-7090:
-

[~Timay] no problem, thanks for the update! Looks like a good and elegant 
solution, I think were almost there. I left you a few minor comments in the PR, 
I think we should clear the map manually and adjust the state accordingly, to 
avoid calling a transaction within transaction. Thanks!

> Semaphore Stuck when no acquirers to assign permit
> --
>
> Key: IGNITE-7090
> URL: https://issues.apache.org/jira/browse/IGNITE-7090
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, data structures
>Affects Versions: 2.1, 2.4
>Reporter: Tim Onyschak
>Priority: Major
> Fix For: 2.5
>
> Attachments: SemaphoreFailoverNoWaitingAcquirerTest.java
>
>
> If no acquirers are available to take permit of semaphore, the permit never 
> gets release and any further acquirerers will wait forever. 
> On node shut down DataStructuresProcessor.dsMap gets cleared out prior to 
> event listener being able to execute onNodeRemoved, hence owner is never 
> cleared out if it was unable to pass to a different acquirer. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-5097:
-

[~daradurvs], as environment variable backward-compatibility approach has been 
rejected, there is much more effort needed now to implement it on C++ side now 
and it is harder for me now to find timespan long enough for that. I do 
remember about this task though.

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>Priority: Major
>  Labels: iep-2, performance
> Fix For: 2.5
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7019) Cluster can not survive after IgniteOOM

[Dmitriy Sorokin (JIRA)]

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

Dmitriy Sorokin commented on IGNITE-7019:
-

[~avinogradov],
Review my patch, please.

> Cluster can not survive after IgniteOOM
> ---
>
> Key: IGNITE-7019
> URL: https://issues.apache.org/jira/browse/IGNITE-7019
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Mikhail Cherkasov
>Assignee: Dmitriy Sorokin
>Priority: Critical
>  Labels: iep-7
> Fix For: 2.5
>
>
> even if we have full sync mode and transactional cache we can't add new nodes 
> if there  was IgniteOOM, after adding new nodes and re-balancing, old nodes 
> can't evict partitions:
> {code}
> [2017-11-17 20:02:24,588][ERROR][sys-#65%DR1%][GridDhtPreloader] Partition 
> eviction failed, this can cause grid hang.
> class org.apache.ignite.internal.mem.IgniteOutOfMemoryException: Not enough 
> memory allocated [policyName=100MB_Region_Eviction, size=104.9 MB]
> Consider increasing memory policy size, enabling evictions, adding more nodes 
> to the cluster, reducing number of backups or reducing model size.
> at 
> org.apache.ignite.internal.pagemem.impl.PageMemoryNoStoreImpl.allocatePage(PageMemoryNoStoreImpl.java:294)
> at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.allocatePageNoReuse(DataStructure.java:117)
> at 
> org.apache.ignite.internal.processors.cache.persistence.DataStructure.allocatePage(DataStructure.java:105)
> at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.addStripe(PagesList.java:413)
> at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.getPageForPut(PagesList.java:528)
> at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.put(PagesList.java:617)
> at 
> org.apache.ignite.internal.processors.cache.persistence.freelist.FreeListImpl.addForRecycle(FreeListImpl.java:582)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Remove.reuseFreePages(BPlusTree.java:3847)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Remove.releaseAll(BPlusTree.java:4106)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree$Remove.access$6900(BPlusTree.java:3166)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doRemove(BPlusTree.java:1782)
> at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.remove(BPlusTree.java:1567)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1387)
> at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:374)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3233)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.clearInternal(GridDhtCacheEntry.java:588)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.clearAll(GridDhtLocalPartition.java:892)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:750)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:593)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:580)
> at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6639)
> at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> 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:748)
> {code}
> Discussion on the dev list: 
> http://apache-ignite-developers.2346864.n4.nabble.com/How-properly-handle-IgniteOOM-td25288.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-425) Introduce transformers for continuous queries

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov edited comment on IGNITE-425 at 1/29/18 10:55 AM:
--

Hello, [~avinogradov]!
Thank you!

I have resolved all issues in upsource.

I also make some benchmarks, as you advised:

Source of benchmark - https://github.com/nizhikov/ignite-425-benchmark
Results - [https://gist.github.com/nizhikov/ff6f32f853316f07a6701ea41379b1ea]

Please, take a look.

{noformat}
# Run complete. Total time: 00:04:14

BenchmarkMode  Cnt  Score 
Error  Units
Ignite425CQBenchmark.testMethod thrpt   10  18168,916 ± 
218,356  ops/s
Ignite425CQBenchmark.testMethod:listenerExecutedthrpt   10  18168,866 ± 
218,290  ops/s
Ignite425CQWTBenchmark.testMethod   thrpt   10  18245,549 ± 
677,447  ops/s
Ignite425CQWTBenchmark.testMethod:listenerExecuted  thrpt   10  18245,529 ± 
677,447  ops/s
{noformat}


was (Author: nizhikov):
Hello, [~avinogradov]!
Thank you!

I resolve all issues in upsource.

I also make some benchmarks, as you advised:

Source of benchmark - https://github.com/nizhikov/ignite-425-benchmark
Results - [https://gist.github.com/nizhikov/ff6f32f853316f07a6701ea41379b1ea]

Please, take a look.

{noformat}
# Run complete. Total time: 00:04:14

BenchmarkMode  Cnt  Score 
Error  Units
Ignite425CQBenchmark.testMethod thrpt   10  18168,916 ± 
218,356  ops/s
Ignite425CQBenchmark.testMethod:listenerExecutedthrpt   10  18168,866 ± 
218,290  ops/s
Ignite425CQWTBenchmark.testMethod   thrpt   10  18245,549 ± 
677,447  ops/s
Ignite425CQWTBenchmark.testMethod:listenerExecuted  thrpt   10  18245,529 ± 
677,447  ops/s
{noformat}

> Introduce transformers for continuous queries
> -
>
> Key: IGNITE-425
> URL: https://issues.apache.org/jira/browse/IGNITE-425
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Affects Versions: 2.2
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.5
>
>
> Currently if updated entry passes the filter, it is sent to node initiated 
> the query entirely. It would be good to provide user with the ability to 
> transform entry and, for example, select only fields that are important. This 
> may bring huge economy to traffic and lower GC pressure as well.
> Possible signatures will be:
> {noformat}
> public final class ContinuousQuery {..} // T is a type transformer 
> transforms to
> public ContinuousQuery setLocalListener(Listener locLsnr) {..} // 
> Probably, we will have to introduce new listener type, since user may want to 
> wipe out key as well.
> /* new method to add */
> public ContinuousQuery setRemoteTransformerFactory(Factory ContinuousQueryTransformer> factory) { ..}
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-425) Introduce transformers for continuous queries

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-425:


Hello, [~avinogradov]!
Thank you!

I resolve all issues in upsource.

I also make some benchmarks, as you advised:

Source of benchmark - https://github.com/nizhikov/ignite-425-benchmark
Results - [https://gist.github.com/nizhikov/ff6f32f853316f07a6701ea41379b1ea]

Please, take a look.

{noformat}
# Run complete. Total time: 00:04:14

BenchmarkMode  Cnt  Score 
Error  Units
Ignite425CQBenchmark.testMethod thrpt   10  18168,916 ± 
218,356  ops/s
Ignite425CQBenchmark.testMethod:listenerExecutedthrpt   10  18168,866 ± 
218,290  ops/s
Ignite425CQWTBenchmark.testMethod   thrpt   10  18245,549 ± 
677,447  ops/s
Ignite425CQWTBenchmark.testMethod:listenerExecuted  thrpt   10  18245,529 ± 
677,447  ops/s
{noformat}

> Introduce transformers for continuous queries
> -
>
> Key: IGNITE-425
> URL: https://issues.apache.org/jira/browse/IGNITE-425
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Affects Versions: 2.2
>Reporter: Yakov Zhdanov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.5
>
>
> Currently if updated entry passes the filter, it is sent to node initiated 
> the query entirely. It would be good to provide user with the ability to 
> transform entry and, for example, select only fields that are important. This 
> may bring huge economy to traffic and lower GC pressure as well.
> Possible signatures will be:
> {noformat}
> public final class ContinuousQuery {..} // T is a type transformer 
> transforms to
> public ContinuousQuery setLocalListener(Listener locLsnr) {..} // 
> Probably, we will have to introduce new listener type, since user may want to 
> wipe out key as well.
> /* new method to add */
> public ContinuousQuery setRemoteTransformerFactory(Factory ContinuousQueryTransformer> factory) { ..}
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (IGNITE-7422) Thin client Java API - startClient

[Alexey Kukushkin (JIRA)]

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

Alexey Kukushkin reassigned IGNITE-7422:


Assignee: Alexey Kukushkin

> Thin client Java API - startClient
> --
>
> Key: IGNITE-7422
> URL: https://issues.apache.org/jira/browse/IGNITE-7422
> Project: Ignite
>  Issue Type: Sub-task
>  Components: thin client
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
>Priority: Major
>  Labels: data, java, thin
>
> Implement below thin client Java API including unit and system tests and 
> samples. BinaryObject, failover and encryption is not part of this task.
> Ignition
>     startClient(:ClientConfiguration): Ignite
> ClientConfiguration(port, host, binaryConfiguration, sslConfiguration,
> etc...)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7556) Docs should feature specifying SQL key more prominently

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev commented on IGNITE-7556:
-

I have submitted documentation change to 
https://apacheignite-sql.readme.io/docs/insert

> Docs should feature specifying SQL key more prominently
> ---
>
> Key: IGNITE-7556
> URL: https://issues.apache.org/jira/browse/IGNITE-7556
> Project: Ignite
>  Issue Type: Bug
>  Components: documentation
>Reporter: Ilya Kasnacheev
>Priority: Minor
>
> Descriptions on [https://apacheignite-sql.readme.io/docs/schema-and-indexes] 
> are not DML-friendly
> After reading this page and [https://apacheignite-sql.readme.io/docs/insert], 
> one would likely still unable to write working INSERT because there won't be 
> primary key in it.
> Their only chance is to spot _key reference in infoblock, or infer usability 
> of setKeyFields() with single key type. Both are unlikely, leading to 
> questions such as 
> [https://stackoverflow.com/questions/48460214/how-do-i-read-data-from-ignite-kv-storage-using-jdbc]
>  see {{Key is missing from query}}
> Such problems are hard to debug. They can be avoided if all examples of 
> QueryEntities in docs will contain setKeyFields, and INSERT docs page will 
> refer to _key field.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7556) Docs should feature specifying SQL key more prominently

[Ilya Kasnacheev (JIRA)]

Ilya Kasnacheev created IGNITE-7556:
---

 Summary: Docs should feature specifying SQL key more prominently
 Key: IGNITE-7556
 URL: https://issues.apache.org/jira/browse/IGNITE-7556
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Reporter: Ilya Kasnacheev


Descriptions on [https://apacheignite-sql.readme.io/docs/schema-and-indexes] 
are not DML-friendly
After reading this page and [https://apacheignite-sql.readme.io/docs/insert], 
one would likely still unable to write working INSERT because there won't be 
primary key in it.

Their only chance is to spot _key reference in infoblock, or infer usability of 
setKeyFields() with single key type. Both are unlikely, leading to questions 
such as 
[https://stackoverflow.com/questions/48460214/how-do-i-read-data-from-ignite-kv-storage-using-jdbc]
 see {{Key is missing from query}}

Such problems are hard to debug. They can be avoided if all examples of 
QueryEntities in docs will contain setKeyFields, and INSERT docs page will 
refer to _key field.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (IGNITE-7543) Rename KEYS.txt

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov resolved IGNITE-7543.
--
Resolution: Fixed

> Rename KEYS.txt
> ---
>
> Key: IGNITE-7543
> URL: https://issues.apache.org/jira/browse/IGNITE-7543
> Project: Ignite
>  Issue Type: Task
>Reporter: Peter Ivanov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.4
>
>
> Since IGNITE-7107, http://apache.org/dist/ignite/KEYS.txt will be used also 
> for GPG repository check, it is desirable to rename {{KEYS.txt}} to {{KEYS}} 
> for more convenient usage (like Cassandra has: 
> http://apache.org/dist/cassandra/)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7534) ClusterGroupExample duplicate

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7534:


GitHub user vveider opened a pull request:

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

IGNITE-7534 ClusterGroupExample duplicate

 * removed 
examples/src/main/java/org/apache/ignite/examples/computegrid/cluster

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

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

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

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


commit 857b1f317f852cc1a4c5e60ed07973dc10ec21a4
Author: Ivanov Petr 
Date:   2018-01-29T09:45:32Z

IGNITE-7534 ClusterGroupExample duplicate
 * removed 
examples/src/main/java/org/apache/ignite/examples/computegrid/cluster




> ClusterGroupExample duplicate
> -
>
> Key: IGNITE-7534
> URL: https://issues.apache.org/jira/browse/IGNITE-7534
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.3
>Reporter: Sergey Kozlov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.4
>
>
> The examples \{{org.apache.ignite.examples.cluster.ClusterGroupExample}} and 
> \{{org.apache.ignite.examples.computegrid.cluster.ClusterGroupExample}} are 
> same



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7543) Rename KEYS.txt

[Anton Vinogradov (JIRA)]

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

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

> Rename KEYS.txt
> ---
>
> Key: IGNITE-7543
> URL: https://issues.apache.org/jira/browse/IGNITE-7543
> Project: Ignite
>  Issue Type: Task
>Reporter: Peter Ivanov
>Assignee: Anton Vinogradov
>Priority: Major
> Fix For: 2.4
>
>
> Since IGNITE-7107, http://apache.org/dist/ignite/KEYS.txt will be used also 
> for GPG repository check, it is desirable to rename {{KEYS.txt}} to {{KEYS}} 
> for more convenient usage (like Cassandra has: 
> http://apache.org/dist/cassandra/)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-6113) Partition eviction prevents exchange from completion

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6113:


GitHub user Jokser opened a pull request:

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

IGNITE-6113 Async eviction



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

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

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

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


commit 2890c096f072b1f3a6a81e653bf1b4742f34b34c
Author: ilantukh 
Date:   2018-01-24T14:09:32Z

gg-12001 : Rebalance mechanics redesign.

commit 7063a41c18749a4a206e84eda8c1a775dee055f4
Author: Pavel Kovalenko 
Date:   2018-01-29T09:17:25Z

WIP




> Partition eviction prevents exchange from completion
> 
>
> Key: IGNITE-6113
> URL: https://issues.apache.org/jira/browse/IGNITE-6113
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Assignee: Pavel Kovalenko
>Priority: Major
>
> I has waited for 3 hours for completion without any success.
> exchange-worker is blocked.
> {noformat}
> "exchange-worker-#92%DPL_GRID%grid554.ca.sbrf.ru%" #173 prio=5 os_prio=0 
> tid=0x7f0835c2e000 nid=0xb907 runnable [0x7e74ab1d]
>java.lang.Thread.State: TIMED_WAITING (parking)
> at sun.misc.Unsafe.park(Native Method)
> - parking to wait for  <0x7efee630a7c0> (a 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition$1)
> at 
> java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedNanos(AbstractQueuedSynchronizer.java:1037)
> at 
> java.util.concurrent.locks.AbstractQueuedSynchronizer.tryAcquireSharedNanos(AbstractQueuedSynchronizer.java:1328)
> 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 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader.assign(GridDhtPreloader.java:340)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1801)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:748)
>Locked ownable synchronizers:
> - None
> {noformat}
> {noformat}
> "sys-#124%DPL_GRID%grid554.ca.sbrf.ru%" #278 prio=5 os_prio=0 
> tid=0x7e731c02d000 nid=0xbf4d runnable [0x7e734e7f7000]
>java.lang.Thread.State: RUNNABLE
> at sun.nio.ch.FileDispatcherImpl.write0(Native Method)
> at sun.nio.ch.FileDispatcherImpl.write(FileDispatcherImpl.java:60)
> at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93)
> at sun.nio.ch.IOUtil.write(IOUtil.java:51)
> at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:211)
> - locked <0x7f056161bf88> (a java.lang.Object)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.writeBuffer(FileWriteAheadLogManager.java:1829)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.flush(FileWriteAheadLogManager.java:1572)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.addRecord(FileWriteAheadLogManager.java:1421)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager$FileWriteHandle.access$800(FileWriteAheadLogManager.java:1331)
> at 
> org.gridgain.grid.cache.db.wal.FileWriteAheadLogManager.log(FileWriteAheadLogManager.java:339)
> at 
> org.gridgain.grid.internal.processors.cache.database.pagemem.PageMemoryImpl.beforeReleaseWrite(PageMemoryImpl.java:1287)
> at 
> org.gridgain.grid.internal.processors.cache.database.pagemem.PageMemoryImpl.writeUnlockPage(PageMemoryImpl.java:1142)
> at 
> org.gridgain.grid.internal.processors.cache.database.pagemem.PageImpl.releaseWrite(PageImpl.java:167)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writeUnlock(PageHandler.java:193)
> at 
> org.apache.ignite.internal.processors.cache.database.tree.util.PageHandler.writePage(PageHandler.java:242)
> at 
> 

[jira] [Comment Edited] (IGNITE-7469) Update Apache Ignite documentation about RPM-repository usage

[Peter Ivanov (JIRA)]

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

Peter Ivanov edited comment on IGNITE-7469 at 1/29/18 9:11 AM:
---

??I guess the node can be started without . What will be used as 
the config on this occasion???
 No, it can be not. The only way to have multiple instance of Apache Ignite 
started on single workstation – is to provide separate configuration files.

?? is a relative path. How can I pass an absolute pass to the 
configuration???
 {{systemctl}} does not support paths in {{@<...>}} notation (they are 
striped), so it was decided (and agreed by community and reviewer) that all 
configurations have to reside at default configuration directory 
({{/etc/apache-ignite-fabric}}).

Fixed some minor errors. Will double check the instruction when first RC will 
be available.


was (Author: vveider):
??I guess the node can be started without . What will be used as 
the config on this occasion???
 No, it can be not. The only way to have multiple instance of ignite started on 
single workstation – is to provide separate configuration files.

?? is a relative path. How can I pass an absolute pass to the 
configuration???
 {{systemctl}} does not support paths in @<...> notation (they are striped) so 
it was decided (and agreed by community and reviewer) that all configurations 
have to reside at default configuration directory 
({{/etc/apache-ignite-fabric}})

Fixed some minor errors. Will double check the instruction when first RC will 
be available.

> Update Apache Ignite documentation about RPM-repository usage
> -
>
> Key: IGNITE-7469
> URL: https://issues.apache.org/jira/browse/IGNITE-7469
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.4
>
>
> After IGNITE-7107 release in 2.4 version Apache Ignite will be available 
> through custom RPM repository packed in RPM package. Corresponding 
> documentation (how to add RPM-repository and install from it) should be 
> created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7469) Update Apache Ignite documentation about RPM-repository usage

[Peter Ivanov (JIRA)]

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

Peter Ivanov commented on IGNITE-7469:
--

>I guess the node can be started without . What will be used as 
>the config on this occasion?
No, it can be not. The only way to have multiple instance of ignite started on 
single workstation -- is to provide separate configuration files.
> is a relative path. How can I pass an absolute pass to the 
>configuration?
{{systemctl}} does not support paths in @<...> notation (they are striped) so 
it was decided (and agreed by community and reviewer) that all configurations 
have to reside at default configuration directory 
({{/etc/apache-ignite-fabric}})

Fixed some minor errors. Will double check the instruction when first RC will 
be available.

> Update Apache Ignite documentation about RPM-repository usage
> -
>
> Key: IGNITE-7469
> URL: https://issues.apache.org/jira/browse/IGNITE-7469
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.4
>
>
> After IGNITE-7107 release in 2.4 version Apache Ignite will be available 
> through custom RPM repository packed in RPM package. Corresponding 
> documentation (how to add RPM-repository and install from it) should be 
> created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7469) Update Apache Ignite documentation about RPM-repository usage

[Peter Ivanov (JIRA)]

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

Peter Ivanov edited comment on IGNITE-7469 at 1/29/18 9:09 AM:
---

??I guess the node can be started without . What will be used as 
the config on this occasion???
 No, it can be not. The only way to have multiple instance of ignite started on 
single workstation – is to provide separate configuration files.

?? is a relative path. How can I pass an absolute pass to the 
configuration???
 {{systemctl}} does not support paths in @<...> notation (they are striped) so 
it was decided (and agreed by community and reviewer) that all configurations 
have to reside at default configuration directory 
({{/etc/apache-ignite-fabric}})

Fixed some minor errors. Will double check the instruction when first RC will 
be available.


was (Author: vveider):
>I guess the node can be started without . What will be used as 
>the config on this occasion?
No, it can be not. The only way to have multiple instance of ignite started on 
single workstation -- is to provide separate configuration files.
> is a relative path. How can I pass an absolute pass to the 
>configuration?
{{systemctl}} does not support paths in @<...> notation (they are striped) so 
it was decided (and agreed by community and reviewer) that all configurations 
have to reside at default configuration directory 
({{/etc/apache-ignite-fabric}})

Fixed some minor errors. Will double check the instruction when first RC will 
be available.

> Update Apache Ignite documentation about RPM-repository usage
> -
>
> Key: IGNITE-7469
> URL: https://issues.apache.org/jira/browse/IGNITE-7469
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.4
>
>
> After IGNITE-7107 release in 2.4 version Apache Ignite will be available 
> through custom RPM repository packed in RPM package. Corresponding 
> documentation (how to add RPM-repository and install from it) should be 
> created.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7410) IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko updated IGNITE-7410:
---
Affects Version/s: (was: 2.5)
   2.4

> IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs 
> --
>
> Key: IGNITE-7410
> URL: https://issues.apache.org/jira/browse/IGNITE-7410
> Project: Ignite
>  Issue Type: Bug
>  Components: ml, yardstick
>Affects Versions: 2.4
>Reporter: Ilya Suntsov
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.5
>
> Attachments: logs_sparse-distributed-matrix-mul.zip
>
>
> I tried to run the benchmarks bellow on 2 servers and 3 clients:
>  * IgniteSparseDistributedMatrixMulBenchmark
>  * IgniteSparseDistributedMatrixMul2Benchmark
> They hang.
> I've attached logs and configs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7323) Update Storm dependencies to 1.1.1

[Roman Shtykh (JIRA)]

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

Roman Shtykh commented on IGNITE-7323:
--

Passed on https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8

> Update Storm dependencies to 1.1.1
> --
>
> Key: IGNITE-7323
> URL: https://issues.apache.org/jira/browse/IGNITE-7323
> Project: Ignite
>  Issue Type: Bug
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>Priority: Major
> Fix For: 2.5
>
>
> http://storm.apache.org/2017/08/01/storm111-released.html



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7410) IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko updated IGNITE-7410:
---
Fix Version/s: 2.5

> IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs 
> --
>
> Key: IGNITE-7410
> URL: https://issues.apache.org/jira/browse/IGNITE-7410
> Project: Ignite
>  Issue Type: Bug
>  Components: ml, yardstick
>Affects Versions: 2.4
>Reporter: Ilya Suntsov
>Assignee: Oleg Ignatenko
>Priority: Major
> Fix For: 2.5
>
> Attachments: logs_sparse-distributed-matrix-mul.zip
>
>
> I tried to run the benchmarks bellow on 2 servers and 3 clients:
>  * IgniteSparseDistributedMatrixMulBenchmark
>  * IgniteSparseDistributedMatrixMul2Benchmark
> They hang.
> I've attached logs and configs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (IGNITE-7410) IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko updated IGNITE-7410:
---
Affects Version/s: (was: 2.4)
   2.5

> IgniteSparseDistributedMatrixMulBenchmark(Mul2) hangs 
> --
>
> Key: IGNITE-7410
> URL: https://issues.apache.org/jira/browse/IGNITE-7410
> Project: Ignite
>  Issue Type: Bug
>  Components: ml, yardstick
>Affects Versions: 2.5
>Reporter: Ilya Suntsov
>Assignee: Oleg Ignatenko
>Priority: Major
> Attachments: logs_sparse-distributed-matrix-mul.zip
>
>
> I tried to run the benchmarks bellow on 2 servers and 3 clients:
>  * IgniteSparseDistributedMatrixMulBenchmark
>  * IgniteSparseDistributedMatrixMul2Benchmark
> They hang.
> I've attached logs and configs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-6386) Introduction of distributed neural networks.

[Yury Babak (JIRA)]

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

Yury Babak edited comment on IGNITE-6386 at 1/29/18 8:44 AM:
-

Done in IGNITE-7332 an IGNITE-7129. Currently we have implementation of 
distributed and local multilayer perceptrons. Currently integration with any 
other libs was postponed.


was (Author: chief):
Done in IGNITE-7332 an IGNITE-7129. Currently we have implementation of 
distributed and local multilayer perceptrons.

> Introduction of distributed neural networks.
> 
>
> Key: IGNITE-6386
> URL: https://issues.apache.org/jira/browse/IGNITE-6386
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
>Priority: Major
>  Labels: important
> Fix For: 2.4
>
>
> We want to have deep learning algorithms and for this we need to implement 
> neural network over Apache Ignite. Currently we think about using 
> [dl4j|https://deeplearning4j.org] as backend but in this case we cannot  
> train one model over multiple nodes efficiently. Also we will think about 
> integration/connector with dl4j.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (IGNITE-6386) Introduction of distributed neural networks.

[Yury Babak (JIRA)]

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

Yury Babak resolved IGNITE-6386.

Resolution: Fixed

Done in IGNITE-7332 an IGNITE-7129. Currently we have implementation of 
distributed and local multilayer perceptrons.

> Introduction of distributed neural networks.
> 
>
> Key: IGNITE-6386
> URL: https://issues.apache.org/jira/browse/IGNITE-6386
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Yury Babak
>Priority: Major
>  Labels: important
> Fix For: 2.4
>
>
> We want to have deep learning algorithms and for this we need to implement 
> neural network over Apache Ignite. Currently we think about using 
> [dl4j|https://deeplearning4j.org] as backend but in this case we cannot  
> train one model over multiple nodes efficiently. Also we will think about 
> integration/connector with dl4j.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Resolved] (IGNITE-7129) Implement Multilayer Perceptron

[Yury Babak (JIRA)]

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

Yury Babak resolved IGNITE-7129.

   Resolution: Implemented
Fix Version/s: 2.4

> Implement Multilayer Perceptron
> ---
>
> Key: IGNITE-7129
> URL: https://issues.apache.org/jira/browse/IGNITE-7129
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Artem Malykh
>Assignee: Artem Malykh
>Priority: Major
>  Labels: important
> Fix For: 2.4
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7555) Create documentation for using Ignite Persistence on Kubernetes

[Evgenii Zhuravlev (JIRA)]

Evgenii Zhuravlev created IGNITE-7555:
-

 Summary: Create documentation for using Ignite Persistence on 
Kubernetes
 Key: IGNITE-7555
 URL: https://issues.apache.org/jira/browse/IGNITE-7555
 Project: Ignite
  Issue Type: Task
  Components: documentation
Reporter: Evgenii Zhuravlev
 Fix For: 2.5






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur commented on IGNITE-5097:


Hi, [~vozerov], [~isapego], could you please review Java part changes and port 
the changes to the C++ platform?

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>Priority: Major
>  Labels: iep-2, performance
> Fix For: 2.5
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (IGNITE-7295) Log of thin client is not disabled in special case

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-7295:
---
Comment: was deleted

(was: Tested in 2.3-master)

> Log of thin client is not disabled in special case
> --
>
> Key: IGNITE-7295
> URL: https://issues.apache.org/jira/browse/IGNITE-7295
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
>Affects Versions: 2.3
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Should be possibility to enable/disable thin client log.
> We try to disable thin client log in GridClientImpl.java. 
> If log4j is located in a classpath log will be showed (f.e. when thin client 
> is run from Windows console) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7295) Log of thin client is not disabled in special case

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7295:


Tested in 2.4.3

> Log of thin client is not disabled in special case
> --
>
> Key: IGNITE-7295
> URL: https://issues.apache.org/jira/browse/IGNITE-7295
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
>Affects Versions: 2.3
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Should be possibility to enable/disable thin client log.
> We try to disable thin client log in GridClientImpl.java. 
> If log4j is located in a classpath log will be showed (f.e. when thin client 
> is run from Windows console) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (IGNITE-7295) Log of thin client is not disabled in special case

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov closed IGNITE-7295.
--

> Log of thin client is not disabled in special case
> --
>
> Key: IGNITE-7295
> URL: https://issues.apache.org/jira/browse/IGNITE-7295
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
>Affects Versions: 2.3
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Should be possibility to enable/disable thin client log.
> We try to disable thin client log in GridClientImpl.java. 
> If log4j is located in a classpath log will be showed (f.e. when thin client 
> is run from Windows console) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Issue Comment Deleted] (IGNITE-7295) Log of thin client is not disabled in special case

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-7295:
---
Comment: was deleted

(was: Tested in 2.4.3)

> Log of thin client is not disabled in special case
> --
>
> Key: IGNITE-7295
> URL: https://issues.apache.org/jira/browse/IGNITE-7295
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
>Affects Versions: 2.3
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Should be possibility to enable/disable thin client log.
> We try to disable thin client log in GridClientImpl.java. 
> If log4j is located in a classpath log will be showed (f.e. when thin client 
> is run from Windows console) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7295) Log of thin client is not disabled in special case

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7295:


Tested

> Log of thin client is not disabled in special case
> --
>
> Key: IGNITE-7295
> URL: https://issues.apache.org/jira/browse/IGNITE-7295
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
>Affects Versions: 2.3
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Should be possibility to enable/disable thin client log.
> We try to disable thin client log in GridClientImpl.java. 
> If log4j is located in a classpath log will be showed (f.e. when thin client 
> is run from Windows console) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (IGNITE-7295) Log of thin client is not disabled in special case

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov edited comment on IGNITE-7295 at 1/29/18 8:16 AM:
-

Tested. Client output printed out only if IGNITE_GRID_CLIENT_LOG_ENABLED = true
To test run snapshot utility and try to execute any command (f.e. list)


was (Author: pkonstantinov):
Tested. Client output printed out only if IGNITE_GRID_CLIENT_LOG_ENABLED = true

> Log of thin client is not disabled in special case
> --
>
> Key: IGNITE-7295
> URL: https://issues.apache.org/jira/browse/IGNITE-7295
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
>Affects Versions: 2.3
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Should be possibility to enable/disable thin client log.
> We try to disable thin client log in GridClientImpl.java. 
> If log4j is located in a classpath log will be showed (f.e. when thin client 
> is run from Windows console) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (IGNITE-7295) Log of thin client is not disabled in special case

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-7295:


Tested in 2.3-master

> Log of thin client is not disabled in special case
> --
>
> Key: IGNITE-7295
> URL: https://issues.apache.org/jira/browse/IGNITE-7295
> Project: Ignite
>  Issue Type: Bug
>  Components: thin client
>Affects Versions: 2.3
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
>Priority: Minor
> Fix For: 2.4
>
>
> Should be possibility to enable/disable thin client log.
> We try to disable thin client log in GridClientImpl.java. 
> If log4j is located in a classpath log will be showed (f.e. when thin client 
> is run from Windows console) 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)