[jira] [Commented] (IGNITE-9746) [ML] Add Complement Naive Bayes

[Ravil Galeyev (JIRA)]

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

Ravil Galeyev commented on IGNITE-9746:
---

Dear [~aplatonov],

I don't mind about merging. It makes sense to move my Bayes tasks under your 
tickets as subtasks.

But it looks like I don't have rights to move subtasks.

So, I'd be nice, if you move them.

> [ML] Add Complement Naive Bayes
> ---
>
> Key: IGNITE-9746
> URL: https://issues.apache.org/jira/browse/IGNITE-9746
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Ravil Galeyev
>Priority: Major
>
> Naive Bayes classifiers are a family of simple probabilistic classifiers 
> based on applying Bayes' theorem with strong (naive) independence assumptions 
> between the features.
> So we want to add this algorithm to Apache Ignite ML module.
> [Complement Naive 
> Bayes|http://scikit-learn.org/stable/modules/naive_bayes.html#complement-naive-bayes]
>  is an adaptation of the standard multinomial naive Bayes (MNB) algorithm 
> that is particularly suited for imbalanced data sets.
> Requirements for successful PR:
>  # PartitionedDataset usage
>  # Trainer-Model paradigm support
>  # Tests for Model and for Trainer (and other stuff)
>  # Example of usage with small, but famous dataset like IRIS, Titanic or 
> House Prices
>  # Javadocs/codestyle according guidelines



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

[jira] [Commented] (IGNITE-10134) control.sh --cache list . --config not working on big cache setup

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-10134:
-

GitHub user antonovsergey93 opened a pull request:

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

IGNITE-10134 fix bug in --cache list --config command.



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

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

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

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


commit a5510150fd0ecb2a0b7d7b3837c0b77ed6b95daa
Author: Sergey Antonov 
Date:   2018-11-02T20:44:39Z

IGNITE-10134 Fix bug in reducing result on multinode execution.

commit 5363c47f670cb6b9dc659130cf67d00d9282465c
Author: Sergey Antonov 
Date:   2018-11-02T20:45:32Z

IGNITE-10134 Code was reformatted.




> control.sh --cache list . --config not working on big cache setup
> -
>
> Key: IGNITE-10134
> URL: https://issues.apache.org/jira/browse/IGNITE-10134
> Project: Ignite
>  Issue Type: Bug
>Reporter: ARomantsov
>Assignee: Sergey Antonov
>Priority: Critical
> Fix For: 2.8
>
>
> {code:java}
> [17:09:31,352][SEVERE][mgmt-#271][GridTaskWorker] Failed to reduce job 
> results due to undeclared user exception 
> [task=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask@22c7b357, 
> err=java.lang.AssertionError]
> java.lang.AssertionError
> at 
> org.apache.ignite.internal.visor.VisorOneNodeTask.reduce0(VisorOneNodeTask.java:30)
> at 
> org.apache.ignite.internal.visor.VisorMultiNodeTask.reduce(VisorMultiNodeTask.java:139)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$6.call(GridTaskWorker.java:1133)
> at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6726)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1131)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> [17:09:31,354][SEVERE][mgmt-#271][GridTaskCommandHandler] Failed to execute 
> task [name=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask, 
> clientId=606bf232-20e0-4799-bfb1-8d6e44b0d1ad]
> class org.apache.ignite.IgniteCheckedException: Failed to reduce job results 
> due to undeclared user exception 
> [task=org.apache.ignite.internal.visor.cache.VisorCacheConfigurationCollectorTask@22c7b357,
>  err=java.lang.AssertionError]
> at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7338)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at 
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:263)
> at 
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:257)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at 
> 

[jira] [Commented] (IGNITE-10134) control.sh --cache list . --config not working on big cache setup

[Sergey Antonov (JIRA)]

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

Sergey Antonov commented on IGNITE-10134:
-

Actualy, the bug in multinode execution.

> control.sh --cache list . --config not working on big cache setup
> -
>
> Key: IGNITE-10134
> URL: https://issues.apache.org/jira/browse/IGNITE-10134
> Project: Ignite
>  Issue Type: Bug
>Reporter: ARomantsov
>Assignee: Sergey Antonov
>Priority: Critical
> Fix For: 2.8
>
>
> {code:java}
> [17:09:31,352][SEVERE][mgmt-#271][GridTaskWorker] Failed to reduce job 
> results due to undeclared user exception 
> [task=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask@22c7b357, 
> err=java.lang.AssertionError]
> java.lang.AssertionError
> at 
> org.apache.ignite.internal.visor.VisorOneNodeTask.reduce0(VisorOneNodeTask.java:30)
> at 
> org.apache.ignite.internal.visor.VisorMultiNodeTask.reduce(VisorMultiNodeTask.java:139)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$6.call(GridTaskWorker.java:1133)
> at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6726)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1131)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> [17:09:31,354][SEVERE][mgmt-#271][GridTaskCommandHandler] Failed to execute 
> task [name=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask, 
> clientId=606bf232-20e0-4799-bfb1-8d6e44b0d1ad]
> class org.apache.ignite.IgniteCheckedException: Failed to reduce job results 
> due to undeclared user exception 
> [task=org.apache.ignite.internal.visor.cache.VisorCacheConfigurationCollectorTask@22c7b357,
>  err=java.lang.AssertionError]
> at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7338)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at 
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:263)
> at 
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:257)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1617)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1585)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1175)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
> at 

[jira] [Created] (IGNITE-10137) [TC Bot] Add button 'Expand all' on 'PR failures' page

[Nikolai Kulagin (JIRA)]

Nikolai Kulagin created IGNITE-10137:


 Summary: [TC Bot] Add button 'Expand all' on 'PR failures' page
 Key: IGNITE-10137
 URL: https://issues.apache.org/jira/browse/IGNITE-10137
 Project: Ignite
  Issue Type: Sub-task
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin


Add button 'Expand all' on '[PR failures|http://localhost:8080/prs.html]' page. 
The button should show additional information for all available lines.



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

[jira] [Issue Comment Deleted] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module

[PetrovMikhail (JIRA)]

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

PetrovMikhail updated IGNITE-9165:
--
Comment: was deleted

(was: {panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199976]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199974]]
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in 
last 100 master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 100 
master runs.

{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2067910buildTypeId=IgniteTests24Java8_RunAll])

> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
> Attachments: 
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields, 
> pass it to other methods that might close it, or return it, and does not 
> appear to close the stream on all paths out of the method.  This may result 
> in a file descriptor leak.
> Example:
>  
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
>  props.load(new FileReader(GridTestUtils.resolveIgnitePath(
>  "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
>  throw new RuntimeException(e);
> }{code}
>  
>  One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>   
>  +org.apache.ignite.internal:+   
>  * *BinaryContext*#classesInPackage(String)
>  * *GridClientJdkMarshaller*#marshal(Object, int)
>  * 
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
>  * *OptimizedObjectStreamSelfTest*#testReadLine()
>  * *PageIdDistributionTest*#_testRealHistory()
>  * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
>  * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
>  * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
>  * *GridTestUtils*.sslContext()



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

[jira] [Issue Comment Deleted] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module

[PetrovMikhail (JIRA)]

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

PetrovMikhail updated IGNITE-9165:
--
Comment: was deleted

(was: {panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199976]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199974]]
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in 
last 100 master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 100 
master runs.

{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2067910buildTypeId=IgniteTests24Java8_RunAll])

> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
> Attachments: 
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields, 
> pass it to other methods that might close it, or return it, and does not 
> appear to close the stream on all paths out of the method.  This may result 
> in a file descriptor leak.
> Example:
>  
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
>  props.load(new FileReader(GridTestUtils.resolveIgnitePath(
>  "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
>  throw new RuntimeException(e);
> }{code}
>  
>  One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>   
>  +org.apache.ignite.internal:+   
>  * *BinaryContext*#classesInPackage(String)
>  * *GridClientJdkMarshaller*#marshal(Object, int)
>  * 
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
>  * *OptimizedObjectStreamSelfTest*#testReadLine()
>  * *PageIdDistributionTest*#_testRealHistory()
>  * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
>  * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
>  * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
>  * *GridTestUtils*.sslContext()



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

[jira] [Issue Comment Deleted] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module

[PetrovMikhail (JIRA)]

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

PetrovMikhail updated IGNITE-9165:
--
Comment: was deleted

(was: {panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199976]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199974]]
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in 
last 100 master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 100 
master runs.

{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2067910buildTypeId=IgniteTests24Java8_RunAll])

> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
> Attachments: 
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields, 
> pass it to other methods that might close it, or return it, and does not 
> appear to close the stream on all paths out of the method.  This may result 
> in a file descriptor leak.
> Example:
>  
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
>  props.load(new FileReader(GridTestUtils.resolveIgnitePath(
>  "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
>  throw new RuntimeException(e);
> }{code}
>  
>  One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>   
>  +org.apache.ignite.internal:+   
>  * *BinaryContext*#classesInPackage(String)
>  * *GridClientJdkMarshaller*#marshal(Object, int)
>  * 
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
>  * *OptimizedObjectStreamSelfTest*#testReadLine()
>  * *PageIdDistributionTest*#_testRealHistory()
>  * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
>  * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
>  * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
>  * *GridTestUtils*.sslContext()



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

[jira] [Issue Comment Deleted] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module

[PetrovMikhail (JIRA)]

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

PetrovMikhail updated IGNITE-9165:
--
Comment: was deleted

(was: {panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199976]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199974]]
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in 
last 100 master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 100 
master runs.

{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2067910buildTypeId=IgniteTests24Java8_RunAll])

> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
> Attachments: 
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields, 
> pass it to other methods that might close it, or return it, and does not 
> appear to close the stream on all paths out of the method.  This may result 
> in a file descriptor leak.
> Example:
>  
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
>  props.load(new FileReader(GridTestUtils.resolveIgnitePath(
>  "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
>  throw new RuntimeException(e);
> }{code}
>  
>  One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>   
>  +org.apache.ignite.internal:+   
>  * *BinaryContext*#classesInPackage(String)
>  * *GridClientJdkMarshaller*#marshal(Object, int)
>  * 
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
>  * *OptimizedObjectStreamSelfTest*#testReadLine()
>  * *PageIdDistributionTest*#_testRealHistory()
>  * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
>  * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
>  * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
>  * *GridTestUtils*.sslContext()



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

[jira] [Commented] (IGNITE-10037) Cache 2 tests optimization

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-10037:
-

Yes, I'll try to look at the fix during the weekend.

> Cache 2 tests optimization
> --
>
> Key: IGNITE-10037
> URL: https://issues.apache.org/jira/browse/IGNITE-10037
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Platonov
>Assignee: Alexey Platonov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> We need to investigate how to optimize these tests:
> GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead
>  
> CacheTxLoadingConcurrentGridStartSelfTestAllowOverwrite.testLoadCacheWithDataStreamerSequentialWithConfigAndRestarts
>  IgniteCacheEntryProcessorNodeJoinTest.testEntryProcessorNodeLeave
>  
> CacheTxLoadingConcurrentGridStartSelfTestAllowOverwrite.testLoadCacheWithDataStreamerSequentialWithConfig
>  
> CacheTxLoadingConcurrentGridStartSelfTestAllowOverwrite.testLoadCacheWithDataStreamerSequentialClientWithConfig
>  
> and optimize them.



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

[jira] [Commented] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module

[PetrovMikhail (JIRA)]

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

PetrovMikhail commented on IGNITE-9165:
---

{panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199976]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199974]]
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in 
last 100 master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 100 
master runs.

{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2067910buildTypeId=IgniteTests24Java8_RunAll]

> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
> Attachments: 
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields, 
> pass it to other methods that might close it, or return it, and does not 
> appear to close the stream on all paths out of the method.  This may result 
> in a file descriptor leak.
> Example:
>  
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
>  props.load(new FileReader(GridTestUtils.resolveIgnitePath(
>  "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
>  throw new RuntimeException(e);
> }{code}
>  
>  One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>   
>  +org.apache.ignite.internal:+   
>  * *BinaryContext*#classesInPackage(String)
>  * *GridClientJdkMarshaller*#marshal(Object, int)
>  * 
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
>  * *OptimizedObjectStreamSelfTest*#testReadLine()
>  * *PageIdDistributionTest*#_testRealHistory()
>  * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
>  * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
>  * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
>  * *GridTestUtils*.sslContext()



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

[jira] [Created] (IGNITE-10136) NPE in PartitionUpdateCountersMessage

[Sergey Kozlov (JIRA)]

Sergey Kozlov created IGNITE-10136:
--

 Summary: NPE in PartitionUpdateCountersMessage
 Key: IGNITE-10136
 URL: https://issues.apache.org/jira/browse/IGNITE-10136
 Project: Ignite
  Issue Type: Bug
Affects Versions: 2.7
Reporter: Sergey Kozlov
 Fix For: 2.7


{noformat}
[14:00:55,950][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager] 
Checkpoint started [checkpointId=9d5398bc-896a-469c-8686-38e2afd517c1, 
startPtr=FileWALPointer [idx=0, fileOff=17828636, len=210609], 
checkpointLockWait=0ms, checkpointLockHoldTime=11ms, 
walCpRecordFsyncDuration=12ms, pages=636, reason='timeout']
[14:00:56,029][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager] 
Checkpoint finished [cpId=9d5398bc-896a-469c-8686-38e2afd517c1, pages=636, 
markPos=FileWALPointer [idx=0, fileOff=17828636, len=210609], 
walSegmentsCleared=0, walSegmentsCovered=[], markDuration=26ms, 
pagesWrite=21ms, fsync=58ms, total=105ms]
[14:00:56,940][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager] 
Checkpoint started [checkpointId=5f46c89e-ead8-4c87-adad-72a50c26bd7c, 
startPtr=FileWALPointer [idx=0, fileOff=20005440, len=210609], 
checkpointLockWait=0ms, checkpointLockHoldTime=8ms, 
walCpRecordFsyncDuration=5ms, pages=474, reason='timeout']
[14:00:57,003][INFO][db-checkpoint-thread-#73][GridCacheDatabaseSharedManager] 
Checkpoint finished [cpId=5f46c89e-ead8-4c87-adad-72a50c26bd7c, pages=474, 
markPos=FileWALPointer [idx=0, fileOff=20005440, len=210609], 
walSegmentsCleared=0, walSegmentsCovered=[], markDuration=15ms, 
pagesWrite=10ms, fsync=53ms, total=78ms]
[14:00:57,065][SEVERE][grid-nio-worker-tcp-comm-2-#42][GridDirectParser] Failed 
to read message [msg=GridIoMessage [plc=0, topic=null, topicOrd=-1, 
ordered=false, timeout=0, skipOnTimeout=false, msg=null], 
buf=java.nio.DirectByteBuffer[pos=792 lim=885 cap=32768], 
reader=RollingUpgradeMessageReader [state=StateItem 
[stream=DirectByteBufferStreamImplV2 [baseOff=140703933959040, arrOff=-1, 
tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=true, 
msg=GridCacheIdMessage [cacheId=0]GridDistributedBaseMessage 
[ver=GridCacheVersion [topVer=152301622, order=1540821647376, nodeOrder=4], 
committedVers=null, rolledbackVers=null, cnt=0, 
super=]GridDistributedTxPrepareRequest [threadId=236, concurrency=PESSIMISTIC, 
isolation=REPEATABLE_READ, writeVer=GridCacheVersion [topVer=152301622, 
order=1540821647377, nodeOrder=4], timeout=0, reads=null, writes=ArrayList [], 
dhtVers=null, txSize=-1, plc=2, txState=null, flags=last, 
super=]GridDhtTxPrepareRequest 
[nearNodeId=3800f476-beb1-46b0-8a39-faa51c91831d, 
futId=f794020c661-cc8749ef-caa5-4f1e-9d89-4a9beff59798, miniId=1, 
topVer=AffinityTopologyVersion [topVer=5, minorTopVer=8], 
invalidateNearEntries={}, nearWrites=null, owned=null, 
nearXidVer=GridCacheVersion [topVer=152301622, order=1540821647374, 
nodeOrder=5], subjId=3800f476-beb1-46b0-8a39-faa51c91831d, taskNameHash=0, 
preloadKeys=null, mvccSnapshot=MvccSnapshotResponse [futId=1, 
crdVer=1540821617885, cntr=16, opCntr=1, txs=null, cleanupVer=15, tracking=0], 
skipCompletedVers=false, super=], mapIt=null, it=null, arrPos=-1, 
keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0, uuidState=0, 
uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true], state=0, fieldCnt=7, 
readFieldCnt=0, curName=msg, typeRead=true, itemTypeRead=false, 
keyTypeRead=false, valTypeRead=false, curType=21, curItemType=null, 
curKeyType=null, curValType=null, readMsgCls=class 
o.a.i.i.managers.communication.GridIoMessage]StateItem 
[stream=DirectByteBufferStreamImplV2 [baseOff=140703933959040, arrOff=-1, 
tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=true, 
msg=PartitionUpdateCountersMessage{cacheId=-553317389, size=0, cntrs=}, 
mapIt=null, it=null, arrPos=-1, keyDone=false, readSize=1, readItems=0, prim=0, 
primShift=0, uuidState=0, uuidMost=0, uuidLeast=0, uuidLocId=0, 
lastFinished=true], state=0, fieldCnt=-1, readFieldCnt=0, curName=null, 
typeRead=false, itemTypeRead=false, keyTypeRead=false, valTypeRead=false, 
curType=0, curItemType=null, curKeyType=null, curValType=null, 
readMsgCls=null]StateItem [stream=DirectByteBufferStreamImplV2 
[baseOff=140703933959040, arrOff=-1, tmpArrOff=0, valReadBytes=0, 
tmpArrBytes=0, msgTypeDone=false, msg=null, mapIt=null, it=null, arrPos=-1, 
keyDone=false, readSize=-1, readItems=0, prim=0, primShift=0, uuidState=0, 
uuidMost=0, uuidLeast=0, uuidLocId=0, lastFinished=true], state=0, fieldCnt=-1, 
readFieldCnt=0, curName=null, typeRead=false, itemTypeRead=false, 
keyTypeRead=false, valTypeRead=false, curType=0, curItemType=null, 
curKeyType=null, curValType=null, readMsgCls=null]StateItem 
[stream=DirectByteBufferStreamImplV2 [baseOff=140703933959040, arrOff=-1, 
tmpArrOff=0, valReadBytes=0, tmpArrBytes=0, msgTypeDone=false, msg=null, 
mapIt=null, it=null, arrPos=-1, keyDone=false, 

[jira] [Commented] (IGNITE-10128) IO race during read\write cache configurations.

[Ignite TC Bot (JIRA)]

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

Ignite TC Bot commented on IGNITE-10128:


{panel:title=No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2226874buildTypeId=IgniteTests24Java8_RunAll]

> IO race during read\write cache configurations.
> ---
>
> Key: IGNITE-10128
> URL: https://issues.apache.org/jira/browse/IGNITE-10128
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
>
> During grid usage, found problem below. I tries simultaneously start several 
> nodes and call *activate* on ** each node.
> {code:java}
> [15:38:25,186][INFO][exchange-worker-#63][FileWriteAheadLogManager] Resuming 
> logging to WAL segment 
> [file=/storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/wal/node2/.wal,
>  offset=0, ver=2]
> [15:38:25,210][INFO][exchange-worker-#63][GridSnapshotAwareClusterStateProcessorImpl]
>  Writing BaselineTopology[id=0]
> [15:38:25,225][INFO][exchange-worker-#63][GridCacheDatabaseSharedManager] 
> Resume logging performed in 41 ms.
> [15:38:25,252][INFO][exchange-worker-#63][CacheAffinitySharedManager] 
> Updating caches registry performed in 27 ms.
> [15:38:25,743][SEVERE][sys-#70][] Critical system error detected. Will be 
> handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler 
> [tryStop=false, timeout=0, super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED]]], 
> failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=java.nio.file.NoSuchFileException: 
> /storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp]]
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
> [SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=java.nio.file.NoSuchFileException: 
> /storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp]]
> java.nio.file.NoSuchFileException: 
> /storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp
> at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:409)
> at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.storeCacheData(FilePageStoreManager.java:390)
> at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.lambda$persistCacheConfigurations$4(CachesRegistry.java:303)
> at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6875)
> at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}



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

[jira] [Created] (IGNITE-10135) Documentation link to ClusterNodeAttributeAffinityBackupFilter

[David Harvey (JIRA)]

David Harvey created IGNITE-10135:
-

 Summary: Documentation link to 
ClusterNodeAttributeAffinityBackupFilter
 Key: IGNITE-10135
 URL: https://issues.apache.org/jira/browse/IGNITE-10135
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Reporter: David Harvey
 Fix For: 2.7


IGNITE-9365 adds ClusterNodeAttributeAffinityBackupFilter to allow "Crash-safe 
Affinity"  
([https://apacheignite.readme.io/docs/affinity-collocation|https://apacheignite.readme.io/docs/affinity-collocation_])
 to be configured from spring.  

The class should have an adequate description of how to set this up, but the 
above section should link to or otherwise flag that such a procedure exist.

[https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/cache/affinity/rendezvous/ClusterNodeAttributeAffinityBackupFilter.java]

 

Note: the implementation is generic, allowing any node attribute (or 
environment variable) to be configured so that primary and backup's are always 
forced to not be on the same node.



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

[jira] [Assigned] (IGNITE-10127) GridCacheRebalancingSyncSelfTest ignores check result

[Rodion (JIRA)]

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

Rodion reassigned IGNITE-10127:
---

Assignee: Rodion

> GridCacheRebalancingSyncSelfTest ignores check result
> -
>
> Key: IGNITE-10127
> URL: https://issues.apache.org/jira/browse/IGNITE-10127
> Project: Ignite
>  Issue Type: Test
>Reporter: Ryabov Dmitrii
>Assignee: Rodion
>Priority: Trivial
>  Labels: newbie
> Fix For: 2.8
>
>
> {{checkSupplyContextMapIsEmpty()}} method checks that map is empty, but 
> ignores result of this check.
> {code:java}
> GridTestUtils.waitForCondition(new PA() {
> @Override public boolean apply() {
> synchronized (map) {
> return map.isEmpty();
> }
> }
> }, 15_000);
> {code}
> We should check that {{waitForCondition()}} returns true to be sure that map 
> is cleared.



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

[jira] [Commented] (IGNITE-9406) Improve SQL "Performance and Debugging" page

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-9406:
-

[~Artem Budnikov], [~vozerov], please also include an example of the query with 
sub-selects (e.g. when we need to make a union of 2 selects). The collocated 
flag makes a lot of sense for that queries as well. We need to show them 
explicitly.

> Improve SQL "Performance and Debugging" page
> 
>
> Key: IGNITE-9406
> URL: https://issues.apache.org/jira/browse/IGNITE-9406
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.7
>
> Attachments: ignite_sql_perf.txt
>
>
> I prepared a document for one of Ignite clients with some advanced 
> information about how various performance optimizations work in Ignite SQL. 
> Let's compare this document with our "Performance and Debugging" page [1], 
> and enhance the latter with missing info (if any).
> P.S.: Document is attached. Russian language.
> [1] 
> https://apacheignite-sql.readme.io/docs/performance-and-debugging#query-execution-flow-optimizations



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

[jira] [Assigned] (IGNITE-10134) control.sh --cache list . --config not working on big cache setup

[Sergey Antonov (JIRA)]

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

Sergey Antonov reassigned IGNITE-10134:
---

Assignee: Sergey Antonov

> control.sh --cache list . --config not working on big cache setup
> -
>
> Key: IGNITE-10134
> URL: https://issues.apache.org/jira/browse/IGNITE-10134
> Project: Ignite
>  Issue Type: Bug
>Reporter: ARomantsov
>Assignee: Sergey Antonov
>Priority: Critical
> Fix For: 2.8
>
>
> {code:java}
> [17:09:31,352][SEVERE][mgmt-#271][GridTaskWorker] Failed to reduce job 
> results due to undeclared user exception 
> [task=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask@22c7b357, 
> err=java.lang.AssertionError]
> java.lang.AssertionError
> at 
> org.apache.ignite.internal.visor.VisorOneNodeTask.reduce0(VisorOneNodeTask.java:30)
> at 
> org.apache.ignite.internal.visor.VisorMultiNodeTask.reduce(VisorMultiNodeTask.java:139)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$6.call(GridTaskWorker.java:1133)
> at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6726)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1131)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> [17:09:31,354][SEVERE][mgmt-#271][GridTaskCommandHandler] Failed to execute 
> task [name=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask, 
> clientId=606bf232-20e0-4799-bfb1-8d6e44b0d1ad]
> class org.apache.ignite.IgniteCheckedException: Failed to reduce job results 
> due to undeclared user exception 
> [task=org.apache.ignite.internal.visor.cache.VisorCacheConfigurationCollectorTask@22c7b357,
>  err=java.lang.AssertionError]
> at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7338)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at 
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:263)
> at 
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:257)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1617)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1585)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1175)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
> at 
> 

[jira] [Commented] (IGNITE-10079) FileWriteAheadLogManager may return invalid lastCompactedSegment

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov commented on IGNITE-10079:
---

[~akalashnikov], thanks for your notes and suggestions. I will work on them 
next week.

> FileWriteAheadLogManager may return invalid lastCompactedSegment
> 
>
> Key: IGNITE-10079
> URL: https://issues.apache.org/jira/browse/IGNITE-10079
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
> Attachments: WalCompactionAfterRestartTest.java
>
>
> As of current {{master}} branch, 
> {{FileWriteAheadLogManager#lastCompactedSegment}} may report -1 even after 
> some segments have been actually compressed. Reproducer is attached.



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

[jira] [Commented] (IGNITE-9746) [ML] Add Complement Naive Bayes

[Alexey Platonov (JIRA)]

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

Alexey Platonov commented on IGNITE-9746:
-

Dear [~rgaleyev],

could you merge your Naive-Bayes-tickets with these:

https://issues.apache.org/jira/browse/IGNITE-9978

https://issues.apache.org/jira/browse/IGNITE-9979

I understand that these tickets was created later than your but they are more 
general than your. For example Naive Bayes with discrete distribution = 
Bernoulli + Multinominal model.

> [ML] Add Complement Naive Bayes
> ---
>
> Key: IGNITE-9746
> URL: https://issues.apache.org/jira/browse/IGNITE-9746
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Ravil Galeyev
>Priority: Major
>
> Naive Bayes classifiers are a family of simple probabilistic classifiers 
> based on applying Bayes' theorem with strong (naive) independence assumptions 
> between the features.
> So we want to add this algorithm to Apache Ignite ML module.
> [Complement Naive 
> Bayes|http://scikit-learn.org/stable/modules/naive_bayes.html#complement-naive-bayes]
>  is an adaptation of the standard multinomial naive Bayes (MNB) algorithm 
> that is particularly suited for imbalanced data sets.
> Requirements for successful PR:
>  # PartitionedDataset usage
>  # Trainer-Model paradigm support
>  # Tests for Model and for Trainer (and other stuff)
>  # Example of usage with small, but famous dataset like IRIS, Titanic or 
> House Prices
>  # Javadocs/codestyle according guidelines



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

[jira] [Commented] (IGNITE-10134) control.sh --cache list . --config not working on big cache setup

[ARomantsov (JIRA)]

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

ARomantsov commented on IGNITE-10134:
-

I found that command on - https://issues.apache.org/jira/browse/IGNITE-9853

> control.sh --cache list . --config not working on big cache setup
> -
>
> Key: IGNITE-10134
> URL: https://issues.apache.org/jira/browse/IGNITE-10134
> Project: Ignite
>  Issue Type: Bug
>Reporter: ARomantsov
>Priority: Critical
> Fix For: 2.8
>
>
> {code:java}
> [17:09:31,352][SEVERE][mgmt-#271][GridTaskWorker] Failed to reduce job 
> results due to undeclared user exception 
> [task=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask@22c7b357, 
> err=java.lang.AssertionError]
> java.lang.AssertionError
> at 
> org.apache.ignite.internal.visor.VisorOneNodeTask.reduce0(VisorOneNodeTask.java:30)
> at 
> org.apache.ignite.internal.visor.VisorMultiNodeTask.reduce(VisorMultiNodeTask.java:139)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$6.call(GridTaskWorker.java:1133)
> at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6726)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1131)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> [17:09:31,354][SEVERE][mgmt-#271][GridTaskCommandHandler] Failed to execute 
> task [name=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask, 
> clientId=606bf232-20e0-4799-bfb1-8d6e44b0d1ad]
> class org.apache.ignite.IgniteCheckedException: Failed to reduce job results 
> due to undeclared user exception 
> [task=org.apache.ignite.internal.visor.cache.VisorCacheConfigurationCollectorTask@22c7b357,
>  err=java.lang.AssertionError]
> at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7338)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at 
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:263)
> at 
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:257)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1617)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1585)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1175)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
> at 
> 

[jira] [Created] (IGNITE-10134) control.sh --cache list . --config not working on big cache setup

[ARomantsov (JIRA)]

ARomantsov created IGNITE-10134:
---

 Summary: control.sh --cache list . --config not working on big 
cache setup
 Key: IGNITE-10134
 URL: https://issues.apache.org/jira/browse/IGNITE-10134
 Project: Ignite
  Issue Type: Bug
Reporter: ARomantsov



{code:java}
[17:09:31,352][SEVERE][mgmt-#271][GridTaskWorker] Failed to reduce job results 
due to undeclared user exception 
[task=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask@22c7b357, 
err=java.lang.AssertionError]
java.lang.AssertionError
at 
org.apache.ignite.internal.visor.VisorOneNodeTask.reduce0(VisorOneNodeTask.java:30)
at 
org.apache.ignite.internal.visor.VisorMultiNodeTask.reduce(VisorMultiNodeTask.java:139)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker$6.call(GridTaskWorker.java:1133)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6726)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1131)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
[17:09:31,354][SEVERE][mgmt-#271][GridTaskCommandHandler] Failed to execute 
task [name=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask, 
clientId=606bf232-20e0-4799-bfb1-8d6e44b0d1ad]
class org.apache.ignite.IgniteCheckedException: Failed to reduce job results 
due to undeclared user exception 
[task=org.apache.ignite.internal.visor.cache.VisorCacheConfigurationCollectorTask@22c7b357,
 err=java.lang.AssertionError]
at 
org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7338)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
at 
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:263)
at 
org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:257)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1617)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1585)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1175)
at 
org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
at 
org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at 
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at 
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
at 

[jira] [Updated] (IGNITE-10134) control.sh --cache list . --config not working on big cache setup

[ARomantsov (JIRA)]

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

ARomantsov updated IGNITE-10134:

Fix Version/s: 2.8

