[jira] [Commented] (IGNITE-5083) Add default cache for Redis

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5083:


GitHub user shroman opened a pull request:

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

IGNITE-5083: Add default cache for Redis.



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

$ git pull https://github.com/shroman/ignite IGNITE-5083

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

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


commit d9fcc6490272b5cdcf80a9f0c15c606a1096d852
Author: shtykh_roman 
Date:   2017-04-26T05:47:17Z

IGNITE-5083: Add default cache for Redis.




> Add default cache for Redis
> ---
>
> Key: IGNITE-5083
> URL: https://issues.apache.org/jira/browse/IGNITE-5083
> Project: Ignite
>  Issue Type: Task
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 2.0
>
>
> Default "redis_cache" for Redis data.
> NOTE: the name will have to be "externalized"  in future.
> http://apache-ignite-developers.2346864.n4.nabble.com/Null-cache-names-td17073.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5083) Add default cache for Redis

[Roman Shtykh (JIRA)]

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

Roman Shtykh updated IGNITE-5083:
-
Description: 
Default "redis_cache" for Redis data.
NOTE: the name will have to be "externalized"  in future.

http://apache-ignite-developers.2346864.n4.nabble.com/Null-cache-names-td17073.html

  was:
Default "redis_cache" for Redis data.
NOTE: the name will have to be "externalized"  in future.


> Add default cache for Redis
> ---
>
> Key: IGNITE-5083
> URL: https://issues.apache.org/jira/browse/IGNITE-5083
> Project: Ignite
>  Issue Type: Task
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 2.0
>
>
> Default "redis_cache" for Redis data.
> NOTE: the name will have to be "externalized"  in future.
> http://apache-ignite-developers.2346864.n4.nabble.com/Null-cache-names-td17073.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5083) Add default cache for Redis

[Roman Shtykh (JIRA)]

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

Roman Shtykh updated IGNITE-5083:
-
Labels: redis  (was: )

> Add default cache for Redis
> ---
>
> Key: IGNITE-5083
> URL: https://issues.apache.org/jira/browse/IGNITE-5083
> Project: Ignite
>  Issue Type: Task
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: redis
> Fix For: 2.0
>
>
> Default "redis_cache" for Redis data.
> NOTE: the name will have to be "externalized"  in future.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5083) Add default cache for Redis

[Roman Shtykh (JIRA)]

Roman Shtykh created IGNITE-5083:


 Summary: Add default cache for Redis
 Key: IGNITE-5083
 URL: https://issues.apache.org/jira/browse/IGNITE-5083
 Project: Ignite
  Issue Type: Task
Reporter: Roman Shtykh
Assignee: Roman Shtykh


Default "redis_cache" for Redis data.
NOTE: the name will have to be "externalized"  in future.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5082) Redesign base template

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin updated IGNITE-5082:
-
Attachment: base layout.png

> Redesign base template
> --
>
> Key: IGNITE-5082
> URL: https://issues.apache.org/jira/browse/IGNITE-5082
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Fix For: 2.1
>
> Attachments: base layout.png
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5082) Redesign base template

[Dmitriy Shabalin (JIRA)]

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

Dmitriy Shabalin updated IGNITE-5082:
-
Attachment: Apache Layout.png

> Redesign base template
> --
>
> Key: IGNITE-5082
> URL: https://issues.apache.org/jira/browse/IGNITE-5082
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 2.1
>Reporter: Dmitriy Shabalin
>Assignee: Dmitriy Shabalin
> Fix For: 2.1
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5082) Redesign base template

[Dmitriy Shabalin (JIRA)]

Dmitriy Shabalin created IGNITE-5082:


 Summary: Redesign base template
 Key: IGNITE-5082
 URL: https://issues.apache.org/jira/browse/IGNITE-5082
 Project: Ignite
  Issue Type: Task
  Components: wizards
Affects Versions: 2.1
Reporter: Dmitriy Shabalin
Assignee: Dmitriy Shabalin
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4965) Document enum fileds handling and changes with 'select * ...' in SQL

[Prachi Garg (JIRA)]

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

Prachi Garg closed IGNITE-4965.
---

> Document enum fileds handling and changes with 'select * ...' in SQL 
> -
>
> Key: IGNITE-4965
> URL: https://issues.apache.org/jira/browse/IGNITE-4965
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Prachi Garg
> Fix For: 2.0
>
>
> Document the following:
> * enum fields handling in SQL (IGNITE-3595)
> * _key and _val are no longer returned in "select *..." result set 
> (IGNITE-3487)
> Readme page:
> https://dash.readme.io/project/apacheignite/v1.9/docs/distributed-queries-20



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-1173) Hive over Ignite integration should be documented in public

[Konstantin Boudnik (JIRA)]

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

Konstantin Boudnik commented on IGNITE-1173:


The referred URL does no longer exist, BTW


> Hive over Ignite integration should be documented in public
> ---
>
> Key: IGNITE-1173
> URL: https://issues.apache.org/jira/browse/IGNITE-1173
> Project: Ignite
>  Issue Type: Improvement
>  Components: hadoop
>Affects Versions: sprint-7
>Reporter: Ivan Veselovsky
>Assignee: Ivan Veselovsky
> Fix For: ignite-1.4
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-5044) JVM crash

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky edited comment on IGNITE-5044 at 4/25/17 5:52 PM:
--

branch {{ignite-5044}}: looks like I was able to provide an Exception instead 
of crash, so the error is now much more graceful.


was (Author: iveselovskiy):
branch `ignite-5044`: looks like I was able to provide an Exception instead of 
crash, so the error is now much more graceful.

> JVM crash
> -
>
> Key: IGNITE-5044
> URL: https://issues.apache.org/jira/browse/IGNITE-5044
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
>Assignee: Ivan Veselovsky
>Priority: Critical
> Fix For: 2.1
>
> Attachments: grid.2.node.1.0.out.log, hs_err_pid4079.log
>
>
> Sometimes testing Apache Hadoop +  Apache Hive kills JVM
> Take a look on the attached file



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-5044) JVM crash

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky edited comment on IGNITE-5044 at 4/25/17 5:51 PM:
--

branch `ignite-5044`: looks like I was able to provide an Exception instead of 
crash, so the error is now much more graceful.


was (Author: iveselovskiy):
branch {ignite-5044}: looks like I was able to provide an Exception instead of 
crash, so the error is now much more graceful.

> JVM crash
> -
>
> Key: IGNITE-5044
> URL: https://issues.apache.org/jira/browse/IGNITE-5044
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
>Assignee: Ivan Veselovsky
>Priority: Critical
> Fix For: 2.1
>
> Attachments: grid.2.node.1.0.out.log, hs_err_pid4079.log
>
>
> Sometimes testing Apache Hadoop +  Apache Hive kills JVM
> Take a look on the attached file



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5044) JVM crash

[Ivan Veselovsky (JIRA)]

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

Ivan Veselovsky commented on IGNITE-5044:
-

branch {ignite-5044}: looks like I was able to provide an Exception instead of 
crash, so the error is now much more graceful.

> JVM crash
> -
>
> Key: IGNITE-5044
> URL: https://issues.apache.org/jira/browse/IGNITE-5044
> Project: Ignite
>  Issue Type: Bug
>  Components: hadoop
>Affects Versions: 2.0
>Reporter: Sergey Kozlov
>Assignee: Ivan Veselovsky
>Priority: Critical
> Fix For: 2.1
>
> Attachments: grid.2.node.1.0.out.log, hs_err_pid4079.log
>
>
> Sometimes testing Apache Hadoop +  Apache Hive kills JVM
> Take a look on the attached file



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4539) RocketMQ data streamer

[Denis Magda (JIRA)]

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

Denis Magda commented on IGNITE-4539:
-

[~roman_s], I'm fully for that! [~agoncharuk], are we ready to merge the 
changes?

> RocketMQ data streamer
> --
>
> Key: IGNITE-4539
> URL: https://issues.apache.org/jira/browse/IGNITE-4539
> Project: Ignite
>  Issue Type: New Feature
>  Components: streaming
>Reporter: Roman Shtykh
>Assignee: Roman Shtykh
>  Labels: important
> Fix For: 2.1
>
>
> Streamer for RocketMQ (https://github.com/rocketmq)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5041) NPE during deadlock detection because cache isn't started on node

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5041:

Fix Version/s: (was: 2.0)
   2.1

> NPE during deadlock detection because cache isn't started on node
> -
>
> Key: IGNITE-5041
> URL: https://issues.apache.org/jira/browse/IGNITE-5041
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 2.1
>
>
> NPE is possible during deadlock detection process in case when one of 
> participating cache isn't started on node that initiates transaction:
> {noformat}
> Exception in thread "sys-#66%transactions.TxDeadlockNpeClientTest1%" 
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxKey.finishUnmarshal(IgniteTxKey.java:92)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.TxLocksResponse.finishUnmarshal(TxLocksResponse.java:190)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$DeadlockDetectionListener.unmarshall(IgniteTxManager.java:2588)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$DeadlockDetectionListener.onMessage(IgniteTxManager.java:2478)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> *Steps to reproduce:*
> # Start server node with two caches.
> # Start two transactions on server node that involve both caches and lead to 
> deadlock.
> # Start client node and create only one cache
> # Start transaction on client node that will try to update key that involved 
> into deadlock
> As result transaction on client node will hang until deadlock detection 
> timeout happens.
> The same result could be achived using node filters for caches.
> *Workaround:*
> Start all caches on node if possible.
> Another way is deadlock detection disabling using JVM parameter 
> {{-DIGNITE_TX_DEADLOCK_DETECTION_MAX_ITERS=0}}
> *Possible solution:*
> Try to create {{CacheObjectContext}} without starting of the cache.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5076) Optimization of multi-threaded start nodes in tests

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5076:

