[jira] [Commented] (IGNITE-2766) Cache instance is closed when client disconnects

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2766:


Github user asfgit closed the pull request at:

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


> Cache instance is closed when client disconnects
> 
>
> Key: IGNITE-2766
> URL: https://issues.apache.org/jira/browse/IGNITE-2766
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.5
>
>
> In case client disconnects and reconnects after network timeout (i.e., with a 
> new ID), all cache instances acquired by this client are closed and are not 
> functional. User has to create a special logic to handle this case.
> Cache proxy should be able to handle this automatically.



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

[jira] [Closed] (IGNITE-2766) Cache instance is closed when client disconnects

[Valentin Kulichenko (JIRA)]

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

Valentin Kulichenko closed IGNITE-2766.
---

> Cache instance is closed when client disconnects
> 
>
> Key: IGNITE-2766
> URL: https://issues.apache.org/jira/browse/IGNITE-2766
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Ilya Kasnacheev
>Priority: Major
> Fix For: 2.5
>
>
> In case client disconnects and reconnects after network timeout (i.e., with a 
> new ID), all cache instances acquired by this client are closed and are not 
> functional. User has to create a special logic to handle this case.
> Cache proxy should be able to handle this automatically.



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

[jira] [Created] (IGNITE-8265) TDE - MEK replacement

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-8265:
---

 Summary: TDE - MEK replacement
 Key: IGNITE-8265
 URL: https://issues.apache.org/jira/browse/IGNITE-8265
 Project: Ignite
  Issue Type: Sub-task
Reporter: Nikolay Izhikov


If MEK is lost or stolen while the cluster is alive, TDE should provide way to 
replace(regenerate) MEK.



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

[jira] [Updated] (IGNITE-8263) TDE - Encryption/Decryption of pages

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov updated IGNITE-8263:

Summary: TDE - Encryption/Decryption of pages  (was: TDE - 
Encryption/Decription of pages)

> TDE - Encryption/Decryption of pages
> 
>
> Key: IGNITE-8263
> URL: https://issues.apache.org/jira/browse/IGNITE-8263
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 2.4
>Reporter: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-18
> Fix For: 2.6
>
>
> When data for an encrypted cache are written to the persistence store. 
> Data page should be encrypted through configured encryption provider. 
> * Encryption/decryption should be implemented



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

[jira] [Updated] (IGNITE-8260) Transparent data encryption

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov updated IGNITE-8260:

Summary: Transparent data encryption  (was: Transparend data encryption)

> Transparent data encryption
> ---
>
> Key: IGNITE-8260
> URL: https://issues.apache.org/jira/browse/IGNITE-8260
> Project: Ignite
>  Issue Type: New Feature
>Affects Versions: 2.4
>Reporter: Nikolay Izhikov
>Assignee: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-18
> Fix For: 2.6
>
>
> TDE feature should allow to user to protect data stored in the persistence 
> storage with some cypher algorithm.
> Design details described in 
> [IEP-18|https://cwiki.apache.org/confluence/display/IGNITE/IEP-18%3A+Transparent+Data+Encryption].
> When this task will be done production ready TDE implementation should be 
> available for Ignite.



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

[jira] [Created] (IGNITE-8264) TDE - Node join enhanecements

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-8264:
---

 Summary: TDE - Node join enhanecements
 Key: IGNITE-8264
 URL: https://issues.apache.org/jira/browse/IGNITE-8264
 Project: Ignite
  Issue Type: Sub-task
Reporter: Nikolay Izhikov


All nodes that are joined to the cluster with TDE enabled should be configured 
to get TDE working. 
They need access to MEK and CEK's. 
We should extend node join mechanism to support TDE.



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

[jira] [Commented] (IGNITE-8232) ML package cleanup for 2.5 release

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8232:


Github user asfgit closed the pull request at:

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


> ML package cleanup for 2.5 release
> --
>
> Key: IGNITE-8232
> URL: https://issues.apache.org/jira/browse/IGNITE-8232
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Affects Versions: 2.5
>Reporter: Anton Dmitriev
>Assignee: Yury Babak
>Priority: Major
> Fix For: 2.5
>
>
> To prepare release 2.5 we need to cleanup existing code.
> # Cleanup {{org.apache.ignite.ml.Trainer}} and correspondent 
> {{LinearRegressionQRTrainer}}.
> # Cleanup {{org.apache.ignite.ml.trainers.Trainer}} and correspondent 
> {{GroupTrainer}}/{{Metaoptimizer}}.
> # Cleanup {{Estimators}} class.
> # Use {{SimpleLabeledDatasetData}} instead of {{LinSysPartitionDataOnHeap}}.
> # Cleanup {{GradientFunction}}, {{GradientDescent}}, 
> {{LeastSquaresGradientFunction}}, etc. in {{optimization}} package.



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

[jira] [Created] (IGNITE-8263) TDE - Encryption/Decription of pages

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-8263:
---

 Summary: TDE - Encryption/Decription of pages
 Key: IGNITE-8263
 URL: https://issues.apache.org/jira/browse/IGNITE-8263
 Project: Ignite
  Issue Type: Sub-task
Affects Versions: 2.4
Reporter: Nikolay Izhikov
 Fix For: 2.6


When data for an encrypted cache are written to the persistence store. 
Data page should be encrypted through configured encryption provider. 

* Encryption/decryption should be implemented



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

[jira] [Updated] (IGNITE-8261) TDE - Configuration

[Nikolay Izhikov (JIRA)]

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

Nikolay Izhikov updated IGNITE-8261:

Description: 
Ignite configuration should be extended to support all TDE specific 
configuration parameters: 

* KeyStore configuration. 
* Default KeyStore implementation should use JDK provided KeyStore - 
https://docs.oracle.com/javase/8/docs/api/java/security/KeyStore.html. 
* Other(not default) implementation of KeyStore should be allowed.
* New option for encrypted caches.

  was:
Ignite configuration should be extended to support all TDE specific 
configuration parameters: 

* KeyStore configuration. 
* New option for encrypted caches. 
* Default KeyStore implementation should use JDK provided KeyStore - 
https://docs.oracle.com/javase/8/docs/api/java/security/KeyStore.html. 


> TDE - Configuration
> ---
>
> Key: IGNITE-8261
> URL: https://issues.apache.org/jira/browse/IGNITE-8261
> Project: Ignite
>  Issue Type: Sub-task
>Affects Versions: 2.4
>Reporter: Nikolay Izhikov
>Priority: Major
>  Labels: IEP-18
> Fix For: 2.6
>
>
> Ignite configuration should be extended to support all TDE specific 
> configuration parameters: 
> * KeyStore configuration. 
> * Default KeyStore implementation should use JDK provided KeyStore - 
> https://docs.oracle.com/javase/8/docs/api/java/security/KeyStore.html. 
> * Other(not default) implementation of KeyStore should be allowed.
> * New option for encrypted caches.



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

[jira] [Created] (IGNITE-8262) TDE - MEK and CEK processing

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-8262:
---

 Summary: TDE - MEK and CEK processing
 Key: IGNITE-8262
 URL: https://issues.apache.org/jira/browse/IGNITE-8262
 Project: Ignite
  Issue Type: Sub-task
Reporter: Nikolay Izhikov


To get TDE working we should implement managing MEK and CEK's

* MEK should be loaded from configured KeyStore
* CEK's should be stored in some internal data storage and be encrypted with 
MEK.
* Cluster shouldn't get activated before MEK are loaded.



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

[jira] [Created] (IGNITE-8261) TDE - Configuration

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-8261:
---

 Summary: TDE - Configuration
 Key: IGNITE-8261
 URL: https://issues.apache.org/jira/browse/IGNITE-8261
 Project: Ignite
  Issue Type: Sub-task
Affects Versions: 2.4
Reporter: Nikolay Izhikov
 Fix For: 2.6


Ignite configuration should be extended to support all TDE specific 
configuration parameters: 

* KeyStore configuration. 
* New option for encrypted caches. 
* Default KeyStore implementation should use JDK provided KeyStore - 
https://docs.oracle.com/javase/8/docs/api/java/security/KeyStore.html. 



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

[jira] [Created] (IGNITE-8260) Transparend data encryption

[Nikolay Izhikov (JIRA)]

Nikolay Izhikov created IGNITE-8260:
---

 Summary: Transparend data encryption
 Key: IGNITE-8260
 URL: https://issues.apache.org/jira/browse/IGNITE-8260
 Project: Ignite
  Issue Type: New Feature
Affects Versions: 2.4
Reporter: Nikolay Izhikov
Assignee: Nikolay Izhikov
 Fix For: 2.6


TDE feature should allow to user to protect data stored in the persistence 
storage with some cypher algorithm.
Design details described in 
[IEP-18|https://cwiki.apache.org/confluence/display/IGNITE/IEP-18%3A+Transparent+Data+Encryption].
When this task will be done production ready TDE implementation should be 
available for Ignite.



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

[jira] [Commented] (IGNITE-7972) NPE in TTL manager.

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7972:


Could you provide link for convinience?

> NPE in TTL manager.
> ---
>
> Key: IGNITE-7972
> URL: https://issues.apache.org/jira/browse/IGNITE-7972
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.5
>
> Attachments: npe.log
>
>
> TTL manager can try to evict expired entries on cache that wasn't initialized 
> yet due to a race.
> This lead to NPE in unwindEvicts method.
> PFA stacktrace.



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

[jira] [Commented] (IGNITE-7972) NPE in TTL manager.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov commented on IGNITE-7972:
--

TC tests looks fine.

> NPE in TTL manager.
> ---
>
> Key: IGNITE-7972
> URL: https://issues.apache.org/jira/browse/IGNITE-7972
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Major
> Fix For: 2.5
>
> Attachments: npe.log
>
>
> TTL manager can try to evict expired entries on cache that wasn't initialized 
> yet due to a race.
> This lead to NPE in unwindEvicts method.
> PFA stacktrace.



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

[jira] [Commented] (IGNITE-8232) ML package cleanup for 2.5 release

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8232:


GitHub user ybabak opened a pull request:

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

IGNITE-8232 ML package cleanup for 2.5 release.

fixed javadoc

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

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

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

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


commit 098d2832b3f4af23c72bc25f43e4ab8a95f2f416
Author: Zinoviev Alexey 
Date:   2018-04-11T18:40:27Z

IGNITE-7829: Added example

commit da58736d2c223061ebbc8e54a252661165d10919
Author: Zinoviev Alexey 
Date:   2018-04-11T18:47:59Z

IGNITE-7829: Added example

commit f806dcff52a51692c4d80d20d3d33c2220eb4a9c
Author: zaleslaw 
Date:   2018-04-12T12:10:05Z

IGNITE-7829: Fixed Anton's review

commit d81ee7f72b78820d664661ef269eeb4fe1178c04
Author: zaleslaw 
Date:   2018-04-12T12:12:54Z

IGNITE-7829: Fixed Anton's review 2

commit 550eb79d771c97bfb9cfb6dc24882af7d1215692
Author: Zinoviev Alexey 
Date:   2018-04-12T12:14:31Z

Merge branch 'master' into ignite-7829

commit 3ea8e3df0f7b72ea6f58e2a47d1677dd6863d077
Author: Anton Dmitriev 
Date:   2018-04-12T12:30:08Z

IGNITE-8232 Remove all trainers except DatasetTrainer.

commit a79f28d671a66c1c8722dbe036686fdb9427fc61
Author: zaleslaw 
Date:   2018-04-12T12:30:09Z

IGNITE-7829: Fixed tests

commit 652581ac57eb0741677f5bd727ccbd04cc86e4e8
Author: zaleslaw 
Date:   2018-04-12T12:30:35Z

Merge branch 'ignite-7829' of https://github.com/gridgain/apache-ignite 
into ignite-7829

commit 0b7ec05427015dd014c811468b037c7ae308028c
Author: Anton Dmitriev 
Date:   2018-04-12T12:40:45Z

IGNITE-8232 Remove estimators.

commit 053bfb72105be69b6032459377ec41e92ab0d5ac
Author: Anton Dmitriev 
Date:   2018-04-12T12:59:50Z

IGNITE-8232 Use SimpleLabeledDatasetData instead of dedicated
LinSysOnHeapData.

commit 14a7357afc0f33b07f5d4f56d6081222ec5bb437
Author: Anton Dmitriev 
Date:   2018-04-12T13:35:59Z

IGNITE-8233 Add protection of dataset compute method from empty data.

commit c63105c2cd4d4d8829ff300eaa7d11ed6620ebdb
Author: Anton Dmitriev 
Date:   2018-04-12T13:44:55Z

IGNITE-8233 Fix tests after adding protection of dataset compute method
from empty data.

commit da4baaf246b24867636578ea95fd53f2e92ea86c
Author: Anton Dmitriev 
Date:   2018-04-12T13:53:33Z

IGNITE-8233 Fix tests after adding protection of dataset compute method
from empty data.

commit 64656650ed4d2ebd165b7d62f59b9ce8cf027a6e
Author: Anton Dmitriev 
Date:   2018-04-12T13:55:57Z

IGNITE-8233 Fix tests after adding protection of dataset compute method
from empty data.

commit bd7aa5cf6da0b37c37862851d50b85fd822da344
Author: Anton Dmitriev 
Date:   2018-04-12T13:56:30Z

IGNITE-8233 Fix tests after adding protection of dataset compute method
from empty data.

commit 95d30e4175a55761760e7b3f8bb1d9a5bc00823f
Author: Anton Dmitriev 
Date:   2018-04-12T14:06:54Z

Merge branch 'ignite-8233' into ignite-8232

commit 02bd96b25568af2edf36965dfa0c7d66c0a4a256
Author: Anton Dmitriev 
Date:   2018-04-12T14:17:25Z

IGNITE-8233 Use Precision.EPSILON in AbstractLSQR.

commit e6066f572f40ebc709aa011ed1083d09303f601b
Author: dmitrievanthony 
Date:   2018-04-13T08:33:02Z

Revert "IGNITE-8233 Fix tests after adding protection of dataset compute 
method from empty data."

This reverts commit bd7aa5c

commit f1638a475826c37dbd0b0f71585a3c3ebfc37e2e
Author: dmitrievanthony 
Date:   2018-04-13T08:33:06Z

Revert "IGNITE-8233 Fix tests after adding protection of dataset compute 
method from empty data."

This reverts commit 6465665

commit 887b45fb659378f4a4b9e786b8169bd402688ffd
Author: dmitrievanthony 
Date:   2018-04-13T08:34:45Z

IGNITE-8233 Test SVM on 10 partitions instead of 1.

commit 85fa1771da8dc84ca6e35a10c7da596170f1637f
Author: dmitrievanthony 
Date:   2018-04-13T08:37:24Z

Merge remote-tracking branch 'prof/ignite-7829' into ignite-8233

# Conflicts:
#   
modules/ml/src/test/java/org/apache/ignite/ml/knn/KNNClassificationTest.java
#   

[jira] [Comment Edited] (IGNITE-8232) ML package cleanup for 2.5 release

[Yury Babak (JIRA)]

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

Yury Babak edited comment on IGNITE-8232 at 4/13/18 5:05 PM:
-

Broken javadocs

[Step 1/1] [WARNING] 
/data/teamcity/work/8241162b5ce21231/modules/ml/src/main/java/org/apache/ignite/ml/math/functions/IgniteBiFunction.java:31:
 warning - @inheritDoc used but andThen(IgniteFunction) 
does not override or implement any method.


was (Author: chief):
Broken javadocs

> ML package cleanup for 2.5 release
> --
>
> Key: IGNITE-8232
> URL: https://issues.apache.org/jira/browse/IGNITE-8232
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Affects Versions: 2.5
>Reporter: Anton Dmitriev
>Assignee: Yury Babak
>Priority: Major
> Fix For: 2.5
>
>
> To prepare release 2.5 we need to cleanup existing code.
> # Cleanup {{org.apache.ignite.ml.Trainer}} and correspondent 
> {{LinearRegressionQRTrainer}}.
> # Cleanup {{org.apache.ignite.ml.trainers.Trainer}} and correspondent 
> {{GroupTrainer}}/{{Metaoptimizer}}.
> # Cleanup {{Estimators}} class.
> # Use {{SimpleLabeledDatasetData}} instead of {{LinSysPartitionDataOnHeap}}.
> # Cleanup {{GradientFunction}}, {{GradientDescent}}, 
> {{LeastSquaresGradientFunction}}, etc. in {{optimization}} package.



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

[jira] [Reopened] (IGNITE-8232) ML package cleanup for 2.5 release

[Yury Babak (JIRA)]

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

Yury Babak reopened IGNITE-8232:

  Assignee: Yury Babak  (was: Anton Dmitriev)

Broken javadocs

> ML package cleanup for 2.5 release
> --
>
> Key: IGNITE-8232
> URL: https://issues.apache.org/jira/browse/IGNITE-8232
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Affects Versions: 2.5
>Reporter: Anton Dmitriev
>Assignee: Yury Babak
>Priority: Major
> Fix For: 2.5
>
>
> To prepare release 2.5 we need to cleanup existing code.
> # Cleanup {{org.apache.ignite.ml.Trainer}} and correspondent 
> {{LinearRegressionQRTrainer}}.
> # Cleanup {{org.apache.ignite.ml.trainers.Trainer}} and correspondent 
> {{GroupTrainer}}/{{Metaoptimizer}}.
> # Cleanup {{Estimators}} class.
> # Use {{SimpleLabeledDatasetData}} instead of {{LinSysPartitionDataOnHeap}}.
> # Cleanup {{GradientFunction}}, {{GradientDescent}}, 
> {{LeastSquaresGradientFunction}}, etc. in {{optimization}} package.



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

[jira] [Updated] (IGNITE-8259) Node join should be failed if it has cache not existed in cluster

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev updated IGNITE-8259:
--
Summary: Node join should be failed if it has cache not existed in cluster  
(was: Node join should be failed if it has cache not contained in cluster)

> Node join should be failed if it has cache not existed in cluster
> -
>
> Key: IGNITE-8259
> URL: https://issues.apache.org/jira/browse/IGNITE-8259
> Project: Ignite
>  Issue Type: Bug
>Reporter: Anton Kalashnikov
>Priority: Major
>
> Node join should be failed if it has cache not contained in cluster otherwise 
> it may be cause of cache corrupt



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

[jira] [Created] (IGNITE-8259) Node join should be failed if it has cache not contained in cluster

[Anton Kalashnikov (JIRA)]

Anton Kalashnikov created IGNITE-8259:
-

 Summary: Node join should be failed if it has cache not contained 
in cluster
 Key: IGNITE-8259
 URL: https://issues.apache.org/jira/browse/IGNITE-8259
 Project: Ignite
  Issue Type: Bug
Reporter: Anton Kalashnikov


Node join should be failed if it has cache not contained in cluster otherwise 
it may be cause of cache corrupt



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

[jira] [Commented] (IGNITE-8097) Java thin client: throw handshake exception on connect phase

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8097:


GitHub user kukushal opened a pull request:

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

IGNITE-8097 Java thin client: throw handshake exception on connect phase



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

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

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

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


commit 2286c06b8140cd2f86b404da2271e24b0a8fe26f
Author: Alexey Kukushkin 
Date:   2018-04-13T16:39:15Z

IGNITE-8097 Java thin client: throw handshake exception on connect phase




> Java thin client: throw handshake exception on connect phase
> 
>
> Key: IGNITE-8097
> URL: https://issues.apache.org/jira/browse/IGNITE-8097
> Project: Ignite
>  Issue Type: Task
>  Components: thin client
>Reporter: Vladimir Ozerov
>Assignee: Alexey Kukushkin
>Priority: Major
> Fix For: 2.5
>
>
> Currently a call to {{Ignition.startClient}} return client instance even if 
> we know for sure that connection is not usable. Real exception (e.g. protocol 
> mismatch, auth error, etc.) is thrown on attempt to execute first operation 
> on the client. This is bad UX - use may think that everything is OK for a 
> long time.
> Instead, connection should be established eagerly in {{startClient}}, any 
> exception should be propagated to the user immediately.



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

[jira] [Updated] (IGNITE-8258) Ignite PDS 1 suite, test probably failed suite IgnitePdsPageReplacementTest.testPageReplacement (last started)

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk updated IGNITE-8258:
-
Priority: Critical  (was: Major)

> Ignite PDS 1 suite, test probably failed suite 
> IgnitePdsPageReplacementTest.testPageReplacement (last started)
> --
>
> Key: IGNITE-8258
> URL: https://issues.apache.org/jira/browse/IGNITE-8258
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>Priority: Critical
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1199095=IgniteTests24Java8_IgnitePds1=buildLog
> {noformat}
> [2018-04-13 
> 03:06:28,479][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
>  Critical failure. Will be handled accordingly to configured handler 
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Compound 
> exception for CountDownFuture.]]
> class org.apache.ignite.IgniteCheckedException: Compound exception for 
> CountDownFuture.
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.addError(CountDownFuture.java:72)
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:46)
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:28)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:462)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3545)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
>   Suppressed: java.lang.IllegalMonitorStateException: Attempted to 
> release write lock while not holding it [lock=7f360ad0d630, 
> state=0001
>   at 
> org.apache.ignite.internal.util.OffheapReadWriteLock.writeUnlock(OffheapReadWriteLock.java:266)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.copyPageForCheckpoint(PageMemoryImpl.java:1185)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.getForCheckpoint(PageMemoryImpl.java:1117)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3508)
>   ... 3 more
> [2018-04-13 
> 03:06:28,483][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
>  Critical failure. Will be handled accordingly to configured handler 
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to 
> begin checkpoint (it is already in progress).]]
> class org.apache.ignite.IgniteException: Failed to begin checkpoint (it is 
> already in progress).
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.beginCheckpoint(PageMemoryImpl.java:997)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.beginAllCheckpoints(GridCacheDatabaseSharedManager.java:3309)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:3183)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:2909)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:2808)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> [2018-04-13 
> 03:06:28,485][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][GridCacheDatabaseSharedManager]
>  Runtime error caught during grid runnable execution: GridWorker 
> [name=db-checkpoint-thread, 
> igniteInstanceName=file.IgnitePdsPageReplacementTest0, finished=false, 
> hashCode=564969718, interrupted=false, 
> runner=db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%]
> class org.apache.ignite.IgniteException: Failed to begin checkpoint (it is 
> already in progress).
>   at 