> control.sh --cache list . --config not working on big cache setup
> -
>
> Key: IGNITE-10134
> URL: https://issues.apache.org/jira/browse/IGNITE-10134
> Project: Ignite
>  Issue Type: Bug
>Reporter: ARomantsov
>Priority: Critical
> Fix For: 2.8
>
>
> {code:java}
> [17:09:31,352][SEVERE][mgmt-#271][GridTaskWorker] Failed to reduce job 
> results due to undeclared user exception 
> [task=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask@22c7b357, 
> err=java.lang.AssertionError]
> java.lang.AssertionError
> at 
> org.apache.ignite.internal.visor.VisorOneNodeTask.reduce0(VisorOneNodeTask.java:30)
> at 
> org.apache.ignite.internal.visor.VisorMultiNodeTask.reduce(VisorMultiNodeTask.java:139)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker$6.call(GridTaskWorker.java:1133)
> at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6726)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1131)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> [17:09:31,354][SEVERE][mgmt-#271][GridTaskCommandHandler] Failed to execute 
> task [name=o.a.i.i.v.cache.VisorCacheConfigurationCollectorTask, 
> clientId=606bf232-20e0-4799-bfb1-8d6e44b0d1ad]
> class org.apache.ignite.IgniteCheckedException: Failed to reduce job results 
> due to undeclared user exception 
> [task=org.apache.ignite.internal.visor.cache.VisorCacheConfigurationCollectorTask@22c7b357,
>  err=java.lang.AssertionError]
> at 
> org.apache.ignite.internal.util.IgniteUtils.cast(IgniteUtils.java:7338)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.resolve(GridFutureAdapter.java:259)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:171)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:140)
> at 
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:263)
> at 
> org.apache.ignite.internal.processors.rest.handlers.task.GridTaskCommandHandler$2.apply(GridTaskCommandHandler.java:257)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.notifyListener(GridFutureAdapter.java:383)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblock(GridFutureAdapter.java:347)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.unblockAll(GridFutureAdapter.java:335)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:495)
> at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:474)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1617)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.finishTask(GridTaskWorker.java:1585)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.reduce(GridTaskWorker.java:1175)
> at 
> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:958)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1104)
> at 
> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1339)
> at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)

[jira] [Commented] (IGNITE-10133) ML: Switch to per-node TensorFlow worker strategy

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-10133:
-

GitHub user dmitrievanthony opened a pull request:

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

IGNITE-10133: Switch to per-node TensorFlow worker strategy.



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

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

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

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


commit 13962c2c13d1cf945cac90ce003831d0a4a4fd33
Author: Anton Dmitriev 
Date:   2018-11-02T15:20:52Z

IGNITE-10133: Switch to per-node TensorFlow worker strategy.




> ML: Switch to per-node TensorFlow worker strategy
> -
>
> Key: IGNITE-10133
> URL: https://issues.apache.org/jira/browse/IGNITE-10133
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Affects Versions: 2.8
>Reporter: Anton Dmitriev
>Assignee: Anton Dmitriev
>Priority: Major
> Fix For: 2.8
>
>
> Currently we start TensorFlow worker process per every cache partition. In 
> case node is equipped by GPU and TensorFlow uses this GPU it acquires all GPU 
> memory. If two worker processes try to acquire all GPU memory they will fail.
> To eliminate this problem and allow users utilizing GPU during the training 
> we need to switch to per-node strategy. It means we need to start one 
> TensorFlow worker process per node, not per partition.



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

[jira] [Created] (IGNITE-10133) ML: Switch to per-node TensorFlow worker strategy

[Anton Dmitriev (JIRA)]

Anton Dmitriev created IGNITE-10133:
---

 Summary: ML: Switch to per-node TensorFlow worker strategy
 Key: IGNITE-10133
 URL: https://issues.apache.org/jira/browse/IGNITE-10133
 Project: Ignite
  Issue Type: Improvement
  Components: ml
Affects Versions: 2.8
Reporter: Anton Dmitriev
Assignee: Anton Dmitriev
 Fix For: 2.8


Currently we start TensorFlow worker process per every cache partition. In case 
node is equipped by GPU and TensorFlow uses this GPU it acquires all GPU 
memory. If two worker processes try to acquire all GPU memory they will fail.

To eliminate this problem and allow users utilizing GPU during the training we 
need to switch to per-node strategy. It means we need to start one TensorFlow 
worker process per node, not per partition.



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

[jira] [Commented] (IGNITE-7955) MVCC TX: cache peek for key-value API

[Ivan Pavlukhin (JIRA)]

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

Ivan Pavlukhin commented on IGNITE-7955:


{{ONHEAP}} mode seems to have a little sense for MVCC. Proposed behavior is to 
always return {{null}} for that mode. _Near_ caches are not supported for MVCC, 
{{null}} will be returned for them as well.

> MVCC TX: cache peek for key-value API
> -
>
> Key: IGNITE-7955
> URL: https://issues.apache.org/jira/browse/IGNITE-7955
> Project: Ignite
>  Issue Type: Task
>  Components: cache, mvcc
>Reporter: Alexander Paschenko
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.8
>
>
> We need to implement MVCC-compatible cache peek operation for key-value API.



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

[jira] [Comment Edited] (IGNITE-10103) Fix IgnitePersistentStoreDataStructuresTest.testSequenceAfterAutoactivation

[Ivan Pavlukhin (JIRA)]

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

Ivan Pavlukhin edited comment on IGNITE-10103 at 11/2/18 3:04 PM:
--

[~slukyanov]
An original test purpose was to ensure that {{atomicSequence}} call does not 
hang. Fair awaiting for an activation would break an experiment.


was (Author: pavlukhin):
[~slukyanov]
An original test purpose was to ensure that `atomicSequence` call does not 
hang. Fair awaiting for an activation would break an experiment.

> Fix IgnitePersistentStoreDataStructuresTest.testSequenceAfterAutoactivation
> ---
>
> Key: IGNITE-10103
> URL: https://issues.apache.org/jira/browse/IGNITE-10103
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> IgnitePersistentStoreDataStructuresTest.testSequenceAfterAutoactivation can 
> fail with exception stating that the cluster is not activated. A proposed fix 
> is catching exception and retrying an operation until success.



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

[jira] [Commented] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module

[PetrovMikhail (JIRA)]

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

PetrovMikhail commented on IGNITE-9165:
---

{panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199976]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199974]]
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in 
last 100 master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 100 
master runs.

{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2067910buildTypeId=IgniteTests24Java8_RunAll]

> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
> Attachments: 
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields, 
> pass it to other methods that might close it, or return it, and does not 
> appear to close the stream on all paths out of the method.  This may result 
> in a file descriptor leak.
> Example:
>  
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
>  props.load(new FileReader(GridTestUtils.resolveIgnitePath(
>  "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
>  throw new RuntimeException(e);
> }{code}
>  
>  One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>   
>  +org.apache.ignite.internal:+   
>  * *BinaryContext*#classesInPackage(String)
>  * *GridClientJdkMarshaller*#marshal(Object, int)
>  * 
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
>  * *OptimizedObjectStreamSelfTest*#testReadLine()
>  * *PageIdDistributionTest*#_testRealHistory()
>  * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
>  * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
>  * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
>  * *GridTestUtils*.sslContext()



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

[jira] [Updated] (IGNITE-10132) TC: the thin client suites (PHP, nodejs etc) must contain log of the Ignite node

[Peter Ivanov (JIRA)]

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

Peter Ivanov updated IGNITE-10132:
--
Summary: TC: the thin client suites (PHP, nodejs etc) must contain log of 
the Ignite node  (was: TC: the thin client suites (PHP, nodejs etc) must 
contains log of the Ignite node)

> TC: the thin client suites (PHP, nodejs etc) must contain log of the Ignite 
> node
> 
>
> Key: IGNITE-10132
> URL: https://issues.apache.org/jira/browse/IGNITE-10132
> Project: Ignite
>  Issue Type: Task
>  Components: thin client
>Reporter: Taras Ledkov
>Assignee: Peter Ivanov
>Priority: Major
>
> It will be great to add the Ignite node's log to a build artifact for thin 
> clients tests suites.
> It makes troubleshooting easier.
> If there is another way to publish node's log that is more convenient please 
> use it (I know nothing about it).
> Test suites:
> - Thin client: Node.js;
> - Thin client: PHP;
> - Thin client: Python.



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

[jira] [Resolved] (IGNITE-10132) TC: the thin client suites (PHP, nodejs etc) must contains log of the Ignite node

[Peter Ivanov (JIRA)]

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

Peter Ivanov resolved IGNITE-10132.
---
Resolution: Done

Added work/log extraction to logs.zip after build is finished.

> TC: the thin client suites (PHP, nodejs etc) must contains log of the Ignite 
> node
> -
>
> Key: IGNITE-10132
> URL: https://issues.apache.org/jira/browse/IGNITE-10132
> Project: Ignite
>  Issue Type: Task
>  Components: thin client
>Reporter: Taras Ledkov
>Assignee: Peter Ivanov
>Priority: Major
>
> It will be great to add the Ignite node's log to a build artifact for thin 
> clients tests suites.
> It makes troubleshooting easier.
> If there is another way to publish node's log that is more convenient please 
> use it (I know nothing about it).
> Test suites:
> - Thin client: Node.js;
> - Thin client: PHP;
> - Thin client: Python.



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

[jira] [Resolved] (IGNITE-9309) LocalNodeMovingPartitionsCount metrics may calculates incorrect due to processFullPartitionUpdate

[Oleg Ostanin (JIRA)]

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

Oleg Ostanin resolved IGNITE-9309.
--
Resolution: Fixed

> LocalNodeMovingPartitionsCount metrics may calculates incorrect due to 
> processFullPartitionUpdate
> -
>
> Key: IGNITE-9309
> URL: https://issues.apache.org/jira/browse/IGNITE-9309
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Maxim Muzafarov
>Assignee: Oleg Ostanin
>Priority: Major
> Attachments: GridCacheRebalancingCancelTestNoReproduce.java, 
> node-2-jstack.log, node-NO_REBALANCE-7165.log
>
>
> [~qvad] have found incorrect {{LocalNodeMovingPartitionsCount}} metrics 
> calculation on client node {{JOIN\LEFT}}. Full issue reproducer is absent.
> Probable scenario:
> {code}
> Repeat 10 times:
> 1. stop node
> 2. clean lfs
> 3. add stopped node (trigger rebalance)
> 4. 3 times: start 2 clients, wait for topology snapshot, close clients
> 5. for each cache group check JMX metrics LocalNodeMovingPartitionsCount 
> (like waitForFinishRebalance())
> {code}
> Whole discussion and all configuration details can be found in comments of 
> [IGNITE-7165|https://issues.apache.org/jira/browse/IGNITE-7165].



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

[jira] [Closed] (IGNITE-9309) LocalNodeMovingPartitionsCount metrics may calculates incorrect due to processFullPartitionUpdate

[Oleg Ostanin (JIRA)]

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

Oleg Ostanin closed IGNITE-9309.


> LocalNodeMovingPartitionsCount metrics may calculates incorrect due to 
> processFullPartitionUpdate
> -
>
> Key: IGNITE-9309
> URL: https://issues.apache.org/jira/browse/IGNITE-9309
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Maxim Muzafarov
>Assignee: Oleg Ostanin
>Priority: Major
> Attachments: GridCacheRebalancingCancelTestNoReproduce.java, 
> node-2-jstack.log, node-NO_REBALANCE-7165.log
>
>
> [~qvad] have found incorrect {{LocalNodeMovingPartitionsCount}} metrics 
> calculation on client node {{JOIN\LEFT}}. Full issue reproducer is absent.
> Probable scenario:
> {code}
> Repeat 10 times:
> 1. stop node
> 2. clean lfs
> 3. add stopped node (trigger rebalance)
> 4. 3 times: start 2 clients, wait for topology snapshot, close clients
> 5. for each cache group check JMX metrics LocalNodeMovingPartitionsCount 
> (like waitForFinishRebalance())
> {code}
> Whole discussion and all configuration details can be found in comments of 
> [IGNITE-7165|https://issues.apache.org/jira/browse/IGNITE-7165].



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

[jira] [Commented] (IGNITE-9309) LocalNodeMovingPartitionsCount metrics may calculates incorrect due to processFullPartitionUpdate

[Oleg Ostanin (JIRA)]

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

Oleg Ostanin commented on IGNITE-9309:
--

fixed in https://issues.apache.org/jira/browse/IGNITE-9492

> LocalNodeMovingPartitionsCount metrics may calculates incorrect due to 
> processFullPartitionUpdate
> -
>
> Key: IGNITE-9309
> URL: https://issues.apache.org/jira/browse/IGNITE-9309
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Maxim Muzafarov
>Assignee: Oleg Ostanin
>Priority: Major
> Attachments: GridCacheRebalancingCancelTestNoReproduce.java, 
> node-2-jstack.log, node-NO_REBALANCE-7165.log
>
>
> [~qvad] have found incorrect {{LocalNodeMovingPartitionsCount}} metrics 
> calculation on client node {{JOIN\LEFT}}. Full issue reproducer is absent.
> Probable scenario:
> {code}
> Repeat 10 times:
> 1. stop node
> 2. clean lfs
> 3. add stopped node (trigger rebalance)
> 4. 3 times: start 2 clients, wait for topology snapshot, close clients
> 5. for each cache group check JMX metrics LocalNodeMovingPartitionsCount 
> (like waitForFinishRebalance())
> {code}
> Whole discussion and all configuration details can be found in comments of 
> [IGNITE-7165|https://issues.apache.org/jira/browse/IGNITE-7165].



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

[jira] [Commented] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module

[PetrovMikhail (JIRA)]

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

PetrovMikhail commented on IGNITE-9165:
---

{panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199976]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199974]]
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in 
last 100 master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 100 
master runs.

{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2067910buildTypeId=IgniteTests24Java8_RunAll]

> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
> Attachments: 
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields, 
> pass it to other methods that might close it, or return it, and does not 
> appear to close the stream on all paths out of the method.  This may result 
> in a file descriptor leak.
> Example:
>  
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
>  props.load(new FileReader(GridTestUtils.resolveIgnitePath(
>  "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
>  throw new RuntimeException(e);
> }{code}
>  
>  One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>   
>  +org.apache.ignite.internal:+   
>  * *BinaryContext*#classesInPackage(String)
>  * *GridClientJdkMarshaller*#marshal(Object, int)
>  * 
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
>  * *OptimizedObjectStreamSelfTest*#testReadLine()
>  * *PageIdDistributionTest*#_testRealHistory()
>  * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
>  * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
>  * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
>  * *GridTestUtils*.sslContext()



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

[jira] [Commented] (IGNITE-9897) Quering with PDO returns null for all column values except the 1st one

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-9897:


GitHub user isapego opened a pull request:

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

IGNITE-9897: ODBC fix for PDO when used with unixODBC



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

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

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

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


commit 28f4a3a866f0d090baf4b20fa2085e9e58c68cee
Author: Igor Sapego 
Date:   2018-11-02T14:16:37Z

IGNITE-9897: ODBC fix for PDO when used with unixODBC




> Quering with PDO returns null for all column values except the 1st one
> --
>
> Key: IGNITE-9897
> URL: https://issues.apache.org/jira/browse/IGNITE-9897
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Affects Versions: 2.6
> Environment: CentOS
>Reporter: Roman Shtykh
>Assignee: Igor Sapego
>Priority: Major
> Attachments: odbc.log, phpPDO2.out, phpPdo.out, unixOdbc.log
>
>
> Using _odbc_connect_ returns all column values, but with _PDO_ only the 1st 
> one – all the rest are null.
>  Reproduced on CentOS.
>  # Start a server node with Ignite CPP
>  # Run odbc-example (which will create two tables)
>  # Run a simple PHP script
> {code:php}
>  try {
> echo PHP_EOL,PHP_EOL,"# Using PDO",PHP_EOL;
> $dbh = new PDO('odbc:ApacheIgnite');
> $dbh->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
> $sql = 'SELECT * FROM "Person".Person';
> $data = $dbh->query($sql);
> foreach($data as $row) {
> var_export($row);
>   }
> echo PHP_EOL,PHP_EOL,"# Using odbc_*( ) Functions",PHP_EOL;
>   
> $conn = odbc_connect('ApacheIgnite','','');
> $rs = odbc_exec($conn, $sql);
>   
> while($row = odbc_fetch_array($rs)) {
> var_export($row);
>   }
> 
> } catch (PDOException $e) {
> print "Error!: " . $e->getMessage() . "\n";
> die();
> }
> ?>
> {code}
>  



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

[jira] [Commented] (IGNITE-10079) FileWriteAheadLogManager may return invalid lastCompactedSegment

[Anton Kalashnikov (JIRA)]

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

Anton Kalashnikov commented on IGNITE-10079:


[~andrey-kuznetsov], I left some comments in UpSource you can check it.
[~ivandasch], [~ivan.glukos], if it possible can you also take a look the 
changes.

> FileWriteAheadLogManager may return invalid lastCompactedSegment
> 
>
> Key: IGNITE-10079
> URL: https://issues.apache.org/jira/browse/IGNITE-10079
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Andrey Kuznetsov
>Assignee: Andrey Kuznetsov
>Priority: Major
> Fix For: 2.8
>
> Attachments: WalCompactionAfterRestartTest.java
>
>
> As of current {{master}} branch, 
> {{FileWriteAheadLogManager#lastCompactedSegment}} may report -1 even after 
> some segments have been actually compressed. Reproducer is attached.



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

[jira] [Commented] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module

[PetrovMikhail (JIRA)]

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

PetrovMikhail commented on IGNITE-9165:
---

{panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199976]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199974]]
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in 
last 100 master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 100 
master runs.

{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2067910buildTypeId=IgniteTests24Java8_RunAll]

> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
> Attachments: 
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields, 
> pass it to other methods that might close it, or return it, and does not 
> appear to close the stream on all paths out of the method.  This may result 
> in a file descriptor leak.
> Example:
>  
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
>  props.load(new FileReader(GridTestUtils.resolveIgnitePath(
>  "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
>  throw new RuntimeException(e);
> }{code}
>  
>  One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>   
>  +org.apache.ignite.internal:+   
>  * *BinaryContext*#classesInPackage(String)
>  * *GridClientJdkMarshaller*#marshal(Object, int)
>  * 
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
>  * *OptimizedObjectStreamSelfTest*#testReadLine()
>  * *PageIdDistributionTest*#_testRealHistory()
>  * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
>  * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
>  * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
>  * *GridTestUtils*.sslContext()



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

[jira] [Issue Comment Deleted] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module

[PetrovMikhail (JIRA)]

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

PetrovMikhail updated IGNITE-9165:
--
Comment: was deleted

(was: {panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199976]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199974]]
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in 
last 100 master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 100 
master runs.

{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2067910buildTypeId=IgniteTests24Java8_RunAll])

> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
> Attachments: 
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields, 
> pass it to other methods that might close it, or return it, and does not 
> appear to close the stream on all paths out of the method.  This may result 
> in a file descriptor leak.
> Example:
>  
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
>  props.load(new FileReader(GridTestUtils.resolveIgnitePath(
>  "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
>  throw new RuntimeException(e);
> }{code}
>  
>  One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>   
>  +org.apache.ignite.internal:+   
>  * *BinaryContext*#classesInPackage(String)
>  * *GridClientJdkMarshaller*#marshal(Object, int)
>  * 
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
>  * *OptimizedObjectStreamSelfTest*#testReadLine()
>  * *PageIdDistributionTest*#_testRealHistory()
>  * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
>  * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
>  * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
>  * *GridTestUtils*.sslContext()



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

[jira] [Comment Edited] (IGNITE-8871) TDE - Phase-1. Documentation

[Artem Budnikov (JIRA)]

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

Artem Budnikov edited comment on IGNITE-8871 at 11/2/18 2:25 PM:
-

[~NIzhikov]

I use JDK 1.8.0_181, the error I've got is: "Invalid AES key length: 1218 
bytes" , although I know the key length is 2048 bit.

Also, I managed to start Ignite with a different key, which I got from someone 
who already tested TDE, and it worked. So I think my JDK is ok, but the key 
isn't right.

What is the right command to generate a key? We can add it to the documentation 
as an example, but only as an example, because people may want to use other 
tools as well.


was (Author: artem budnikov):
[~NIzhikov]

I use JDK 1.8.0_181, the error I've got is: "Invalid AES key length: 1218 
bytes" , although I know the key length is 2048 bit.

Also, I managed to start Ignite with a different key, which I got from someone 
who already tested TDE, and it worked. So I think my JDK is ok, but the key 
isn't right.

What is the right command to generate a key? We can add it to the documentation 
as an example, because people may want to use other tools as well.

> TDE - Phase-1. Documentation
> 
>
> Key: IGNITE-8871
> URL: https://issues.apache.org/jira/browse/IGNITE-8871
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 2.5
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: documentation
> Fix For: 2.7
>
>
> TDE feature should be documented.



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

[jira] [Commented] (IGNITE-10125) [TC Bot] Uniform style for buttons

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-10125:
-

zzzadruga opened a new pull request #58: IGNITE-10125 Uniform style for buttons
URL: https://github.com/apache/ignite-teamcity-bot/pull/58
 
 
   Uniform style for buttons: "Inspect" from PR selection, "Show graph" from 
Master Trends, "More >>" from PR Failures


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> [TC Bot] Uniform style for buttons
> --
>
> Key: IGNITE-10125
> URL: https://issues.apache.org/jira/browse/IGNITE-10125
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Attachments: image-2018-11-02-12-06-59-734.png
>
>
> Uniform style for buttons: "Inspect" from [PR 
> selection|https://mtcga.gridgain.com/prs.html], "Show graph" from [Master 
> Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR 
> Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest]
>  
> !image-2018-11-02-12-06-59-734.png! 



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

[jira] [Comment Edited] (IGNITE-8871) TDE - Phase-1. Documentation

[Artem Budnikov (JIRA)]

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

Artem Budnikov edited comment on IGNITE-8871 at 11/2/18 2:21 PM:
-

[~NIzhikov]

I use JDK 1.8.0_181, the error I've got is: "Invalid AES key length: 1218 
bytes" , although I know the key length is 2048 bit.

Also, I managed to start Ignite with a different key, which I got from someone 
who already tested TDE, and it worked. So I think my JDK is ok, but the key 
isn't right.

What is the right command to generate a key? We can add it to the documentation 
as an example, because people may want to use other tools as well.


was (Author: artem budnikov):
[~NIzhikov]

I use JDK 1.8.0_181, the error I've got is: "Invalid AES key length: 1218 
bytes" , although I know the key length is 2048 bit.

Also, I managed to start Ignite with a different key, which I got from someone 
who already tested TDE, and it worked. So it think my JDK is ok, but the key 
isn't right.

What is the right command to generate a key? We can add it to the documentation 
as an example, because people may want to use other tools as well.

> TDE - Phase-1. Documentation
> 
>
> Key: IGNITE-8871
> URL: https://issues.apache.org/jira/browse/IGNITE-8871
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 2.5
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: documentation
> Fix For: 2.7
>
>
> TDE feature should be documented.



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

[jira] [Commented] (IGNITE-8871) TDE - Phase-1. Documentation

[Artem Budnikov (JIRA)]

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

Artem Budnikov commented on IGNITE-8871:


[~NIzhikov]

I use JDK 1.8.0_181, the error I've got is: "Invalid AES key length: 1218 
bytes" , although I know the key length is 2048 bit.

Also, I managed to start Ignite with a different key, which I got from someone 
who already tested TDE, and it worked. So it think my JDK is ok, but the key 
isn't right.

What is the right command to generate a key? We can add it to the documentation 
as an example, because people may want to use other tools as well.

> TDE - Phase-1. Documentation
> 
>
> Key: IGNITE-8871
> URL: https://issues.apache.org/jira/browse/IGNITE-8871
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 2.5
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: documentation
> Fix For: 2.7
>
>
> TDE feature should be documented.



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

[jira] [Created] (IGNITE-10132) TC: the thin client suites (PHP, nodejs etc) must contains log of the Ignite node

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-10132:
-

 Summary: TC: the thin client suites (PHP, nodejs etc) must 
contains log of the Ignite node
 Key: IGNITE-10132
 URL: https://issues.apache.org/jira/browse/IGNITE-10132
 Project: Ignite
  Issue Type: Task
  Components: thin client
Reporter: Taras Ledkov
Assignee: Peter Ivanov


It will be great to add the Ignite node's log to a build artifact for thin 
clients tests suites.
It makes troubleshooting easier.
If there is another way to publish node's log that is more convenient please 
use it (I know nothing about it).

Test suites:
- Thin client: Node.js;
- Thin client: PHP;
- Thin client: Python.




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

[jira] [Commented] (IGNITE-10109) MVCC TX: data become inconsistent after several updates

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-10109:
-

GitHub user gvvinblade opened a pull request:

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

IGNITE-10109 MVCC TX: data become inconsistent after several updates



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

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

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

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


commit bc9d4dbe96bc9de3cf80aaa58a3be8536aed66d5
Author: Igor Seliverstov 
Date:   2018-11-02T14:05:59Z

IGNITE-10109 fixed wrong keys postprocessing on backup nodes




> MVCC TX: data become inconsistent after several updates
> ---
>
> Key: IGNITE-10109
> URL: https://issues.apache.org/jira/browse/IGNITE-10109
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, mvcc
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.7
>
>
> see [TC test 
> history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4365543959682167276=testDetails]
> Here we do concurrent updates on several accounts (update their balances 
> incrementing one and decrementing another), we expect consistent sum of all 
> accounts at any time.
> The sum become inconsistent after while.



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

[jira] [Updated] (IGNITE-10109) MVCC TX: data become inconsistent after several updates

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov updated IGNITE-10109:
--
Component/s: cache

> MVCC TX: data become inconsistent after several updates
> ---
>
> Key: IGNITE-10109
> URL: https://issues.apache.org/jira/browse/IGNITE-10109
> Project: Ignite
>  Issue Type: Bug
>  Components: cache, mvcc
>Reporter: Igor Seliverstov
>Assignee: Igor Seliverstov
>Priority: Major
> Fix For: 2.7
>
>
> see [TC test 
> history|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=4365543959682167276=testDetails]
> Here we do concurrent updates on several accounts (update their balances 
> incrementing one and decrementing another), we expect consistent sum of all 
> accounts at any time.
> The sum become inconsistent after while.



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

[jira] [Updated] (IGNITE-10131) Wrong processing of loaded from store keys on backup nodes.

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov updated IGNITE-10131:
--
Ignite Flags:   (was: Docs Required)

> Wrong processing of loaded from store keys on backup nodes.
> ---
>
> Key: IGNITE-10131
> URL: https://issues.apache.org/jira/browse/IGNITE-10131
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Igor Seliverstov
>Priority: Major
>
> In scope of IGNITE-7086 was added a closure, which puts a key value pair in 
> case the node is a local backup and readThrough is enabled and the key is 
> absent on the node (in other words the key was read from store on a primary 
> node).
> Currently this closure post-processes each call even in case 3rd party 
> persistence store is disabled for the cache because readThrough flag is 
> obtained by inversion of skipStore flag of operation context (which is false 
> by default).
> see {{CU.createBackupPostProcessingClosure(..)}} for details



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

[jira] [Created] (IGNITE-10131) Wrong processing of loaded from store keys on backup nodes.

[Igor Seliverstov (JIRA)]

Igor Seliverstov created IGNITE-10131:
-

 Summary: Wrong processing of loaded from store keys on backup 
nodes.
 Key: IGNITE-10131
 URL: https://issues.apache.org/jira/browse/IGNITE-10131
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Igor Seliverstov


In scope of IGNITE-7086 was added a closure, which puts a key value pair in 
case the node is a local backup and readThrough is enabled and the key is 
absent on the node (in other words the key was read from store on a primary 
node).

Currently this closure post-processes each call even in case 3rd party 
persistence store is disabled for the cache because readThrough flag is 
obtained by inversion of skipStore flag of operation context (which is false by 
default).

see {{CU.createBackupPostProcessingClosure(..)}} for details



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

[jira] [Comment Edited] (IGNITE-9858) [Test Failed] SystemCacheNotConfiguredTest#test flaky fails on TC (timeout).

[Pavel Pereslegin (JIRA)]

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

Pavel Pereslegin edited comment on IGNITE-9858 at 11/2/18 1:51 PM:
---

Hello [~agoncharuk].
I implemented workaround for option 3. Without changing TcpDiscoveryIpFinder 
API - empty addresses list indicates that we're initializing client node.
I didn't change API, because I think it may affect compatibility, but it seems 
the better way is to add boolean flag to the  
{{TcpDiscoveryIpFinder#initializeLocalAddresses}} method.

If we merge this workaround I can create ticket for change API in 3.0.

What do you think?


was (Author: xtern):
Hello [~agoncharuk].
I tested the ability to disable the check in 
{{TcpDiscoveryIpFinderAdapter#initializeLocalAddresses}} (option 2) - it's not 
correct option, since we have clients with forceServerMode.
So, I implemented workaround for option 3. Without changing 
TcpDiscoveryIpFinder API - empty addresses list indicates that we're 
initializing client node.
I didn't change API, because I think it may affect compatibility, but it seems 
the better way is to add boolean flag to the  
{{TcpDiscoveryIpFinder#initializeLocalAddresses}} method.

If we merge this workaround I can create ticket for change API in 3.0.

What do you think?

> [Test Failed] SystemCacheNotConfiguredTest#test flaky fails on TC (timeout).
> 
>
> Key: IGNITE-9858
> URL: https://issues.apache.org/jira/browse/IGNITE-9858
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> SystemCacheNotConfiguredTest hangs sometimes on TeamCity (timeout).
> Example of such failures on master branch: 
> [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8==testDetails=-2762467041583095183=TEST_STATUS_DESC=50_IgniteTests24Java8=%3Cdefault%3E]
> When we using ip finder in shared mode each node should register self address 
> (except clients, obviously).
> Check that the node is a client uses installed (via DI 
> @IgniteInstanceResource) Ignite instance (see 
> {{TcpDiscoveryIpFinderAdapter#initializeLocalAddresses}}).
> So when client and server starts simultaneously, the following scenario is 
> possible - Ignite server injected at first, then the Ignite client injected 
> when the SPI is initialized ({{spiStart}}) both nodes assume that the local 
> node is a client and don't register local address.
> {noformat}
> [2018-10-11 18:03:49,794][WARN 
> ][tcp-client-disco-msg-worker-#57%client%][TcpDiscoverySpi] IP finder 
> returned empty addresses list. Please check IP finder configuration. Will 
> retry every 2000 ms. Change 'reconnectDelay' to configure the frequency of 
> retries.{noformat}



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

[jira] [Commented] (IGNITE-9897) Quering with PDO returns null for all column values except the 1st one

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-9897:
-

Ok, it seems that root cause is the same as in IGNITE-7362 - PDO sets 
{{SQL_ATTR_ODBC_CURSORS}} connection attribute to {{SQL_CUR_USE_IF_NEEDED}}, 
except that unixODBC decides to use cursor library if the {{SQL_CA1_ABSOLUTE}} 
flag of {{SQL_STATIC_CURSOR_ATTRIBUTES1}} attribute is not set.

So, the current fix is to add {{SQL_CA1_ABSOLUTE}} flag for 
{{SQL_STATIC_CURSOR_ATTRIBUTES1}} driver info.

> Quering with PDO returns null for all column values except the 1st one
> --
>
> Key: IGNITE-9897
> URL: https://issues.apache.org/jira/browse/IGNITE-9897
> Project: Ignite
>  Issue Type: Bug
>  Components: odbc
>Affects Versions: 2.6
> Environment: CentOS
>Reporter: Roman Shtykh
>Assignee: Igor Sapego
>Priority: Major
> Attachments: odbc.log, phpPDO2.out, phpPdo.out, unixOdbc.log
>
>
> Using _odbc_connect_ returns all column values, but with _PDO_ only the 1st 
> one – all the rest are null.
>  Reproduced on CentOS.
>  # Start a server node with Ignite CPP
>  # Run odbc-example (which will create two tables)
>  # Run a simple PHP script
> {code:php}
>  try {
> echo PHP_EOL,PHP_EOL,"# Using PDO",PHP_EOL;
> $dbh = new PDO('odbc:ApacheIgnite');
> $dbh->setAttribute(PDO::ATTR_ERRMODE, PDO::ERRMODE_EXCEPTION);
> $sql = 'SELECT * FROM "Person".Person';
> $data = $dbh->query($sql);
> foreach($data as $row) {
> var_export($row);
>   }
> echo PHP_EOL,PHP_EOL,"# Using odbc_*( ) Functions",PHP_EOL;
>   
> $conn = odbc_connect('ApacheIgnite','','');
> $rs = odbc_exec($conn, $sql);
>   
> while($row = odbc_fetch_array($rs)) {
> var_export($row);
>   }
> 
> } catch (PDOException $e) {
> print "Error!: " . $e->getMessage() . "\n";
> die();
> }
> ?>
> {code}
>  



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

[jira] [Commented] (IGNITE-9165) FindBugs: Methods may fail to close stream in core module

[PetrovMikhail (JIRA)]

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

PetrovMikhail commented on IGNITE-9165:
---

{panel:title=Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Platform .NET (Long Running){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199976]]
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* exe: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* exe: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.

{color:#d04437}Platform .NET (Core Linux){color} [[tests 
4|https://ci.ignite.apache.org/viewLog.html?buildId=2199974]]
* dll: CacheQueriesTest.TestSqlFieldsQueryTimeout - 0,0% fails in last 100 
master runs.
* dll: CacheQueriesTest.TestSqlQueryTimeout - 0,0% fails in last 100 master 
runs.
* dll: CacheQueriesTestSimpleName.TestSqlFieldsQueryTimeout - 0,0% fails in 
last 100 master runs.
* dll: CacheQueriesTestSimpleName.TestSqlQueryTimeout - 0,0% fails in last 100 
master runs.

{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2067910buildTypeId=IgniteTests24Java8_RunAll]

> FindBugs: Methods may fail to close stream in core module
> -
>
> Key: IGNITE-9165
> URL: https://issues.apache.org/jira/browse/IGNITE-9165
> Project: Ignite
>  Issue Type: Bug
>  Components: binary
>Affects Versions: 2.6
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
> Attachments: 
> findbugs-result-apache-ignite[ignite-core]_2018_08_02_12_38_02.html
>
>
> The method creates an IO stream object, does not assign it to any fields, 
> pass it to other methods that might close it, or return it, and does not 
> appear to close the stream on all paths out of the method.  This may result 
> in a file descriptor leak.
> Example:
>  
> {code:java}
> // GridCacheAbstractLoadTest#GridCacheAbstractLoadTest()
> try {
>  props.load(new FileReader(GridTestUtils.resolveIgnitePath(
>  "modules/tests/config/cache-load.properties")));
> }
> catch (IOException e) {
>  throw new RuntimeException(e);
> }{code}
>  
>  One of possible solutions:
> {code:java}
> try (Reader reader = new FileReader(GridTestUtils.resolveIgnitePath(
> "modules/tests/config/cache-load.properties"))) {
> props.load(reader);
> }
> catch (IOException e) {
> throw new RuntimeException(e);
> }{code}
> List of classes in "core" module:
>   
>  +org.apache.ignite.internal:+   
>  * *BinaryContext*#classesInPackage(String)
>  * *GridClientJdkMarshaller*#marshal(Object, int)
>  * 
> *IgniteExplicitImplicitDeploymentSelfTest*$GridDeploymentResourceTestJob#execute()
>  * *OptimizedObjectStreamSelfTest*#testReadLine()
>  * *PageIdDistributionTest*#_testRealHistory()
>  * *HttpIgniteUpdatesChecker*#getUpdates(boolean)
>  * *IpcSharedMemoryNativeLoaderSelfTest*#readStreams(Process)
> +org.apache.ignite:+
>  * *GridCacheAbstractLoadTest*#GridCacheAbstractLoadTest()
>  * *GridTestUtils*.sslContext()



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

[jira] [Commented] (IGNITE-10052) Restart node during TX causes vacuum error.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-10052:
-

GitHub user AMashenkov opened a pull request:

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

IGNITE-10052: Restart node during TX causes vacuum error.



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

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

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

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


commit 363b5707b21a4d07d4b45845ffe3172fd8335c05
Author: Andrey V. Mashenkov 
Date:   2018-10-31T15:29:30Z

IGNITE-10052: Introduce MvccDataRecord - WAL record for mvcc entries.

commit 0f1de5bc46d4ca9ccd1e34b6c0e1104f3d1a21d9
Author: Andrey V. Mashenkov 
Date:   2018-11-01T10:09:03Z

IGNITE-10052: Introduce MvccDataRecord - WAL record for mvcc entries.

commit 7ddbe1375cfad152712da9a1a5b073c52a082332
Author: Andrey V. Mashenkov 
Date:   2018-11-01T10:13:51Z

IGNITE-10052: Fix orphan rows handling.

Grid restart case:
Treat rows created by unknown (non-active and non-finished) TX with on old 
coordinator version as aborted TX.

Backup node restart case:
Treat non-primary rows created by unknown (non-active and non-finished) TX 
with older version, but same coordinator as aborted TX.

commit c6928c32c80ea52cd68c76c29cceef585b8ed048
Author: Andrey V. Mashenkov 
Date:   2018-11-01T17:38:50Z

IGNITE-10052: Fix rebalanced entries.

commit f826a1db1919c634707dc64375510e008962e46f
Author: Andrey V. Mashenkov 
Date:   2018-11-01T17:38:50Z

IGNITE-10052: Fix rebalanced entries.

commit dbdc280e9414e2ea33f73f904239738bb4e713ce
Author: Andrey V. Mashenkov 
Date:   2018-11-01T17:53:13Z

Merge remote-tracking branch 'origin/ignite-10052' into ignite-10052

commit 862093ab1b5e640abdcd59649b3b52efb70cb466
Author: Andrey V. Mashenkov 
Date:   2018-11-02T09:11:01Z

IGNITE-10052: Fix rebalanced entries.

commit 8007faa41c2db083470a547d28aed5be0bce4b70
Author: Andrey V. Mashenkov 
Date:   2018-11-02T11:26:32Z

IGNITE-10052: Fix recovery from WAL.




> Restart node during TX causes vacuum error.
> ---
>
> Key: IGNITE-10052
> URL: https://issues.apache.org/jira/browse/IGNITE-10052
> Project: Ignite
>  Issue Type: Bug
>  Components: mvcc
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Andrew Mashenkov
>Priority: Blocker
> Fix For: 2.7
>
>
> 1. Start 2 nodes with PDS, activate , start {{sqlline}}
> 2. Create table
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> create table t1 (a int, b int, primary 
> key(a)) with "atomicity=TRANSACTIONAL_SNAPSHOT,
> backups=1";
> No rows affected (0,294 seconds)
> {noformat}
> 3. Open TX:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> begin;
> No rows affected (0,007 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> insert into t1 values (1,1);
> 1 row affected (0,112 seconds)
> {noformat}
> 4. Stop and then start 2nd node
> 5. Rollback TX and check the table data (no rows added):
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> rollback;
> No rows affected (0,011 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> select * from t1;
> +++
> |   A|   B|
> +++
> +++
> No rows selected (0,067 seconds)
> {noformat}
> 6. Start second TX that throws the exception:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> begin;
> No rows affected (0,001 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> insert into t1 values (1,1);
> Error: Failed to run update. Runtime failure on bounds: 
> [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []] (state=50
> 000,code=1)
> java.sql.SQLException: Failed to run update. Runtime failure on bounds: 
> [lower=MvccMaxSearchRow [], upper=MvccMinSearchR
> ow []]
> at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> 

[jira] [Updated] (IGNITE-10052) Restart node during TX causes vacuum error.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-10052:
--
Summary: Restart node during TX causes vacuum error.  (was: Restart node 
during TX causes vacuum error)

> Restart node during TX causes vacuum error.
> ---
>
> Key: IGNITE-10052
> URL: https://issues.apache.org/jira/browse/IGNITE-10052
> Project: Ignite
>  Issue Type: Bug
>  Components: mvcc
>Affects Versions: 2.7
>Reporter: Sergey Kozlov
>Assignee: Andrew Mashenkov
>Priority: Blocker
> Fix For: 2.7
>
>
> 1. Start 2 nodes with PDS, activate , start {{sqlline}}
> 2. Create table
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> create table t1 (a int, b int, primary 
> key(a)) with "atomicity=TRANSACTIONAL_SNAPSHOT,
> backups=1";
> No rows affected (0,294 seconds)
> {noformat}
> 3. Open TX:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> begin;
> No rows affected (0,007 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> insert into t1 values (1,1);
> 1 row affected (0,112 seconds)
> {noformat}
> 4. Stop and then start 2nd node
> 5. Rollback TX and check the table data (no rows added):
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> rollback;
> No rows affected (0,011 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> select * from t1;
> +++
> |   A|   B|
> +++
> +++
> No rows selected (0,067 seconds)
> {noformat}
> 6. Start second TX that throws the exception:
> {noformat}
> 0: jdbc:ignite:thin://127.0.0.1/> begin;
> No rows affected (0,001 seconds)
> 0: jdbc:ignite:thin://127.0.0.1/> insert into t1 values (1,1);
> Error: Failed to run update. Runtime failure on bounds: 
> [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []] (state=50
> 000,code=1)
> java.sql.SQLException: Failed to run update. Runtime failure on bounds: 
> [lower=MvccMaxSearchRow [], upper=MvccMinSearchR
> ow []]
> at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at 
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1/>
> {noformat}
> The server nodes print out:
> {noformat}
> [18:46:32,136][SEVERE][jdbc-request-handler-worker-#62][DmlStatementsProcessor]
>  Error during update [localNodeId=319a2fda-1315-4bdf-8647-7ddee2d3342e]
> class org.apache.ignite.IgniteCheckedException: Runtime failure on bounds: 
> [lower=MvccMaxSearchRow [], upper=MvccMinSearchRow []]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.visit(BPlusTree.java:1061)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:1919)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.mvccUpdate(GridCacheOffheapManager.java:1840)
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.mvccUpdate(IgniteCacheOffheapManagerImpl.java:530)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.mvccSet(GridCacheMapEntry.java:1104)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.continueLoop(GridDhtTxAbstractEnlistFuture.java:460)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTxAbstractEnlistFuture.init(GridDhtTxAbstractEnlistFuture.java:368)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.processNearTxQueryResultsEnlistRequest(GridDhtTransactionalCacheAdapter.java:2000)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter.access$700(GridDhtTransactionalCacheAdapter.java:112)
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtTransactionalCacheAdapter$12.apply(GridDhtTransactionalCacheAdapter.java:215)
>   at 
> 

[jira] [Commented] (IGNITE-8871) TDE - Phase-1. Documentation

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-8871:
-

[~Artem Budnikov]

I think it's a known JDK issue.

Please, take a look into thread - 
http://apache-ignite-developers.2346864.n4.nabble.com/How-to-run-TDE-tests-locally-td37164.html

I think we should add this to the documentation page.
Can you do it?)

We should add to the documentation commands to generate valid JKS file, also.

> TDE - Phase-1. Documentation
> 
>
> Key: IGNITE-8871
> URL: https://issues.apache.org/jira/browse/IGNITE-8871
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 2.5
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: documentation
> Fix For: 2.7
>
>
> TDE feature should be documented.



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

[jira] [Resolved] (IGNITE-5689) IgniteCommunicationBalanceTest hangs on Windows

[Semen Boikov (JIRA)]

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

Semen Boikov resolved IGNITE-5689.
--
Resolution: Cannot Reproduce
  Assignee: (was: Semen Boikov)

Was not able to reproduce it (on Teamcity and locally).

> IgniteCommunicationBalanceTest hangs on Windows
> ---
>
> Key: IGNITE-5689
> URL: https://issues.apache.org/jira/browse/IGNITE-5689
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, test-fail
>
> Test runner is waiting for ComputeTask to finish:
> {noformat}
> "test-runner-#40602%communication.IgniteCommunicationBalanceMultipleConnectionsTest%"
>  prio=6 tid=0x766d6000 nid=0x7934 waiting on condition 
> [0xeacfe000]
>java.lang.Thread.State: WAITING (parking)
>   at sun.misc.Unsafe.park(Native Method)
>   at java.util.concurrent.locks.LockSupport.park(LockSupport.java:315)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:176)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:139)
>   at 
> org.apache.ignite.internal.AsyncSupportAdapter.saveOrGet(AsyncSupportAdapter.java:112)
>   at 
> org.apache.ignite.internal.IgniteComputeImpl.call(IgniteComputeImpl.java:785)
>   at 
> org.apache.ignite.internal.managers.communication.IgniteCommunicationBalanceTest$1.apply(IgniteCommunicationBalanceTest.java:158)
>   at 
> org.apache.ignite.testframework.GridTestUtils.waitForCondition(GridTestUtils.java:1603)
>   at 
> org.apache.ignite.internal.managers.communication.IgniteCommunicationBalanceTest.testBalance1(IgniteCommunicationBalanceTest.java:148)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:606)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:1997)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1912)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> While thread that tried to send job result got stuck in 
> IgniteUtils.reachable(...):
> {noformat}
> "pub-#40657%communication.IgniteCommunicationBalanceMultipleConnectionsTest5%"
>  prio=6 tid=0x11b8 nid=0x3868 runnable [0xeecfe000]
>java.lang.Thread.State: RUNNABLE
>   at java.net.Inet4AddressImpl.isReachable0(Native Method)
>   at java.net.Inet4AddressImpl.isReachable(Inet4AddressImpl.java:70)
>   at java.net.InetAddress.isReachable(InetAddress.java:475)
>   at java.net.InetAddress.isReachable(InetAddress.java:434)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.reachable(IgniteUtils.java:2113)
>   at 
> org.apache.ignite.internal.util.IgniteUtils.filterReachable(IgniteUtils.java:1877)
>   at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createTcpClient(TcpCommunicationSpi.java:2955)
>   at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.createNioClient(TcpCommunicationSpi.java:2763)
>   at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.reserveClient(TcpCommunicationSpi.java:2655)
>   at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage0(TcpCommunicationSpi.java:2516)
>   at 
> org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi.sendMessage(TcpCommunicationSpi.java:2480)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.send(GridIoManager.java:1643)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.sendToGridTopic(GridIoManager.java:1715)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:928)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.finishJob(GridJobWorker.java:773)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:625)
>   at 
> org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:489)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at 
> org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1181)
>   at 
> 

[jira] [Commented] (IGNITE-8871) TDE - Phase-1. Documentation

[Artem Budnikov (JIRA)]

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

Artem Budnikov commented on IGNITE-8871:


[~NIzhikov] 

Thank you for the response. With regard to master key requirements: I mean, are 
there any requirements to the algorithm or key size? I generated a key using 
keytool but got an error trying to launch a node (something about invalid key 
size).

> TDE - Phase-1. Documentation
> 
>
> Key: IGNITE-8871
> URL: https://issues.apache.org/jira/browse/IGNITE-8871
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 2.5
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: documentation
> Fix For: 2.7
>
>
> TDE feature should be documented.



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

[jira] [Commented] (IGNITE-8871) TDE - Phase-1. Documentation

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-8871:
-

Hello, [~Artem Budnikov]

> 0) Are there any requirements for the master encryption key? 

It must be the same on all nodes in the same cluster.
It must have name provided in config.

> 1) Do I get it right that Cache Encryption Key is generated when the cache is 
> started the first time and then stored in an encrypted form in a system cache?

Cache Encryption Key generated with the key generation request(a bit earlier 
then actual cache creation).
Yes, Cache encryption key is stored in MetaStor.

> 2) Is SSL connection between node required for TDE to work or will it work 
> without it? I tried to start a cluster without SSL configured and it launched 
> just fine. 

Not required.

> 3) You have this phrase in the wiki: "MEK must be decrypted by an 
> administrator during cluster activation."  What actions are required from the 
> administrator? 

Sorry, this definition is out of date. 
Password to open keystore is provided in config file.
No other actions required to start nodes and activate cluster.

> 4) Similarly, "Administrator sends the password via SSL for MEK decryption to 
> any server node." What does the administrator need to do to send the 
> password? 

Sorry, this definition is out of date.

> 5) Is the master key exchanged between the nodes?

No. 
Joining node sends local master key *hash* that is compared with other nodes 
master key hashes.
If hashes are not equal - joining node rejected.


> TDE - Phase-1. Documentation
> 
>
> Key: IGNITE-8871
> URL: https://issues.apache.org/jira/browse/IGNITE-8871
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 2.5
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: documentation
> Fix For: 2.7
>
>
> TDE feature should be documented.



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

[jira] [Commented] (IGNITE-10080) IgniteCacheTestSuite6 (Cache 6) contains some long-running tests that should be optimized.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-10080:
-

GitHub user xtern opened a pull request:

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

IGNITE-10080



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

$ git pull https://github.com/xtern/ignite IGNITE-10080

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

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


commit 3f4d7a2cd76042f7562de2f902575dbd5337d5f9
Author: pereslegin-pa 
Date:   2018-10-31T09:20:23Z

IGNITE-10080 TxOptimisticPrepareOnUnstableTopologyTest decrese startup 
delay.

commit 716d8a85290e59abf4853eadab6e270e7cec2879
Author: pereslegin-pa 
Date:   2018-10-31T09:21:30Z

IGNITE-10080 CacheExchangeMergeTest#concurrentStart decrese iterations 
count.

commit e054cfd263082c5bd65a48cd53923e99dc7a7761
Author: pereslegin-pa 
Date:   2018-11-02T12:04:45Z

IGNITE-10080 Suspend/resume test optimization

commit ae3605b59f2a29bc38209ae43d7766b94a276b01
Author: pereslegin-pa 
Date:   2018-11-02T12:43:02Z

IGNITE-10080 TxRollbackAsyncTest decrese tx count.

commit 497e1fe1322aba20b62d0711205fd1d128a0c4f2
Author: pereslegin-pa 
Date:   2018-11-02T12:51:23Z

IGNITE-10080 Codestyle.




> IgniteCacheTestSuite6 (Cache 6) contains some long-running tests that should 
> be optimized.
> --
>
> Key: IGNITE-10080
> URL: https://issues.apache.org/jira/browse/IGNITE-10080
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Pavel Pereslegin
>Assignee: Pavel Pereslegin
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> We found that these tests take too long to complete and need to be optimized:
> {noformat}
> TxOptimisticPrepareOnUnstableTopologyTest.testPrepareOnUnstableTopology
> IgniteOptimisticTxSuspendResumeMultiServerTest.testSuspendTxAndResumeAfterTopologyChange
> TxRollbackAsyncTest.testSynchronousRollback
> TxRollbackAsyncNearCacheTest.testSynchronousRollback
> CacheExchangeMergeTest.testConcurrentStartServersAndClients
> CacheExchangeMergeTest.testConcurrentStartServers
> {noformat}



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

[jira] [Resolved] (IGNITE-10120) Create docker images for Web Console Frontend & Backend

[Peter Ivanov (JIRA)]

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

Peter Ivanov resolved IGNITE-10120.
---
Resolution: Done

Images are built and uploaded to apacheignite Docker Hub

> Create docker images for Web Console Frontend & Backend
> ---
>
> Key: IGNITE-10120
> URL: https://issues.apache.org/jira/browse/IGNITE-10120
> Project: Ignite
>  Issue Type: Task
>Reporter: Yuriy Sergeev
>Assignee: Peter Ivanov
>Priority: Major
>
> Add docker images 2.6.0:
> [https://hub.docker.com/r/apacheignite/web-console-frontend/tags/]
> [https://hub.docker.com/r/apacheignite/web-console-backend/tags/]
> Thx



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

[jira] [Commented] (IGNITE-7582) Document 'No Archiver' WAL mode

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7582:


[~Artem Budnikov], thank you, this section looks good. Could you re-assign 
issue to you and resolve it?

> Document 'No Archiver' WAL mode
> ---
>
> Key: IGNITE-7582
> URL: https://issues.apache.org/jira/browse/IGNITE-7582
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.7
>
>
> Document new 'no archiver' WAL mode activated if WAL Path & WAL Archive Path 
> set to same value.
> Supported under [IGNITE-7017]
> In this mode all WAL segment files are placed in that folder with absolute 
> index in file name. In that case archiver is not activated.
> Configuration example:
> {noformat}
> DataStorageConfiguration dsCfg = new DataStorageConfiguration();
> DataRegionConfiguration regCfg = new DataRegionConfiguration();
> regCfg.setPersistenceEnabled(true);
> dsCfg.setDefaultDataRegionConfiguration(regCfg);
> dsCfg.setWalPath(walAbsPath);
> dsCfg.setWalArchivePath(walAbsPath);
> {noformat}



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

[jira] [Created] (IGNITE-10130) Add option to API for disable triggering cache interceptor.

[Sergey Antonov (JIRA)]

Sergey Antonov created IGNITE-10130:
---

 Summary: Add option to API for disable triggering cache 
interceptor.
 Key: IGNITE-10130
 URL: https://issues.apache.org/jira/browse/IGNITE-10130
 Project: Ignite
  Issue Type: Improvement
Reporter: Sergey Antonov
Assignee: Sergey Antonov






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

[jira] [Updated] (IGNITE-9547) Document DML operations prohibited inside transaction

[Yury Gerzhedovich (JIRA)]

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

Yury Gerzhedovich updated IGNITE-9547:
--
Fix Version/s: (was: 2.7)
   2.8

> Document DML operations prohibited inside transaction
> -
>
> Key: IGNITE-9547
> URL: https://issues.apache.org/jira/browse/IGNITE-9547
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, sql
>Reporter: Yury Gerzhedovich
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.8
>
>
> Docs says:
> ""Presently, DML supports the atomic mode only meaning that if there is a DML 
> query that is executed as a part of an Ignite transaction then it will not be 
> enlisted in the transaction's writing queue and will be executed right away""
> However it's wrong.
> We need to document that now any DML operations is prohibited and throw 
> Exception in case it will be executed inside a transaction.
>  
> Also appeared new boolean property IGNITE_ALLOW_DML_INSIDE_TRANSACTION. it is 
> necessary to emulate the old behavior. In case value is true then DML 
> operation is allowed, but it be applied only after transaction will be 
> commited.
> By default value is false.



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

[jira] [Commented] (IGNITE-10129) MVCC TX: do not log Vacuum warnings if mvcc is not enabled

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-10129:
-

GitHub user rkondakov opened a pull request:

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

IGNITE-10129: Disable Vacuum warnings if mvcc is not enabled.



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

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

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

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


commit 25a8625438204bccf988ed1e3f39ee54c3c164c1
Author: rkondakov 
Date:   2018-11-02T12:09:48Z

IGNITE-10129: Disable Vacuum warnings if mvcc is not enabled.




> MVCC TX: do not log Vacuum warnings if mvcc is not enabled
> --
>
> Key: IGNITE-10129
> URL: https://issues.apache.org/jira/browse/IGNITE-10129
> Project: Ignite
>  Issue Type: Bug
>  Components: mvcc
>Reporter: Igor Seliverstov
>Assignee: Roman Kondakov
>Priority: Minor
> Fix For: 2.7
>
>
> currently we can see warnings like : 
> {{[10:18:48,741][INFO][exchange-worker-#64][MvccProcessorImpl] Attempting to 
> stop inactive vacuum.}} on node stop.
> Such warnings should not appear in case MVCC is disabled (there is no MVCC 
> caches).



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

[jira] [Updated] (IGNITE-9525) Ignite + Informatica Integration

[Alexander Gerus (JIRA)]

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

Alexander Gerus updated IGNITE-9525:

Attachment: Ignite_Informatica_Integration.pdf

> Ignite + Informatica Integration
> 
>
> Key: IGNITE-9525
> URL: https://issues.apache.org/jira/browse/IGNITE-9525
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Prachi Garg
>Assignee: Pavel Vinokurov
>Priority: Major
> Fix For: 2.7
>
> Attachments: Ignite_Informatica_Integration.pdf
>
>
> Mentioned in https://cwiki.apache.org/confluence/display/IGNITE/Required+Docs



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

[jira] [Assigned] (IGNITE-10129) MVCC TX: do not log Vacuum warnings if mvcc is not enabled

[Roman Kondakov (JIRA)]

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

Roman Kondakov reassigned IGNITE-10129:
---

Assignee: Roman Kondakov

> MVCC TX: do not log Vacuum warnings if mvcc is not enabled
> --
>
> Key: IGNITE-10129
> URL: https://issues.apache.org/jira/browse/IGNITE-10129
> Project: Ignite
>  Issue Type: Bug
>  Components: mvcc
>Reporter: Igor Seliverstov
>Assignee: Roman Kondakov
>Priority: Minor
> Fix For: 2.7
>
>
> currently we can see warnings like : 
> {{[10:18:48,741][INFO][exchange-worker-#64][MvccProcessorImpl] Attempting to 
> stop inactive vacuum.}} on node stop.
> Such warnings should not appear in case MVCC is disabled (there is no MVCC 
> caches).



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

[jira] [Commented] (IGNITE-10123) Intermittent OOME errors in PDS indexing tests

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-10123:
-

Github user asfgit closed the pull request at:

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


> Intermittent OOME errors in PDS indexing tests
> --
>
> Key: IGNITE-10123
> URL: https://issues.apache.org/jira/browse/IGNITE-10123
> Project: Ignite
>  Issue Type: Test
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Analyzing the heap dump reveals the source of the leak - the massive amount 
> (700MB) of cache events in {{IgniteLogicalRecoveryTest}}. Disabling events 
> should resolve the issue.
> Disabling events by default in all tests should be investigated separately.



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

[jira] [Commented] (IGNITE-8871) TDE - Phase-1. Documentation

[Artem Budnikov (JIRA)]

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

Artem Budnikov commented on IGNITE-8871:


[~NIzhikov] 

I've read the IEP-18 description in Ignite Wiki and have some questions with 
regard to implementation details. Is the page up to date? Could you please 
provide information on the following questions:

0) Are there any requirements for the master encryption key? 
1) Do I get it right that Cache Encryption Key is generated when the cache is 
started the first time and then stored in an encrypted form in a system cache?
2) Is SSL connection between node required for TDE to work or will it work 
without it? I tried to start a cluster without SSL configured and it launched 
just fine. 
3) You have this phrase in the wiki: "MEK must be decrypted by an administrator 
during cluster activation."  What actions are required from the administrator? 
4) Similarly, "Administrator sends the password via SSL for MEK decryption to 
any server node." What does the administrator need to do to send the password? 
5) Is the master key exchanged between the nodes?

> TDE - Phase-1. Documentation
> 
>
> Key: IGNITE-8871
> URL: https://issues.apache.org/jira/browse/IGNITE-8871
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 2.5
>Reporter: Nikolay Izhikov
>Assignee: Artem Budnikov
>Priority: Major
>  Labels: documentation
> Fix For: 2.7
>
>
> TDE feature should be documented.



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

[jira] [Assigned] (IGNITE-8871) TDE - Phase-1. Documentation

[Artem Budnikov (JIRA)]

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

Artem Budnikov reassigned IGNITE-8871:
--

Assignee: Nikolay Izhikov  (was: Artem Budnikov)

> TDE - Phase-1. Documentation
> 
>
> Key: IGNITE-8871
> URL: https://issues.apache.org/jira/browse/IGNITE-8871
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Affects Versions: 2.5
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: documentation
> Fix For: 2.7
>
>
> TDE feature should be documented.



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

[jira] [Commented] (IGNITE-10128) IO race during read\write cache configurations.

[Ivan Daschinskiy (JIRA)]

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

Ivan Daschinskiy commented on IGNITE-10128:
---

[~zstan] idea of moving unnecessary temp files deletion logic to start0 looks 
goot to me. However, let's wait for TC bot visa.

> IO race during read\write cache configurations.
> ---
>
> Key: IGNITE-10128
> URL: https://issues.apache.org/jira/browse/IGNITE-10128
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
>
> During grid usage, found problem below. I tries simultaneously start several 
> nodes and call *activate* on ** each node.
> {code:java}
> [15:38:25,186][INFO][exchange-worker-#63][FileWriteAheadLogManager] Resuming 
> logging to WAL segment 
> [file=/storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/wal/node2/.wal,
>  offset=0, ver=2]
> [15:38:25,210][INFO][exchange-worker-#63][GridSnapshotAwareClusterStateProcessorImpl]
>  Writing BaselineTopology[id=0]
> [15:38:25,225][INFO][exchange-worker-#63][GridCacheDatabaseSharedManager] 
> Resume logging performed in 41 ms.
> [15:38:25,252][INFO][exchange-worker-#63][CacheAffinitySharedManager] 
> Updating caches registry performed in 27 ms.
> [15:38:25,743][SEVERE][sys-#70][] Critical system error detected. Will be 
> handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler 
> [tryStop=false, timeout=0, super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED]]], 
> failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=java.nio.file.NoSuchFileException: 
> /storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp]]
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
> [SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=java.nio.file.NoSuchFileException: 
> /storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp]]
> java.nio.file.NoSuchFileException: 
> /storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp
> at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:409)
> at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.storeCacheData(FilePageStoreManager.java:390)
> at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.lambda$persistCacheConfigurations$4(CachesRegistry.java:303)
> at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6875)
> at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}



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

[jira] [Commented] (IGNITE-10128) IO race during read\write cache configurations.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-10128:
-

Github user zstan closed the pull request at:

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


> IO race during read\write cache configurations.
> ---
>
> Key: IGNITE-10128
> URL: https://issues.apache.org/jira/browse/IGNITE-10128
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
>
> During grid usage, found problem below. I tries simultaneously start several 
> nodes and call *activate* on ** each node.
> {code:java}
> [15:38:25,186][INFO][exchange-worker-#63][FileWriteAheadLogManager] Resuming 
> logging to WAL segment 
> [file=/storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/wal/node2/.wal,
>  offset=0, ver=2]
> [15:38:25,210][INFO][exchange-worker-#63][GridSnapshotAwareClusterStateProcessorImpl]
>  Writing BaselineTopology[id=0]
> [15:38:25,225][INFO][exchange-worker-#63][GridCacheDatabaseSharedManager] 
> Resume logging performed in 41 ms.
> [15:38:25,252][INFO][exchange-worker-#63][CacheAffinitySharedManager] 
> Updating caches registry performed in 27 ms.
> [15:38:25,743][SEVERE][sys-#70][] Critical system error detected. Will be 
> handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler 
> [tryStop=false, timeout=0, super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED]]], 
> failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=java.nio.file.NoSuchFileException: 
> /storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp]]
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
> [SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=java.nio.file.NoSuchFileException: 
> /storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp]]
> java.nio.file.NoSuchFileException: 
> /storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp
> at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:409)
> at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.storeCacheData(FilePageStoreManager.java:390)
> at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.lambda$persistCacheConfigurations$4(CachesRegistry.java:303)
> at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6875)
> at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}



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