Fix Version/s: (was: 2.0)
   2.1

> Optimization of multi-threaded start nodes in tests
> ---
>
> Key: IGNITE-5076
> URL: https://issues.apache.org/jira/browse/IGNITE-5076
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
> Fix For: 2.1
>
>
> Concurrent start,will more effective if we have coordinator before, 
> multi-threaded start nodes. If start all nodes concurrent, they will be 
> compete for coordinator role, it is not effective way.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4962) Document New Eviction and Expiration Policies

[Prachi Garg (JIRA)]

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

Prachi Garg reassigned IGNITE-4962:
---

Assignee: Denis Magda  (was: Prachi Garg)

Denis, 
I have made some edits. Please review.

> Document New Eviction and Expiration Policies 
> --
>
> Key: IGNITE-4962
> URL: https://issues.apache.org/jira/browse/IGNITE-4962
> Project: Ignite
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Denis Magda
>Assignee: Denis Magda
>Priority: Critical
> Fix For: 2.0
>
>
> This following is intended to be done as a part of this ticket:
> * refine eviction policy documentation 
> (https://apacheignite.readme.io/docs/evictions). Take a look at the changes - 
> IGNITE-4534
> * make sure everything left unchanged with the expiration policy 
> (https://apacheignite.readme.io/docs/expiry-policies)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5024) Default MemoryPolicy settings improvements

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5024:


[~agoncharuk] done, .NET side fixed, tests seem to be fine.

> Default MemoryPolicy settings improvements
> --
>
> Key: IGNITE-5024
> URL: https://issues.apache.org/jira/browse/IGNITE-5024
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Sergey Chugunov
>Assignee: Alexey Goncharuk
>  Labels: general
> Fix For: 2.0
>
>
> h2. Notes
> Currently when user doesn't specify any MemoryPolicy configuration a default 
> one is created. It has a fixed size of 1 GB which seems to be too rigid.
> Also when user wants to override size of the default MemoryPolicy, the full 
> syntax of this configuration must be used; it is cumbersome in such simple 
> case.
> h2. Acceptance Criteria
> # Default MemoryPolicy is created with size of 80% of physical memory 
> available on machine.
> # New configuration property *defaultMemoryPolicySize* is introduced in 
> *memoryConfiguration* section to allow user to specify exact size in bytes 
> without applying verbose syntax of *memoryPolicyConfiguration* section.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-602) [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by infinite recursion

[Ryabov Dmitrii (JIRA)]

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

Ryabov Dmitrii commented on IGNITE-602:
---

[~agura], the main idea is to call GridToStringBuilder.toString(...) inside of 
GridToStringBuilder.toString(...) instead of obj.toString() method. It is the 
only way to prevent infinite loops of toString() inside of toString() which are 
uncontolled by GridToStringBuilder.

I made some changes, so your example works too. Can you look it?

> [Test] GridToStringBuilder is vulnerable for StackOverflowError caused by 
> infinite recursion
> 
>
> Key: IGNITE-602
> URL: https://issues.apache.org/jira/browse/IGNITE-602
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Artem Shutak
>Assignee: Ryabov Dmitrii
>  Labels: Muted_test
> Fix For: 2.1
>
>
> See test 
> org.gridgain.grid.util.tostring.GridToStringBuilderSelfTest#_testToStringCheckAdvancedRecursionPrevention
>  and related TODO in same source file.
> Also take a look at 
> http://stackoverflow.com/questions/11300203/most-efficient-way-to-prevent-an-infinite-recursion-in-tostring
> Test should be unmuted on TC after fix.
> see GG-5000.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-3487) _key and _val fields should be excluded from 'select * from' queries

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-3487 at 4/25/17 3:01 PM:
-

.NET:
* LINQ fixed in to handle {{*}} properly.
* Added test for custom key/val field names.


was (Author: ptupitsyn):
LINQ fixed in .NET to handle {{*}} properly.

> _key and _val fields should be excluded from 'select * from' queries
> 
>
> Key: IGNITE-3487
> URL: https://issues.apache.org/jira/browse/IGNITE-3487
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.0
>
>
> We have a pretty serious usability issue - predefined {{_key}} and {{_val}} 
> fields are returned when query like {{select * from}} is executed. First of 
> all, this is counterintuitive because user never defines or configures these 
> fields. Second of all, they actually duplicate all other fields. And finally, 
> they cause serialization exceptions because classes for key and value are not 
> always available.
> We should exclude these fields from {{select * from}} queries, but this is a 
> compatibility breaking change. It should be done in 2.0.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3487) _key and _val fields should be excluded from 'select * from' queries

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-3487:


LINQ fixed in .NET to handle {{*}} properly.

> _key and _val fields should be excluded from 'select * from' queries
> 
>
> Key: IGNITE-3487
> URL: https://issues.apache.org/jira/browse/IGNITE-3487
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.0
>
>
> We have a pretty serious usability issue - predefined {{_key}} and {{_val}} 
> fields are returned when query like {{select * from}} is executed. First of 
> all, this is counterintuitive because user never defines or configures these 
> fields. Second of all, they actually duplicate all other fields. And finally, 
> they cause serialization exceptions because classes for key and value are not 
> always available.
> We should exclude these fields from {{select * from}} queries, but this is a 
> compatibility breaking change. It should be done in 2.0.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5081) SecurityPermissionSetBuilder duplicates permission if it's appended more than once

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-5081:
---

 Summary: SecurityPermissionSetBuilder duplicates permission if 
it's appended more than once
 Key: IGNITE-5081
 URL: https://issues.apache.org/jira/browse/IGNITE-5081
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.9
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
 Fix For: 2.1


If the same permission is appended to builder more than once, builder 
duplicates it in the resulting collection. This doesn't actually break 
anything, but seems to be redundant.

Example:
{code}
new SecurityPermissionSetBuilder()
.appendSystemPermissions(ADMIN_VIEW)
.appendSystemPermissions(ADMIN_VIEW, ADMIN_QUERY)
.build();
{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5080) SecurityBasicPermissionSet implementation is incomplete

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-5080:
---

 Summary: SecurityBasicPermissionSet implementation is incomplete
 Key: IGNITE-5080
 URL: https://issues.apache.org/jira/browse/IGNITE-5080
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 1.9
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
 Fix For: 2.1


There are several issues with {{SecurityBasicPermissionSet}}:
* It doesn't implement {{hashCode}} and {{equals}} methods. This makes it 
impossible to use it as part of validation token.
* {{Collection}} fields are not marked with {{@GridToStringInclude}} 
annotation, so {{toString}} method doesn't actually print out all the 
information.
* {{systemPermissions}} method returns empty collection instead of {{null}} by 
default. This actually means 'no system permissions' even if 
{{defaultAllowAll}} is true.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5079) Improve debug logging for binary metadata exchange

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-5079:
---

 Summary: Improve debug logging for binary metadata exchange
 Key: IGNITE-5079
 URL: https://issues.apache.org/jira/browse/IGNITE-5079
 Project: Ignite
  Issue Type: Improvement
  Components: binary
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
Priority: Minor
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3487) _key and _val fields should be excluded from 'select * from' queries

[Igor Sapego (JIRA)]

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

Igor Sapego commented on IGNITE-3487:
-

[~skalashnikov] looks good overall. Why don't you add a test to 
{{core-test/src/cache_query_test.cpp}} as well?

> _key and _val fields should be excluded from 'select * from' queries
> 
>
> Key: IGNITE-3487
> URL: https://issues.apache.org/jira/browse/IGNITE-3487
> Project: Ignite
>  Issue Type: Improvement
>  Components: SQL
>Affects Versions: 1.6
>Reporter: Valentin Kulichenko
>Assignee: Sergey Kalashnikov
>  Labels: important
> Fix For: 2.0
>
>
> We have a pretty serious usability issue - predefined {{_key}} and {{_val}} 
> fields are returned when query like {{select * from}} is executed. First of 
> all, this is counterintuitive because user never defines or configures these 
> fields. Second of all, they actually duplicate all other fields. And finally, 
> they cause serialization exceptions because classes for key and value are not 
> always available.
> We should exclude these fields from {{select * from}} queries, but this is a 
> compatibility breaking change. It should be done in 2.0.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-4922) JDBC Driver: renew thin client based solution

[Taras Ledkov (JIRA)]

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

Taras Ledkov reassigned IGNITE-4922:


Assignee: Taras Ledkov

> JDBC Driver: renew thin client based solution
> -
>
> Key: IGNITE-4922
> URL: https://issues.apache.org/jira/browse/IGNITE-4922
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
>Assignee: Taras Ledkov
> Fix For: 2.1
>
>
> This is a parent ticket for all the activities that are intended to improve 
> the thin client based implementation of the JDBC driver making it default one.
>  
> Refer to the corresponding discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/jdbc-vs-jdbc2-packages-td14309.html
> In a nutshell, depending on a type of a protocol to be used for the next-gen 
> version the options are the following:
> - This type of driver might be a default driver for tools and applications 
> that don't need transactional support. Existing REST based protocol can be 
> used for this scenario.
> - If we want to support transactions (which is optional at the beginning) 
> then Yakov solution (see discussion) can be applied. However, it makes sense 
> to implement it only after MVCC is ready.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-5036) Disallow @QuerySqlField and @QueryTextField on methods

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-5036 at 4/25/17 1:12 PM:
---