[jira] [Updated] (IGNITE-8258) Ignite PDS 1 suite, test probably failed suite IgnitePdsPageReplacementTest.testPageReplacement (last started)

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk updated IGNITE-8258:
-
Fix Version/s: 2.5

> Ignite PDS 1 suite, test probably failed suite 
> IgnitePdsPageReplacementTest.testPageReplacement (last started)
> --
>
> Key: IGNITE-8258
> URL: https://issues.apache.org/jira/browse/IGNITE-8258
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1199095=IgniteTests24Java8_IgnitePds1=buildLog
> {noformat}
> [2018-04-13 
> 03:06:28,479][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
>  Critical failure. Will be handled accordingly to configured handler 
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Compound 
> exception for CountDownFuture.]]
> class org.apache.ignite.IgniteCheckedException: Compound exception for 
> CountDownFuture.
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.addError(CountDownFuture.java:72)
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:46)
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:28)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:462)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3545)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
>   Suppressed: java.lang.IllegalMonitorStateException: Attempted to 
> release write lock while not holding it [lock=7f360ad0d630, 
> state=0001
>   at 
> org.apache.ignite.internal.util.OffheapReadWriteLock.writeUnlock(OffheapReadWriteLock.java:266)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.copyPageForCheckpoint(PageMemoryImpl.java:1185)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.getForCheckpoint(PageMemoryImpl.java:1117)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3508)
>   ... 3 more
> [2018-04-13 
> 03:06:28,483][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
>  Critical failure. Will be handled accordingly to configured handler 
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to 
> begin checkpoint (it is already in progress).]]
> class org.apache.ignite.IgniteException: Failed to begin checkpoint (it is 
> already in progress).
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.beginCheckpoint(PageMemoryImpl.java:997)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.beginAllCheckpoints(GridCacheDatabaseSharedManager.java:3309)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:3183)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:2909)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:2808)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> [2018-04-13 
> 03:06:28,485][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][GridCacheDatabaseSharedManager]
>  Runtime error caught during grid runnable execution: GridWorker 
> [name=db-checkpoint-thread, 
> igniteInstanceName=file.IgnitePdsPageReplacementTest0, finished=false, 
> hashCode=564969718, interrupted=false, 
> runner=db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%]
> class org.apache.ignite.IgniteException: Failed to begin checkpoint (it is 
> already in progress).
>   at 
> 

[jira] [Commented] (IGNITE-8169) [ML] Adopt KMeans to the new Partitioned Dataset and cleanup old code

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-8169:


related discussion at dev list: [\[ML\] Remove Old FuzzyCMeans 
Implementation|http://apache-ignite-developers.2346864.n4.nabble.com/ML-Remove-Old-FuzzyCMeans-Implementation-td29407.html]

> [ML] Adopt KMeans to the new Partitioned Dataset and cleanup old code
> -
>
> Key: IGNITE-8169
> URL: https://issues.apache.org/jira/browse/IGNITE-8169
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Aleksey Zinoviev
>Assignee: Aleksey Zinoviev
>Priority: Major
>




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

[jira] [Resolved] (IGNITE-7659) Reduce multiple Trainer interfaces to one

[Anton Dmitriev (JIRA)]

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

Anton Dmitriev resolved IGNITE-7659.

Resolution: Resolved

> Reduce multiple Trainer interfaces to one
> -
>
> Key: IGNITE-7659
> URL: https://issues.apache.org/jira/browse/IGNITE-7659
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Anton Dmitriev
>Assignee: Anton Dmitriev
>Priority: Minor
> Fix For: 2.5
>
>
> Currently there are two `Trainer` interfaces: in package 
> `org.apache.ignite.ml` and `org.apache.ignite.ml.trainers`. We need to use 
> only one.



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

[jira] [Commented] (IGNITE-8210) Rebalancing sometimes is not triggered when a node is added to the baseline topology

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-8210:
--

The change looks good to me. Re-started a couple of suspicious tests, if TC is 
good, will merge.

> Rebalancing sometimes is not triggered when a node is added to the baseline 
> topology
> 
>
> Key: IGNITE-8210
> URL: https://issues.apache.org/jira/browse/IGNITE-8210
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Reporter: Stanislav Lukyanov
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.5
>
> Attachments: RebalanceAfterNodeAddedToBaseline.java
>
>
> When a cluster already has baseline topology set and activated adding a new 
> node to the baseline should lead to rebalancing. However, in some cases the 
> new node will not receive any data when joined and added to the baseline; if 
> a cluster is later deactivated and activated again, the rebalancing happens 
> properly and partitions are assigned and transferred to the new node.



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

[jira] [Assigned] (IGNITE-8082) No management bean for ZookeeperDiscoverySpi

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov reassigned IGNITE-8082:
---

Assignee: Sergey Chugunov

> No management bean for ZookeeperDiscoverySpi
> 
>
> Key: IGNITE-8082
> URL: https://issues.apache.org/jira/browse/IGNITE-8082
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Max Shonichev
>Assignee: Sergey Chugunov
>Priority: Major
> Fix For: 2.5
>
>
> TcpDiscoverySpi provides management bean, allowing user to obtain 
> configuration and metrics from it via JMX.
> However, Zookeeper discovery spi provides no management bean, please add it 
> with similar attributes.



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

[jira] [Commented] (IGNITE-8258) Ignite PDS 1 suite, test probably failed suite IgnitePdsPageReplacementTest.testPageReplacement (last started)

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-8258:


Triggered run-all: https://ci.ignite.apache.org/viewQueued.html?itemId=1202998

> Ignite PDS 1 suite, test probably failed suite 
> IgnitePdsPageReplacementTest.testPageReplacement (last started)
> --
>
> Key: IGNITE-8258
> URL: https://issues.apache.org/jira/browse/IGNITE-8258
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1199095=IgniteTests24Java8_IgnitePds1=buildLog
> {noformat}
> [2018-04-13 
> 03:06:28,479][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
>  Critical failure. Will be handled accordingly to configured handler 
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Compound 
> exception for CountDownFuture.]]
> class org.apache.ignite.IgniteCheckedException: Compound exception for 
> CountDownFuture.
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.addError(CountDownFuture.java:72)
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:46)
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:28)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:462)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3545)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
>   Suppressed: java.lang.IllegalMonitorStateException: Attempted to 
> release write lock while not holding it [lock=7f360ad0d630, 
> state=0001
>   at 
> org.apache.ignite.internal.util.OffheapReadWriteLock.writeUnlock(OffheapReadWriteLock.java:266)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.copyPageForCheckpoint(PageMemoryImpl.java:1185)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.getForCheckpoint(PageMemoryImpl.java:1117)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3508)
>   ... 3 more
> [2018-04-13 
> 03:06:28,483][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
>  Critical failure. Will be handled accordingly to configured handler 
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to 
> begin checkpoint (it is already in progress).]]
> class org.apache.ignite.IgniteException: Failed to begin checkpoint (it is 
> already in progress).
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.beginCheckpoint(PageMemoryImpl.java:997)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.beginAllCheckpoints(GridCacheDatabaseSharedManager.java:3309)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:3183)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:2909)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:2808)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> [2018-04-13 
> 03:06:28,485][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][GridCacheDatabaseSharedManager]
>  Runtime error caught during grid runnable execution: GridWorker 
> [name=db-checkpoint-thread, 
> igniteInstanceName=file.IgnitePdsPageReplacementTest0, finished=false, 
> hashCode=564969718, interrupted=false, 
> runner=db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%]
> class org.apache.ignite.IgniteException: Failed to begin 