[jira] [Resolved] (IGNITE-10084) Cache 5 tests optimization

[Alexey Platonov (JIRA)]

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

Alexey Platonov resolved IGNITE-10084.
--
Resolution: Duplicate

it is duplicate of https://issues.apache.org/jira/browse/IGNITE-10106

> Cache 5 tests optimization
> --
>
> Key: IGNITE-10084
> URL: https://issues.apache.org/jira/browse/IGNITE-10084
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Ivan Bessonov
>Assignee: Alexey Platonov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> We need to investigate how to optimize these tests:
> IgniteCacheStarvationOnRebalanceTest.testLoadSystemWithPutAndStartRebalancing 
> (/)
>  CacheSerializableTransactionsTest.testGetRemoveTxNearCache2
>  CacheSerializableTransactionsTest.testGetRemoveTxNearCache1
>  CacheSerializableTransactionsTest.testRandomOperations
>  CacheSerializableTransactionsTest.testIncrementTxRestart
>  CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockNodeRestart
>  
> CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClientsNodeRestart
>  
> CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockWithNonSerializable
>  CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockGetPut
>  CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlockFromClients
>  CacheSerializableTransactionsTest.testConcurrentUpdateNoDeadlock
> and optimize them.



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

[jira] [Commented] (IGNITE-9406) Improve SQL "Performance and Debugging" page

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-9406:
-