Tests 
[results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1863%2Fhead]
 are OK with me.


was (Author: tledkov-gridgain):
Waits for TC 
[results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1863%2Fhead]

> Disallow @QuerySqlField and @QueryTextField on methods
> --
>
> Key: IGNITE-5036
> URL: https://issues.apache.org/jira/browse/IGNITE-5036
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5072) Move memory metrics to snapshots

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-5072:
--

Added ability to configure memory metrics on node start.

> Move memory metrics to snapshots
> 
>
> Key: IGNITE-5072
> URL: https://issues.apache.org/jira/browse/IGNITE-5072
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.0
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
> Fix For: 2.0
>
>
> This is a follow-up ticket for the following discussion:
> http://apache-ignite-developers.2346864.n4.nabble.com/MemoryMetrics-interface-inconsistencies-td17156.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5074) Split up asynchronous and synchronous calls in PlatformCompute

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-5074:

Labels: .net cpp  (was: )

> Split up asynchronous and synchronous calls in PlatformCompute
> --
>
> Key: IGNITE-5074
> URL: https://issues.apache.org/jira/browse/IGNITE-5074
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: .net, cpp
> Fix For: 2.1
>
>
> Currently, there is only asynchronous version of calls in 
> {{PlatformCompute}}, which means we create temporary objects (like futures 
> and listeners) which we do not need during synchronous calls.
> Add synchronous version of API calls which generate less garbage.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5074) Split up asynchronous and synchronous calls in PlatformCompute

[Igor Sapego (JIRA)]

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

Igor Sapego reassigned IGNITE-5074:
---

Assignee: Igor Sapego

> Split up asynchronous and synchronous calls in PlatformCompute
> --
>
> Key: IGNITE-5074
> URL: https://issues.apache.org/jira/browse/IGNITE-5074
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.9
>Reporter: Igor Sapego
>Assignee: Igor Sapego
> Fix For: 2.1
>
>
> Currently, there is only asynchronous version of calls in 
> {{PlatformCompute}}, which means we create temporary objects (like futures 
> and listeners) which we do not need during synchronous calls.
> Add synchronous version of API calls which generate less garbage.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5041) NPE during deadlock detection because cache isn't started on node

[Andrey Gura (JIRA)]

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

Andrey Gura updated IGNITE-5041:

Fix Version/s: 2.0

> NPE during deadlock detection because cache isn't started on node
> -
>
> Key: IGNITE-5041
> URL: https://issues.apache.org/jira/browse/IGNITE-5041
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Andrey Gura
> Fix For: 2.0
>
>
> NPE is possible during deadlock detection process in case when one of 
> participating cache isn't started on node that initiates transaction:
> {noformat}
> Exception in thread "sys-#66%transactions.TxDeadlockNpeClientTest1%" 
> java.lang.NullPointerException
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxKey.finishUnmarshal(IgniteTxKey.java:92)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.TxLocksResponse.finishUnmarshal(TxLocksResponse.java:190)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$DeadlockDetectionListener.unmarshall(IgniteTxManager.java:2588)
>   at 
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxManager$DeadlockDetectionListener.onMessage(IgniteTxManager.java:2478)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1082)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:710)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1700(GridIoManager.java:102)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$5.run(GridIoManager.java:673)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> *Steps to reproduce:*
> # Start server node with two caches.
> # Start two transactions on server node that involve both caches and lead to 
> deadlock.
> # Start client node and create only one cache
> # Start transaction on client node that will try to update key that involved 
> into deadlock
> As result transaction on client node will hang until deadlock detection 
> timeout happens.
> The same result could be achived using node filters for caches.
> *Workaround:*
> Start all caches on node if possible.
> Another way is deadlock detection disabling using JVM parameter 
> {{-DIGNITE_TX_DEADLOCK_DETECTION_MAX_ITERS=0}}
> *Possible solution:*
> Try to create {{CacheObjectContext}} without starting of the cache.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5050) .NET: IIgnite.GetMemoryMetrics

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5050:

Fix Version/s: (was: 2.0)
   2.1

> .NET: IIgnite.GetMemoryMetrics
> --
>
> Key: IGNITE-5050
> URL: https://issues.apache.org/jira/browse/IGNITE-5050
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> Add {{IIgnite.GetMemoryMetrics()}} in .NET which delegates to 
> {{Ignite.memoryMetrics()}} in Java



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5077) Support service security permissions

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5077:


GitHub user dkarachentsev opened a pull request:

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

IGNITE-5077 - Support service security permissions



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

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

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

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


commit a19938d1fdce87ccaa5b1262921f7281348bffca
Author: dkarachentsev 
Date:   2017-04-25T11:53:48Z

IGNITE-5077 - Support service security permissions




> Support service security permissions
> 
>
> Key: IGNITE-5077
> URL: https://issues.apache.org/jira/browse/IGNITE-5077
> Project: Ignite
>  Issue Type: New Feature
>  Components: managed services
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.1
>
>
> Need to add capability to specify permissions to allow/disallow executions of 
> particular services (similar to compute tasks).
> The following permissions should be added to the SecurityPermission enum:
> SERVICE_DEPLOY - for IgniteServices.deployXXX methods.
> SERVICE_CANCEL - for IgniteServices.cancel and IgniteServices.cancelAll 
> methods.
> SERVICE_INVOKE - for IgniteServices.service, IgniteServices.services and 
> IgniteServices.serviceProxy methods.
> SERVICE_INVOKE should allow fine-grained authorization based on service name, 
> similar to TASK_EXECUTE. E.g., a particular user should be able to execute 
> service A, but not service B.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4799) Remove TcpDiscoverySpi.heartbeatsFrequency parameter

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4799:


IGNITE-5062 done in {{ignite-4799-2.0}} branch. See {{// TODO}} in 
{{TcpDiscoverySpi}}

> Remove TcpDiscoverySpi.heartbeatsFrequency parameter
> 
>
> Key: IGNITE-4799
> URL: https://issues.apache.org/jira/browse/IGNITE-4799
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Denis Magda
>Assignee: Semen Boikov
>  Labels: important
> Fix For: 2.0
>
>  Time Spent: 16h
>  Remaining Estimate: 0h
>
> {{TcpDiscoverySpi.heartbeatsFrequency}} is no longer used to adjust the 
> heartbeats frequence. It affects the frequency of metrics messages sent over 
> the cluster ring.
> The following has to be done as a part of 2.0 release:
> * Remove {{TcpDiscoverySpi.heartbeatsFrequency}} parameter.
> * Use {{IgniteConfiguraion.getMetricsUpdateFrequency}} to adjust the rate of 
> metrics messages.
> * Make sure {{IgniteConfiguraion.getMetricsUpdateFrequency}} and metrics 
> messages are not participated in the failure detection process. We have to 
> clean up legacy code in {{ServerImpl}}.
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Renaming-TcpDiscoverySpi-heartbeatsFrequency-to-TcpDiscoverySpi-metricsUpdateFrequency-td14941.html
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-5062) .NET: Support new communication parameters in configuration

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-5062.

Resolution: Fixed

Done in {{ignite-4799-2.0}}

> .NET: Support new communication parameters in configuration
> ---
>
> Key: IGNITE-5062
> URL: https://issues.apache.org/jira/browse/IGNITE-5062
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Reporter: Alexander Belyak
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Need to support new value and remove old ones:
> In TcpDiscoverySpi:
> remove maxMissedHeartbeats
> remove maxMissedClientHeartbeats
> remove heartbeatFrequency
> rename hbFreq to metricsUpdateFrequency
> In IgniteConfiguration:
> add clientFailureDetectionTimeout (long with bounds from 
> metricsUpdateFrequency to Integer.MAX_VALUE)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5067) Absolute swapFilePath for MemoryPolicy is merged incorrectly with working dir path

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov updated IGNITE-5067:

Fix Version/s: (was: 2.0)
   2.1

> Absolute swapFilePath for MemoryPolicy is merged incorrectly with working dir 
> path
> --
>
> Key: IGNITE-5067
> URL: https://issues.apache.org/jira/browse/IGNITE-5067
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>  Labels: general
> Fix For: 2.1
>
>
> h2. Steps to reproduce
> * Create *MemoryPolicyConfiguration* with swapFilePath specified to some 
> *absolute* path
> * Start Ignite node with this configuration.
> h2. Expected outcome
> Swap file is allocated by absolute path specified by configuration.
> h2. Actual outcome
> Swap file is allocated by path where current working directory is merged with 
> swapFilePath.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5067) Absolute swapFilePath for MemoryPolicy is merged incorrectly with working dir path

[Sergey Chugunov (JIRA)]

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

Sergey Chugunov updated IGNITE-5067:

Fix Version/s: (was: 2.1)
   2.0

> Absolute swapFilePath for MemoryPolicy is merged incorrectly with working dir 
> path
> --
>
> Key: IGNITE-5067
> URL: https://issues.apache.org/jira/browse/IGNITE-5067
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.0
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>  Labels: general
> Fix For: 2.0
>
>
> h2. Steps to reproduce
> * Create *MemoryPolicyConfiguration* with swapFilePath specified to some 
> *absolute* path
> * Start Ignite node with this configuration.
> h2. Expected outcome
> Swap file is allocated by absolute path specified by configuration.
> h2. Actual outcome
> Swap file is allocated by path where current working directory is merged with 
> swapFilePath.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5024) Default MemoryPolicy settings improvements

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-5024:
--

[~ptupitsyn] I renamed size field of MemoryPolicyConfiguration to maxSize and 
added initialSize. Can you please make corresponding changes on .NET side? 
Branch name is ignite-5024