[jira] [Commented] (IGNITE-8258) Ignite PDS 1 suite, test probably failed suite IgnitePdsPageReplacementTest.testPageReplacement (last started)

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-8258:
--

Attempting to fix the issue:
https://github.com/apache/ignite/pull/3821

> Ignite PDS 1 suite, test probably failed suite 
> IgnitePdsPageReplacementTest.testPageReplacement (last started)
> --
>
> Key: IGNITE-8258
> URL: https://issues.apache.org/jira/browse/IGNITE-8258
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1199095=IgniteTests24Java8_IgnitePds1=buildLog
> {noformat}
> [2018-04-13 
> 03:06:28,479][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
>  Critical failure. Will be handled accordingly to configured handler 
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Compound 
> exception for CountDownFuture.]]
> class org.apache.ignite.IgniteCheckedException: Compound exception for 
> CountDownFuture.
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.addError(CountDownFuture.java:72)
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:46)
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:28)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:462)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3545)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
>   Suppressed: java.lang.IllegalMonitorStateException: Attempted to 
> release write lock while not holding it [lock=7f360ad0d630, 
> state=0001
>   at 
> org.apache.ignite.internal.util.OffheapReadWriteLock.writeUnlock(OffheapReadWriteLock.java:266)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.copyPageForCheckpoint(PageMemoryImpl.java:1185)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.getForCheckpoint(PageMemoryImpl.java:1117)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3508)
>   ... 3 more
> [2018-04-13 
> 03:06:28,483][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
>  Critical failure. Will be handled accordingly to configured handler 
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to 
> begin checkpoint (it is already in progress).]]
> class org.apache.ignite.IgniteException: Failed to begin checkpoint (it is 
> already in progress).
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.beginCheckpoint(PageMemoryImpl.java:997)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.beginAllCheckpoints(GridCacheDatabaseSharedManager.java:3309)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:3183)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:2909)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:2808)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> [2018-04-13 
> 03:06:28,485][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][GridCacheDatabaseSharedManager]
>  Runtime error caught during grid runnable execution: GridWorker 
> [name=db-checkpoint-thread, 
> igniteInstanceName=file.IgnitePdsPageReplacementTest0, finished=false, 
> hashCode=564969718, interrupted=false, 
> runner=db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%]
> class org.apache.ignite.IgniteException: Failed to begin 

[jira] [Assigned] (IGNITE-8258) Ignite PDS 1 suite, test probably failed suite IgnitePdsPageReplacementTest.testPageReplacement (last started)

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk reassigned IGNITE-8258:


Assignee: Alexey Goncharuk

> Ignite PDS 1 suite, test probably failed suite 
> IgnitePdsPageReplacementTest.testPageReplacement (last started)
> --
>
> Key: IGNITE-8258
> URL: https://issues.apache.org/jira/browse/IGNITE-8258
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1199095=IgniteTests24Java8_IgnitePds1=buildLog
> {noformat}
> [2018-04-13 
> 03:06:28,479][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
>  Critical failure. Will be handled accordingly to configured handler 
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Compound 
> exception for CountDownFuture.]]
> class org.apache.ignite.IgniteCheckedException: Compound exception for 
> CountDownFuture.
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.addError(CountDownFuture.java:72)
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:46)
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:28)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:462)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3545)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
>   Suppressed: java.lang.IllegalMonitorStateException: Attempted to 
> release write lock while not holding it [lock=7f360ad0d630, 
> state=0001
>   at 
> org.apache.ignite.internal.util.OffheapReadWriteLock.writeUnlock(OffheapReadWriteLock.java:266)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.copyPageForCheckpoint(PageMemoryImpl.java:1185)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.getForCheckpoint(PageMemoryImpl.java:1117)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3508)
>   ... 3 more
> [2018-04-13 
> 03:06:28,483][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
>  Critical failure. Will be handled accordingly to configured handler 
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to 
> begin checkpoint (it is already in progress).]]
> class org.apache.ignite.IgniteException: Failed to begin checkpoint (it is 
> already in progress).
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.beginCheckpoint(PageMemoryImpl.java:997)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.beginAllCheckpoints(GridCacheDatabaseSharedManager.java:3309)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:3183)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:2909)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:2808)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>   at java.lang.Thread.run(Thread.java:745)
> [2018-04-13 
> 03:06:28,485][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][GridCacheDatabaseSharedManager]
>  Runtime error caught during grid runnable execution: GridWorker 
> [name=db-checkpoint-thread, 
> igniteInstanceName=file.IgnitePdsPageReplacementTest0, finished=false, 
> hashCode=564969718, interrupted=false, 
> runner=db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%]
> class org.apache.ignite.IgniteException: Failed to begin checkpoint (it is 
> already in progress).
>   at 
> 

[jira] [Commented] (IGNITE-8258) Ignite PDS 1 suite, test probably failed suite IgnitePdsPageReplacementTest.testPageReplacement (last started)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8258:


GitHub user agoncharuk opened a pull request:

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

IGNITE-8258 Fixed page acquire/write unlock order during checkpoint



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

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

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

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


commit 85f5ea404150d625f8c9d1ad172a3aff8f9c8dbc
Author: Alexey Goncharuk 
Date:   2018-04-13T15:58:49Z

IGNITE-8258 Fixed page acquire/write unlock order during checkpoint




> Ignite PDS 1 suite, test probably failed suite 
> IgnitePdsPageReplacementTest.testPageReplacement (last started)
> --
>
> Key: IGNITE-8258
> URL: https://issues.apache.org/jira/browse/IGNITE-8258
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Alexey Goncharuk
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> https://ci.ignite.apache.org/viewLog.html?buildId=1199095=IgniteTests24Java8_IgnitePds1=buildLog
> {noformat}
> [2018-04-13 
> 03:06:28,479][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
>  Critical failure. Will be handled accordingly to configured handler 
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
> [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Compound 
> exception for CountDownFuture.]]
> class org.apache.ignite.IgniteCheckedException: Compound exception for 
> CountDownFuture.
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.addError(CountDownFuture.java:72)
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:46)
>   at 
> org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:28)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:462)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3545)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
>   Suppressed: java.lang.IllegalMonitorStateException: Attempted to 
> release write lock while not holding it [lock=7f360ad0d630, 
> state=0001
>   at 
> org.apache.ignite.internal.util.OffheapReadWriteLock.writeUnlock(OffheapReadWriteLock.java:266)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.copyPageForCheckpoint(PageMemoryImpl.java:1185)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.getForCheckpoint(PageMemoryImpl.java:1117)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3508)
>   ... 3 more
> [2018-04-13 
> 03:06:28,483][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
>  Critical failure. Will be handled accordingly to configured handler 
> [hnd=class o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to 
> begin checkpoint (it is already in progress).]]
> class org.apache.ignite.IgniteException: Failed to begin checkpoint (it is 
> already in progress).
>   at 
> org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.beginCheckpoint(PageMemoryImpl.java:997)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.beginAllCheckpoints(GridCacheDatabaseSharedManager.java:3309)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:3183)
>   at 
> org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:2909)
>   at 
> 

[jira] [Created] (IGNITE-8258) Ignite PDS 1 suite, test probably failed suite IgnitePdsPageReplacementTest.testPageReplacement (last started)

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-8258:
--

 Summary: Ignite PDS 1 suite, test probably failed suite 
IgnitePdsPageReplacementTest.testPageReplacement (last started)
 Key: IGNITE-8258
 URL: https://issues.apache.org/jira/browse/IGNITE-8258
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Pavlov


https://ci.ignite.apache.org/viewLog.html?buildId=1199095=IgniteTests24Java8_IgnitePds1=buildLog

{noformat}
[2018-04-13 
03:06:28,479][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
 Critical failure. Will be handled accordingly to configured handler [hnd=class 
o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
[type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Compound 
exception for CountDownFuture.]]
class org.apache.ignite.IgniteCheckedException: Compound exception for 
CountDownFuture.
at 
org.apache.ignite.internal.util.future.CountDownFuture.addError(CountDownFuture.java:72)
at 
org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:46)
at 
org.apache.ignite.internal.util.future.CountDownFuture.onDone(CountDownFuture.java:28)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.onDone(GridFutureAdapter.java:462)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3545)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Suppressed: java.lang.IllegalMonitorStateException: Attempted to 
release write lock while not holding it [lock=7f360ad0d630, 
state=0001
at 
org.apache.ignite.internal.util.OffheapReadWriteLock.writeUnlock(OffheapReadWriteLock.java:266)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.copyPageForCheckpoint(PageMemoryImpl.java:1185)
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.getForCheckpoint(PageMemoryImpl.java:1117)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$WriteCheckpointPages.run(GridCacheDatabaseSharedManager.java:3508)
... 3 more
[2018-04-13 
03:06:28,483][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][IgniteTestResources]
 Critical failure. Will be handled accordingly to configured handler [hnd=class 
o.a.i.failure.NoOpFailureHandler, failureCtx=FailureContext 
[type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: Failed to 
begin checkpoint (it is already in progress).]]
class org.apache.ignite.IgniteException: Failed to begin checkpoint (it is 
already in progress).
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.beginCheckpoint(PageMemoryImpl.java:997)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.beginAllCheckpoints(GridCacheDatabaseSharedManager.java:3309)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:3183)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.doCheckpoint(GridCacheDatabaseSharedManager.java:2909)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.body(GridCacheDatabaseSharedManager.java:2808)
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:745)
[2018-04-13 
03:06:28,485][ERROR][db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%][GridCacheDatabaseSharedManager]
 Runtime error caught during grid runnable execution: GridWorker 
[name=db-checkpoint-thread, 
igniteInstanceName=file.IgnitePdsPageReplacementTest0, finished=false, 
hashCode=564969718, interrupted=false, 
runner=db-checkpoint-thread-#52662%file.IgnitePdsPageReplacementTest0%]
class org.apache.ignite.IgniteException: Failed to begin checkpoint (it is 
already in progress).
at 
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.beginCheckpoint(PageMemoryImpl.java:997)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.beginAllCheckpoints(GridCacheDatabaseSharedManager.java:3309)
at 
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager$Checkpointer.markCheckpointBegin(GridCacheDatabaseSharedManager.java:3183)
at 

[jira] [Commented] (IGNITE-8257) GridFutureAdapterSelfTest#testChaining flaky-fails on TC (rarely)

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8257:


GitHub user BiryukovVA opened a pull request:

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

IGNITE-8257: GridFutureAdapterSelfTest#testChaining fixed.



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

$ git pull https://github.com/BiryukovVA/ignite IGNITE-8257

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

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


commit 7a2fe2b4a7d82b742f308936981149a4182a
Author: Vitaliy Biryukov 
Date:   2018-04-13T15:14:27Z

IGNITE-8257: Test fixed.




> GridFutureAdapterSelfTest#testChaining flaky-fails on TC (rarely)
> -
>
> Key: IGNITE-8257
> URL: https://issues.apache.org/jira/browse/IGNITE-8257
> Project: Ignite
>  Issue Type: Test
>Reporter: Vitaliy Biryukov
>Assignee: Vitaliy Biryukov
>Priority: Minor
> Fix For: 2.6
>
>
> {code:java}
> class org.apache.ignite.internal.IgniteFutureTimeoutCheckedException: Timeout 
> was reached before computation completed.
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:242)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:159)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:151)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapterSelfTest.checkChaining(GridFutureAdapterSelfTest.java:283)
>   at 
> org.apache.ignite.internal.util.future.GridFutureAdapterSelfTest.testChaining(GridFutureAdapterSelfTest.java:237)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
>   at java.lang.Thread.run(Thread.java:745)
> {code}



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

[jira] [Commented] (IGNITE-8232) ML package cleanup for 2.5 release

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8232:


Github user asfgit closed the pull request at:

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


> ML package cleanup for 2.5 release
> --
>
> Key: IGNITE-8232
> URL: https://issues.apache.org/jira/browse/IGNITE-8232
> Project: Ignite
>  Issue Type: Improvement
>  Components: ml
>Affects Versions: 2.5
>Reporter: Anton Dmitriev
>Assignee: Anton Dmitriev
>Priority: Major
> Fix For: 2.5
>
>
> To prepare release 2.5 we need to cleanup existing code.
> # Cleanup {{org.apache.ignite.ml.Trainer}} and correspondent 
> {{LinearRegressionQRTrainer}}.
> # Cleanup {{org.apache.ignite.ml.trainers.Trainer}} and correspondent 
> {{GroupTrainer}}/{{Metaoptimizer}}.
> # Cleanup {{Estimators}} class.
> # Use {{SimpleLabeledDatasetData}} instead of {{LinSysPartitionDataOnHeap}}.
> # Cleanup {{GradientFunction}}, {{GradientDescent}}, 
> {{LeastSquaresGradientFunction}}, etc. in {{optimization}} package.



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

[jira] [Commented] (IGNITE-8233) KNN and SVM algorithms don't work when partition doesn't contain data

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8233:


Github user asfgit closed the pull request at:

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


> KNN and SVM algorithms don't work when partition doesn't contain data
> -
>
> Key: IGNITE-8233
> URL: https://issues.apache.org/jira/browse/IGNITE-8233
> Project: Ignite
>  Issue Type: Bug
>  Components: ml
>Affects Versions: 2.5
>Reporter: Anton Dmitriev
>Assignee: Anton Dmitriev
>Priority: Major
> Fix For: 2.5
>
>
> KNN and SVM algorithms implemented with assumption that partition data won't 
> be null:
> {code:java}
> public LabeledDataset(double[][] mtx, double[] lbs, String[] featureNames, 
> boolean isDistributed) {
> super();
> assert mtx != null;
> assert lbs != null;
> {code}
> Currently it's wrong assumption, so we need to update dataset to support this 
> assumption or update these algorithms.



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

[jira] [Created] (IGNITE-8257) GridFutureAdapterSelfTest#testChaining flaky-fails on TC (rarely)

[Vitaliy Biryukov (JIRA)]

Vitaliy Biryukov created IGNITE-8257:


 Summary: GridFutureAdapterSelfTest#testChaining flaky-fails on TC 
(rarely)
 Key: IGNITE-8257
 URL: https://issues.apache.org/jira/browse/IGNITE-8257
 Project: Ignite
  Issue Type: Test
Reporter: Vitaliy Biryukov
Assignee: Vitaliy Biryukov
 Fix For: 2.6



{code:java}
class org.apache.ignite.internal.IgniteFutureTimeoutCheckedException: Timeout 
was reached before computation completed.
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:242)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:159)
at 
org.apache.ignite.internal.util.future.GridFutureAdapter.get(GridFutureAdapter.java:151)
at 
org.apache.ignite.internal.util.future.GridFutureAdapterSelfTest.checkChaining(GridFutureAdapterSelfTest.java:283)
at 
org.apache.ignite.internal.util.future.GridFutureAdapterSelfTest.testChaining(GridFutureAdapterSelfTest.java:237)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at junit.framework.TestCase.runTest(TestCase.java:176)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2080)
at 
org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:140)
at 
org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1995)
at java.lang.Thread.run(Thread.java:745)
{code}




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