[~Artem Budnikov], we need to better explain partition pruning technique. Let's 
rename the section "Query Execution Flow Optimizations" to "Partition Pruning" 
and translate the text from attached document along with examples.

> Improve SQL "Performance and Debugging" page
> 
>
> Key: IGNITE-9406
> URL: https://issues.apache.org/jira/browse/IGNITE-9406
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Vladimir Ozerov
>Priority: Major
> Fix For: 2.7
>
> Attachments: ignite_sql_perf.txt
>
>
> I prepared a document for one of Ignite clients with some advanced 
> information about how various performance optimizations work in Ignite SQL. 
> Let's compare this document with our "Performance and Debugging" page [1], 
> and enhance the latter with missing info (if any).
> P.S.: Document is attached. Russian language.
> [1] 
> https://apacheignite-sql.readme.io/docs/performance-and-debugging#query-execution-flow-optimizations



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

[jira] [Commented] (IGNITE-10128) IO race during read\write cache configurations.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-10128:
-

GitHub user zstan opened a pull request:

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

IGNITE-10128 Race in read\write cache configurations.



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

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

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

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


commit e21cecdfc0df7651175792b73b8814b8f83ed402
Author: zstan 
Date:   2018-11-02T10:02:55Z

IGNITE-10128 Race in read\write cache configurations.