> Default MemoryPolicy settings improvements
> --
>
> Key: IGNITE-5024
> URL: https://issues.apache.org/jira/browse/IGNITE-5024
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Sergey Chugunov
>Assignee: Alexey Goncharuk
>  Labels: general
> Fix For: 2.0
>
>
> h2. Notes
> Currently when user doesn't specify any MemoryPolicy configuration a default 
> one is created. It has a fixed size of 1 GB which seems to be too rigid.
> Also when user wants to override size of the default MemoryPolicy, the full 
> syntax of this configuration must be used; it is cumbersome in such simple 
> case.
> h2. Acceptance Criteria
> # Default MemoryPolicy is created with size of 80% of physical memory 
> available on machine.
> # New configuration property *defaultMemoryPolicySize* is introduced in 
> *memoryConfiguration* section to allow user to specify exact size in bytes 
> without applying verbose syntax of *memoryPolicyConfiguration* section.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5018) review and improve javadocs in ML module

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-5018:


Github user oignatenko closed the pull request at:

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


> review and improve javadocs in ML module
> 
>
> Key: IGNITE-5018
> URL: https://issues.apache.org/jira/browse/IGNITE-5018
> Project: Ignite
>  Issue Type: Task
>  Components: ml
>Reporter: Oleg Ignatenko
>Assignee: Oleg Ignatenko
>Priority: Minor
> Fix For: 2.0
>
>
> Review and improve javadocs in Ignite ML module (added per IGNITE-4572). To 
> name a few, add descriptions for constructor parameters in classes 
> {{CacheMatrix}}, {{CacheMatrixStorage}}, {{RandomVector}}. Etc.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Comment Edited] (IGNITE-5024) Default MemoryPolicy settings improvements

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk edited comment on IGNITE-5024 at 4/25/17 11:30 AM:


[~dsetrakyan], sure, examples are below. I'll use this proposed setting in them 
and at the end explain how configuration looks like without it.

I would consider Memory Policy configuration on three different levels.

*Fully default*: user doesn't need to specify anything, default MemoryPolicy 
with default name and 80% of available RAM size is created.

*Semi-default*: user wants to override this "80% RAM" setting. All is needed is 
to use the following configuration:
{code:xml}
 
 
 
 
 
{code}

*Fully customized*: user defines everything by his/her own including name and 
size of default Memory Policy.
{code:xml}
 
 
 

 
 
 
 
 
 
 
 
 
 
 
{code}


Proposed setting allows to simplify semi-default level; without it user needs 
to use verbose fully-customized syntax in order to adjust only default Memory 
Policy size.


was (Author: sergey-chugunov):
[~dsetrakyan], sure, examples are below. I'll use this proposed setting in them 
and at the end explain how configuration looks like without it.

I would consider Memory Policy configuration on three different levels.

*Fully default*: user doesn't need to specify anything, default MemoryPolicy 
with default name and 80% of available RAM size is created.

*Semi-default*: user wants to override this "80% RAM" setting. All is needed is 
to use the following configuration:
{code:xml}
 
 
 
 
 
{code}

*Fully customized*: user defines everything by his/her own including name and 
size of default Memory Policy.
{code:xml}
 
 
 

 
 
 
 
 
 
 
 
 
 
{code}


Proposed setting allows to simplify semi-default level; without it user needs 
to use verbose fully-customized syntax in order to adjust only default Memory 
Policy size.

> Default MemoryPolicy settings improvements
> --
>
> Key: IGNITE-5024
> URL: https://issues.apache.org/jira/browse/IGNITE-5024
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Reporter: Sergey Chugunov
>Assignee: Alexey Goncharuk
>  Labels: general
> Fix For: 2.0
>
>
> h2. Notes
> Currently when user doesn't specify any MemoryPolicy configuration a default 
> one is created. It has a fixed size of 1 GB which seems to be too rigid.
> Also when user wants to override size of the default MemoryPolicy, the full 
> syntax of this configuration must be used; it is cumbersome in such simple 
> case.
> h2. Acceptance Criteria
> # Default MemoryPolicy is created with size of 80% of physical memory 
> available on machine.
> # New configuration property *defaultMemoryPolicySize* is introduced in 
> *memoryConfiguration* section to allow user to specify exact size in bytes 
> without applying verbose syntax of *memoryPolicyConfiguration* section.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5078) Partition lost event is fired only on coordinator when partition loss policy is IGNORE

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5078:


 Summary: Partition lost event is fired only on coordinator when 
partition loss policy is IGNORE
 Key: IGNITE-5078
 URL: https://issues.apache.org/jira/browse/IGNITE-5078
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.0
Reporter: Alexey Goncharuk
 Fix For: 2.1






--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-4799) Remove TcpDiscoverySpi.heartbeatsFrequency parameter

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4799:


[~sbberkov] {{TcpDiscoverySpi.metricsUpdateFreq}} is a private field and does 
not have accessor property, is it intended?

> Remove TcpDiscoverySpi.heartbeatsFrequency parameter
> 
>
> Key: IGNITE-4799
> URL: https://issues.apache.org/jira/browse/IGNITE-4799
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Denis Magda
>Assignee: Semen Boikov
>  Labels: important
> Fix For: 2.0
>
>  Time Spent: 16h
>  Remaining Estimate: 0h
>
> {{TcpDiscoverySpi.heartbeatsFrequency}} is no longer used to adjust the 
> heartbeats frequence. It affects the frequency of metrics messages sent over 
> the cluster ring.
> The following has to be done as a part of 2.0 release:
> * Remove {{TcpDiscoverySpi.heartbeatsFrequency}} parameter.
> * Use {{IgniteConfiguraion.getMetricsUpdateFrequency}} to adjust the rate of 
> metrics messages.
> * Make sure {{IgniteConfiguraion.getMetricsUpdateFrequency}} and metrics 
> messages are not participated in the failure detection process. We have to 
> clean up legacy code in {{ServerImpl}}.
> Refer to this discussion for more details:
> http://apache-ignite-developers.2346864.n4.nabble.com/Renaming-TcpDiscoverySpi-heartbeatsFrequency-to-TcpDiscoverySpi-metricsUpdateFrequency-td14941.html
>  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4523) Allow distributed SQL query execution over explicit set of partitions

[Alexei Scherbakov (JIRA)]

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

Alexei Scherbakov updated IGNITE-4523:
--
Fix Version/s: (was: 2.1)
   2.0

> Allow distributed SQL query execution over explicit set of partitions
> -
>
> Key: IGNITE-4523
> URL: https://issues.apache.org/jira/browse/IGNITE-4523
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, SQL
>Affects Versions: 1.8
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>  Labels: important
> Fix For: 2.0
>
>
> 3Currently distributed SQL query is executed on all nodes containing primary 
> partitions for a cache, sending map query requests on all nodes in grid.
> Sometimes we know in advance which partitions hold a data for query, on 
> example, in case of custom affinity function. 
> Therefore it's possible to reduce number of nodes receiving map query request 
> by providing explicit set of partitions, which will give significant 
> performance advantage and traffic reduction in case of very large clusters.
> Internally we already have such functionality, so the only necessary thing is 
> to provide public API for what.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-4523) Allow distributed SQL query execution over explicit set of partitions

[Sergi Vladykin (JIRA)]

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

Sergi Vladykin closed IGNITE-4523.
--

> Allow distributed SQL query execution over explicit set of partitions
> -
>
> Key: IGNITE-4523
> URL: https://issues.apache.org/jira/browse/IGNITE-4523
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, SQL
>Affects Versions: 1.8
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>  Labels: important
> Fix For: 2.1
>
>
> 3Currently distributed SQL query is executed on all nodes containing primary 
> partitions for a cache, sending map query requests on all nodes in grid.
> Sometimes we know in advance which partitions hold a data for query, on 
> example, in case of custom affinity function. 
> Therefore it's possible to reduce number of nodes receiving map query request 
> by providing explicit set of partitions, which will give significant 
> performance advantage and traffic reduction in case of very large clusters.
> Internally we already have such functionality, so the only necessary thing is 
> to provide public API for what.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5077) Support service security permissions

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev updated IGNITE-5077:

Summary: Support service security permissions  (was: Support service 
permissions)

> Support service security permissions
> 
>
> Key: IGNITE-5077
> URL: https://issues.apache.org/jira/browse/IGNITE-5077
> Project: Ignite
>  Issue Type: New Feature
>  Components: managed services
>Reporter: Dmitry Karachentsev
>Assignee: Dmitry Karachentsev
> Fix For: 2.1
>
>
> Need to add capability to specify permissions to allow/disallow executions of 
> particular services (similar to compute tasks).
> The following permissions should be added to the SecurityPermission enum:
> SERVICE_DEPLOY - for IgniteServices.deployXXX methods.
> SERVICE_CANCEL - for IgniteServices.cancel and IgniteServices.cancelAll 
> methods.
> SERVICE_INVOKE - for IgniteServices.service, IgniteServices.services and 
> IgniteServices.serviceProxy methods.
> SERVICE_INVOKE should allow fine-grained authorization based on service name, 
> similar to TASK_EXECUTE. E.g., a particular user should be able to execute 
> service A, but not service B.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5077) Support service permissions

[Dmitry Karachentsev (JIRA)]

Dmitry Karachentsev created IGNITE-5077:
---

 Summary: Support service permissions
 Key: IGNITE-5077
 URL: https://issues.apache.org/jira/browse/IGNITE-5077
 Project: Ignite
  Issue Type: New Feature
  Components: managed services