[jira] [Updated] (IGNITE-8256) TxRecoveryStoreEnabledTest.testPessimistic fails on TC

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk updated IGNITE-8256:
-
Labels: MakeTeamcityGreenAgain  (was: )

> TxRecoveryStoreEnabledTest.testPessimistic fails on TC
> --
>
> Key: IGNITE-8256
> URL: https://issues.apache.org/jira/browse/IGNITE-8256
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> The reason for the failure is that simulateNodeFailure does not work anymore 
> if failure handler is not a StopNodeFailureHandler



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

[jira] [Resolved] (IGNITE-8256) TxRecoveryStoreEnabledTest.testPessimistic fails on TC

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk resolved IGNITE-8256.
--
   Resolution: Fixed
Fix Version/s: 2.5

Change only in test, no TC run needed.

> TxRecoveryStoreEnabledTest.testPessimistic fails on TC
> --
>
> Key: IGNITE-8256
> URL: https://issues.apache.org/jira/browse/IGNITE-8256
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> The reason for the failure is that simulateNodeFailure does not work anymore 
> if failure handler is not a StopNodeFailureHandler



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

[jira] [Created] (IGNITE-8256) TxRecoveryStoreEnabledTest.testPessimistic fails on TC

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-8256:


 Summary: TxRecoveryStoreEnabledTest.testPessimistic fails on TC
 Key: IGNITE-8256
 URL: https://issues.apache.org/jira/browse/IGNITE-8256
 Project: Ignite
  Issue Type: Improvement
Reporter: Alexey Goncharuk


The reason for the failure is that simulateNodeFailure does not work anymore if 
failure handler is not a StopNodeFailureHandler



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

[jira] [Assigned] (IGNITE-8256) TxRecoveryStoreEnabledTest.testPessimistic fails on TC

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk reassigned IGNITE-8256:


Assignee: Alexey Goncharuk

> TxRecoveryStoreEnabledTest.testPessimistic fails on TC
> --
>
> Key: IGNITE-8256
> URL: https://issues.apache.org/jira/browse/IGNITE-8256
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>Priority: Major
>
> The reason for the failure is that simulateNodeFailure does not work anymore 
> if failure handler is not a StopNodeFailureHandler



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

[jira] [Commented] (IGNITE-8255) Possible name collisions in WorkersRegistry

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8255:


GitHub user x-kreator opened a pull request:

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

IGNITE-8255: Possible name collisions in WorkersRegistry.



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

$ git pull https://github.com/x-kreator/ignite ignite-8255

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

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


commit cd5805c4e61254bcc9f69ca8d2a1b46115120fbe
Author: Dmitriy Sorokin 
Date:   2018-04-13T14:54:38Z

IGNITE-8255: Possible name collisions in WorkersRegistry.