> IO race during read\write cache configurations.
> ---
>
> Key: IGNITE-10128
> URL: https://issues.apache.org/jira/browse/IGNITE-10128
> Project: Ignite
>  Issue Type: Improvement
>  Components: persistence
>Affects Versions: 2.6
>Reporter: Stanilovsky Evgeny
>Assignee: Stanilovsky Evgeny
>Priority: Major
> Fix For: 2.8
>
>
> During grid usage, found problem below. I tries simultaneously start several 
> nodes and call *activate* on ** each node.
> {code:java}
> [15:38:25,186][INFO][exchange-worker-#63][FileWriteAheadLogManager] Resuming 
> logging to WAL segment 
> [file=/storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/wal/node2/.wal,
>  offset=0, ver=2]
> [15:38:25,210][INFO][exchange-worker-#63][GridSnapshotAwareClusterStateProcessorImpl]
>  Writing BaselineTopology[id=0]
> [15:38:25,225][INFO][exchange-worker-#63][GridCacheDatabaseSharedManager] 
> Resume logging performed in 41 ms.
> [15:38:25,252][INFO][exchange-worker-#63][CacheAffinitySharedManager] 
> Updating caches registry performed in 27 ms.
> [15:38:25,743][SEVERE][sys-#70][] Critical system error detected. Will be 
> handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler 
> [tryStop=false, timeout=0, super=AbstractFailureHandler 
> [ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED]]], 
> failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=java.nio.file.NoSuchFileException: 
> /storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp]]
> Critical system error detected. Will be handled accordingly to configured 
> handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
> [SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext [type=CRITICAL_ERROR, 
> err=java.nio.file.NoSuchFileException: 
> /storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp]]
> java.nio.file.NoSuchFileException: 
> /storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp
> at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
> at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
> at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:409)
> at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
> at java.nio.file.Files.move(Files.java:1395)
> at 
> org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.storeCacheData(FilePageStoreManager.java:390)
> at 
> org.apache.ignite.internal.processors.cache.CachesRegistry.lambda$persistCacheConfigurations$4(CachesRegistry.java:303)
> at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6875)
> at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> {code}



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

[jira] [Assigned] (IGNITE-9406) Improve SQL "Performance and Debugging" page

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-9406:
---

Assignee: Artem Budnikov  (was: Vladimir Ozerov)

> Improve SQL "Performance and Debugging" page
> 
>
> Key: IGNITE-9406
> URL: https://issues.apache.org/jira/browse/IGNITE-9406
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Artem Budnikov
>Priority: Major
> Fix For: 2.7
>
> Attachments: ignite_sql_perf.txt
>
>
> I prepared a document for one of Ignite clients with some advanced 
> information about how various performance optimizations work in Ignite SQL. 
> Let's compare this document with our "Performance and Debugging" page [1], 
> and enhance the latter with missing info (if any).
> P.S.: Document is attached. Russian language.
> [1] 
> https://apacheignite-sql.readme.io/docs/performance-and-debugging#query-execution-flow-optimizations



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

[jira] [Created] (IGNITE-10129) MVCC TX: do not log Vacuum warnings if mvcc is not enabled

[Igor Seliverstov (JIRA)]

Igor Seliverstov created IGNITE-10129:
-

 Summary: MVCC TX: do not log Vacuum warnings if mvcc is not enabled
 Key: IGNITE-10129
 URL: https://issues.apache.org/jira/browse/IGNITE-10129
 Project: Ignite
  Issue Type: Bug
  Components: mvcc
Reporter: Igor Seliverstov
 Fix For: 2.7


currently we can see warnings like : 
{{[10:18:48,741][INFO][exchange-worker-#64][MvccProcessorImpl] Attempting to 
stop inactive vacuum.}} on node stop.

Such warnings should not appear in case MVCC is disabled (there is no MVCC 
caches).



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

[jira] [Created] (IGNITE-10128) IO race during read\write cache configurations.

[Stanilovsky Evgeny (JIRA)]

Stanilovsky Evgeny created IGNITE-10128:
---

 Summary: IO race during read\write cache configurations.
 Key: IGNITE-10128
 URL: https://issues.apache.org/jira/browse/IGNITE-10128
 Project: Ignite
  Issue Type: Improvement
  Components: persistence
Affects Versions: 2.6
Reporter: Stanilovsky Evgeny
Assignee: Stanilovsky Evgeny
 Fix For: 2.8


During grid usage, found problem below. I tries simultaneously start several 
nodes and call *activate* on ** each node.
{code:java}
[15:38:25,186][INFO][exchange-worker-#63][FileWriteAheadLogManager] Resuming 
logging to WAL segment 
[file=/storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/wal/node2/.wal,
 offset=0, ver=2]
[15:38:25,210][INFO][exchange-worker-#63][GridSnapshotAwareClusterStateProcessorImpl]
 Writing BaselineTopology[id=0]
[15:38:25,225][INFO][exchange-worker-#63][GridCacheDatabaseSharedManager] 
Resume logging performed in 41 ms.
[15:38:25,252][INFO][exchange-worker-#63][CacheAffinitySharedManager] Updating 
caches registry performed in 27 ms.
[15:38:25,743][SEVERE][sys-#70][] Critical system error detected. Will be 
handled accordingly to configured handler [hnd=StopNodeOrHaltFailureHandler 
[tryStop=false, timeout=0, super=AbstractFailureHandler 
[ignoredFailureTypes=UnmodifiableSet [SYSTEM_WORKER_BLOCKED]]], 
failureCtx=FailureContext [type=CRITICAL_ERROR, 
err=java.nio.file.NoSuchFileException: 
/storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp]]
Critical system error detected. Will be handled accordingly to configured 
handler [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext [type=CRITICAL_ERROR, 
err=java.nio.file.NoSuchFileException: 
/storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp]]
java.nio.file.NoSuchFileException: 
/storage/ssd/mshonichev/tiden/pme-181030-153724/test_pme_bench/ignite.server.2/work/db/node2/cacheGroup-cache_group_2/cache_group_1_010cache_data.dat.tmp
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:86)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:409)
at sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:262)
at java.nio.file.Files.move(Files.java:1395)
at 
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.storeCacheData(FilePageStoreManager.java:390)
at 
org.apache.ignite.internal.processors.cache.CachesRegistry.lambda$persistCacheConfigurations$4(CachesRegistry.java:303)
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6875)
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$1.body(GridClosureProcessor.java:827)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
{code}



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

[jira] [Commented] (IGNITE-9972) Deleted entries remain in local partition internal map

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-9972:


Github user asfgit closed the pull request at:

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


> Deleted entries remain in local partition internal map
> --
>
> Key: IGNITE-9972
> URL: https://issues.apache.org/jira/browse/IGNITE-9972
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Anton Kurbanov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.8
>
> Attachments: IgniteTxConcurrentRemoveObjectsTest.java
>
>
> Concurrent transactions leave entries in deleted state in local partition map.



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

[jira] [Commented] (IGNITE-9972) Deleted entries remain in local partition internal map

[Ignite TC Bot (JIRA)]

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

Ignite TC Bot commented on IGNITE-9972:
---

{panel:title=No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2202053buildTypeId=IgniteTests24Java8_RunAll]

> Deleted entries remain in local partition internal map
> --
>
> Key: IGNITE-9972
> URL: https://issues.apache.org/jira/browse/IGNITE-9972
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Anton Kurbanov
>Assignee: Ivan Bessonov
>Priority: Major
> Fix For: 2.8
>
> Attachments: IgniteTxConcurrentRemoveObjectsTest.java
>
>
> Concurrent transactions leave entries in deleted state in local partition map.



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

[jira] [Created] (IGNITE-10127) GridCacheRebalancingSyncSelfTest ignores check result

[Ryabov Dmitrii (JIRA)]

Ryabov Dmitrii created IGNITE-10127:
---

 Summary: GridCacheRebalancingSyncSelfTest ignores check result
 Key: IGNITE-10127
 URL: https://issues.apache.org/jira/browse/IGNITE-10127
 Project: Ignite
  Issue Type: Test
Reporter: Ryabov Dmitrii
 Fix For: 2.8


{{checkSupplyContextMapIsEmpty()}} method checks that map is empty, but ignores 
result of this check.

{code:java}
GridTestUtils.waitForCondition(new PA() {
@Override public boolean apply() {
synchronized (map) {
return map.isEmpty();
}
}
}, 15_000);
{code}

We should check that {{waitForCondition()}} returns true to be sure that map is 
cleared.



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

[jira] [Updated] (IGNITE-9539) Add SQL column precision existence check if scale parameter is setted

[PetrovMikhail (JIRA)]

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

PetrovMikhail updated IGNITE-9539:
--
Description: 
We should handle situation when user sets only scale without precision in 
decimal column constraints. According to 
[http://www.h2database.com/html/datatypes.html#decimal_type] it's not valid 
behavior.

Currently, we ignore it.

 

  was:
We should check situation when user sets only scale parameter without precision 
for column, while creating SQL table. According to 
[http://www.h2database.com/html/datatypes.html#decimal_type] it's not valid 
behavior.

Currently, we ignore it.

 


> Add SQL column precision existence check if scale parameter is setted
> -
>
> Key: IGNITE-9539
> URL: https://issues.apache.org/jira/browse/IGNITE-9539
> Project: Ignite
>  Issue Type: Bug
>Reporter: PetrovMikhail
>Assignee: PetrovMikhail
>Priority: Major
>  Labels: sql-engine
>
> We should handle situation when user sets only scale without precision in 
> decimal column constraints. According to 
> [http://www.h2database.com/html/datatypes.html#decimal_type] it's not valid 
> behavior.
> Currently, we ignore it.
>  



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

[jira] [Commented] (IGNITE-8331) SQL: Add Decimal precision and scale constraint

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8331:


Github user asfgit closed the pull request at:

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


> SQL: Add Decimal precision and scale constraint
> ---
>
> Key: IGNITE-8331
> URL: https://issues.apache.org/jira/browse/IGNITE-8331
> Project: Ignite
>  Issue Type: Bug
>Reporter: Nikolay Izhikov
>Assignee: PetrovMikhail
>Priority: Major
>  Labels: sql-engine
>
> We should support DECIMAL(X, Y) syntax. 
> Currently, we ignore it. 
> It affects semantics. 
> E.g., one can insert a DECIMAL with greater precision into a cache/table 
> without any problems. 



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

[jira] [Assigned] (IGNITE-10105) AI 2.7: Prepare release notes

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov reassigned IGNITE-10105:


Assignee: Nikolay Izhikov

> AI 2.7: Prepare release notes
> -
>
> Key: IGNITE-10105
> URL: https://issues.apache.org/jira/browse/IGNITE-10105
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Reporter: Vladimir Ozerov
>Assignee: Nikolay Izhikov
>Priority: Major
> Fix For: 2.7
>
>




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

[jira] [Commented] (IGNITE-8552) Unable to use date as primary key

[Yury Gerzhedovich (JIRA)]

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

Yury Gerzhedovich commented on IGNITE-8552:
---

Now it works only for WRAP_VALUE=false parameter. In case key is wrapped then 
it doesn't work. 

> Unable to use date as primary key
> -
>
> Key: IGNITE-8552
> URL: https://issues.apache.org/jira/browse/IGNITE-8552
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.4
>Reporter: Pavel Vinokurov
>Priority: Blocker
> Fix For: 2.8
>
> Attachments: IGNITE-8552_implemented.patch
>
>
> It' is unable to create cache via ddl:
> create table tab(id date primary key, date_field date);
> Result:
> ERROR CacheAffinitySharedManager - Failed to initialize cache. Will try to 
> rollback cache start routine. [cacheName=SQL_PUBLIC_T3]
> class org.apache.ignite.IgniteCheckedException: Failed to find value class in 
> the node classpath (use default marshaller to enable binary objects) : 
> SQL_PUBLIC_T3_e90848b2_fe30_4adb_a934_6e13ca0eb409
>   at 
> org.apache.ignite.internal.processors.query.QueryUtils.typeForQueryEntity(QueryUtils.java:426)



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

[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-9312:


Github user asfgit closed the pull request at:

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


> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
>  Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
>  Labels: inspections
>
> New `Code Inspections` profile can be found 
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}} 
> annotation regarding this inscpetion profile.



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

[jira] [Comment Edited] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov edited comment on IGNITE-9312 at 11/2/18 9:37 AM:
--

merged to master

[~PetrovMikhail] Thanks for the contribution!


was (Author: nizhikov):
merge to master

[~PetrovMikhail] Thanks for the contribution!

> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
>  Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
>  Labels: inspections
>
> New `Code Inspections` profile can be found 
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}} 
> annotation regarding this inscpetion profile.



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

[jira] [Commented] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov commented on IGNITE-9312:
-

merge to master

[~PetrovMikhail] Thanks for the contribution!

> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
>  Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
>  Labels: inspections
>
> New `Code Inspections` profile can be found 
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}} 
> annotation regarding this inscpetion profile.



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

[jira] [Resolved] (IGNITE-9312) Remove unnecessary @SuppressWarnings annotation

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov resolved IGNITE-9312.
-
Resolution: Fixed

> Remove unnecessary @SuppressWarnings annotation
> ---
>
> Key: IGNITE-9312
> URL: https://issues.apache.org/jira/browse/IGNITE-9312
> Project: Ignite
>  Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: PetrovMikhail
>Priority: Minor
>  Labels: inspections
>
> New `Code Inspections` profile can be found 
> \idea\ignite_inspections.xml.
> We will need to fix all methods with unnecessary {{@SuppressWarnings}} 
> annotation regarding this inscpetion profile.



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

[jira] [Commented] (IGNITE-10101) Web Console: Filed to get cache list on Query page.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-10101:


Successfully tested with nodes: master, 2.5.2, 1.9.14