Reporter: Dmitry Karachentsev
Assignee: Dmitry Karachentsev
 Fix For: 2.1


Need to add capability to specify permissions to allow/disallow executions of 
particular services (similar to compute tasks).

The following permissions should be added to the SecurityPermission enum:

SERVICE_DEPLOY - for IgniteServices.deployXXX methods.
SERVICE_CANCEL - for IgniteServices.cancel and IgniteServices.cancelAll 
methods.
SERVICE_INVOKE - for IgniteServices.service, IgniteServices.services and 
IgniteServices.serviceProxy methods.

SERVICE_INVOKE should allow fine-grained authorization based on service name, 
similar to TASK_EXECUTE. E.g., a particular user should be able to execute 
service A, but not service B.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3488) Prohibit null as name in all the components (cache name first of all).

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-3488:


.NET tests fixed, local run looks good. Let me know if something fails on TC.

> Prohibit null as name in all the components (cache name first of all).
> --
>
> Key: IGNITE-3488
> URL: https://issues.apache.org/jira/browse/IGNITE-3488
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergi Vladykin
>Assignee: Igor Seliverstov
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
>
> Need to create a list of all the affected components.
> 2.0 migration guide has to be updated: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide
> Check REST API and update documentation (cacheName becomes mandatory)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4922) JDBC Driver: renew thin client based solution

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4922:

Priority: Major  (was: Blocker)

> JDBC Driver: renew thin client based solution
> -
>
> Key: IGNITE-4922
> URL: https://issues.apache.org/jira/browse/IGNITE-4922
> Project: Ignite
>  Issue Type: Task
>Reporter: Denis Magda
> Fix For: 2.1
>
>
> This is a parent ticket for all the activities that are intended to improve 
> the thin client based implementation of the JDBC driver making it default one.
>  
> Refer to the corresponding discussion on the dev list:
> http://apache-ignite-developers.2346864.n4.nabble.com/jdbc-vs-jdbc2-packages-td14309.html
> In a nutshell, depending on a type of a protocol to be used for the next-gen 
> version the options are the following:
> - This type of driver might be a default driver for tools and applications 
> that don't need transactional support. Existing REST based protocol can be 
> used for this scenario.
> - If we want to support transactions (which is optional at the beginning) 
> then Yakov solution (see discussion) can be applied. However, it makes sense 
> to implement it only after MVCC is ready.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-4523) Allow distributed SQL query execution over explicit set of partitions

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4523:

Fix Version/s: (was: 2.0)
   2.1

> Allow distributed SQL query execution over explicit set of partitions
> -
>
> Key: IGNITE-4523
> URL: https://issues.apache.org/jira/browse/IGNITE-4523
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, SQL
>Affects Versions: 1.8
>Reporter: Alexei Scherbakov
>Assignee: Alexei Scherbakov
>  Labels: important
> Fix For: 2.1
>
>
> 3Currently distributed SQL query is executed on all nodes containing primary 
> partitions for a cache, sending map query requests on all nodes in grid.
> Sometimes we know in advance which partitions hold a data for query, on 
> example, in case of custom affinity function. 
> Therefore it's possible to reduce number of nodes receiving map query request 
> by providing explicit set of partitions, which will give significant 
> performance advantage and traffic reduction in case of very large clusters.
> Internally we already have such functionality, so the only necessary thing is 
> to provide public API for what.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Closed] (IGNITE-5064) Obsolete EventTypes to be removed

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov closed IGNITE-5064.


Merged to ignite-2.0.

> Obsolete EventTypes to be removed
> -
>
> Key: IGNITE-5064
> URL: https://issues.apache.org/jira/browse/IGNITE-5064
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Sergey Chugunov
>Assignee: Alexey Kuznetsov
>  Labels: web-console
> Fix For: 2.0
>
>
> The following list of EventTypes were removed as part of 
> [IGNITE-4952|https://issues.apache.org/jira/browse/IGNITE-4952]:
> * *EventType#EVT_CACHE_OBJECT_SWAPPED*
> * *EventType#EVT_CACHE_OBJECT_UNSWAPPED*
> * *EventType#EVT_SWAP_SPACE_DATA_READ*
> * *EventType#EVT_SWAP_SPACE_DATA_STORED*
> * *EventType#EVT_SWAP_SPACE_DATA_REMOVED*
> * *EventType#EVT_SWAP_SPACE_CLEARED*
> * *EventType#EVT_SWAP_SPACE_DATA_EVICTED*
> * *EventType#EVT_CACHE_OBJECT_TO_OFFHEAP*
> * *EventType#EVT_CACHE_OBJECT_FROM_OFFHEAP*
> Corresponding array of swap events was also removed: 
> *EventType#EVTS_SWAPSPACE*.
> All references to these events must be removed from sources of web-console.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (IGNITE-5064) Obsolete EventTypes to be removed

[Alexey Kuznetsov (JIRA)]

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

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

> Obsolete EventTypes to be removed
> -
>
> Key: IGNITE-5064
> URL: https://issues.apache.org/jira/browse/IGNITE-5064
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Sergey Chugunov
>Assignee: Alexey Kuznetsov
>  Labels: web-console
> Fix For: 2.0
>
>
> The following list of EventTypes were removed as part of 
> [IGNITE-4952|https://issues.apache.org/jira/browse/IGNITE-4952]:
> * *EventType#EVT_CACHE_OBJECT_SWAPPED*
> * *EventType#EVT_CACHE_OBJECT_UNSWAPPED*
> * *EventType#EVT_SWAP_SPACE_DATA_READ*
> * *EventType#EVT_SWAP_SPACE_DATA_STORED*
> * *EventType#EVT_SWAP_SPACE_DATA_REMOVED*
> * *EventType#EVT_SWAP_SPACE_CLEARED*
> * *EventType#EVT_SWAP_SPACE_DATA_EVICTED*
> * *EventType#EVT_CACHE_OBJECT_TO_OFFHEAP*
> * *EventType#EVT_CACHE_OBJECT_FROM_OFFHEAP*
> Corresponding array of swap events was also removed: 
> *EventType#EVTS_SWAPSPACE*.
> All references to these events must be removed from sources of web-console.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-5050) .NET: IIgnite.GetMemoryMetrics

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-5050:


Blocked by IGNITE-5072. Looks like there will be no way to enable metrics from 
code in 2.0.

> .NET: IIgnite.GetMemoryMetrics
> --
>
> Key: IGNITE-5050
> URL: https://issues.apache.org/jira/browse/IGNITE-5050
> Project: Ignite
>  Issue Type: New Feature
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> Add {{IIgnite.GetMemoryMetrics()}} in .NET which delegates to 
> {{Ignite.memoryMetrics()}} in Java



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5076) Optimization of multi-threaded start nodes in tests

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-5076:
--

 Summary: Optimization of multi-threaded start nodes in tests
 Key: IGNITE-5076
 URL: https://issues.apache.org/jira/browse/IGNITE-5076
 Project: Ignite
  Issue Type: Improvement
Reporter: Dmitriy Govorukhin
Assignee: Dmitriy Govorukhin
 Fix For: 2.0


Concurrent start,will more effective if we have coordinator before, 
multi-threaded start nodes. If start all nodes concurrent, they will be compete 
for coordinator role, it is not effective way.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5020) Client node failed with NPE

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-5020:
--

Assignee: Pavel Konstantinov  (was: Dmitriy Govorukhin)