> Possible name collisions in WorkersRegistry
> ---
>
> Key: IGNITE-8255
> URL: https://issues.apache.org/jira/browse/IGNITE-8255
> Project: Ignite
>  Issue Type: Bug
>Reporter: Dmitriy Sorokin
>Assignee: Dmitriy Sorokin
>Priority: Blocker
>  Labels: iep-14
> Fix For: 2.5
>
>
>  
> {code:java}
> java.lang.IllegalStateException: Worker is already registered 
> [worker=GridWorker [name=ttl-cleanup-worker, igniteInstanceName=null, 
> finished=false, hashCode=612569625, interrupted=true, 
> runner=ttl-cleanup-worker-#66]]
> at 
> org.apache.ignite.internal.worker.WorkersRegistry.register(WorkersRegistry.java:40)
> at 
> org.apache.ignite.internal.worker.WorkersRegistry.onStarted(WorkersRegistry.java:73)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
> at java.lang.Thread.run(Thread.java:748){code}
>  



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

[jira] [Commented] (IGNITE-8013) CPP: Check pending snapshots in BinaryTypeManager::GetHandler

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-8013:


[~isapego], Looks good to me.

> CPP: Check pending snapshots in BinaryTypeManager::GetHandler
> -
>
> Key: IGNITE-8013
> URL: https://issues.apache.org/jira/browse/IGNITE-8013
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
>  Labels: cpp
>
> This will improve performance a lot, when using operations like {{PutAll()}}



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

[jira] [Commented] (IGNITE-8012) CPP: BinaryWriter::WriteElement should accept const reference instead of value.

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-8012:


[~isapego], Looks good to me.

> CPP: BinaryWriter::WriteElement should accept const reference instead of 
> value.
> ---
>
> Key: IGNITE-8012
> URL: https://issues.apache.org/jira/browse/IGNITE-8012
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>Priority: Major
>  Labels: cpp
>
> This will improve performance in case when large objects are used.



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

[jira] [Created] (IGNITE-8255) Possible name collisions in WorkersRegistry

[Dmitriy Sorokin (JIRA)]

Dmitriy Sorokin created IGNITE-8255:
---

 Summary: Possible name collisions in WorkersRegistry
 Key: IGNITE-8255
 URL: https://issues.apache.org/jira/browse/IGNITE-8255
 Project: Ignite
  Issue Type: Bug
Reporter: Dmitriy Sorokin
Assignee: Dmitriy Sorokin
 Fix For: 2.5


 
{code:java}
java.lang.IllegalStateException: Worker is already registered 
[worker=GridWorker [name=ttl-cleanup-worker, igniteInstanceName=null, 
finished=false, hashCode=612569625, interrupted=true, 
runner=ttl-cleanup-worker-#66]]
at 
org.apache.ignite.internal.worker.WorkersRegistry.register(WorkersRegistry.java:40)
at 
org.apache.ignite.internal.worker.WorkersRegistry.onStarted(WorkersRegistry.java:73)
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:108)
at java.lang.Thread.run(Thread.java:748){code}
 



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

[jira] [Commented] (IGNITE-7809) Ignite PDS 2 & PDS 2 Direct IO: stable failures of IgniteWalFlushDefaultSelfTest

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7809:


[~ilantukh] please set status to Patch Available if issue is ready for review

> Ignite PDS 2 & PDS 2 Direct IO: stable failures of 
> IgniteWalFlushDefaultSelfTest
> 
>
> Key: IGNITE-7809
> URL: https://issues.apache.org/jira/browse/IGNITE-7809
> Project: Ignite
>  Issue Type: Task
>  Components: persistence
>Affects Versions: 2.4
>Reporter: Dmitriy Pavlov
>Assignee: Ilya Lantukh
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
>
> Probably after last WAL default changes 'IGNITE-7594 Fixed performance drop 
> after WAL optimization for FSYNC' 2 tests in 2 build configs began to fail
>Ignite PDS 2 (Direct IO) [ tests 2 ]  
>  IgnitePdsNativeIoTestSuite2: 
> IgniteWalFlushDefaultSelfTest.testFailAfterStart (fail rate 13,0%) 
>  IgnitePdsNativeIoTestSuite2: 
> IgniteWalFlushDefaultSelfTest.testFailWhileStart (fail rate 13,0%) 
>Ignite PDS 2 [ tests 2 ]  
>  IgnitePdsTestSuite2: IgniteWalFlushDefaultSelfTest.testFailAfterStart 
> (fail rate 8,4%) 
>  IgnitePdsTestSuite2: IgniteWalFlushDefaultSelfTest.testFailWhileStart 
> (fail rate 8,4%) 



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

[jira] [Commented] (IGNITE-8237) Ignite blocks on SecurityException in exchange-worker due to unauthorised on-heap cache configuration

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8237:


GitHub user kukushal opened a pull request:

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

IGNITE-8237 Ignite blocks on SecurityException in exchange-worker due to 
unauthorised on-heap cache configuration 



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

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

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

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


commit 2821e0411a84245e8ff25b5a58d01a791df84ff7
Author: Alexey Kukushkin 
Date:   2018-04-13T14:29:48Z

IGNITE-8237 Ignite blocks on SecurityException in exchange-worker due to 
unauthorised on-heap cache configuration

commit f1017230c38f96d0be3f3ebe133059761813a602
Author: Alexey Kukushkin 
Date:   2018-04-13T14:30:42Z

Merge remote-tracking branch 'origin/master' into ignite-8237




> Ignite blocks on SecurityException in exchange-worker due to unauthorised 
> on-heap cache configuration 
> --
>
> Key: IGNITE-8237
> URL: https://issues.apache.org/jira/browse/IGNITE-8237
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Alexey Kukushkin
>Assignee: Alexey Kukushkin
>Priority: Blocker
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.5
>
>
> Ignite blocks on SecurityException in exchange-worker due to unauthorised 
> on-heap cache configuration. Consider moving IGNITE_DISABLE_ONHEAP_CACHE 
> system property check to a more appropriate place to avoid blocking Ignite.



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

[jira] [Updated] (IGNITE-7908) NULLS LAST works incorrectly for PARTITIONED caches

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev updated IGNITE-7908:

Priority: Major  (was: Critical)

> NULLS LAST works incorrectly for PARTITIONED caches
> ---
>
> Key: IGNITE-7908
> URL: https://issues.apache.org/jira/browse/IGNITE-7908
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Reporter: Stanislav Lukyanov
>Priority: Major
>
> When a `SELECT  ORDER BY ... NULLS LAST` query is executed on a 
> partitioned cache, the null values at the end of the result are interleaved 
> with non-null values. 
> It seems that for each node participating in the query all null values that 
> are stored on that node are returned immediately after the last non-null 
> value. As a result, non-null values are correctly ordered and null values 
> appear in a few "portions" (the number of "portions" is equal to the number 
> of nodes) among the last values.
> Example:
>  
> {code:java}
> public class NullsLastBug {
> public static void main(String[] args) throws Exception {
> try (
> Ignite srv1 = 
> IgnitionEx.start("examples/config/example-ignite.xml", "server-1");
> Ignite srv2 = 
> IgnitionEx.start("examples/config/example-ignite.xml", "server-2");
> Ignite srv3 = 
> IgnitionEx.start("examples/config/example-ignite.xml", "server-3")
> ) {
> Ignition.setClientMode(true);
> try (Ignite client = 
> IgnitionEx.start("examples/config/example-ignite.xml", "client")) {
> IgniteCache cache = client.getOrCreateCache(
> new CacheConfiguration("cache")
> .setCacheMode(CacheMode.PARTITIONED)
> .setIndexedTypes(Long.class, Box.class)
> );
> for (long i = 0; i < 30; i++) {
> Long num = (i % 2 != 0) ? i : null;
> cache.put(i, new Box(num));
> }
> SqlFieldsQuery selectAll = new SqlFieldsQuery("SELECT num 
> FROM Box ORDER BY num NULLS LAST");
> for (List list : cache.query(selectAll))
> System.out.println(list);
> }
> }
> }
> }
> class Box implements Serializable {
> @QuerySqlField(index = true) private Long num;
> Box(Long num) {
> this.num = num;
> }
> }
> {code}
>  
> Output:
>  
> {code}
>  [1]
>  [3]
>  [5]
>  [7]
>  [9]
>  [11]
>  [13]
>  [15]
>  [17]
>  [19]
>  [21]
>  [23]
>  [null]
>  [null]
>  [25]
>  [27]
>  [null]
>  [null]
>  [null]
>  [null]
>  [null]
>  [null]
>  [null]
>  [null]
>  [29]
>  [null]
>  [null]
>  [null]
>  [null]
>  [null]
> {code}
>  



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

[jira] [Updated] (IGNITE-8254) OSGI test is failed almost everytime IgniteOsgiTestSuite: IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled failed

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-8254:
---
Labels: MakeTeamcityGreenAgain Muted_test  (was: MakeTeamcityGreenAgain)

> OSGI test is failed almost everytime IgniteOsgiTestSuite: 
> IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled  
> failed
> --
>
> Key: IGNITE-8254
> URL: https://issues.apache.org/jira/browse/IGNITE-8254
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain, Muted_test
>
> Test related to OSGI/Karaf 
> (IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled)
>  is currently failing 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=451522206339372479=%3Cdefault%3E=testDetails
>   with low success rate.
> Recently Igniters have done 2 fixes for make this test passing 
> (https://issues.apache.org/jira/browse/IGNITE-7646 , 
> https://issues.apache.org/jira/browse/IGNITE-7814 ) but test is failing 
> anyway.



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

[jira] [Created] (IGNITE-8254) OSGI test is failed almost everytime IgniteOsgiTestSuite: IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled failed

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-8254:
--

 Summary: OSGI test is failed almost everytime IgniteOsgiTestSuite: 
IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled  
failed
 Key: IGNITE-8254
 URL: https://issues.apache.org/jira/browse/IGNITE-8254
 Project: Ignite
  Issue Type: Test
Reporter: Dmitriy Pavlov


Test related to OSGI/Karaf 
(IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled) 
is currently failing 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=451522206339372479=%3Cdefault%3E=testDetailswith
 low success rate.

Recently Igniters have done 2 fixes for make this test passing 
(https://issues.apache.org/jira/browse/IGNITE-7646 , 
https://issues.apache.org/jira/browse/IGNITE-7814 ) but test is failing anyway.




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

[jira] [Updated] (IGNITE-8254) OSGI test is failed almost everytime IgniteOsgiTestSuite: IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled failed

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov updated IGNITE-8254:
---
Description: 
Test related to OSGI/Karaf 
(IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled) 
is currently failing 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=451522206339372479=%3Cdefault%3E=testDetails
  with low success rate.

Recently Igniters have done 2 fixes for make this test passing 
(https://issues.apache.org/jira/browse/IGNITE-7646 , 
https://issues.apache.org/jira/browse/IGNITE-7814 ) but test is failing anyway.


  was:
Test related to OSGI/Karaf 
(IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled) 
is currently failing 
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=451522206339372479=%3Cdefault%3E=testDetailswith
 low success rate.

Recently Igniters have done 2 fixes for make this test passing 
(https://issues.apache.org/jira/browse/IGNITE-7646 , 
https://issues.apache.org/jira/browse/IGNITE-7814 ) but test is failing anyway.



> OSGI test is failed almost everytime IgniteOsgiTestSuite: 
> IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled  
> failed
> --
>
> Key: IGNITE-8254
> URL: https://issues.apache.org/jira/browse/IGNITE-8254
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Test related to OSGI/Karaf 
> (IgniteKarafFeaturesInstallationTest.testAllBundlesActiveAndFeaturesInstalled)
>  is currently failing 
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=451522206339372479=%3Cdefault%3E=testDetails
>   with low success rate.
> Recently Igniters have done 2 fixes for make this test passing 
> (https://issues.apache.org/jira/browse/IGNITE-7646 , 
> https://issues.apache.org/jira/browse/IGNITE-7814 ) but test is failing 
> anyway.



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

[jira] [Commented] (IGNITE-8253) CacheConfiguration.keyConfiguration is never documented

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev commented on IGNITE-8253:
-

Should probably go here:
https://apacheignite.readme.io/docs/affinity-collocation

> CacheConfiguration.keyConfiguration is never documented
> ---
>
> Key: IGNITE-8253
> URL: https://issues.apache.org/jira/browse/IGNITE-8253
> Project: Ignite
>  Issue Type: Improvement
>  Components: documentation
>Affects Versions: 2.4
>Reporter: Ilya Kasnacheev
>Priority: Major
>
> See 
> http://apache-ignite-users.70518.x6.nabble.com/How-do-you-configure-affinityKey-in-xml-tp21165.html



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

[jira] [Created] (IGNITE-8253) CacheConfiguration.keyConfiguration is never documented

[Ilya Kasnacheev (JIRA)]

Ilya Kasnacheev created IGNITE-8253:
---

 Summary: CacheConfiguration.keyConfiguration is never documented
 Key: IGNITE-8253
 URL: https://issues.apache.org/jira/browse/IGNITE-8253
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Affects Versions: 2.4
Reporter: Ilya Kasnacheev


See 
http://apache-ignite-users.70518.x6.nabble.com/How-do-you-configure-affinityKey-in-xml-tp21165.html




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

[jira] [Commented] (IGNITE-6908) Check PartitionLossPolicy during a cluster activation

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-6908:
--

I do not think we should fire LOST events if we activate a cluster and some 
partitions are fully mapped on offline nodes. All cache operations will throw 
an exception in such case, which is expected behavior.

LOST event should be fired if we reduce baseline topology, which I believe is 
the current behavior.

Will close the ticket if there are no objections from community.

> Check PartitionLossPolicy during a cluster activation 
> --
>
> Key: IGNITE-6908
> URL: https://issues.apache.org/jira/browse/IGNITE-6908
> Project: Ignite
>  Issue Type: New Feature
>  Components: persistence
>Reporter: Sergey Puchnin
>Priority: Major
>  Labels: IEP-4
> Fix For: 2.5
>
>
> During a cluster activation from not full BLT, we should check if a partition 
> lost policy is respected.



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

[jira] [Commented] (IGNITE-7791) Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7791:


[~Mmuzaf], please check 
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_LicensesHeaders=pull%2F3779%2Fhead=buildTypeStatusDiv
and its artifacts. There is link to file with incorrect header:
 
/data/teamcity/work/8241162b5ce21231/modules/core/src/test/java/org/apache/ignite/internal/IgniteClientReconnectDelayedSpiTest.java


I've restarted also 
Binary Objects (Simple Mapper Queries) 
because it had suspicious test failure.

> Ignite Client Nodes: failed test 
> IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
> ---
>
> Key: IGNITE-7791
> URL: https://issues.apache.org/jira/browse/IGNITE-7791
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Maxim Muzafarov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
> Attachments: IgniteClientReconnectCacheDelayExchangeTest.java
>
>
> Test is flaky, success rate: 32.4%, test history is 
> [here|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9174769196124217030=testDetails]
> Reproducible locally.
> Test fails on waiting for disco cache content:
> {noformat}
> junit.framework.AssertionFailedError
>   at junit.framework.Assert.fail(Assert.java:55)
>   at junit.framework.Assert.assertTrue(Assert.java:22)
>   at junit.framework.Assert.assertTrue(Assert.java:31)
>   at junit.framework.TestCase.assertTrue(TestCase.java:201)
>   at 
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.checkCacheDiscoveryData(IgniteClientReconnectCacheTest.java:1414)
>   at 
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated(IgniteClientReconnectCacheTest.java:897)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This fail may be caused by another exception earlier in the log:
> {noformat}
> [2018-02-22 
> 14:32:57,972][ERROR][exchange-worker-#3025%internal.IgniteClientReconnectCacheTest3%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=6, 
> minorTopVer=1], discoEvt=DiscoveryCustomEvent 
> [customMsg=CacheAffinityChangeMessage 
> [id=3cea94db161-760b7b18-b776-4ee7-ae5a-64f9494eaa36, 
> topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], exchId=null, 
> partsMsg=null, exchangeNeeded=true], affTopVer=AffinityTopologyVersion 
> [topVer=6, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
> [id=1b7f7330-69d8-4bd0-b2e9-71773610, addrs=[127.0.0.1], 
> sockAddrs=[/127.0.0.1:47500], discPort=47500, order=1, intOrder=1, 
> lastExchangeTime=1519299177395, loc=false, ver=2.5.0#19700101-sha1:, 
> isClient=false], topVer=6, nodeId8=658aeb36, msg=null, 
> type=DISCOVERY_CUSTOM_EVT, tstamp=1519299177971]], nodeId=1b7f7330, 
> evt=DISCOVERY_CUSTOM_EVT]
> java.lang.AssertionError: 236160867
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$CachesInfo.group(CacheAffinitySharedManager.java:2636)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:989)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:983)
>   at 
> org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllCacheGroups(CacheAffinitySharedManager.java:1118)
>   at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onChangeAffinityMessage(CacheAffinitySharedManager.java:983)
>   at 
> 

[jira] [Commented] (IGNITE-8169) [ML] Adopt KMeans to the new Partitioned Dataset and cleanup old code

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8169:


GitHub user zaleslaw opened a pull request:

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

IGNITE-8169: Adopt KMeans and remove FuzzyCMeans



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

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

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

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


commit 897de46fec2b5474f39b0a3c232e1fdb43a51ab9
Author: zaleslaw 
Date:   2018-04-07T13:44:19Z

Added KMeans

commit 2d1763253a84447f0421afd23d01f27762fc61ee
Author: zaleslaw 
Date:   2018-04-10T08:24:25Z

Added KMeans

commit 5f5e9c9565fab39b17afc168ea9cdd6c31ee613e
Author: Zinoviev Alexey 
Date:   2018-04-11T18:32:39Z

Fixed KMeans

commit 64c09cbf962d6001b5cbad2f9556dd2be6bc3e3f
Author: zaleslaw 
Date:   2018-04-13T06:32:12Z

IGNITE-7829: Fixed tests

commit 5e5681c0e6db6540685bf27bfc7afc32856cbdce
Author: Zinoviev Alexey 
Date:   2018-04-13T12:54:55Z

IGNITE-7829: Fixed Trainer and cleaned up the cluster package

commit 269266785fb330283df4f13a6383e97288a074ce
Author: Zinoviev Alexey 
Date:   2018-04-13T13:17:22Z

IGNITE-7829: Added seed




> [ML] Adopt KMeans to the new Partitioned Dataset and cleanup old code
> -
>
> Key: IGNITE-8169
> URL: https://issues.apache.org/jira/browse/IGNITE-8169
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Aleksey Zinoviev
>Assignee: Aleksey Zinoviev
>Priority: Major
>




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

[jira] [Commented] (IGNITE-7791) Ignite Client Nodes: failed test IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()

[Maxim Muzafarov (JIRA)]

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

Maxim Muzafarov commented on IGNITE-7791:
-

[~agoncharuk], 
 
 As part of implementation of [IEP-4 Baseline topology for 
caches|https://cwiki.apache.org/confluence/display/IGNITE/IEP-4+Baseline+topology+for+caches]
 and IGNITE-7308 the new {{LocalJoinCachesContext}} class was introduced. This 
context used to capture caches state for a node joining to an active cluster 
and pass it to the exchange thread. 
 
 In my opinion, we should not perform caches info removing from captured state 
on reconnect event happened. It leads to incorrect 
{{CacheAffinityChangeMessage}} message processing after client node reconnects. 
Could you, please, look at my [Pull Request 
#3779|https://github.com/apache/ignite/pull/3779] and share your thoughts?
 100% {{testReconnectCacheDestroyedWithDelayedSpiMsgs}} reproducer also 
included to this PR and passed due to these changes. 
 
||Profile||Test||Status||
|Cache (Failover) 
[1]|[testReconnectCacheDestroyedAndCreated|https://ci.ignite.apache.org/viewLog.html?buildId=1196532=IgniteTests24Java8_CacheFailover1=testsInfo]|(/)
 OK ~(200 runs)~|
|Client 
Nodes|[testReconnectCacheDestroyedWithDelayedSpiMsgs|https://ci.ignite.apache.org/viewLog.html?currentGroup=test=org.apache.ignite.testsuites.IgniteClientNodesTestSuite%23teamcity%23org.apache.ignite.internal%23teamcity%23IgniteClientReconnectDelayedSpiTest=1=DURATION_DESC=20===IgniteTests24Java8_ClientNodes=1192536=testsInfo]
 _newly added_|(/) OK|
|Client 
Nodes|[IgniteClientNodesTestSuite|https://ci.ignite.apache.org/viewLog.html?buildId=1192536=buildResultsDiv=IgniteTests24Java8_ClientNodes]|(/)
 OK ~Tests passed: 72~|
|Run :: All|[#1142 (11 Apr 18 
19:15)|https://ci.ignite.apache.org/viewLog.html?buildId=1192255] _NO new fails 
due to changes of PR_|(x) FAIL ~19 test failed(18 new)~|

> Ignite Client Nodes: failed test 
> IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated()
> ---
>
> Key: IGNITE-7791
> URL: https://issues.apache.org/jira/browse/IGNITE-7791
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Maxim Muzafarov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
> Fix For: 2.6
>
> Attachments: IgniteClientReconnectCacheDelayExchangeTest.java
>
>
> Test is flaky, success rate: 32.4%, test history is 
> [here|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9174769196124217030=testDetails]
> Reproducible locally.
> Test fails on waiting for disco cache content:
> {noformat}
> junit.framework.AssertionFailedError
>   at junit.framework.Assert.fail(Assert.java:55)
>   at junit.framework.Assert.assertTrue(Assert.java:22)
>   at junit.framework.Assert.assertTrue(Assert.java:31)
>   at junit.framework.TestCase.assertTrue(TestCase.java:201)
>   at 
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.checkCacheDiscoveryData(IgniteClientReconnectCacheTest.java:1414)
>   at 
> org.apache.ignite.internal.IgniteClientReconnectCacheTest.testReconnectCacheDestroyedAndCreated(IgniteClientReconnectCacheTest.java:897)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2001)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:133)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1916)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> This fail may be caused by another exception earlier in the log:
> {noformat}
> [2018-02-22 
> 14:32:57,972][ERROR][exchange-worker-#3025%internal.IgniteClientReconnectCacheTest3%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=6, 
> minorTopVer=1], discoEvt=DiscoveryCustomEvent 
> [customMsg=CacheAffinityChangeMessage 
> [id=3cea94db161-760b7b18-b776-4ee7-ae5a-64f9494eaa36, 
> topVer=AffinityTopologyVersion [topVer=3, minorTopVer=0], exchId=null, 
> partsMsg=null, exchangeNeeded=true], affTopVer=AffinityTopologyVersion 
> [topVer=6, minorTopVer=1], super=DiscoveryEvent [evtNode=TcpDiscoveryNode 
> 

[jira] [Commented] (IGNITE-8048) Dynamic indexes are not stored to cache data on node join

[Anton Kalashnikov (JIRA)]

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

Anton Kalashnikov commented on IGNITE-8048:
---

Thank you, Eduard. I fixed you notes in upsource, also I added couple test for  
inlineSize and saving config.

But I didn't add tests from your table because I can't reproduce it because  it 
is invalid state by baseline topoligy(branching history hash conflict) .

> Dynamic indexes are not stored to cache data on node join
> -
>
> Key: IGNITE-8048
> URL: https://issues.apache.org/jira/browse/IGNITE-8048
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.4
>Reporter: Alexey Goncharuk
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.5
>
> Attachments: IgniteDynamicIndexRestoreTest.java
>
>
> Consider the following scenario:
> 1) Start nodes, add some data
> 2) Shutdown a node, create a dynamic index
> 3) Shutdown the whole cluster, startup with the absent node, activate from 
> the absent node
> 4) Since the absent node did not 'see' the create index, index will not be 
> active after cluster activation
> 5) Update some data in the cluster
> 6) Restart the cluster, but activate from the node which did 'see' the create 
> index
> 7) Attempt to update data. Depending on the updates in (5), this will either 
> hang or result in an exception



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

[jira] [Assigned] (IGNITE-7778) User's authentication data must be persisted on cluster with disabled persistence

[Taras Ledkov (JIRA)]

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

Taras Ledkov reassigned IGNITE-7778:


Assignee: Taras Ledkov

> User's authentication data must be persisted on cluster with disabled 
> persistence
> -
>
> Key: IGNITE-7778
> URL: https://issues.apache.org/jira/browse/IGNITE-7778
> Project: Ignite
>  Issue Type: Task
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
>Priority: Major
>
> The ticket is related to the: IGNITE-7436 (introduce users in Ignite)
> {{IgniteAuthenticationProcessor}} uses metastorage to persist user data. But 
> metastorage works only with persistent cluster. We have to support user 
> authentication for in-memory cluster.



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

[jira] [Commented] (IGNITE-7918) Huge memory leak when data streamer used together with local cache

[Andrey Aleksandrov (JIRA)]

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

Andrey Aleksandrov commented on IGNITE-7918:


[~agoncharuk] In current case with this fix the size of this map should not be 
bigger then IGNITE_AFFINITY_HISTORY_SIZE value. Yes it could be changed to 
ConcurrentSkipListMap  as you mentioned for avoiding of the full iteration over 
the affMap. Thank you!

> Huge memory leak when data streamer used together with local cache
> --
>
> Key: IGNITE-7918
> URL: https://issues.apache.org/jira/browse/IGNITE-7918
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Zbyszek B
>Assignee: Andrey Aleksandrov
>Priority: Major
> Fix For: 2.5
>
> Attachments: Demo.java, MemLeak-Ignite.png, MemLeak-Ignite.txt
>
>
> Dear Igniters,
> We observe huge memory leak when data streamer used together with local cache.
> In the attached demo producer produces local cache with single binary object 
> and passes this to the queue. Consumer picks up the cache from the queue, 
> constructs different binary object from it, adds it to global partitioned 
> cache and destroys local cache.
> This design causes a significant leak - the whole heap is used within minutes 
> (no matter if this is 4G or 24G).
>  
>  



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

[jira] [Created] (IGNITE-8252) NullPointerException is thrown during parallel massive start of nodes

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-8252:
---

 Summary: NullPointerException is thrown during parallel massive 
start of nodes
 Key: IGNITE-8252
 URL: https://issues.apache.org/jira/browse/IGNITE-8252
 Project: Ignite
  Issue Type: Bug
  Components: zookeeper
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov


When many nodes are started in parallel and IGNITE_DISCOVERY_HISTORY_SIZE is 
set to too small value (smaller than size of batch of nodes joining the cluster 
simultaneously) NPE is thrown from the exchange thread:
{noformat}
[ERROR][exchange-worker-#62][GridDhtPartitionsExchangeFuture] Failed to 
reinitialize local partitions (preloading will be stopped): 
GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=5, 
minorTopVer=0], discoEvt=DiscoveryEvent [evtNode=ZookeeperClusterNode 
[id=2f412f7f-d326-4303-86f9-91004c82aa7b, addrs=[172.25.1.18], order=5, 
loc=true, client=false], topVer=5, nodeId8=2f412f7f, msg=null, 
type=NODE_JOINED, tstamp=1523571878505], nodeId=2f412f7f, evt=NODE_JOINED]
java.lang.NullPointerException: null
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.latch.ExchangeLatchManager.getLatchCoordinator(ExchangeLatchManager.java:249)
 ~[ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.latch.ExchangeLatchManager.getOrCreate(ExchangeLatchManager.java:207)
 ~[ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.waitPartitionRelease(GridDhtPartitionsExchangeFuture.java:1227)
 ~[ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1112)
 ~[ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:713)
 [ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2414)
 [ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2294)
 [ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
[ignite-core-2.5.0-SNAPSHOT.jar:2.5.0-SNAPSHOT]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_161]
{noformat}



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

[jira] [Commented] (IGNITE-7681) SQL COPY: local performance improvements

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-7681:
--

I guess the patch is not ready.
The implementation depends on IGNITE-7537 implemetation and conflicts with it.
I propose to close the issue and tune performance as part of the IGNITE-7537 
refactoring.

> SQL COPY: local performance improvements
> 
>
> Key: IGNITE-7681
> URL: https://issues.apache.org/jira/browse/IGNITE-7681
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.4, 2.5
>Reporter: Kirill Shirokov
>Assignee: Taras Ledkov
>Priority: Major
> Attachments: ignite-7681-cache-putall-processor.diff, 
> ignite-7681-perf-test.diff
>
>




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

[jira] [Comment Edited] (IGNITE-7681) SQL COPY: local performance improvements

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-7681 at 4/13/18 12:41 PM:


[~vozerov]
I guess the patch is not ready.
The implementation depends on IGNITE-7537 implemetation and conflicts with it.
I propose to close the issue and tune performance as part of the IGNITE-7537 
refactoring.


was (Author: tledkov-gridgain):
I guess the patch is not ready.
The implementation depends on IGNITE-7537 implemetation and conflicts with it.
I propose to close the issue and tune performance as part of the IGNITE-7537 
refactoring.

> SQL COPY: local performance improvements
> 
>
> Key: IGNITE-7681
> URL: https://issues.apache.org/jira/browse/IGNITE-7681
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.4, 2.5
>Reporter: Kirill Shirokov
>Assignee: Taras Ledkov
>Priority: Major
> Attachments: ignite-7681-cache-putall-processor.diff, 
> ignite-7681-perf-test.diff
>
>




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

[jira] [Created] (IGNITE-8251) Reduce testPageEviction run time

[Dmitriy Pavlov (JIRA)]

Dmitriy Pavlov created IGNITE-8251:
--

 Summary: Reduce testPageEviction run time
 Key: IGNITE-8251
 URL: https://issues.apache.org/jira/browse/IGNITE-8251
 Project: Ignite
  Issue Type: Test
  Components: persistence
Reporter: Dmitriy Pavlov


Cache 3 and suite IgniteBinaryObjectsCacheTestSuite3 several times executes one 
test testPageEviction  and each run requires significiant time.

RandomLruNearEnabledPageEvictionMultinodeTest.testPageEviction duration 6m 
9.41s 
 Random2LruNearEnabledPageEvictionMultinodeTest.testPageEviction duration 5m 
51.353s 
 RandomLruPageEvictionMultinodeTest.testPageEviction duration 5m 36.529s 

It is necessary to understand what exactly the test does and shorten the 
execution time by 
- reducing the number of objects 
- the region size 
- the desired run time. 

Or some other parameter which help to run this test faster.

At the same time, it is necessary to leave the test coverage unchanged.



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

[jira] [Assigned] (IGNITE-8089) Cache group presence assertion failed in (PM) exchange in IgniteStandByClientReconnectToNewClusterTest

[Andrey Kuznetsov (JIRA)]

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

Andrey Kuznetsov reassigned IGNITE-8089:


Assignee: Andrey Kuznetsov

> Cache group presence assertion failed in (PM) exchange in 
> IgniteStandByClientReconnectToNewClusterTest
> --
>
> Key: IGNITE-8089
> URL: https://issues.apache.org/jira/browse/IGNITE-8089
> Project: Ignite
>  Issue Type: Test
>Reporter: Dmitriy Pavlov
>Assignee: Andrey Kuznetsov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> IgniteStandByClusterSuite: 
> IgniteStandByClientReconnectToNewClusterTest.testActiveClientReconnectToActiveCluster
>  (master fail rate 11,3%)
> https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-3118895430102702001=%3Cdefault%3E=testDetails
> {noformat}
> java.lang.AssertionError: -2100569601
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$CachesInfo.group(CacheAffinitySharedManager.java:2636)
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:989)
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager$8.applyx(CacheAffinitySharedManager.java:983)
> at 
> org.apache.ignite.internal.util.lang.IgniteInClosureX.apply(IgniteInClosureX.java:38)
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.forAllCacheGroups(CacheAffinitySharedManager.java:1118)
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onChangeAffinityMessage(CacheAffinitySharedManager.java:983)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onAffinityChangeRequest(GridDhtPartitionsExchangeFuture.java:1003)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:648)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2344)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {noformat}



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