> Web Console: Filed to get cache list on Query page.
> ---
>
> Key: IGNITE-10101
> URL: https://issues.apache.org/jira/browse/IGNITE-10101
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.8
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
>Priority: Major
> Fix For: 2.8
>
> Attachments: ignite-10101.png
>
>
> On opening of Queries page:
>  # For scan query field with cache selection is empty
>  # For query list of caches is empty.



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

[jira] [Assigned] (IGNITE-10101) Web Console: Filed to get cache list on Query page.

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-10101:
--

Assignee: Andrey Novikov  (was: Vasiliy Sisko)

> Web Console: Filed to get cache list on Query page.
> ---
>
> Key: IGNITE-10101
> URL: https://issues.apache.org/jira/browse/IGNITE-10101
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.8
>Reporter: Vasiliy Sisko
>Assignee: Andrey Novikov
>Priority: Major
> Fix For: 2.8
>
> Attachments: ignite-10101.png
>
>
> On opening of Queries page:
>  # For scan query field with cache selection is empty
>  # For query list of caches is empty.



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

[jira] [Assigned] (IGNITE-10120) Create docker images for Web Console Frontend & Backend

[Peter Ivanov (JIRA)]

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

Peter Ivanov reassigned IGNITE-10120:
-

Assignee: Peter Ivanov

> Create docker images for Web Console Frontend & Backend
> ---
>
> Key: IGNITE-10120
> URL: https://issues.apache.org/jira/browse/IGNITE-10120
> Project: Ignite
>  Issue Type: Task
>Reporter: Yuriy Sergeev
>Assignee: Peter Ivanov
>Priority: Major
>
> Add docker images 2.6.0:
> [https://hub.docker.com/r/apacheignite/web-console-frontend/tags/]
> [https://hub.docker.com/r/apacheignite/web-console-backend/tags/]
> Thx



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

[jira] [Commented] (IGNITE-7582) Document 'No Archiver' WAL mode

[Artem Budnikov (JIRA)]

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

Artem Budnikov commented on IGNITE-7582:


[~dpavlov]

the section is waiting for your review: 

[https://apacheignite.readme.io/docs/write-ahead-log#section-disabling-wal-archiving]

 

> Document 'No Archiver' WAL mode
> ---
>
> Key: IGNITE-7582
> URL: https://issues.apache.org/jira/browse/IGNITE-7582
> Project: Ignite
>  Issue Type: Task
>  Components: documentation, persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.7
>
>
> Document new 'no archiver' WAL mode activated if WAL Path & WAL Archive Path 
> set to same value.
> Supported under [IGNITE-7017]
> In this mode all WAL segment files are placed in that folder with absolute 
> index in file name. In that case archiver is not activated.
> Configuration example:
> {noformat}
> DataStorageConfiguration dsCfg = new DataStorageConfiguration();
> DataRegionConfiguration regCfg = new DataRegionConfiguration();
> regCfg.setPersistenceEnabled(true);
> dsCfg.setDefaultDataRegionConfiguration(regCfg);
> dsCfg.setWalPath(walAbsPath);
> dsCfg.setWalArchivePath(walAbsPath);
> {noformat}



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

[jira] [Commented] (IGNITE-8896) Wrong javadoc for TcpCommunicationSpi.setSlowClientQueueLimit()

[Amelchev Nikita (JIRA)]

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

Amelchev Nikita commented on IGNITE-8896:
-

[~RodionVl], Looks good to me. 
[~dpavlov], Could you help with review and merge?

> Wrong javadoc for TcpCommunicationSpi.setSlowClientQueueLimit()
> ---
>
> Key: IGNITE-8896
> URL: https://issues.apache.org/jira/browse/IGNITE-8896
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Dmitry Karachentsev
>Assignee: Rodion
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
>
> Javadoc for TcpCommunicationSpi.setSlowClientQueueLimit() says that is should 
> be set to value equal to TcpCommunicationSpi.getMessageQueueLimit().
> But this is wrong, because first checks back pressure limit and sender thread 
> will be blocked before slow client check. Also, warning checks the value 
> correctly, but message should be "...greater or equal...":
> {code:java}
> if (slowClientQueueLimit > 0 && msgQueueLimit > 0 && slowClientQueueLimit >= 
> msgQueueLimit) {
> U.quietAndWarn(log, "Slow client queue limit is set to a value 
> greater than message queue limit " +
> "(slow client queue limit will have no effect) 
> [msgQueueLimit=" + msgQueueLimit +
> ", slowClientQueueLimit=" + slowClientQueueLimit + ']');
> }
> {code}



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

[jira] [Commented] (IGNITE-8331) SQL: Add Decimal precision and scale constraint

[Ignite TC Bot (JIRA)]

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

Ignite TC Bot commented on IGNITE-8331:
---

{panel:title=No blockers 
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All 
Results|http://ci.ignite.apache.org/viewLog.html?buildId=2221400buildTypeId=IgniteTests24Java8_RunAll]

> SQL: Add Decimal precision and scale constraint
> ---
>
> Key: IGNITE-8331
> URL: https://issues.apache.org/jira/browse/IGNITE-8331
> Project: Ignite
>  Issue Type: Bug
>Reporter: Nikolay Izhikov
>Assignee: PetrovMikhail
>Priority: Major
>  Labels: sql-engine
>
> We should support DECIMAL(X, Y) syntax. 
> Currently, we ignore it. 
> It affects semantics. 
> E.g., one can insert a DECIMAL with greater precision into a cache/table 
> without any problems. 



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

[jira] [Commented] (IGNITE-8896) Wrong javadoc for TcpCommunicationSpi.setSlowClientQueueLimit()

[Rodion (JIRA)]

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

Rodion commented on IGNITE-8896:


ready for review

> Wrong javadoc for TcpCommunicationSpi.setSlowClientQueueLimit()
> ---
>
> Key: IGNITE-8896
> URL: https://issues.apache.org/jira/browse/IGNITE-8896
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Dmitry Karachentsev
>Assignee: Rodion
>Priority: Minor
>  Labels: newbie
> Fix For: 2.8
>
>
> Javadoc for TcpCommunicationSpi.setSlowClientQueueLimit() says that is should 
> be set to value equal to TcpCommunicationSpi.getMessageQueueLimit().
> But this is wrong, because first checks back pressure limit and sender thread 
> will be blocked before slow client check. Also, warning checks the value 
> correctly, but message should be "...greater or equal...":
> {code:java}
> if (slowClientQueueLimit > 0 && msgQueueLimit > 0 && slowClientQueueLimit >= 
> msgQueueLimit) {
> U.quietAndWarn(log, "Slow client queue limit is set to a value 
> greater than message queue limit " +
> "(slow client queue limit will have no effect) 
> [msgQueueLimit=" + msgQueueLimit +
> ", slowClientQueueLimit=" + slowClientQueueLimit + ']');
> }
> {code}



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

[jira] [Updated] (IGNITE-10125) [TC Bot] Uniform style for buttons

[Nikolai Kulagin (JIRA)]

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

Nikolai Kulagin updated IGNITE-10125:
-
 Attachment: image-2018-11-02-12-06-59-734.png
Description: 
Uniform style for buttons: "Inspect" from [PR 
selection|https://mtcga.gridgain.com/prs.html], "Show graph" from [Master 
Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR 
Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest]
 

!image-2018-11-02-12-06-59-734.png! 

  was:Uniform style for buttons: "Inspect" from [PR 
selection|https://mtcga.gridgain.com/prs.html], "Show graph" from [Master 
Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR 
Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest]


> [TC Bot] Uniform style for buttons
> --
>
> Key: IGNITE-10125
> URL: https://issues.apache.org/jira/browse/IGNITE-10125
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
> Attachments: image-2018-11-02-12-06-59-734.png
>
>
> Uniform style for buttons: "Inspect" from [PR 
> selection|https://mtcga.gridgain.com/prs.html], "Show graph" from [Master 
> Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR 
> Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest]
>  
> !image-2018-11-02-12-06-59-734.png! 



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

[jira] [Commented] (IGNITE-10037) Cache 2 tests optimization

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov commented on IGNITE-10037:
--

[~aplatonov],

Now change looks good to me, I think we can proceed with merging.

[~dpavlov], could you please take a look and merge if no objects are on your 
side?

> Cache 2 tests optimization
> --
>
> Key: IGNITE-10037
> URL: https://issues.apache.org/jira/browse/IGNITE-10037
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Platonov
>Assignee: Alexey Platonov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> We need to investigate how to optimize these tests:
> GridCachePartitionNotLoadedEventSelfTest.testPrimaryAndBackupDead
>  
> CacheTxLoadingConcurrentGridStartSelfTestAllowOverwrite.testLoadCacheWithDataStreamerSequentialWithConfigAndRestarts
>  IgniteCacheEntryProcessorNodeJoinTest.testEntryProcessorNodeLeave
>  
> CacheTxLoadingConcurrentGridStartSelfTestAllowOverwrite.testLoadCacheWithDataStreamerSequentialWithConfig
>  
> CacheTxLoadingConcurrentGridStartSelfTestAllowOverwrite.testLoadCacheWithDataStreamerSequentialClientWithConfig
>  
> and optimize them.



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

[jira] [Updated] (IGNITE-10125) [TC Bot] Uniform style for buttons

[Nikolai Kulagin (JIRA)]

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

Nikolai Kulagin updated IGNITE-10125:
-
Description: Uniform style for buttons: "Inspect" from [PR 
selection|https://mtcga.gridgain.com/prs.html], "Show graph" from [Master 
Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR 
Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest]
  (was: Uniform style for buttons: "Inspect" from [PR 
selection|mtcga.gridgain.com/prs.html], "Show graph" from [Master 
Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR 
Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest])

> [TC Bot] Uniform style for buttons
> --
>
> Key: IGNITE-10125
> URL: https://issues.apache.org/jira/browse/IGNITE-10125
> Project: Ignite
>  Issue Type: Sub-task
>Reporter: Nikolai Kulagin
>Assignee: Nikolai Kulagin
>Priority: Minor
>
> Uniform style for buttons: "Inspect" from [PR 
> selection|https://mtcga.gridgain.com/prs.html], "Show graph" from [Master 
> Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR 
> Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest]



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

[jira] [Created] (IGNITE-10125) [TC Bot] Uniform style for buttons

[Nikolai Kulagin (JIRA)]

Nikolai Kulagin created IGNITE-10125:


 Summary: [TC Bot] Uniform style for buttons
 Key: IGNITE-10125
 URL: https://issues.apache.org/jira/browse/IGNITE-10125
 Project: Ignite
  Issue Type: Sub-task
Reporter: Nikolai Kulagin
Assignee: Nikolai Kulagin


Uniform style for buttons: "Inspect" from [PR 
selection|mtcga.gridgain.com/prs.html], "Show graph" from [Master 
Trends|https://mtcga.gridgain.com/comparison.html], "More >>" from [PR 
Failures|https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5200/head=Latest]



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

[jira] [Created] (IGNITE-10124) [TC Bot] Redesign and refactor UI

[Nikolai Kulagin (JIRA)]

Nikolai Kulagin created IGNITE-10124:


 Summary: [TC Bot] Redesign and refactor UI
 Key: IGNITE-10124
 URL: https://issues.apache.org/jira/browse/IGNITE-10124
 Project: Ignite
  Issue Type: Task
Reporter: Nikolai Kulagin


We must make the TC bot more user-friendly, make UI more intuitive and simple



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

[jira] [Commented] (IGNITE-9841) SQL doesn't take lost partitions into account when persistence is enabled

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-9841:


Github user asfgit closed the pull request at:

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


> SQL doesn't take lost partitions into account when persistence is enabled
> -
>
> Key: IGNITE-9841
> URL: https://issues.apache.org/jira/browse/IGNITE-9841
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Stanislav Lukyanov
>Assignee: Stanislav Lukyanov
>Priority: Major
> Fix For: 2.8
>
> Attachments: IgniteSqlQueryWithLostPartitionsTest.java
>
>
> IGNITE-8927 changed SQL queries to honor lost partitions. However, it doesn't 
> work if persistence is enabled. E.g. if there are lost partitions then 
> `select * from T` fails for in-memory caches (good) and silently ignores the 
> lost partitions for persistent caches (bad).
> See attached reproducer.



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

[jira] [Commented] (IGNITE-10123) Intermittent OOME errors in PDS indexing tests

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-10123:
-

GitHub user agoncharuk opened a pull request:

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

IGNITE-10123 Disable events in IgniteLogicalRecoveryTest



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

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

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

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


commit 88dcc8a100a6f2b4dc995a1e28bebe67b0a2edbf
Author: Alexey Goncharuk 
Date:   2018-11-02T08:46:00Z

IGNITE-10123 Disable events in IgniteLogicalRecoveryTest




> Intermittent OOME errors in PDS indexing tests
> --
>
> Key: IGNITE-10123
> URL: https://issues.apache.org/jira/browse/IGNITE-10123
> Project: Ignite
>  Issue Type: Test
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Analyzing the heap dump reveals the source of the leak - the massive amount 
> (700MB) of cache events in {{IgniteLogicalRecoveryTest}}. Disabling events 
> should resolve the issue.
> Disabling events by default in all tests should be investigated separately.



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

[jira] [Resolved] (IGNITE-10110) SQL query with DISTINCT and JOIN in suquery produces "Column not found"

[Taras Ledkov (JIRA)]

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

Taras Ledkov resolved IGNITE-10110.
---
Resolution: Duplicate

> SQL query with DISTINCT and JOIN in suquery produces "Column  not found" 
> -
>
> Key: IGNITE-10110
> URL: https://issues.apache.org/jira/browse/IGNITE-10110
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.4
>Reporter: Pavel Vinokurov
>Priority: Major
>  Labels: sql
>
> Initial script:
> CREATE TABLE Person(
>   person_id INTEGER PRIMARY KEY,
>   company_id INTEGER,
>   last_name VARCHAR(100)
> );
> CREATE TABLE Company(
>   company_id INTEGER PRIMARY KEY,
>   location_id INTEGER
> );
> CREATE TABLE Department(
>   department_id INTEGER PRIMARY KEY,
>   person_id INTEGER
> );
> CREATE TABLE Organization(
>   organization_id INTEGER PRIMARY KEY,
>   company_id INTEGER
> );
> Query:
> {code:java}
> SELECT
> last_name
> FROM
> (  SELECT
> last_name,
> person_id,
> company_id
> FROM
> ( SELECT
> last_name,
> person_id,
> p.company_id as company_id
> FROM
> Person p
> INNER JOIN
> (
> SELECT
> DISTINCT location_id,
> company_id
> FROM
> Company
> WHERE
> location_id = 1
> ) cpy
> ON (
> p.company_id = cpy.company_id
> )
> ) a
>   ) src
> INNER JOIN
> department dep
> ON src.person_id = dep.person_id
> LEFT JOIN
> organization og
> ON src.company_id = og.company_id
> {code}
> Result:
> Caused by: org.h2.jdbc.JdbcSQLException: Column "SRC__Z4.COMPANY_ID" not 
> found; SQL statement:
> SELECT
> DEP__Z5.PERSON_ID __C2_0
> FROM PUBLIC.DEPARTMENT DEP__Z5 
>  LEFT OUTER JOIN PUBLIC.ORGANIZATION OG__Z6 
>  ON SRC__Z4.COMPANY_ID = OG__Z6.COMPANY_ID



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

[jira] [Assigned] (IGNITE-10123) Intermittent OOME errors in PDS indexing tests

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk reassigned IGNITE-10123:
-

Assignee: Alexey Goncharuk

> Intermittent OOME errors in PDS indexing tests
> --
>
> Key: IGNITE-10123
> URL: https://issues.apache.org/jira/browse/IGNITE-10123
> Project: Ignite
>  Issue Type: Test
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.8
>
>
> Analyzing the heap dump reveals the source of the leak - the massive amount 
> (700MB) of cache events in {{IgniteLogicalRecoveryTest}}. Disabling events 
> should resolve the issue.
> Disabling events by default in all tests should be investigated separately.



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