> Client node failed with NPE
> ---
>
> Key: IGNITE-5020
> URL: https://issues.apache.org/jira/browse/IGNITE-5020
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.0
>Reporter: Pavel Konstantinov
>Assignee: Pavel Konstantinov
> Fix For: 2.1
>
> Attachments: ignite-a48cdc72.0.log, ignite-b252f532.0.log, 
> ignite-be032f32.0.log, ignite-d11f70e0.0.log
>
>
> Start 2 server nodes
> Start client
> Stop server nodes
> Start server node
> {code}
> [11:12:58,181][INFO][tcp-client-disco-msg-worker-#5%tester%][TcpDiscoverySpi] 
> Client node disconnected from cluster, will try to reconnect with new id 
> [newId=62cb8b71-4fe1-4fc7-b60b-236063ce9571, 
> prevId=a48cdc72-d9b2-46db-b07f-3250610df1f8, locNode=TcpDiscoveryNode 
> [id=a48cdc72-d9b2-46db-b07f-3250610df1f8, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 192.168.1.40, 192.168.56.1], sockAddrs=[/192.168.1.40:0, /0:0:0:0:0:0:0:1:0, 
> /127.0.0.1:0, /192.168.56.1:0], discPort=0, order=4, intOrder=0, 
> lastExchangeTime=1492575133264, loc=true, ver=2.0.0#20170418-sha1:6a1d263d, 
> isClient=true]]
> [11:12:59,580][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache: 
> igfs-data
> [11:12:59,586][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache: 
> offheap-sorted-100
> [11:12:59,588][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache: 
> c_replicated
> [11:12:59,591][INFO][sys-#30%tester%][GridCacheProcessor] Stopped cache: 
> c_partitioned2
> [11:12:59,591][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache: 
> offheap-fifo-100
> [11:12:59,597][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache: 
> oh_partitioned
> [11:12:59,597][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache: 
> near-lru-100
> [11:12:59,601][INFO][sys-#35%tester%][GridCacheProcessor] Stopped cache: 
> ttl_partitioned
> [11:12:59,603][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache: 
> c_partitioned3
> [11:12:59,603][INFO][sys-#33%tester%][GridCacheProcessor] Stopped cache: 
> offheap-lru-100
> [11:12:59,604][INFO][sys-#27%tester%][GridCacheProcessor] Stopped cache: 
> near-sorted-100
> [11:12:59,608][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache: 
> c_partitioned
> [11:12:59,608][SEVERE][exchange-worker-#36%tester%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=7, 
> minorTopVer=0], nodeId=62cb8b71, evt=NODE_JOINED]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.fetchAffinityOnJoin(CacheAffinitySharedManager.java:953)
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onClientEvent(CacheAffinitySharedManager.java:649)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClientNodeEvent(GridDhtPartitionsExchangeFuture.java:739)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:549)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1806)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (IGNITE-3488) Prohibit null as name in all the components (cache name first of all).

[Igor Seliverstov (JIRA)]

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

Igor Seliverstov commented on IGNITE-3488:
--

[~ptupitsyn] Please take a look. There are quite a lot of fails in .net tests. 
I'll appreciate your help on that.

> Prohibit null as name in all the components (cache name first of all).
> --
>
> Key: IGNITE-3488
> URL: https://issues.apache.org/jira/browse/IGNITE-3488
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.8
>Reporter: Sergi Vladykin
>Assignee: Igor Seliverstov
>Priority: Critical
>  Labels: important
> Fix For: 2.0
>
>
> Need to create a list of all the affected components.
> 2.0 migration guide has to be updated: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide
> Check REST API and update documentation (cacheName becomes mandatory)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5064) Obsolete EventTypes to be removed

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-5064:
-
Fix Version/s: 2.0

> Obsolete EventTypes to be removed
> -
>
> Key: IGNITE-5064
> URL: https://issues.apache.org/jira/browse/IGNITE-5064
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Sergey Chugunov
>Assignee: Alexey Kuznetsov
>  Labels: web-console
> Fix For: 2.0
>
>
> The following list of EventTypes were removed as part of 
> [IGNITE-4952|https://issues.apache.org/jira/browse/IGNITE-4952]:
> * *EventType#EVT_CACHE_OBJECT_SWAPPED*
> * *EventType#EVT_CACHE_OBJECT_UNSWAPPED*
> * *EventType#EVT_SWAP_SPACE_DATA_READ*
> * *EventType#EVT_SWAP_SPACE_DATA_STORED*
> * *EventType#EVT_SWAP_SPACE_DATA_REMOVED*
> * *EventType#EVT_SWAP_SPACE_CLEARED*
> * *EventType#EVT_SWAP_SPACE_DATA_EVICTED*
> * *EventType#EVT_CACHE_OBJECT_TO_OFFHEAP*
> * *EventType#EVT_CACHE_OBJECT_FROM_OFFHEAP*
> Corresponding array of swap events was also removed: 
> *EventType#EVTS_SWAPSPACE*.
> All references to these events must be removed from sources of web-console.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5064) Obsolete EventTypes to be removed

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov updated IGNITE-5064:
-
Component/s: (was: general)
 wizards

> Obsolete EventTypes to be removed
> -
>
> Key: IGNITE-5064
> URL: https://issues.apache.org/jira/browse/IGNITE-5064
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Reporter: Sergey Chugunov
>Assignee: Alexey Kuznetsov
>  Labels: web-console
>
> The following list of EventTypes were removed as part of 
> [IGNITE-4952|https://issues.apache.org/jira/browse/IGNITE-4952]:
> * *EventType#EVT_CACHE_OBJECT_SWAPPED*
> * *EventType#EVT_CACHE_OBJECT_UNSWAPPED*
> * *EventType#EVT_SWAP_SPACE_DATA_READ*
> * *EventType#EVT_SWAP_SPACE_DATA_STORED*
> * *EventType#EVT_SWAP_SPACE_DATA_REMOVED*
> * *EventType#EVT_SWAP_SPACE_CLEARED*
> * *EventType#EVT_SWAP_SPACE_DATA_EVICTED*
> * *EventType#EVT_CACHE_OBJECT_TO_OFFHEAP*
> * *EventType#EVT_CACHE_OBJECT_FROM_OFFHEAP*
> Corresponding array of swap events was also removed: 
> *EventType#EVTS_SWAPSPACE*.
> All references to these events must be removed from sources of web-console.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5020) Client node failed with NPE

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk updated IGNITE-5020:
-
Fix Version/s: (was: 2.0)
   2.1

> Client node failed with NPE
> ---
>
> Key: IGNITE-5020
> URL: https://issues.apache.org/jira/browse/IGNITE-5020
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.0
>Reporter: Pavel Konstantinov
>Assignee: Dmitriy Govorukhin
> Fix For: 2.1
>
> Attachments: ignite-a48cdc72.0.log, ignite-b252f532.0.log, 
> ignite-be032f32.0.log, ignite-d11f70e0.0.log
>
>
> Start 2 server nodes
> Start client
> Stop server nodes
> Start server node
> {code}
> [11:12:58,181][INFO][tcp-client-disco-msg-worker-#5%tester%][TcpDiscoverySpi] 
> Client node disconnected from cluster, will try to reconnect with new id 
> [newId=62cb8b71-4fe1-4fc7-b60b-236063ce9571, 
> prevId=a48cdc72-d9b2-46db-b07f-3250610df1f8, locNode=TcpDiscoveryNode 
> [id=a48cdc72-d9b2-46db-b07f-3250610df1f8, addrs=[0:0:0:0:0:0:0:1, 127.0.0.1, 
> 192.168.1.40, 192.168.56.1], sockAddrs=[/192.168.1.40:0, /0:0:0:0:0:0:0:1:0, 
> /127.0.0.1:0, /192.168.56.1:0], discPort=0, order=4, intOrder=0, 
> lastExchangeTime=1492575133264, loc=true, ver=2.0.0#20170418-sha1:6a1d263d, 
> isClient=true]]
> [11:12:59,580][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache: 
> igfs-data
> [11:12:59,586][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache: 
> offheap-sorted-100
> [11:12:59,588][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache: 
> c_replicated
> [11:12:59,591][INFO][sys-#30%tester%][GridCacheProcessor] Stopped cache: 
> c_partitioned2
> [11:12:59,591][INFO][sys-#31%tester%][GridCacheProcessor] Stopped cache: 
> offheap-fifo-100
> [11:12:59,597][INFO][sys-#34%tester%][GridCacheProcessor] Stopped cache: 
> oh_partitioned
> [11:12:59,597][INFO][sys-#29%tester%][GridCacheProcessor] Stopped cache: 
> near-lru-100
> [11:12:59,601][INFO][sys-#35%tester%][GridCacheProcessor] Stopped cache: 
> ttl_partitioned
> [11:12:59,603][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache: 
> c_partitioned3
> [11:12:59,603][INFO][sys-#33%tester%][GridCacheProcessor] Stopped cache: 
> offheap-lru-100
> [11:12:59,604][INFO][sys-#27%tester%][GridCacheProcessor] Stopped cache: 
> near-sorted-100
> [11:12:59,608][INFO][sys-#32%tester%][GridCacheProcessor] Stopped cache: 
> c_partitioned
> [11:12:59,608][SEVERE][exchange-worker-#36%tester%][GridDhtPartitionsExchangeFuture]
>  Failed to reinitialize local partitions (preloading will be stopped): 
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=7, 
> minorTopVer=0], nodeId=62cb8b71, evt=NODE_JOINED]
> java.lang.NullPointerException
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.fetchAffinityOnJoin(CacheAffinitySharedManager.java:953)
> at 
> org.apache.ignite.internal.processors.cache.CacheAffinitySharedManager.onClientEvent(CacheAffinitySharedManager.java:649)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.onClientNodeEvent(GridDhtPartitionsExchangeFuture.java:739)
> at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:549)
> at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1806)
> at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5069) QueryWords example fails with exception

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5069:

Component/s: general

> QueryWords example fails with exception
> ---
>
> Key: IGNITE-5069
> URL: https://issues.apache.org/jira/browse/IGNITE-5069
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.0
>
>
> [~sergi.vladykin], please have a look. It may happen so that avg(cnt) in 
> former Ignite versions was returned as double for long column. For current 
> master it is returned as long and causes exception in formatter. I was able 
> to reproduce it on 1.9 also, but did not try other versions.
> Steps to reproduce
> # start {{ExampleNodeStartup}}
> # start {{QueryWords}}
> # start {{StreamWords}}
> {noformat}
> /opt/jdk/jdk1.8.0_121/bin/java...
> org.apache.ignite.examples.streaming.wordcount.QueryWords
> [18:20:17]__   
> [18:20:17]   /  _/ ___/ |/ /  _/_  __/ __/ 
> [18:20:17]  _/ // (7 7// /  / / / _/   
> [18:20:17] /___/\___/_/|_/___/ /_/ /___/  
> [18:20:17] 
> [18:20:17] ver. 2.1.0-SNAPSHOT#19700101-sha1:DEV
> [18:20:17] 2017 Copyright(C) Apache Software Foundation
> [18:20:17] 
> [18:20:17] Ignite documentation: http://ignite.apache.org
> [18:20:17] 
> [18:20:17] Quiet mode.
> [18:20:17]   ^-- Logging to file 
> '/home/yzhdanov/projects/incubator-ignite/work/log/ignite-dbfdab2d.log'
> [18:20:17]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [18:20:17] 
> [18:20:17] OS: Linux 4.8.0-46-generic amd64
> [18:20:17] VM information: Java(TM) SE Runtime Environment 1.8.0_121-b13 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.121-b13
> [18:20:17] Initial heap size is 246MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [18:20:17] Configured plugins:
> [18:20:17]   ^-- None
> [18:20:17] 
> [18:20:17] Message queue limit is set to 0 which may lead to potential OOMEs 
> when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to 
> message queues growth on sender and receiver sides.
> [18:20:17] Security status [authentication=off, tls/ssl=off]
> [18:20:18] REST protocols do not start on client node. To start the protocols 
> on client node set '-DIGNITE_REST_START_ON_CLIENT=true' system property.
> [18:20:20] Performance suggestions for grid  (fix if possible)
> [18:20:20] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [18:20:20]   ^-- Disable grid events (remove 'includeEventTypes' from 
> configuration)
> [18:20:20]   ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM 
> options)
> [18:20:20]   ^-- Specify JVM heap max size (add '-Xmx[g|G|m|M|k|K]' to 
> JVM options)
> [18:20:20]   ^-- Set max direct memory size if getting 'OOME: Direct buffer 
> memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
> [18:20:20]   ^-- Disable processing of calls to System.gc() (add 
> '-XX:+DisableExplicitGC' to JVM options)
> [18:20:20] Refer to this page for more performance suggestions: 
> https://apacheignite.readme.io/docs/jvm-and-system-tuning
> [18:20:20] 
> [18:20:20] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [18:20:20] 
> [18:20:20] Ignite node started OK (id=dbfdab2d)
> [18:20:20] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=6.8GB]
> Query result set is empty.
> Query result set is empty.
> [18:20:27] Topology snapshot [ver=3, servers=1, clients=2, CPUs=4, 
> heap=10.0GB]
> Query results [avg=[18:20:33] Ignite node stopped OK [uptime=00:00:12:733]
> Exception in thread "main" java.util.IllegalFormatConversionException: f != 
> java.lang.Long
>   at 
> java.util.Formatter$FormatSpecifier.failConversion(Formatter.java:4302)
>   at java.util.Formatter$FormatSpecifier.printFloat(Formatter.java:2806)
>   at java.util.Formatter$FormatSpecifier.print(Formatter.java:2753)
>   at java.util.Formatter.format(Formatter.java:2520)
>   at java.io.PrintStream.format(PrintStream.java:970)
>   at java.io.PrintStream.printf(PrintStream.java:871)
>   at 
> org.apache.ignite.examples.streaming.wordcount.QueryWords.main(QueryWords.java:78)
> Process finished with exit code 1
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5069) QueryWords example fails with exception

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5069:

Component/s: (was: general)
 examples

> QueryWords example fails with exception
> ---
>
> Key: IGNITE-5069
> URL: https://issues.apache.org/jira/browse/IGNITE-5069
> Project: Ignite
>  Issue Type: Bug
>  Components: examples
>Reporter: Yakov Zhdanov
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.0
>
>
> [~sergi.vladykin], please have a look. It may happen so that avg(cnt) in 
> former Ignite versions was returned as double for long column. For current 
> master it is returned as long and causes exception in formatter. I was able 
> to reproduce it on 1.9 also, but did not try other versions.
> Steps to reproduce
> # start {{ExampleNodeStartup}}
> # start {{QueryWords}}
> # start {{StreamWords}}
> {noformat}
> /opt/jdk/jdk1.8.0_121/bin/java...
> org.apache.ignite.examples.streaming.wordcount.QueryWords
> [18:20:17]__   
> [18:20:17]   /  _/ ___/ |/ /  _/_  __/ __/ 
> [18:20:17]  _/ // (7 7// /  / / / _/   
> [18:20:17] /___/\___/_/|_/___/ /_/ /___/  
> [18:20:17] 
> [18:20:17] ver. 2.1.0-SNAPSHOT#19700101-sha1:DEV
> [18:20:17] 2017 Copyright(C) Apache Software Foundation
> [18:20:17] 
> [18:20:17] Ignite documentation: http://ignite.apache.org
> [18:20:17] 
> [18:20:17] Quiet mode.
> [18:20:17]   ^-- Logging to file 
> '/home/yzhdanov/projects/incubator-ignite/work/log/ignite-dbfdab2d.log'
> [18:20:17]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [18:20:17] 
> [18:20:17] OS: Linux 4.8.0-46-generic amd64
> [18:20:17] VM information: Java(TM) SE Runtime Environment 1.8.0_121-b13 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.121-b13
> [18:20:17] Initial heap size is 246MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [18:20:17] Configured plugins:
> [18:20:17]   ^-- None
> [18:20:17] 
> [18:20:17] Message queue limit is set to 0 which may lead to potential OOMEs 
> when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to 
> message queues growth on sender and receiver sides.
> [18:20:17] Security status [authentication=off, tls/ssl=off]
> [18:20:18] REST protocols do not start on client node. To start the protocols 
> on client node set '-DIGNITE_REST_START_ON_CLIENT=true' system property.
> [18:20:20] Performance suggestions for grid  (fix if possible)
> [18:20:20] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [18:20:20]   ^-- Disable grid events (remove 'includeEventTypes' from 
> configuration)
> [18:20:20]   ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM 
> options)
> [18:20:20]   ^-- Specify JVM heap max size (add '-Xmx[g|G|m|M|k|K]' to 
> JVM options)
> [18:20:20]   ^-- Set max direct memory size if getting 'OOME: Direct buffer 
> memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
> [18:20:20]   ^-- Disable processing of calls to System.gc() (add 
> '-XX:+DisableExplicitGC' to JVM options)
> [18:20:20] Refer to this page for more performance suggestions: 
> https://apacheignite.readme.io/docs/jvm-and-system-tuning
> [18:20:20] 
> [18:20:20] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [18:20:20] 
> [18:20:20] Ignite node started OK (id=dbfdab2d)
> [18:20:20] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=6.8GB]
> Query result set is empty.
> Query result set is empty.
> [18:20:27] Topology snapshot [ver=3, servers=1, clients=2, CPUs=4, 
> heap=10.0GB]
> Query results [avg=[18:20:33] Ignite node stopped OK [uptime=00:00:12:733]
> Exception in thread "main" java.util.IllegalFormatConversionException: f != 
> java.lang.Long
>   at 
> java.util.Formatter$FormatSpecifier.failConversion(Formatter.java:4302)
>   at java.util.Formatter$FormatSpecifier.printFloat(Formatter.java:2806)
>   at java.util.Formatter$FormatSpecifier.print(Formatter.java:2753)
>   at java.util.Formatter.format(Formatter.java:2520)
>   at java.io.PrintStream.format(PrintStream.java:970)
>   at java.io.PrintStream.printf(PrintStream.java:871)
>   at 
> org.apache.ignite.examples.streaming.wordcount.QueryWords.main(QueryWords.java:78)
> Process finished with exit code 1
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5075) Implement logical 'cache groups' sharing the same physical caches

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-5075:


 Summary: Implement logical 'cache groups' sharing the same 
physical caches
 Key: IGNITE-5075
 URL: https://issues.apache.org/jira/browse/IGNITE-5075
 Project: Ignite
  Issue Type: Task
  Components: cache
Reporter: Semen Boikov
Assignee: Semen Boikov
Priority: Critical
 Fix For: 2.1


Currently started caches have pretty large memory overhead (e.g. to store 
affinity and partitions state information). If some application requires 
thousands caches with similar configuration then it would be useful to allow 
for 'logical' cache to reuse the same 'physical' cache. Let's introduce new 
CacheConfiguration property - 'groupName', caches with the same groupName will 
use the same 'physical' cache.




--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (IGNITE-5069) QueryWords example fails with exception

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-5069:
---

Assignee: Vladimir Ozerov

> QueryWords example fails with exception
> ---
>
> Key: IGNITE-5069
> URL: https://issues.apache.org/jira/browse/IGNITE-5069
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Vladimir Ozerov
>Priority: Blocker
> Fix For: 2.0
>
>
> [~sergi.vladykin], please have a look. It may happen so that avg(cnt) in 
> former Ignite versions was returned as double for long column. For current 
> master it is returned as long and causes exception in formatter. I was able 
> to reproduce it on 1.9 also, but did not try other versions.
> Steps to reproduce
> # start {{ExampleNodeStartup}}
> # start {{QueryWords}}
> # start {{StreamWords}}
> {noformat}
> /opt/jdk/jdk1.8.0_121/bin/java...
> org.apache.ignite.examples.streaming.wordcount.QueryWords
> [18:20:17]__   
> [18:20:17]   /  _/ ___/ |/ /  _/_  __/ __/ 
> [18:20:17]  _/ // (7 7// /  / / / _/   
> [18:20:17] /___/\___/_/|_/___/ /_/ /___/  
> [18:20:17] 
> [18:20:17] ver. 2.1.0-SNAPSHOT#19700101-sha1:DEV
> [18:20:17] 2017 Copyright(C) Apache Software Foundation
> [18:20:17] 
> [18:20:17] Ignite documentation: http://ignite.apache.org
> [18:20:17] 
> [18:20:17] Quiet mode.
> [18:20:17]   ^-- Logging to file 
> '/home/yzhdanov/projects/incubator-ignite/work/log/ignite-dbfdab2d.log'
> [18:20:17]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [18:20:17] 
> [18:20:17] OS: Linux 4.8.0-46-generic amd64
> [18:20:17] VM information: Java(TM) SE Runtime Environment 1.8.0_121-b13 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.121-b13
> [18:20:17] Initial heap size is 246MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [18:20:17] Configured plugins:
> [18:20:17]   ^-- None
> [18:20:17] 
> [18:20:17] Message queue limit is set to 0 which may lead to potential OOMEs 
> when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to 
> message queues growth on sender and receiver sides.
> [18:20:17] Security status [authentication=off, tls/ssl=off]
> [18:20:18] REST protocols do not start on client node. To start the protocols 
> on client node set '-DIGNITE_REST_START_ON_CLIENT=true' system property.
> [18:20:20] Performance suggestions for grid  (fix if possible)
> [18:20:20] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [18:20:20]   ^-- Disable grid events (remove 'includeEventTypes' from 
> configuration)
> [18:20:20]   ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM 
> options)
> [18:20:20]   ^-- Specify JVM heap max size (add '-Xmx[g|G|m|M|k|K]' to 
> JVM options)
> [18:20:20]   ^-- Set max direct memory size if getting 'OOME: Direct buffer 
> memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
> [18:20:20]   ^-- Disable processing of calls to System.gc() (add 
> '-XX:+DisableExplicitGC' to JVM options)
> [18:20:20] Refer to this page for more performance suggestions: 
> https://apacheignite.readme.io/docs/jvm-and-system-tuning
> [18:20:20] 
> [18:20:20] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [18:20:20] 
> [18:20:20] Ignite node started OK (id=dbfdab2d)
> [18:20:20] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=6.8GB]
> Query result set is empty.
> Query result set is empty.
> [18:20:27] Topology snapshot [ver=3, servers=1, clients=2, CPUs=4, 
> heap=10.0GB]
> Query results [avg=[18:20:33] Ignite node stopped OK [uptime=00:00:12:733]
> Exception in thread "main" java.util.IllegalFormatConversionException: f != 
> java.lang.Long
>   at 
> java.util.Formatter$FormatSpecifier.failConversion(Formatter.java:4302)
>   at java.util.Formatter$FormatSpecifier.printFloat(Formatter.java:2806)
>   at java.util.Formatter$FormatSpecifier.print(Formatter.java:2753)
>   at java.util.Formatter.format(Formatter.java:2520)
>   at java.io.PrintStream.format(PrintStream.java:970)
>   at java.io.PrintStream.printf(PrintStream.java:871)
>   at 
> org.apache.ignite.examples.streaming.wordcount.QueryWords.main(QueryWords.java:78)
> Process finished with exit code 1
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (IGNITE-5069) QueryWords example fails with exception

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-5069:

Priority: Minor  (was: Blocker)

> QueryWords example fails with exception
> ---
>
> Key: IGNITE-5069
> URL: https://issues.apache.org/jira/browse/IGNITE-5069
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Yakov Zhdanov
>Assignee: Vladimir Ozerov
>Priority: Minor
> Fix For: 2.0
>
>
> [~sergi.vladykin], please have a look. It may happen so that avg(cnt) in 
> former Ignite versions was returned as double for long column. For current 
> master it is returned as long and causes exception in formatter. I was able 
> to reproduce it on 1.9 also, but did not try other versions.
> Steps to reproduce
> # start {{ExampleNodeStartup}}
> # start {{QueryWords}}
> # start {{StreamWords}}
> {noformat}
> /opt/jdk/jdk1.8.0_121/bin/java...
> org.apache.ignite.examples.streaming.wordcount.QueryWords
> [18:20:17]__   
> [18:20:17]   /  _/ ___/ |/ /  _/_  __/ __/ 
> [18:20:17]  _/ // (7 7// /  / / / _/   
> [18:20:17] /___/\___/_/|_/___/ /_/ /___/  
> [18:20:17] 
> [18:20:17] ver. 2.1.0-SNAPSHOT#19700101-sha1:DEV
> [18:20:17] 2017 Copyright(C) Apache Software Foundation
> [18:20:17] 
> [18:20:17] Ignite documentation: http://ignite.apache.org
> [18:20:17] 
> [18:20:17] Quiet mode.
> [18:20:17]   ^-- Logging to file 
> '/home/yzhdanov/projects/incubator-ignite/work/log/ignite-dbfdab2d.log'
> [18:20:17]   ^-- To see **FULL** console log here add -DIGNITE_QUIET=false or 
> "-v" to ignite.{sh|bat}
> [18:20:17] 
> [18:20:17] OS: Linux 4.8.0-46-generic amd64
> [18:20:17] VM information: Java(TM) SE Runtime Environment 1.8.0_121-b13 
> Oracle Corporation Java HotSpot(TM) 64-Bit Server VM 25.121-b13
> [18:20:17] Initial heap size is 246MB (should be no less than 512MB, use 
> -Xms512m -Xmx512m).
> [18:20:17] Configured plugins:
> [18:20:17]   ^-- None
> [18:20:17] 
> [18:20:17] Message queue limit is set to 0 which may lead to potential OOMEs 
> when running cache operations in FULL_ASYNC or PRIMARY_SYNC modes due to 
> message queues growth on sender and receiver sides.
> [18:20:17] Security status [authentication=off, tls/ssl=off]
> [18:20:18] REST protocols do not start on client node. To start the protocols 
> on client node set '-DIGNITE_REST_START_ON_CLIENT=true' system property.
> [18:20:20] Performance suggestions for grid  (fix if possible)
> [18:20:20] To disable, set -DIGNITE_PERFORMANCE_SUGGESTIONS_DISABLED=true
> [18:20:20]   ^-- Disable grid events (remove 'includeEventTypes' from 
> configuration)
> [18:20:20]   ^-- Enable G1 Garbage Collector (add '-XX:+UseG1GC' to JVM 
> options)
> [18:20:20]   ^-- Specify JVM heap max size (add '-Xmx[g|G|m|M|k|K]' to 
> JVM options)
> [18:20:20]   ^-- Set max direct memory size if getting 'OOME: Direct buffer 
> memory' (add '-XX:MaxDirectMemorySize=[g|G|m|M|k|K]' to JVM options)
> [18:20:20]   ^-- Disable processing of calls to System.gc() (add 
> '-XX:+DisableExplicitGC' to JVM options)
> [18:20:20] Refer to this page for more performance suggestions: 
> https://apacheignite.readme.io/docs/jvm-and-system-tuning
> [18:20:20] 
> [18:20:20] To start Console Management & Monitoring run 
> ignitevisorcmd.{sh|bat}
> [18:20:20] 
> [18:20:20] Ignite node started OK (id=dbfdab2d)
> [18:20:20] Topology snapshot [ver=2, servers=1, clients=1, CPUs=4, heap=6.8GB]
> Query result set is empty.
> Query result set is empty.
> [18:20:27] Topology snapshot [ver=3, servers=1, clients=2, CPUs=4, 
> heap=10.0GB]
> Query results [avg=[18:20:33] Ignite node stopped OK [uptime=00:00:12:733]
> Exception in thread "main" java.util.IllegalFormatConversionException: f != 
> java.lang.Long
>   at 
> java.util.Formatter$FormatSpecifier.failConversion(Formatter.java:4302)
>   at java.util.Formatter$FormatSpecifier.printFloat(Formatter.java:2806)
>   at java.util.Formatter$FormatSpecifier.print(Formatter.java:2753)
>   at java.util.Formatter.format(Formatter.java:2520)
>   at java.io.PrintStream.format(PrintStream.java:970)
>   at java.io.PrintStream.printf(PrintStream.java:871)
>   at 
> org.apache.ignite.examples.streaming.wordcount.QueryWords.main(QueryWords.java:78)
> Process finished with exit code 1
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5074) Split up asynchronous and synchronous calls in PlatformCompute

[Igor Sapego (JIRA)]

Igor Sapego created IGNITE-5074:
---

 Summary: Split up asynchronous and synchronous calls in 
PlatformCompute
 Key: IGNITE-5074
 URL: https://issues.apache.org/jira/browse/IGNITE-5074
 Project: Ignite
  Issue Type: Task
  Components: platforms
Affects Versions: 1.9
Reporter: Igor Sapego
 Fix For: 2.1


Currently, there is only asynchronous version of calls in {{PlatformCompute}}, 
which means we create temporary objects (like futures and listeners) which we 
do not need during synchronous calls.

Add synchronous version of API calls which generate less garbage.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5073) Race between partition exchange process and client cache operations

[Semen Boikov (JIRA)]

Semen Boikov created IGNITE-5073:


 Summary: Race between partition exchange process and client cache 
operations
 Key: IGNITE-5073
 URL: https://issues.apache.org/jira/browse/IGNITE-5073
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Semen Boikov
Assignee: Semen Boikov
Priority: Critical
 Fix For: 2.1


Added test reproducing issue IgniteCacheClientMultiNodeUpdateTopologyLockTest:
- 3 servers (node1, node2, node3), 1 client
- client starts pessimistic tx
- client locks key1 on node2
- new node joins, exchanges starts, on node3 there are no ongoging cache 
operations and node3 sends GridDhtPartitionsSingleMessage to coordinator
- client locks key2 on node3
- client commits tx, when tx started on node2 finishes then node2 will send 
GridDhtPartitionsSingleMessage to coordinator and exchange will be completed 
before tx on node3 finished

One potential fix for this issue is change exchange protocol to use two steps.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (IGNITE-5072) Move memory metrics to snapshots

[Alexey Goncharuk (JIRA)]

Alexey Goncharuk created IGNITE-5072:


 Summary: Move memory metrics to snapshots
 Key: IGNITE-5072
 URL: https://issues.apache.org/jira/browse/IGNITE-5072
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.0
Reporter: Alexey Goncharuk
Assignee: Alexey Goncharuk
 Fix For: 2.0


This is a follow-up ticket for the following discussion:
http://apache-ignite-developers.2346864.n4.nabble.com/MemoryMetrics-interface-inconsistencies-td17156.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)