[jira] [Assigned] (IGNITE-5976) [Test Failed] IgniteClientDiscoveryDataStructuresTest.testReentrantLock

[Ivan Fedotov (JIRA)]

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

Ivan Fedotov reassigned IGNITE-5976:


Assignee: Ivan Fedotov

> [Test Failed]  IgniteClientDiscoveryDataStructuresTest.testReentrantLock
> 
>
> Key: IGNITE-5976
> URL: https://issues.apache.org/jira/browse/IGNITE-5976
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Eduard Shangareev
>Assignee: Ivan Fedotov
>Priority: Major
>  Labels: MakeTeamcityGreenAgain
>
> Fails locally.
> Example of failing 
> http://ci.ignite.apache.org/viewLog.html?buildId=758964=buildResultsDiv=Ignite20Tests_IgniteDataStrucutures#testNameId4310032017507935311.



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

[jira] [Commented] (IGNITE-7918) Huge memory leak when data streamer used together with local cache

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7918:


[~aealeksandrov], if you're agree with notes, please set InProgress status.

> Huge memory leak when data streamer used together with local cache
> --
>
> Key: IGNITE-7918
> URL: https://issues.apache.org/jira/browse/IGNITE-7918
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Zbyszek B
>Assignee: Andrey Aleksandrov
>Priority: Major
> Fix For: 2.5
>
> Attachments: Demo.java, MemLeak-Ignite.png, MemLeak-Ignite.txt
>
>
> Dear Igniters,
> We observe huge memory leak when data streamer used together with local cache.
> In the attached demo producer produces local cache with single binary object 
> and passes this to the queue. Consumer picks up the cache from the queue, 
> constructs different binary object from it, adds it to global partitioned 
> cache and destroys local cache.
> This design causes a significant leak - the whole heap is used within minutes 
> (no matter if this is 4G or 24G).
>  
>  



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

[jira] [Updated] (IGNITE-8169) [ML] Adopt KMeans to the new Partitioned Dataset and cleanup old code

[Aleksey Zinoviev (JIRA)]

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

Aleksey Zinoviev updated IGNITE-8169:
-
Summary: [ML] Adopt KMeans to the new Partitioned Dataset and cleanup old 
code  (was: [ML] Implement Model-Trainer pair for KMeans based on Partitioned 
Dataset)

> [ML] Adopt KMeans to the new Partitioned Dataset and cleanup old code
> -
>
> Key: IGNITE-8169
> URL: https://issues.apache.org/jira/browse/IGNITE-8169
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Aleksey Zinoviev
>Assignee: Aleksey Zinoviev
>Priority: Major
>




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

[jira] [Created] (IGNITE-8250) Adopt Fuzzy CMeans to PartitionedDatasets

[Aleksey Zinoviev (JIRA)]

Aleksey Zinoviev created IGNITE-8250:


 Summary: Adopt Fuzzy CMeans to PartitionedDatasets
 Key: IGNITE-8250
 URL: https://issues.apache.org/jira/browse/IGNITE-8250
 Project: Ignite
  Issue Type: Improvement
  Components: ml
Reporter: Aleksey Zinoviev
Assignee: Aleksey Zinoviev






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

[jira] [Created] (IGNITE-8249) Web Console: Convert first letter case for all the inputs

[Vica Abramova (JIRA)]

Vica Abramova created IGNITE-8249:
-

 Summary: Web Console: Convert first letter case for all the inputs
 Key: IGNITE-8249
 URL: https://issues.apache.org/jira/browse/IGNITE-8249
 Project: Ignite
  Issue Type: Improvement
  Components: UI, wizards
Reporter: Vica Abramova
Assignee: Alexey Kuznetsov


We should begin all words with a capital letter (inputs/placeholders).



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

[jira] [Commented] (IGNITE-8048) Dynamic indexes are not stored to cache data on node join

[Eduard Shangareev (JIRA)]

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

Eduard Shangareev commented on IGNITE-8048:
---

Also, I guess, that we have a necessity to have a test where we re-create index 
where *only* inlineSize differs.

> Dynamic indexes are not stored to cache data on node join
> -
>
> Key: IGNITE-8048
> URL: https://issues.apache.org/jira/browse/IGNITE-8048
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.4
>Reporter: Alexey Goncharuk
>Assignee: Anton Kalashnikov
>Priority: Major
> Fix For: 2.5
>
> Attachments: IgniteDynamicIndexRestoreTest.java
>
>
> Consider the following scenario:
> 1) Start nodes, add some data
> 2) Shutdown a node, create a dynamic index
> 3) Shutdown the whole cluster, startup with the absent node, activate from 
> the absent node
> 4) Since the absent node did not 'see' the create index, index will not be 
> active after cluster activation
> 5) Update some data in the cluster
> 6) Restart the cluster, but activate from the node which did 'see' the create 
> index
> 7) Attempt to update data. Depending on the updates in (5), this will either 
> hang or result in an exception



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

[jira] [Updated] (IGNITE-8247) .NET: ICacheLock.TryEnter() returns false if client is disconnected

[Roman Guseinov (JIRA)]

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

Roman Guseinov updated IGNITE-8247:
---
Attachment: TryEnterIssue.cs

> .NET: ICacheLock.TryEnter() returns false if client is disconnected
> ---
>
> Key: IGNITE-8247
> URL: https://issues.apache.org/jira/browse/IGNITE-8247
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Roman Guseinov
>Priority: Major
>  Labels: dot_net
> Attachments: TryEnterIssue.cs
>
>
> It seems that TryEnter() doesn't propagate an 
> IgniteClientDisconnectedException from Java to .NET.
> Reproducer is attached.



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

[jira] [Updated] (IGNITE-8247) .NET: ICacheLock.TryEnter() returns false if client is disconnected

[Roman Guseinov (JIRA)]

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

Roman Guseinov updated IGNITE-8247:
---
Attachment: (was: TryEnterIssue.cs)

> .NET: ICacheLock.TryEnter() returns false if client is disconnected
> ---
>
> Key: IGNITE-8247
> URL: https://issues.apache.org/jira/browse/IGNITE-8247
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Roman Guseinov
>Priority: Major
>  Labels: dot_net
>
> It seems that TryEnter() doesn't propagate an 
> IgniteClientDisconnectedException from Java to .NET.
> Reproducer is attached.



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

[jira] [Updated] (IGNITE-8032) Fix issues within TX DML reducer.

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov updated IGNITE-8032:
---
Component/s: sql

> Fix issues within TX DML reducer.
> -
>
> Key: IGNITE-8032
> URL: https://issues.apache.org/jira/browse/IGNITE-8032
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Reporter: Sergey Kalashnikov
>Assignee: Sergey Kalashnikov
>Priority: Major
>
> The following code review issues need to be addressed:
> 1. GridNearTxQueryResultsEnlistFuture
> 1.1. remove GridCacheCompoundIdentityFuture implementation.
> remote mini-futures.
> 1.2  Improve concurrency around sendNextBatches calls.
> 2. Refactor iterator UpdateIteratorAdapter/TxDmlReducerIterator to avoid 
> multi-level nesting.
> 3. Normalize usage of IgniteBiTuple(k,v)/Object(key) instead of Object[] to 
> represent rows.



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

[jira] [Comment Edited] (IGNITE-8248) Web Console: NullPointException in agent in case of self-signed certificates.

[Andrey Novikov (JIRA)]

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

Andrey Novikov edited comment on IGNITE-8248 at 4/13/18 11:09 AM:
--

Fixed. Merged to master.


was (Author: anovikov):
Fixed.

> Web Console: NullPointException in agent in case of self-signed certificates.
> -
>
> Key: IGNITE-8248
> URL: https://issues.apache.org/jira/browse/IGNITE-8248
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.4
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
>Priority: Major
> Fix For: 2.5
>
>
> [2018-04-13 02:01:12,387][ERROR][EventThread][EventThread] Task threw 
> exception
> java.lang.NullPointerException
> at 
> okhttp3.internal.tls.TrustRootIndex$BasicTrustRootIndex.(TrustRootIndex.java:108)
> at okhttp3.internal.tls.TrustRootIndex.get(TrustRootIndex.java:48)
> at okhttp3.internal.tls.TrustRootIndex.get(TrustRootIndex.java:43)
> at 
> okhttp3.internal.platform.Platform.buildCertificateChainCleaner(Platform.java:167)
> at 
> okhttp3.internal.tls.CertificateChainCleaner.get(CertificateChainCleaner.java:41)
> at okhttp3.OkHttpClient$Builder.sslSocketFactory(OkHttpClient.java:656)
> at io.socket.engineio.client.transports.WebSocket.doOpen(WebSocket.java:50)
> at io.socket.engineio.client.Transport$1.run(Transport.java:82)
> at io.socket.thread.EventThread.exec(EventThread.java:55)
> at io.socket.engineio.client.Transport.open(Transport.java:77)
> at io.socket.engineio.client.Socket.probe(Socket.java:472)
> at io.socket.engineio.client.Socket.onOpen(Socket.java:485)
> at io.socket.engineio.client.Socket.onHandshake(Socket.java:526)
> at io.socket.engineio.client.Socket.onPacket(Socket.java:499)
> at io.socket.engineio.client.Socket.access$1000(Socket.java:31)
> at io.socket.engineio.client.Socket$5.call(Socket.java:313)
> at io.socket.emitter.Emitter.emit(Emitter.java:117)
> at io.socket.engineio.client.Transport.onPacket(Transport.java:134)
> at io.socket.engineio.client.transports.Polling.access$700(Polling.java:17)
> at io.socket.engineio.client.transports.Polling$2.call(Polling.java:124)
> at io.socket.engineio.parser.Parser.decodePayload(Parser.java:251)
> at io.socket.engineio.client.transports.Polling._onData(Polling.java:134)
> at io.socket.engineio.client.transports.Polling.onData(Polling.java:106)
> at 
> io.socket.engineio.client.transports.PollingXHR$5$1.run(PollingXHR.java:111)
> at io.socket.thread.EventThread$2.run(EventThread.java:80)
> 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)
>  



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

[jira] [Closed] (IGNITE-8248) Web Console: NullPointException in agent in case of self-signed certificates.

[Andrey Novikov (JIRA)]

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

Andrey Novikov closed IGNITE-8248.
--

> Web Console: NullPointException in agent in case of self-signed certificates.
> -
>
> Key: IGNITE-8248
> URL: https://issues.apache.org/jira/browse/IGNITE-8248
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.4
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
>Priority: Major
> Fix For: 2.5
>
>
> [2018-04-13 02:01:12,387][ERROR][EventThread][EventThread] Task threw 
> exception
> java.lang.NullPointerException
> at 
> okhttp3.internal.tls.TrustRootIndex$BasicTrustRootIndex.(TrustRootIndex.java:108)
> at okhttp3.internal.tls.TrustRootIndex.get(TrustRootIndex.java:48)
> at okhttp3.internal.tls.TrustRootIndex.get(TrustRootIndex.java:43)
> at 
> okhttp3.internal.platform.Platform.buildCertificateChainCleaner(Platform.java:167)
> at 
> okhttp3.internal.tls.CertificateChainCleaner.get(CertificateChainCleaner.java:41)
> at okhttp3.OkHttpClient$Builder.sslSocketFactory(OkHttpClient.java:656)
> at io.socket.engineio.client.transports.WebSocket.doOpen(WebSocket.java:50)
> at io.socket.engineio.client.Transport$1.run(Transport.java:82)
> at io.socket.thread.EventThread.exec(EventThread.java:55)
> at io.socket.engineio.client.Transport.open(Transport.java:77)
> at io.socket.engineio.client.Socket.probe(Socket.java:472)
> at io.socket.engineio.client.Socket.onOpen(Socket.java:485)
> at io.socket.engineio.client.Socket.onHandshake(Socket.java:526)
> at io.socket.engineio.client.Socket.onPacket(Socket.java:499)
> at io.socket.engineio.client.Socket.access$1000(Socket.java:31)
> at io.socket.engineio.client.Socket$5.call(Socket.java:313)
> at io.socket.emitter.Emitter.emit(Emitter.java:117)
> at io.socket.engineio.client.Transport.onPacket(Transport.java:134)
> at io.socket.engineio.client.transports.Polling.access$700(Polling.java:17)
> at io.socket.engineio.client.transports.Polling$2.call(Polling.java:124)
> at io.socket.engineio.parser.Parser.decodePayload(Parser.java:251)
> at io.socket.engineio.client.transports.Polling._onData(Polling.java:134)
> at io.socket.engineio.client.transports.Polling.onData(Polling.java:106)
> at 
> io.socket.engineio.client.transports.PollingXHR$5$1.run(PollingXHR.java:111)
> at io.socket.thread.EventThread$2.run(EventThread.java:80)
> 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)
>  



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

[jira] [Created] (IGNITE-8248) Web Console: NullPointException in agent in case of self-signed certificates.

[Andrey Novikov (JIRA)]

Andrey Novikov created IGNITE-8248:
--

 Summary: Web Console: NullPointException in agent in case of 
self-signed certificates.
 Key: IGNITE-8248
 URL: https://issues.apache.org/jira/browse/IGNITE-8248
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Reporter: Andrey Novikov
Assignee: Andrey Novikov


[2018-04-13 02:01:12,387][ERROR][EventThread][EventThread] Task threw exception

java.lang.NullPointerException

at 
okhttp3.internal.tls.TrustRootIndex$BasicTrustRootIndex.(TrustRootIndex.java:108)

at okhttp3.internal.tls.TrustRootIndex.get(TrustRootIndex.java:48)

at okhttp3.internal.tls.TrustRootIndex.get(TrustRootIndex.java:43)

at 
okhttp3.internal.platform.Platform.buildCertificateChainCleaner(Platform.java:167)

at 
okhttp3.internal.tls.CertificateChainCleaner.get(CertificateChainCleaner.java:41)

at okhttp3.OkHttpClient$Builder.sslSocketFactory(OkHttpClient.java:656)

at io.socket.engineio.client.transports.WebSocket.doOpen(WebSocket.java:50)

at io.socket.engineio.client.Transport$1.run(Transport.java:82)

at io.socket.thread.EventThread.exec(EventThread.java:55)

at io.socket.engineio.client.Transport.open(Transport.java:77)

at io.socket.engineio.client.Socket.probe(Socket.java:472)

at io.socket.engineio.client.Socket.onOpen(Socket.java:485)

at io.socket.engineio.client.Socket.onHandshake(Socket.java:526)

at io.socket.engineio.client.Socket.onPacket(Socket.java:499)

at io.socket.engineio.client.Socket.access$1000(Socket.java:31)

at io.socket.engineio.client.Socket$5.call(Socket.java:313)

at io.socket.emitter.Emitter.emit(Emitter.java:117)

at io.socket.engineio.client.Transport.onPacket(Transport.java:134)

at io.socket.engineio.client.transports.Polling.access$700(Polling.java:17)

at io.socket.engineio.client.transports.Polling$2.call(Polling.java:124)

at io.socket.engineio.parser.Parser.decodePayload(Parser.java:251)

at io.socket.engineio.client.transports.Polling._onData(Polling.java:134)

at io.socket.engineio.client.transports.Polling.onData(Polling.java:106)

at io.socket.engineio.client.transports.PollingXHR$5$1.run(PollingXHR.java:111)

at io.socket.thread.EventThread$2.run(EventThread.java:80)

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)

 



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

[jira] [Commented] (IGNITE-7918) Huge memory leak when data streamer used together with local cache

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-7918:
--

[~aealeksandrov] I am a bit concerned that cleanup is done using a full 
iteration over the {{affMap}}. What is the expected and max size of this map in 
the use-case you were debugging? Do you think it makes sense to change the map 
type to ConcurrentSkipListMap (make AffinityAssignmentKey comparable with 
topVer being compared first)?

> Huge memory leak when data streamer used together with local cache
> --
>
> Key: IGNITE-7918
> URL: https://issues.apache.org/jira/browse/IGNITE-7918
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Zbyszek B
>Assignee: Andrey Aleksandrov
>Priority: Major
> Fix For: 2.5
>
> Attachments: Demo.java, MemLeak-Ignite.png, MemLeak-Ignite.txt
>
>
> Dear Igniters,
> We observe huge memory leak when data streamer used together with local cache.
> In the attached demo producer produces local cache with single binary object 
> and passes this to the queue. Consumer picks up the cache from the queue, 
> constructs different binary object from it, adds it to global partitioned 
> cache and destroys local cache.
> This design causes a significant leak - the whole heap is used within minutes 
> (no matter if this is 4G or 24G).
>  
>  



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

[jira] [Updated] (IGNITE-6224) Node stoping does not wait all transactions completion

[Vitaliy Biryukov (JIRA)]

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

Vitaliy Biryukov updated IGNITE-6224:
-
Fix Version/s: 2.6

> Node stoping does not wait all transactions completion
> --
>
> Key: IGNITE-6224
> URL: https://issues.apache.org/jira/browse/IGNITE-6224
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Vladislav Pyatkov
>Assignee: Vitaliy Biryukov
>Priority: Major
> Fix For: 2.6
>
> Attachments: TransactionBehindStopNodeTest.java
>
>
> I have started grid node and executing transaction over some cache. After I 
> stopped the node in the middle execution of transaction. I got transaction 
> execution exception:
> {noformat}
> java.lang.IllegalStateException: class 
> org.apache.ignite.internal.processors.cache.CacheStoppedException: Failed to 
> perform cache operation (cache is stopped): cache
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheGateway.enter(GridCacheGateway.java:164)
>   at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.onEnter(GatewayProtectedCacheProxy.java:1656)
>   at 
> org.apache.ignite.internal.processors.cache.GatewayProtectedCacheProxy.put(GatewayProtectedCacheProxy.java:869)
>   at 
> org.apache.ignite.TransactionBehindStopNodeTest.testOneNode(TransactionBehindStopNodeTest.java:56)
>   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>   at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>   at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>   at java.lang.reflect.Method.invoke(Method.java:498)
>   at junit.framework.TestCase.runTest(TestCase.java:176)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2000)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:132)
>   at 
> org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:1915)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> although I stopped node with _false_ {{cancel}} flag.
> {code}
> G.stop(getTestIgniteInstanceName(0), false);
> {code}



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

[jira] [Comment Edited] (IGNITE-8246) Cast exception when using printPartitionState method

[Maxim Muzafarov (JIRA)]

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

Maxim Muzafarov edited comment on IGNITE-8246 at 4/13/18 10:31 AM:
---

[~NIzhikov], [~dpavlov]

Can you review my changes?
 This change will help us to perform better log analysys.


was (Author: mmuzaf):
[~NIzhikov], 

Can you review my changes?
 This change will help us to perform better log analysys.

> Cast exception when using printPartitionState method
> 
>
> Key: IGNITE-8246
> URL: https://issues.apache.org/jira/browse/IGNITE-8246
> Project: Ignite
>  Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Trivial
>  Labels: test
> Fix For: 2.6
>
>
> Using of {{printPartitionState}} produces error which obstructs log analysys.
>  
> {code:java}
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> {code}



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

[jira] [Created] (IGNITE-8247) .NET: ICacheLock.TryEnter() returns false if client is disconnected

[Roman Guseinov (JIRA)]

Roman Guseinov created IGNITE-8247:
--

 Summary: .NET: ICacheLock.TryEnter() returns false if client is 
disconnected
 Key: IGNITE-8247
 URL: https://issues.apache.org/jira/browse/IGNITE-8247
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Roman Guseinov
 Attachments: TryEnterIssue.cs

It seems that TryEnter() doesn't propagate an IgniteClientDisconnectedException 
from Java to .NET.

Reproducer is attached.



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

[jira] [Commented] (IGNITE-7647) Apache Ignite RPM packages (Stage II)

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7647:


[~vveider] could you please add link to dev.list discussion?

It confuses community members because it is not clear there is related 
discussion at dev.list.

> Apache Ignite RPM packages (Stage II)
> -
>
> Key: IGNITE-7647
> URL: https://issues.apache.org/jira/browse/IGNITE-7647
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
> Fix For: 2.5
>
>
> (/) Repack RPM specification to:
> * -(x) be able to build package from source code-
> * (/) divide single package into multiple packages (core + optional).



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

[jira] [Commented] (IGNITE-8246) Cast exception when using printPartitionState method

[Maxim Muzafarov (JIRA)]

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

Maxim Muzafarov commented on IGNITE-8246:
-

[~NIzhikov], 

Can you review my changes?
This change will helps us to perform better log analysys.

> Cast exception when using printPartitionState method
> 
>
> Key: IGNITE-8246
> URL: https://issues.apache.org/jira/browse/IGNITE-8246
> Project: Ignite
>  Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Trivial
>  Labels: test
> Fix For: 2.6
>
>
> Using of {{printPartitionState}} produces error which obstructs log analysys.
>  
> {code:java}
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> {code}



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

[jira] [Comment Edited] (IGNITE-8246) Cast exception when using printPartitionState method

[Maxim Muzafarov (JIRA)]

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

Maxim Muzafarov edited comment on IGNITE-8246 at 4/13/18 10:20 AM:
---

[~NIzhikov], 

Can you review my changes?
 This change will help us to perform better log analysys.


was (Author: mmuzaf):
[~NIzhikov], 

Can you review my changes?
This change will helps us to perform better log analysys.

> Cast exception when using printPartitionState method
> 
>
> Key: IGNITE-8246
> URL: https://issues.apache.org/jira/browse/IGNITE-8246
> Project: Ignite
>  Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Trivial
>  Labels: test
> Fix For: 2.6
>
>
> Using of {{printPartitionState}} produces error which obstructs log analysys.
>  
> {code:java}
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> {code}



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

[jira] [Commented] (IGNITE-8246) Cast exception when using printPartitionState method

[Maxim Muzafarov (JIRA)]

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

Maxim Muzafarov commented on IGNITE-8246:
-

*before:*
{code:java}
rebalance futures
nodeId=1905fe92-b58d-4397-81cd-b0d954c0 isDone=true res=true 
topVer=nodeId=19742aa1-0de7-4df7-ad80-1c2e8df1 isDone=true res=true 
topVer=nodeId=cdbe07fe-ac18-4df2-b500-d5a00212 isDone=true res=true 
topVer=nodeId=018bfc77-481a-44a1-9d21-c5a6dec3 isDone=true res=true
{code}

*after:*
{code:java}
rebalance futures
nodeId=a20e170b-61be-4168-9260-1b6d7e20 isDone=true res=true 
topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1]
remaining:empty
nodeId=402bc5d1-bffb-41c9-8d5f-e575ca31 isDone=true res=true 
topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1]
remaining:empty
nodeId=1fe9fab3-a185-467a-bca0-8e4e4112 isDone=true res=true 
topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1]
remaining:empty
nodeId=fa6c74fc-3745-49f3-bc1a-a4f192d3 isDone=true res=true 
topVer=AffinityTopologyVersion [topVer=4, minorTopVer=1]
remaining:empty
{code}

> Cast exception when using printPartitionState method
> 
>
> Key: IGNITE-8246
> URL: https://issues.apache.org/jira/browse/IGNITE-8246
> Project: Ignite
>  Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Trivial
>  Labels: test
> Fix For: 2.6
>
>
> Using of {{printPartitionState}} produces error which obstructs log analysys.
>  
> {code:java}
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> {code}



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

[jira] [Commented] (IGNITE-8192) Print out information on how many nodes left until auto-activation

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-8192:
--

We already have periodic metrics printout for Ignite nodes: {{Metrics for local 
node (to disable set 'metricsLogFrequency' to 0)}}

We should add something like the following message to this periodic printout:
{code}
^-- Node [id=..., clusterState=INACTIVE]
^-- Baseline [id=123456, size=10, online=8, offline=2]
^-- 2 nodes left for auto-activation (consistentId1, consistentId2)
{code}

The size of nodes left for auto-activation should be limited.

> Print out information on how many nodes left until auto-activation
> --
>
> Key: IGNITE-8192
> URL: https://issues.apache.org/jira/browse/IGNITE-8192
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> We should print out a message (probably on each topology change event) about 
> baseline topology and how many nodes left to be started until 
> auto-activation. Also, when the number of nodes is not too large, print out 
> their consistent IDs.



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

[jira] [Commented] (IGNITE-7918) Huge memory leak when data streamer used together with local cache

[Andrey Aleksandrov (JIRA)]

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

Andrey Aleksandrov commented on IGNITE-7918:


Thank you! I will fix them soon and retun to you.

> Huge memory leak when data streamer used together with local cache
> --
>
> Key: IGNITE-7918
> URL: https://issues.apache.org/jira/browse/IGNITE-7918
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Zbyszek B
>Assignee: Andrey Aleksandrov
>Priority: Major
> Fix For: 2.5
>
> Attachments: Demo.java, MemLeak-Ignite.png, MemLeak-Ignite.txt
>
>
> Dear Igniters,
> We observe huge memory leak when data streamer used together with local cache.
> In the attached demo producer produces local cache with single binary object 
> and passes this to the queue. Consumer picks up the cache from the queue, 
> constructs different binary object from it, adds it to global partitioned 
> cache and destroys local cache.
> This design causes a significant leak - the whole heap is used within minutes 
> (no matter if this is 4G or 24G).
>  
>  



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

[jira] [Assigned] (IGNITE-8245) Web console: "Warning" icon is displayed above "secured key" icon.

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin reassigned IGNITE-8245:


Assignee: Andrey Novikov  (was: Dmitriy Shabalin)

[~anovikov] fixed, pls review it

> Web console: "Warning" icon is displayed above "secured key" icon.
> --
>
> Key: IGNITE-8245
> URL: https://issues.apache.org/jira/browse/IGNITE-8245
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.4
>Reporter: Andrey Novikov
>Assignee: Andrey Novikov
>Priority: Major
> Fix For: 2.5
>
> Attachments: warning_icon.png
>
>
> See attachment. Reproduced in Safari.
> Make the actual input borderless, move the border to outer element, shrink 
> the input element when an error notification has to be shown.



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

[jira] [Assigned] (IGNITE-8245) Web console: "Warning" icon is displayed above "secured key" icon.

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin reassigned IGNITE-8245:


Assignee: Dmitriy Shabalin

> Web console: "Warning" icon is displayed above "secured key" icon.
> --
>
> Key: IGNITE-8245
> URL: https://issues.apache.org/jira/browse/IGNITE-8245
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.4
>Reporter: Andrey Novikov
>Assignee: Dmitriy Shabalin
>Priority: Major
> Fix For: 2.5
>
> Attachments: warning_icon.png
>
>
> See attachment. Reproduced in Safari.
> Make the actual input borderless, move the border to outer element, shrink 
> the input element when an error notification has to be shown.



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

[jira] [Commented] (IGNITE-7918) Huge memory leak when data streamer used together with local cache

[Dmitriy Pavlov (JIRA)]

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

Dmitriy Pavlov commented on IGNITE-7918:


[~aealeksandrov] I left several code style-related proposals in PR comments. 
Could you please address?

> Huge memory leak when data streamer used together with local cache
> --
>
> Key: IGNITE-7918
> URL: https://issues.apache.org/jira/browse/IGNITE-7918
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.3
>Reporter: Zbyszek B
>Assignee: Andrey Aleksandrov
>Priority: Major
> Fix For: 2.5
>
> Attachments: Demo.java, MemLeak-Ignite.png, MemLeak-Ignite.txt
>
>
> Dear Igniters,
> We observe huge memory leak when data streamer used together with local cache.
> In the attached demo producer produces local cache with single binary object 
> and passes this to the queue. Consumer picks up the cache from the queue, 
> constructs different binary object from it, adds it to global partitioned 
> cache and destroys local cache.
> This design causes a significant leak - the whole heap is used within minutes 
> (no matter if this is 4G or 24G).
>  
>  



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

[jira] [Commented] (IGNITE-8191) Print out information when cluster is not activated

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-8191:
--

I think we should add this printout in IgniteKernal#ackStart and add the 
following message:
{{>>> Ignite cluster is not active (limited functionality available). Use 
control.(sh|bat) script or IgniteCluster interface to activate.}}

> Print out information when cluster is not activated
> ---
>
> Key: IGNITE-8191
> URL: https://issues.apache.org/jira/browse/IGNITE-8191
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> We should add additional information to local node statistics when a cluster 
> is not activated and add a hint on how activation is performed.



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

[jira] [Commented] (IGNITE-8246) Cast exception when using printPartitionState method

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8246:


GitHub user Mmuzaf opened a pull request:

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

IGNITE-8246: update print errors

Fix print error

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

$ git pull https://github.com/Mmuzaf/ignite ignite-8246

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

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


commit 925250633e008b04c12cbf2967cadfc9490714ea
Author: Maxim Muzafarov 
Date:   2018-04-13T10:04:15Z

IGNITE-8246: use proper generalization




> Cast exception when using printPartitionState method
> 
>
> Key: IGNITE-8246
> URL: https://issues.apache.org/jira/browse/IGNITE-8246
> Project: Ignite
>  Issue Type: Bug
>Reporter: Maxim Muzafarov
>Assignee: Maxim Muzafarov
>Priority: Trivial
>  Labels: test
> Fix For: 2.6
>
>
> Using of {{printPartitionState}} produces error which obstructs log analysys.
>  
> {code:java}
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> [2018-04-13 
> 12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion 
> cannot be cast to [C
> {code}



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

[jira] [Comment Edited] (IGNITE-8190) Print out an information message when local node is not in baseline

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk edited comment on IGNITE-8190 at 4/13/18 10:05 AM:


I suggest the following message should be printed either on activation exchange 
(if cluster was not active) or local node join exchange (if cluster was active) 
and there is a region with persistence enabled:

{{Local node is not included in Baseline Topology and will not be used for 
persistent data storage. Use control.(sh|bat) script or IgniteCluster interface 
to include the node to Baseline Topology.}}

The message should be U.quietAndInfo()


was (Author: agoncharuk):
I suggest the following message should be printed either on activation exchange 
(if cluster was not active) or local node join exchange (if cluster was active) 
and there is a region with persistence enabled:

{{Local node is not included in Baseline Topology and will not be used for 
persistent data storage. Use ./control.(sh|bat) script or IgniteCluster 
interface to include the node to Baseline Topology.}}

The message should be U.quietAndInfo()

> Print out an information message when local node is not in baseline
> ---
>
> Key: IGNITE-8190
> URL: https://issues.apache.org/jira/browse/IGNITE-8190
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> When a node is joined into the cluster and the node is not in the baseline 
> topology, we should print out an information message that informs how this 
> affects local node and what a user should do in order to add the node to 
> baseline.



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

[jira] [Comment Edited] (IGNITE-8190) Print out an information message when local node is not in baseline

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk edited comment on IGNITE-8190 at 4/13/18 10:01 AM:


I suggest the following message should be printed either on activation exchange 
(if cluster was not active) or local node join exchange (if cluster was active) 
and there is a region with persistence enabled:

{{Local node is not included in Baseline Topology and will not be used for 
persistent data storage. Use ./control.(sh|bat) script or IgniteCluster 
interface to include the node to Baseline Topology.}}

The message should be U.quietAndInfo()


was (Author: agoncharuk):
I suggest the following message should be printed either on activation exchange 
(if cluster was not active) or local node join exchange (if cluster was active) 
and there is a region with persistence enabled:

{{Local node is not included in Baseline Topology and will not be used for 
persistent data storage. Use ./control.{sh|bat} script or IgniteCluster 
interface to include the node to Baseline Topology.}}

The message should be U.quietAndInfo()

> Print out an information message when local node is not in baseline
> ---
>
> Key: IGNITE-8190
> URL: https://issues.apache.org/jira/browse/IGNITE-8190
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> When a node is joined into the cluster and the node is not in the baseline 
> topology, we should print out an information message that informs how this 
> affects local node and what a user should do in order to add the node to 
> baseline.



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

[jira] [Commented] (IGNITE-8190) Print out an information message when local node is not in baseline

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-8190:
--

I suggest the following message should be printed either on activation exchange 
(if cluster was not active) or local node join exchange (if cluster was active) 
and there is a region with persistence enabled:

{{Local node is not included in Baseline Topology and will not be used for 
persistent data storage. Use ./control.{sh|bat} script or IgniteCluster 
interface to include the node to Baseline Topology.}}

The message should be U.quietAndInfo()

> Print out an information message when local node is not in baseline
> ---
>
> Key: IGNITE-8190
> URL: https://issues.apache.org/jira/browse/IGNITE-8190
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexey Goncharuk
>Priority: Major
> Fix For: 2.5
>
>
> When a node is joined into the cluster and the node is not in the baseline 
> topology, we should print out an information message that informs how this 
> affects local node and what a user should do in order to add the node to 
> baseline.



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

[jira] [Commented] (IGNITE-7647) Apache Ignite RPM packages (Stage II)

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev commented on IGNITE-7647:
-

I would postpone package splitting until we can improve packages' contents (be 
able to run visor at all, be able to run sqlline from /usr/bin)

Right now we should probably ship unsplitted package, wait for feedback from 
community.

I would remove package-splitting changes for now if I would you, get the rest 
of infrastructure changes into 2.5 quick.

> Apache Ignite RPM packages (Stage II)
> -
>
> Key: IGNITE-7647
> URL: https://issues.apache.org/jira/browse/IGNITE-7647
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Peter Ivanov
>Assignee: Peter Ivanov
>Priority: Critical
> Fix For: 2.5
>
>
> (/) Repack RPM specification to:
> * -(x) be able to build package from source code-
> * (/) divide single package into multiple packages (core + optional).



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

[jira] [Created] (IGNITE-8246) Cast exception when using printPartitionState method

[Maxim Muzafarov (JIRA)]

Maxim Muzafarov created IGNITE-8246:
---

 Summary: Cast exception when using printPartitionState method
 Key: IGNITE-8246
 URL: https://issues.apache.org/jira/browse/IGNITE-8246
 Project: Ignite
  Issue Type: Bug
Reporter: Maxim Muzafarov
Assignee: Maxim Muzafarov
 Fix For: 2.6


Using of {{printPartitionState}} produces error which obstructs log analysys.

 
{code:java}
[2018-04-13 
12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
 org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion cannot 
be cast to [C
[2018-04-13 
12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
 org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion cannot 
be cast to [C
[2018-04-13 
12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
 org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion cannot 
be cast to [C
[2018-04-13 
12:53:33,055][ERROR][test-runner-#1%distributed.CacheBaselineTopologyTest%][root]
 org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion cannot 
be cast to [C
{code}



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

[jira] [Commented] (IGNITE-7024) Introduce some kind of network compression

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7024:


GitHub user NSAmelchev opened a pull request:

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

IGNITE-7024



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

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

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

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


commit 11424e9eeefc8fe1b8575623c18a8d565a376ab9
Author: NSAmelchev 
Date:   2017-11-28T14:25:13Z

Merge remote-tracking branch 'refs/remotes/apache/master'

commit 0b16700731bda414b8d7921f2c098c5ad1b6540b
Author: NSAmelchev 
Date:   2018-01-19T09:46:31Z

Merge remote-tracking branch 'refs/remotes/apache/master'

commit 0de054fe0a1ae41db58a67d3387d08deaf6d22e2
Author: NSAmelchev 
Date:   2018-02-27T11:00:41Z

Merge remote-tracking branch 'apache/master'

commit 29cb0f44d25621d1e41e00d504c3e7bf44c1d735
Author: NSAmelchev 
Date:   2018-03-15T10:58:37Z

Merge pull request #20 from apache/master

merge

commit 9b0f16930a5e1da4ef3a528b7879cd1fca5307f7
Author: NSAmelchev 
Date:   2018-03-20T08:17:26Z

Merge pull request #21 from apache/master

Merge

commit d888d0e2b5fda995d1aa8e59f51bc181cfd6ca27
Author: NSAmelchev 
Date:   2018-04-10T13:48:07Z

Merge pull request #23 from apache/master

Merge

commit 9d38430687843530d71b5fdb1218534cb2e4985d
Author: NSAmelchev 
Date:   2018-04-12T13:55:02Z

Merge pull request #24 from apache/master

Merge

commit 0e00f13c7ac7496d16ff31015e87572041facdee
Author: NSAmelchev 
Date:   2018-04-13T09:55:27Z

squash comression




> Introduce some kind of network compression
> --
>
> Key: IGNITE-7024
> URL: https://issues.apache.org/jira/browse/IGNITE-7024
> Project: Ignite
>  Issue Type: New Feature
>Affects Versions: 2.3
>Reporter: Amelchev Nikita
>Assignee: Amelchev Nikita
>Priority: Major
> Fix For: 2.5
>
>
> Introduce some kind of pluggable compression at network level
> The main idea is using in-line compression and writes encoded bytes in
> network channel by bytes array buffer. It allows us avoiding expensive
> memory allocation.
> A solution may be implemented at TcpCommunicationSpi level.
> For example, introduce Compressor interface which will allow us to describe 
> our compression strategy, for example, exclude some small messages, choose 
> compression algorithm and other…



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

[jira] [Updated] (IGNITE-8245) Web console: "Warning" icon is displayed above "secured key" icon.

[Andrey Novikov (JIRA)]

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

Andrey Novikov updated IGNITE-8245:
---
Attachment: warning_icon.png

> Web console: "Warning" icon is displayed above "secured key" icon.
> --
>
> Key: IGNITE-8245
> URL: https://issues.apache.org/jira/browse/IGNITE-8245
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.4
>Reporter: Andrey Novikov
>Priority: Major
> Fix For: 2.5
>
> Attachments: warning_icon.png
>
>
> See attachment. Reproduced in Safari.
> Make the actual input borderless, move the border to outer element, shrink 
> the input element when an error notification has to be shown.



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

[jira] [Created] (IGNITE-8245) Web console: "Warning" icon is displayed above "secured key" icon.

[Andrey Novikov (JIRA)]

Andrey Novikov created IGNITE-8245:
--

 Summary: Web console: "Warning" icon is displayed above "secured 
key" icon.
 Key: IGNITE-8245
 URL: https://issues.apache.org/jira/browse/IGNITE-8245
 Project: Ignite
  Issue Type: Bug
  Components: wizards
Affects Versions: 2.4
Reporter: Andrey Novikov
 Fix For: 2.5


See attachment. Reproduced in Safari.

Make the actual input borderless, move the border to outer element, shrink the 
input element when an error notification has to be shown.



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

[jira] [Commented] (IGNITE-7829) Adopt kNN regression example to the new Partitioned Dataset

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-7829:


Github user asfgit closed the pull request at:

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


> Adopt kNN regression example to the new Partitioned Dataset
> ---
>
> Key: IGNITE-7829
> URL: https://issues.apache.org/jira/browse/IGNITE-7829
> Project: Ignite
>  Issue Type: Sub-task
>  Components: ml
>Reporter: Aleksey Zinoviev
>Assignee: Aleksey Zinoviev
>Priority: Major
> Fix For: 2.5
>
>




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

[jira] [Commented] (IGNITE-8240) .NET: Use default scheduler when starting Tasks

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-8240:


Github user asfgit closed the pull request at:

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


> .NET: Use default scheduler when starting Tasks
> ---
>
> Key: IGNITE-8240
> URL: https://issues.apache.org/jira/browse/IGNITE-8240
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
> Fix For: 2.5
>
>
> Default scheduler should be specified explicitly when starting new tasks to 
> avoid deadlocks: 
> http://blog.stephencleary.com/2013/10/continuewith-is-dangerous-too.html
> This applies to {{StartNew}}, {{ConyinueWith}}, etc.



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