[jira] [Commented] (IGNITE-3581) CPP: Place different enums and constants in separate namespaces or structs.

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-3581:


[~isapego] I like the change from {{IGNITE_TX_STATE_MARKED_ROLLBACK}} to 
{{TransactionState::MARKED_ROLLBACK}}, easier to read and to write.

But is it common to place enum inside struct to achieve this?

> CPP: Place different enums and constants in separate namespaces or structs.
> ---
>
> Key: IGNITE-3581
> URL: https://issues.apache.org/jira/browse/IGNITE-3581
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.0
>
>
> The common practice is to place enums and constants in separate namespaces or 
> structs. This way we can group them and avoid name clashes without the need 
> to use long names.
> [Details|http://stackoverflow.com/questions/7090130/enum-in-a-namespace].



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

[jira] [Commented] (IGNITE-4052) Add ability to set up users for MESOS

[Vadim Opolski (JIRA)]

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

Vadim Opolski commented on IGNITE-4052:
---

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

> Add ability to set up users for MESOS
> -
>
> Key: IGNITE-4052
> URL: https://issues.apache.org/jira/browse/IGNITE-4052
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.7
>Reporter: Nikolay Tikhonov
>Assignee: Vadim Opolski
>Priority: Trivial
>
> In current implementation Ignite Mesos Framework connects to MESOS cluster 
> via current user. Need to add ability to configure this parameters via system 
> env properties. Also need to add properties for mesos role.
> See org/apache/ignite/mesos/IgniteFramework.java:537



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

[jira] [Created] (IGNITE-4954) Timeout in ignite-cassandra SessionPool is not configurable

[Valentin Kulichenko (JIRA)]

Valentin Kulichenko created IGNITE-4954:
---

 Summary: Timeout in ignite-cassandra SessionPool is not 
configurable
 Key: IGNITE-4954
 URL: https://issues.apache.org/jira/browse/IGNITE-4954
 Project: Ignite
  Issue Type: Bug
  Components: ignite-cassandra
Affects Versions: 1.9
Reporter: Valentin Kulichenko
Assignee: Valentin Kulichenko
Priority: Critical
 Fix For: 2.0


Cassandra cache store implementation uses {{SessionPool}} class which kills 
idle sessions after 5 minutes. Need to make this timeout configurable.



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

[jira] [Commented] (IGNITE-3581) CPP: Place different enums and constants in separate namespaces or structs.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3581:


GitHub user isapego opened a pull request:

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

IGNITE-3581: CPP: Moved enums to separate structs



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

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

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

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


commit 1fd053e9ff683cb8f82d7fc4f5f8ab97c60ec031
Author: Igor Sapego 
Date:   2017-04-11T10:42:23Z

IGNITE-3581: Moved enums to separate structs for Core

commit 54f1cc311524edc099cc8fb0e580c5dfb75a5842
Author: Igor Sapego 
Date:   2017-04-12T14:19:01Z

IGNITE-3581: Implemented for enums from ODBC

commit b4469927c393fe9cc7db8c839e827c7ad29215f5
Author: Igor Sapego 
Date:   2017-04-12T15:05:05Z

IGNITE-3581: Renaming




> CPP: Place different enums and constants in separate namespaces or structs.
> ---
>
> Key: IGNITE-3581
> URL: https://issues.apache.org/jira/browse/IGNITE-3581
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.0
>
>
> The common practice is to place enums and constants in separate namespaces or 
> structs. This way we can group them and avoid name clashes without the need 
> to use long names.
> [Details|http://stackoverflow.com/questions/7090130/enum-in-a-namespace].



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

[jira] [Commented] (IGNITE-3682) GridFunc: move all inner anonymous classes to separate top-level classes.

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-3682:
-

[~daradurvs], I've removed unused methods during code review. Changes and TC 
look good to me. Merged into master branch with some fixes.
Thanks a lot for your contribution!

> GridFunc: move all inner anonymous classes to separate top-level classes.
> -
>
> Key: IGNITE-3682
> URL: https://issues.apache.org/jira/browse/IGNITE-3682
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important
> Fix For: 2.0
>
>
> Otherwise almost any change to class {{GridFunc}} will lead to serialization 
> issues because we have no control over inner class names.
> E.g. if removed single anonymous class, another anonymous class might change 
> it's name from {{GridFunc$4}} to {{GridFunc$3}}.



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

[jira] [Updated] (IGNITE-3195) Rebalancing: IgniteConfiguration.rebalanceThreadPoolSize is wrongly treated

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov updated IGNITE-3195:
-
Fix Version/s: 2.0

> Rebalancing: IgniteConfiguration.rebalanceThreadPoolSize is wrongly treated
> ---
>
> Key: IGNITE-3195
> URL: https://issues.apache.org/jira/browse/IGNITE-3195
> Project: Ignite
>  Issue Type: Bug
>Reporter: Denis Magda
>Assignee: Anton Vinogradov
> Fix For: 2.0
>
>
> Presently it's considered that the maximum number of threads that has to 
> process all demand and supply messages coming from all the nodes must not be 
> bigger than {{IgniteConfiguration.rebalanceThreadPoolSize}}.
> Current implementation relies on ordered messages functionality creating a 
> number of topics equal to {{IgniteConfiguration.rebalanceThreadPoolSize}}.
> However, the implementation doesn't take into account that ordered messages, 
> that correspond to a particular topic, are processed in parallel for 
> different nodes. Refer to the implementation of 
> {{GridIoManager.processOrderedMessage}} to see that for every topic there 
> will be a unique {{GridCommunicationMessageSet}} for every node.
> Also to prove that this is true you can refer to this execution stack 
> {noformat}
> java.lang.RuntimeException: HAPPENED DEMAND
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:378)
>   at 
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$5.apply(GridCachePartitionExchangeManager.java:364)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:622)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:320)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$300(GridCacheIoManager.java:81)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$OrderedMessageListener.onMessage(GridCacheIoManager.java:1125)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1219)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1600(GridIoManager.java:105)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$GridCommunicationMessageSet.unwind(GridIoManager.java:2456)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.unwindMessageSet(GridIoManager.java:1179)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$1900(GridIoManager.java:105)
>   at 
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:1148)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>   at java.lang.Thread.run(Thread.java:745)
> {noformat}
> All this means that in fact the number of threads that will be busy with 
> replication activity will be equal to 
> {{IgniteConfiguration.rebalanceThreadPoolSize}} x 
> number_of_nodes_participated_in_rebalancing



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

[jira] [Updated] (IGNITE-4953) Rework logic of concurrent schema changes

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4953:

Labels: important  (was: )

> Rework logic of concurrent schema changes
> -
>
> Key: IGNITE-4953
> URL: https://issues.apache.org/jira/browse/IGNITE-4953
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 2.0
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
>  Labels: important
> Fix For: 2.0
>
>
> H2's prepared statements store references to indexes that were present when 
> the statement was parsed and initialized - this means that currently there's 
> no way to prevent index usage if it goes down between the moment when the 
> statement is created and actually executed. Have to come up with some new 
> locking schema.



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

[jira] [Created] (IGNITE-4953) Rework logic of concurrent schema changes

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4953:
---

 Summary: Rework logic of concurrent schema changes
 Key: IGNITE-4953
 URL: https://issues.apache.org/jira/browse/IGNITE-4953
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Affects Versions: 2.0
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko
 Fix For: 2.0


H2's prepared statements store references to indexes that were present when the 
statement was parsed and initialized - this means that currently there's no way 
to prevent index usage if it goes down between the moment when the statement is 
created and actually executed. Have to come up with some new locking schema.



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

[jira] [Commented] (IGNITE-4950) Do not allow AffinityKeyMapped annotation on methods

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov commented on IGNITE-4950:
---

done, please review

[PR|https://github.com/apache/ignite/pull/1781]

> Do not allow AffinityKeyMapped annotation on methods
> 
>
> Key: IGNITE-4950
> URL: https://issues.apache.org/jira/browse/IGNITE-4950
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
>  Labels: important
> Fix For: 2.0
>
>




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

[jira] [Assigned] (IGNITE-3523) IGFS: Remove "initialize default path modes" feature.

[Taras Ledkov (JIRA)]

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

Taras Ledkov reassigned IGNITE-3523:


Assignee: Taras Ledkov

> IGFS: Remove "initialize default path modes" feature.
> -
>
> Key: IGNITE-3523
> URL: https://issues.apache.org/jira/browse/IGNITE-3523
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> Currently IGFS can create several paths by default, which will forcefully 
> work in different modes. This will never require in practice, but caused some 
> problems, e.g. performance degradation in our Hadoop FileSystem implementaions
> Let's just remove that feature along with relevant property in 
> {{FileSystemConfiguration}}.



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

[jira] [Updated] (IGNITE-3546) IGFS: Review events subsystem.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3546:

Fix Version/s: (was: 2.0)
   2.1

> IGFS: Review events subsystem.
> --
>
> Key: IGNITE-3546
> URL: https://issues.apache.org/jira/browse/IGNITE-3546
> Project: Ignite
>  Issue Type: Sub-task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently we have different event types for various file system operations. 
> But we do not fire them always. E.g. if the path {{/a}} is removed, then we 
> will fire only one event. We will not fire events for {{/a/b}}.
> Is it fine or not? Do we need these events at all or not? May be we want to 
> configure event handling somehow? May be users would like to listen such 
> events? Need to think about it.



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

[jira] [Updated] (IGNITE-3580) IGFS: Allow IGFS tasks execution on machines where IGFS is not configured.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-3580:

Fix Version/s: (was: 2.0)
   2.1

> IGFS: Allow IGFS tasks execution on machines where IGFS is not configured.
> --
>
> Key: IGNITE-3580
> URL: https://issues.apache.org/jira/browse/IGNITE-3580
> Project: Ignite
>  Issue Type: Task
>  Components: IGFS
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
> Fix For: 2.1
>
>
> Currently user has to configure IGFS on all nodes where data and meta caches 
> reside. Otherwise, he will not be able to execute metadata and data updates 
> on these machines.
> This requirement is synthetic. No reason to force user doing this. Instead, 
> all required tasks can be executed on data nodes without IGFS started on 
> them. Need to refactor IGFS to allow this.



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

[jira] [Comment Edited] (IGNITE-3469) Get rid of deprecated APIs and entities

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-3469 at 4/12/17 1:53 PM:
---

The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};




was (Author: tledkov-gridgain):
The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};



> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> There are more than 220 deprecated elements in Ignite code kept for the sake 
> of backward compatibility. We need to cleanup the code for Ignite 2.0 release.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



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

[jira] [Comment Edited] (IGNITE-3469) Get rid of deprecated APIs and entities

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-3469 at 4/12/17 1:52 PM:
---

The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};




was (Author: tledkov-gridgain):
The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};



> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> There are more than 220 deprecated elements in Ignite code kept for the sake 
> of backward compatibility. We need to cleanup the code for Ignite 2.0 release.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



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

[jira] [Comment Edited] (IGNITE-3469) Get rid of deprecated APIs and entities

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-3469 at 4/12/17 1:50 PM:
---

The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};




was (Author: tledkov-gridgain):
The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};



> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> There are more than 220 deprecated elements in Ignite code kept for the sake 
> of backward compatibility. We need to cleanup the code for Ignite 2.0 release.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



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

[jira] [Commented] (IGNITE-4173) IgniteSemaphore with failoverSafe enabled doesn't release permits in case permits owner node left topology

[Vladisav Jelisavcic (JIRA)]

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

Vladisav Jelisavcic commented on IGNITE-4173:
-

This was a bug, the cause was that attempt to recover from failure was throwing 
the NPE for the newly created semaphores (because semaphores are lazily 
initialized).
There is also a problem with the  {{SemaphoreFailoverSafeReleasePermitsTest}}: 
second semaphore was created only after the first node failed; in this scenario 
there are no semaphores to attempt recovery so the permit is lost for good. 

> IgniteSemaphore with failoverSafe enabled doesn't release permits in case 
> permits owner node left topology
> --
>
> Key: IGNITE-4173
> URL: https://issues.apache.org/jira/browse/IGNITE-4173
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Vladisav Jelisavcic
> Fix For: 2.0
>
>
> {{IgniteSemaphore}} with {{failoverSafe}} enabled doesn't release permits in 
> case permits owner node left topology.
> See reproducer in test class {{SemaphoreFailoverSafeReleasePermitsTest}}.



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

[jira] [Comment Edited] (IGNITE-3469) Get rid of deprecated APIs and entities

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-3469 at 4/12/17 1:49 PM:
---

The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};




was (Author: tledkov-gridgain):
The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheUtils.cheatCache}};
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};



> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> There are more than 220 deprecated elements in Ignite code kept for the sake 
> of backward compatibility. We need to cleanup the code for Ignite 2.0 release.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



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

[jira] [Commented] (IGNITE-4795) Inherit TransactionException and update Javadoc

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-4795:
-

Code changes and TC look good to me. Merged into master branch.
[~SomeFire], thanks a lot for your contribution.

> Inherit TransactionException and update Javadoc
> ---
>
> Key: IGNITE-4795
> URL: https://issues.apache.org/jira/browse/IGNITE-4795
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache, SQL, website
>Affects Versions: 1.8
>Reporter: Alexandr Kuramshin
>Assignee: Ryabov Dmitrii
>  Labels: documentation, important
> Fix For: 2.0
>
>
> Understanding transactional behaviour is not clear in Javadoc at this point 
> of time. Even after reading website some doubt remain.
> Proposal.
> 1. Create {{TransactionException}} as the marker of transactional methods and 
> inherit from it all the existed transactional exceptions like 
> {{TransactionTimeoutException}}, {{TransactionRollbackException}}, 
> {{TransactionHeuristicException}}, {{TransactionOptimisticException}}, etc.
> 2. Update all the transactional methods ({{get}}, {{put}}, {{invoke}}, etc) 
> as throwing the base {{TransactionException}}. Comment all the 
> {{IgniteCache}} methods whether they are transactional or not, add {{@see 
> TransactionException}} annotation.
> 3. Make extensive documentation in the header of {{TransactionException}} to 
> get understanding of transactional and non-transactional methods behaviour.
> 4. Update website and Javadoc to clarify the fact that {{put}} value is 
> cached within the transaction and affects successive {{get}}.



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

[jira] [Comment Edited] (IGNITE-3469) Get rid of deprecated APIs and entities

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-3469 at 4/12/17 1:42 PM:
---

The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheUtils.cheatCache}};
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};




was (Author: tledkov-gridgain):
The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheUtils.cheatCache}};
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};



> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> There are more than 220 deprecated elements in Ignite code kept for the sake 
> of backward compatibility. We need to cleanup the code for Ignite 2.0 release.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



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

[jira] [Comment Edited] (IGNITE-3469) Get rid of deprecated APIs and entities

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-3469 at 4/12/17 1:35 PM:
---

The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheUtils.cheatCache}};
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};




was (Author: tledkov-gridgain):
The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{CacheConfiguration}} properties: {{rebalanceThreadPoolSize}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheUtils.cheatCache}};
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};



> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> There are more than 220 deprecated elements in Ignite code kept for the sake 
> of backward compatibility. We need to cleanup the code for Ignite 2.0 release.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



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

[jira] [Reopened] (IGNITE-4173) IgniteSemaphore with failoverSafe enabled doesn't release permits in case permits owner node left topology

[Vladisav Jelisavcic (JIRA)]

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

Vladisav Jelisavcic reopened IGNITE-4173:
-
  Assignee: Vladisav Jelisavcic

> IgniteSemaphore with failoverSafe enabled doesn't release permits in case 
> permits owner node left topology
> --
>
> Key: IGNITE-4173
> URL: https://issues.apache.org/jira/browse/IGNITE-4173
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Andrey Gura
>Assignee: Vladisav Jelisavcic
> Fix For: 2.0
>
>
> {{IgniteSemaphore}} with {{failoverSafe}} enabled doesn't release permits in 
> case permits owner node left topology.
> See reproducer in test class {{SemaphoreFailoverSafeReleasePermitsTest}}.



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

[jira] [Commented] (IGNITE-4173) IgniteSemaphore with failoverSafe enabled doesn't release permits in case permits owner node left topology

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4173:


GitHub user vladisav opened a pull request:

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

IGNITE-4173 



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

$ git pull https://github.com/vladisav/ignite ignite-4173

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

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


commit 76e9098bc67bb4bf660ebc147be89b64a8256c8d
Author: vladisav 
Date:   2017-04-12T13:27:55Z

Fixes ignite-4173;




> IgniteSemaphore with failoverSafe enabled doesn't release permits in case 
> permits owner node left topology
> --
>
> Key: IGNITE-4173
> URL: https://issues.apache.org/jira/browse/IGNITE-4173
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Andrey Gura
> Fix For: 2.0
>
>
> {{IgniteSemaphore}} with {{failoverSafe}} enabled doesn't release permits in 
> case permits owner node left topology.
> See reproducer in test class {{SemaphoreFailoverSafeReleasePermitsTest}}.



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

[jira] [Comment Edited] (IGNITE-3469) Get rid of deprecated APIs and entities

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-3469 at 4/12/17 1:19 PM:
---

The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{CacheConfiguration}} properties: {{rebalanceThreadPoolSize}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheUtils.cheatCache}};
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};




was (Author: tledkov-gridgain):
The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{CacheConfiguration}} properties: {rebalanceThreadPoolSize}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheUtils.cheatCache}};
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};



> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> There are more than 220 deprecated elements in Ignite code kept for the sake 
> of backward compatibility. We need to cleanup the code for Ignite 2.0 release.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



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

[jira] [Comment Edited] (IGNITE-3469) Get rid of deprecated APIs and entities

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-3469 at 4/12/17 1:19 PM:
---

The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{CacheConfiguration}} properties: {rebalanceThreadPoolSize}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheUtils.cheatCache}};
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};




was (Author: tledkov-gridgain):
The list of not removed yet:
h3. The list of the deprecated public class / methods / properties:
- The system flags:
-- {{IGNITE_BINARY_SORT_OBJECT_FIELDS}};
-- {{IGNITE_BINARY_DONT_WRAP_TREE_STRUCTURES}};
-- {{IGNITE_MIN_BUFFERED_COMMUNICATION_MSG_CNT}} - not used in the projects now.
- Backup filters for affinity functions;
- {{ContinuousQuery.setRemoteFilter}};
- {{CacheStore.sessionEnd}};
- {{CacheAbstractJdbcStore.translateFields}};
- {{CacheJdbcPojoStoreFactory.setDataSource}};
- {{CacheConfiguration}} properties: {rebalanceThreadPoolSize}};
- {{ConnectorConfiguration.sslContextFactory}} property;
- {{IgniteConfiguration.nodeId}} properties:
- {{StreamTupleExtractor}} class and relations;
- ignite-hadoop: Several constructors of the 
{{IgniteHadoopIgfsSecondaryFileSystem}};
- ignite-yarn: {{ApplicationMaster.getContainers()}}.

h3. The list of the deprecated private class / methods / properties:
- Classes are retated to the {{GridSslContextFactory}};
- {{JdbcConnection}} related classes;
- {{GridCacheUtils.cheatCache}};
- {{GridCacheCommittedTxInfo}};
- {{GridDistributedTxFinishRequest}}: {{syncCommit}}, {{syncRollback}};
- One of the constructors of {{GridLeanSet}};
- Several methods at the {{IgniteUtils}};
- Several methods at the {{GridFunc}};
- {{PlatformDotNetBinaryTypeConfiguration.isKeepDeserialized()}};
- {{ServerImpl.RingMessageWorker.processNodeAddedMessage}};
- {{TcpDiscoverySpi.versionCheckFailed}};



> Get rid of deprecated APIs and entities
> ---
>
> Key: IGNITE-3469
> URL: https://issues.apache.org/jira/browse/IGNITE-3469
> Project: Ignite
>  Issue Type: Task
>Reporter: Alexey Goncharuk
>Assignee: Taras Ledkov
>  Labels: important
> Fix For: 2.0
>
>
> There are more than 220 deprecated elements in Ignite code kept for the sake 
> of backward compatibility. We need to cleanup the code for Ignite 2.0 release.
> 2.0 migration guide has to be updated if needed: 
> https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.0+Migration+Guide



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

[jira] [Created] (IGNITE-4952) Swapping-related Event Types must be deleted

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-4952:
---

 Summary: Swapping-related Event Types must be deleted
 Key: IGNITE-4952
 URL: https://issues.apache.org/jira/browse/IGNITE-4952
 Project: Ignite
  Issue Type: Task
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov


h2. Notes
As swap storage was removed in 
[IGNITE-3477|https://issues.apache.org/jira/browse/IGNITE-3477] there is no 
need to keep swap-related Event Types in ignite codebase.

h2. Acceptance Criteria
# Swap-related Event Types are removed from EventType enum.
# All tests verifying swap functionality are removed from tests set.



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

[jira] [Assigned] (IGNITE-1794) Ignite should support Hibernate 5

[Vadim Opolski (JIRA)]

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

Vadim Opolski reassigned IGNITE-1794:
-

Assignee: Vadim Opolski

> Ignite should support Hibernate 5
> -
>
> Key: IGNITE-1794
> URL: https://issues.apache.org/jira/browse/IGNITE-1794
> Project: Ignite
>  Issue Type: Sub-task
>  Components: Hibernate L2 cache
>Reporter: Artem Shutak
>Assignee: Vadim Opolski
>  Labels: important, newbie
> Fix For: 2.0
>
> Attachments: HibernateCollectionRegionForIgnite.java, 
> HibernateEntityRegionForIgnite.java, HibernateRegionFactoryForIgnite.java, 
> HibernateTimestampsRegionForIgnite.java
>
>
> Currently Ignite supports Hibernate 4. 
> In Hibernate 5 org.hibernate.cache.spi.RegionFactory.start() method signature 
> has been changed from
> {{void start(Settings var1, Properties var2) throws CacheException;}}
> on
> {{void start(SessionFactoryOptions settings, Properties properties) throws 
> CacheException;}}
> Original user list: 
> http://apache-ignite-users.70518.x6.nabble.com/Hibernate-5-L2-Cache-Compatibility-td1656.html



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

[jira] [Updated] (IGNITE-4951) Discontinue AffintiyKeyMapper interface

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4951:

Fix Version/s: 2.0

> Discontinue AffintiyKeyMapper interface
> ---
>
> Key: IGNITE-4951
> URL: https://issues.apache.org/jira/browse/IGNITE-4951
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
>  Labels: important
> Fix For: 2.0
>
>




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

[jira] [Updated] (IGNITE-4951) Discontinue AffintiyKeyMapper interface

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4951:

Affects Version/s: (was: 2.0)

> Discontinue AffintiyKeyMapper interface
> ---
>
> Key: IGNITE-4951
> URL: https://issues.apache.org/jira/browse/IGNITE-4951
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
>  Labels: important
> Fix For: 2.0
>
>




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

[jira] [Commented] (IGNITE-3477) Rework offheap storage

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-3477:


Fixed .NET inspections in {{ignite-3477-master}}

> Rework offheap storage
> --
>
> Key: IGNITE-3477
> URL: https://issues.apache.org/jira/browse/IGNITE-3477
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>  Labels: important
> Fix For: 2.0
>
>
> Current (Ignite 1.x) implementation of cache storage relies on a tiered 
> approach where cache entry can be located in one of the three storage areas: 
> on-heap, off-heap memory and swap. It leads to the following disadvantages:
>  * Entry constantly moves from one storage area to another which leads to a 
> complex code (for example, swap/unswap listeners for queries and rebalancing)
>  * It is not possible to set per-cache memory limit
>  * Off-heap indexes require on-heap row cache. If this cache is small, 
> performance becomes very poor
>  * Continuous put/remove operations with OFFHEAP_TIERED mode lead to 
> uncontrollable memory fragmentation
> We can reapproach the cache storage and base it on a concept of page memory. 
> We will allocate several memory pools of pages of fixed size and assign each 
> cache to one of the memory pools. All storage data structures should operate 
> on memory pages, the main storage will be always off-heap with an optional 
> on-heap cache.
> This gives us the following benefits:
>  * Flexible and precise per-cache memory limit
>  * Transparent swap: we can allocate page memory over a memory-mapped file 
> and OS will take care of swapping
>  * Getting rid of on-heap cache for off-heap SQL indexes
>  * Ability to take a cluster-wide data snapshot
> I suggest the following API for memory policy configuration:
> {code}
> class MemoryPolicy {
> boolean default; // Require at least one memory policy to be default.
> private String name;
> private long size;
> private String tmpFsPath; // If memory-mapped file should be used.
> }
> class CacheConfiguration {
> 
> private String memoryPolicyName;
> 
> }
> {code}



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

[jira] [Updated] (IGNITE-4951) Discontinue AffintiyKeyMapper interface

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-4951:

Labels: important  (was: )

> Discontinue AffintiyKeyMapper interface
> ---
>
> Key: IGNITE-4951
> URL: https://issues.apache.org/jira/browse/IGNITE-4951
> Project: Ignite
>  Issue Type: Task
>  Components: cache
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Konstantin Dudkov
>  Labels: important
>




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

[jira] [Created] (IGNITE-4951) Discontinue AffintiyKeyMapper interface

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4951:
---

 Summary: Discontinue AffintiyKeyMapper interface
 Key: IGNITE-4951
 URL: https://issues.apache.org/jira/browse/IGNITE-4951
 Project: Ignite
  Issue Type: Task
  Components: cache
Affects Versions: 2.0
Reporter: Vladimir Ozerov
Assignee: Konstantin Dudkov






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

[jira] [Created] (IGNITE-4950) Do not allow AffinityKeyMapped annotation on methods

[Vladimir Ozerov (JIRA)]

Vladimir Ozerov created IGNITE-4950:
---

 Summary: Do not allow AffinityKeyMapped annotation on methods
 Key: IGNITE-4950
 URL: https://issues.apache.org/jira/browse/IGNITE-4950
 Project: Ignite
  Issue Type: Task
  Components: cache
Reporter: Vladimir Ozerov
Assignee: Konstantin Dudkov
 Fix For: 2.0






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

[jira] [Commented] (IGNITE-2398) .NET: Change default mapper behavior

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2398:


All done except SQL:

Table name now depends on current name mapper. We should probably extract table 
name resolver from LINQ and use it for SQL queries when {{Type}} is specified.

> .NET: Change default mapper behavior
> 
>
> Key: IGNITE-2398
> URL: https://issues.apache.org/jira/browse/IGNITE-2398
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .net, important
> Fix For: 2.0
>
>
> We need to mirror changes implemented in IGNITE-2191:
> 1) Default mapper must use full class name (i.e. with package)
> 2) Provide additional mapper implementation which will use simple names.



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

[jira] [Comment Edited] (IGNITE-3018) Cache affinity calculation is slow with large nodes number

[Taras Ledkov (JIRA)]

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

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


Patch without balancer: [PR1779|https://github.com/apache/ignite/pull/1779]
Branch {{ignite-3018}}
Waits for TC 
[results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1779%2Fhead]


was (Author: tledkov-gridgain):
Patch without balancer: [PR1779|https://github.com/apache/ignite/pull/1779]
Branch {{ignite-3018}}

> Cache affinity calculation is slow with large nodes number
> --
>
> Key: IGNITE-3018
> URL: https://issues.apache.org/jira/browse/IGNITE-3018
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Yakov Zhdanov
>  Labels: important
> Fix For: 2.0
>
> Attachments: 003.png, 004.png, 008.png, 016.png, 064.png, 100.png, 
> 128.png, 200.png, 256.png, 400.png, 600.png, balanced.003.png, 
> balanced.004.png, balanced.008.png, balanced.016.png, balanced.064.png, 
> balanced.100.png, balanced.128.png, balanced.200.png, balanced.256.png, 
> balanced.400.png, balanced.600.png
>
>
> With large number of cache server nodes (> 200)  RendezvousAffinityFunction 
> and FairAffinityFunction work pretty slow .
> For RendezvousAffinityFunction.assignPartitions can take hundredes of 
> milliseconds, for FairAffinityFunction it can take seconds.
> For RendezvousAffinityFunction most time is spent in MD5 hash calculation and 
> nodes list sorting. As optimization we can try to cache {partion, node} MD5 
> hash or try another hash function. Also several minor optimizations are 
> possible (avoid unncecessary allocations, only one thread local 'get', etc).



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

[jira] [Commented] (IGNITE-4891) Key is deserialized during transactional get() even if withKeepBinary is set

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-4891:
--

Hi Dmitry,

I reviewed fix, looks good to me.

Thanks

> Key is deserialized during transactional get() even if withKeepBinary is set
> 
>
> Key: IGNITE-4891
> URL: https://issues.apache.org/jira/browse/IGNITE-4891
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 1.9
>Reporter: Valentin Kulichenko
>Assignee: Dmitry Karachentsev
>Priority: Critical
> Fix For: 2.0
>
>
> This test reproduces the issue: https://github.com/olegskoblya/tx-binary-bug



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

[jira] [Comment Edited] (IGNITE-3018) Cache affinity calculation is slow with large nodes number

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-3018 at 4/12/17 12:24 PM:


Patch without balancer: [PR1779|https://github.com/apache/ignite/pull/1779]
Branch {{ignite-3018}}


was (Author: tledkov-gridgain):
Patch without balancer: [PR1779|https://github.com/apache/ignite/pull/1779]

> Cache affinity calculation is slow with large nodes number
> --
>
> Key: IGNITE-3018
> URL: https://issues.apache.org/jira/browse/IGNITE-3018
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Yakov Zhdanov
>  Labels: important
> Fix For: 2.0
>
> Attachments: 003.png, 004.png, 008.png, 016.png, 064.png, 100.png, 
> 128.png, 200.png, 256.png, 400.png, 600.png, balanced.003.png, 
> balanced.004.png, balanced.008.png, balanced.016.png, balanced.064.png, 
> balanced.100.png, balanced.128.png, balanced.200.png, balanced.256.png, 
> balanced.400.png, balanced.600.png
>
>
> With large number of cache server nodes (> 200)  RendezvousAffinityFunction 
> and FairAffinityFunction work pretty slow .
> For RendezvousAffinityFunction.assignPartitions can take hundredes of 
> milliseconds, for FairAffinityFunction it can take seconds.
> For RendezvousAffinityFunction most time is spent in MD5 hash calculation and 
> nodes list sorting. As optimization we can try to cache {partion, node} MD5 
> hash or try another hash function. Also several minor optimizations are 
> possible (avoid unncecessary allocations, only one thread local 'get', etc).



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

[jira] [Commented] (IGNITE-3018) Cache affinity calculation is slow with large nodes number

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-3018:
--

Patch without balancer: [PR1779|https://github.com/apache/ignite/pull/1779]

> Cache affinity calculation is slow with large nodes number
> --
>
> Key: IGNITE-3018
> URL: https://issues.apache.org/jira/browse/IGNITE-3018
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Yakov Zhdanov
>  Labels: important
> Fix For: 2.0
>
> Attachments: 003.png, 004.png, 008.png, 016.png, 064.png, 100.png, 
> 128.png, 200.png, 256.png, 400.png, 600.png, balanced.003.png, 
> balanced.004.png, balanced.008.png, balanced.016.png, balanced.064.png, 
> balanced.100.png, balanced.128.png, balanced.200.png, balanced.256.png, 
> balanced.400.png, balanced.600.png
>
>
> With large number of cache server nodes (> 200)  RendezvousAffinityFunction 
> and FairAffinityFunction work pretty slow .
> For RendezvousAffinityFunction.assignPartitions can take hundredes of 
> milliseconds, for FairAffinityFunction it can take seconds.
> For RendezvousAffinityFunction most time is spent in MD5 hash calculation and 
> nodes list sorting. As optimization we can try to cache {partion, node} MD5 
> hash or try another hash function. Also several minor optimizations are 
> possible (avoid unncecessary allocations, only one thread local 'get', etc).



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

[jira] [Commented] (IGNITE-3018) Cache affinity calculation is slow with large nodes number

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3018:


GitHub user tledkov-gridgain opened a pull request:

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

IGNITE-3018  Cache affinity calculation is slow with large nodes number



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

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

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

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


commit ed35a9eb6f02771c5996209a1e19a4b0557309b6
Author: tledkov-gridgain 
Date:   2017-02-27T09:49:31Z

IGNITE-3018: RendezvousAffinityFunction performance tuning

commit 3a6d17c2250158b54e3573af23b9b1534c3c8e92
Author: tledkov-gridgain 
Date:   2017-02-27T10:57:36Z

IGNITE-3018: fix review issues

commit db5512b65ce273d955ecd1c2381ade84491895ad
Author: tledkov-gridgain 
Date:   2017-03-02T14:32:04Z

Merge branch 'ignite-2.0' into ignite-3018

commit 163c05b6cea25aec0ca3b4ae4552338ed683631f
Author: tledkov-gridgain 
Date:   2017-04-12T12:18:14Z

Merge branch '_master' into ignite-3018

# Conflicts:
#   
modules/core/src/main/java/org/apache/ignite/cache/affinity/rendezvous/RendezvousAffinityFunction.java

commit 3695d960597a5fdbebf43bf9a3bb57f85f4f394b
Author: tledkov-gridgain 
Date:   2017-04-12T12:18:57Z

IGNITE-3018: special assignment calculation for replicated cache

commit 9dfed00ba8be7676dc427f329fb9f557f71d4d21
Author: tledkov-gridgain 
Date:   2017-04-12T12:21:37Z

IGNITE-3018: exchange fix




> Cache affinity calculation is slow with large nodes number
> --
>
> Key: IGNITE-3018
> URL: https://issues.apache.org/jira/browse/IGNITE-3018
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Yakov Zhdanov
>  Labels: important
> Fix For: 2.0
>
> Attachments: 003.png, 004.png, 008.png, 016.png, 064.png, 100.png, 
> 128.png, 200.png, 256.png, 400.png, 600.png, balanced.003.png, 
> balanced.004.png, balanced.008.png, balanced.016.png, balanced.064.png, 
> balanced.100.png, balanced.128.png, balanced.200.png, balanced.256.png, 
> balanced.400.png, balanced.600.png
>
>
> With large number of cache server nodes (> 200)  RendezvousAffinityFunction 
> and FairAffinityFunction work pretty slow .
> For RendezvousAffinityFunction.assignPartitions can take hundredes of 
> milliseconds, for FairAffinityFunction it can take seconds.
> For RendezvousAffinityFunction most time is spent in MD5 hash calculation and 
> nodes list sorting. As optimization we can try to cache {partion, node} MD5 
> hash or try another hash function. Also several minor optimizations are 
> possible (avoid unncecessary allocations, only one thread local 'get', etc).



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

[jira] [Updated] (IGNITE-4052) Add ability to set up users for MESOS

[Vadim Opolski (JIRA)]

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

Vadim Opolski updated IGNITE-4052:
--

Hello guys!

Nikolay, I looked at cassandra mesos integration, but cant find how to test
ability to configure mesos and user via system env properties. I will
continue to search in another projects which use Mesos.

Review please pull request - https://github.com/vadopolski/ignite/pull/2.
It contains new test and method for setting system environments.

Can you close issue https://issues.apache.org/jira/browse/IGNITE-4052 and
open new, about testing Mesos Integration.

Vadim Opolski




> Add ability to set up users for MESOS
> -
>
> Key: IGNITE-4052
> URL: https://issues.apache.org/jira/browse/IGNITE-4052
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 1.7
>Reporter: Nikolay Tikhonov
>Assignee: Vadim Opolski
>Priority: Trivial
>
> In current implementation Ignite Mesos Framework connects to MESOS cluster 
> via current user. Need to add ability to configure this parameters via system 
> env properties. Also need to add properties for mesos role.
> See org/apache/ignite/mesos/IgniteFramework.java:537



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

[jira] [Commented] (IGNITE-3682) GridFunc: move all inner anonymous classes to separate top-level classes.

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur commented on IGNITE-3682:


It is remade after rebase.
Sent to [ci.tests|http://ci.ignite.apache.org/viewQueued.html?itemId=543067].

[There is same problem of packaging as in 
master-branch.|http://apache-ignite-developers.2346864.n4.nabble.com/build-failure-in-the-master-branch-td16477.html]

> GridFunc: move all inner anonymous classes to separate top-level classes.
> -
>
> Key: IGNITE-3682
> URL: https://issues.apache.org/jira/browse/IGNITE-3682
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important
> Fix For: 2.0
>
>
> Otherwise almost any change to class {{GridFunc}} will lead to serialization 
> issues because we have no control over inner class names.
> E.g. if removed single anonymous class, another anonymous class might change 
> it's name from {{GridFunc$4}} to {{GridFunc$3}}.



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

[jira] [Commented] (IGNITE-2893) Atomic structures should not use transactions

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-2893:
--

Did changes to do not use explicit transaction, but simple 'invoke' on tx 
cache, but this change revealed issue IGNITE-4929, need fix it before merge.

> Atomic structures should not use transactions
> -
>
> Key: IGNITE-2893
> URL: https://issues.apache.org/jira/browse/IGNITE-2893
> Project: Ignite
>  Issue Type: Task
>  Components: data structures
>Affects Versions: 1.5.0.final
>Reporter: Valentin Kulichenko
>Assignee: Semen Boikov
>  Labels: newbie
> Fix For: 2.1
>
>
> Currently atomic structures like {{AtomicReference}}, {{AtomicLong}} and 
> others use transactional caches and explicit transactions under the hood. 
> This seems redundant, because can be replaced with atomic cache and 
> {{invoke}} operations with {{EntryProcessor}}.



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

[jira] [Updated] (IGNITE-4929) onePhase tx for invoke may fail on changing topology

[Semen Boikov (JIRA)]

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

Semen Boikov updated IGNITE-4929:
-
Fix Version/s: (was: 2.0)
   2.1

> onePhase tx for invoke may fail on changing topology
> 
>
> Key: IGNITE-4929
> URL: https://issues.apache.org/jira/browse/IGNITE-4929
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Semen Boikov
>Priority: Critical
> Fix For: 2.1
>
>
> One phase tx for invoke may fail in this scenario:
> - backup did not rebalanced partition yet
> - in this case primary sends on backup new value instead of entry processor, 
> in this case on backup we loose information about value calculated by entry 
> processor
> - primary fails before it receives response from backup, client sends 'check' 
> request on backup to get return value, but return value on backup does not 
> contain expected invoke result
> Added test IgniteOnePhaseCommitInvokeTest.



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

[jira] [Assigned] (IGNITE-4933) Need to add an option to write all updates in write-behind store

[Alexander Belyak (JIRA)]

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

Alexander Belyak reassigned IGNITE-4933:


Assignee: Alexander Belyak

> Need to add an option to write all updates in write-behind store
> 
>
> Key: IGNITE-4933
> URL: https://issues.apache.org/jira/browse/IGNITE-4933
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 1.9
>Reporter: Valentin Kulichenko
>Assignee: Alexander Belyak
> Fix For: 2.0
>
>
> Currently if there are several updates for the same key, write behind store 
> will write only one of them within a single batch. I.e. second update will 
> override the first one if the latter is not written to DB yet.
> This is good from performance and memory consumption standpoint, however 
> sometimes it's required to write all updates that happen in cache.
> We can add parameter to {{CacheConfiguration}} that will switch this behavior 
> and implement it in {{GridCacheWriteBehindStore}}. Default behavior should 
> remain the same.



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

[jira] [Commented] (IGNITE-4942) Remove old JdbcQueryTask

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-4942:
--

Waits for TC tests 
[results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1772%2Fhead]

> Remove old JdbcQueryTask
> 
>
> Key: IGNITE-4942
> URL: https://issues.apache.org/jira/browse/IGNITE-4942
> Project: Ignite
>  Issue Type: Task
>Reporter: Vladimir Ozerov
>Assignee: Alexander Paschenko
>Priority: Minor
> Fix For: 2.0
>
>




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

[jira] [Updated] (IGNITE-4949) Incorrect behavior CacheJdbcPojoStore if binary marshaller enable

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-4949:
---
Description: 
In case using binary marshaller, CacheJdbcPojoStore.loadCache may not provide 
binary object in callback.
[dev-list| 
http://apache-ignite-developers.2346864.n4.nabble.com/CachePojoStore-data-loading-with-binary-marshaller-td16417.html]
 discussion.

  was:
In case using binary marshaller, CacheJdbcPojoStore.loadCache may not provide 
binary object in callback.
[dev-list| 
http://apache-ignite-developers.2346864.n4.nabble.com/CachePojoStore-data-loading-with-binary-marshaller-td16417.html]


> Incorrect behavior CacheJdbcPojoStore if binary marshaller enable
> -
>
> Key: IGNITE-4949
> URL: https://issues.apache.org/jira/browse/IGNITE-4949
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
> Fix For: 2.0
>
>
> In case using binary marshaller, CacheJdbcPojoStore.loadCache may not provide 
> binary object in callback.
> [dev-list| 
> http://apache-ignite-developers.2346864.n4.nabble.com/CachePojoStore-data-loading-with-binary-marshaller-td16417.html]
>  discussion.



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

[jira] [Updated] (IGNITE-4949) Incorrect behavior CacheJdbcPojoStore if binary marshaller enable

[Dmitriy Govorukhin (JIRA)]

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

Dmitriy Govorukhin updated IGNITE-4949:
---
Description: 
In case using binary marshaller, CacheJdbcPojoStore.loadCache may not provide 
binary object in callback.
[dev-list| 
http://apache-ignite-developers.2346864.n4.nabble.com/CachePojoStore-data-loading-with-binary-marshaller-td16417.html]

> Incorrect behavior CacheJdbcPojoStore if binary marshaller enable
> -
>
> Key: IGNITE-4949
> URL: https://issues.apache.org/jira/browse/IGNITE-4949
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Dmitriy Govorukhin
>Assignee: Dmitriy Govorukhin
> Fix For: 2.0
>
>
> In case using binary marshaller, CacheJdbcPojoStore.loadCache may not provide 
> binary object in callback.
> [dev-list| 
> http://apache-ignite-developers.2346864.n4.nabble.com/CachePojoStore-data-loading-with-binary-marshaller-td16417.html]



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

[jira] [Comment Edited] (IGNITE-4915) Remove deprecated methods and properties at the public API

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-4915 at 4/12/17 10:12 AM:


Waits for TC 
[results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1734%2Fhead]


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

> Remove deprecated methods and properties at the public API
> --
>
> Key: IGNITE-4915
> URL: https://issues.apache.org/jira/browse/IGNITE-4915
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> Methods to remove:
> - {{IgniteCluster.mapKeysToNodes}};
> - {{IgniteCache.randomEntry}};
> - {{FileSystemConfiguration}} properties;
> - {{IgfsPath}} methods.
> - deprecated properties of the {{TcpCommunicationSpi}};
> - {{GridTupleV}};
> - {{AffinityNideHashResolver}}.



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

[jira] [Updated] (IGNITE-4915) Remove deprecated methods and properties at the public API

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4915:
-
Description: 
Methods to remove:
- {{IgniteCluster.mapKeysToNodes}};
- {{IgniteCache.randomEntry}};
- {{FileSystemConfiguration}} properties;
- {{IgfsPath}} methods.
- deprecated properties of the {{TcpCommunicationSpi}};
- {{GridTupleV}};
- {{AffinityNideHashResolver}}.

  was:
Methods to remove:
- {{IgniteCluster.mapKeysToNodes}};
- {{IgniteCache.randomEntry}};
- {{FileSystemConfiguration}} properties;
- {{IgfsPath}} methods.


> Remove deprecated methods and properties at the public API
> --
>
> Key: IGNITE-4915
> URL: https://issues.apache.org/jira/browse/IGNITE-4915
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>
> Methods to remove:
> - {{IgniteCluster.mapKeysToNodes}};
> - {{IgniteCache.randomEntry}};
> - {{FileSystemConfiguration}} properties;
> - {{IgfsPath}} methods.
> - deprecated properties of the {{TcpCommunicationSpi}};
> - {{GridTupleV}};
> - {{AffinityNideHashResolver}}.



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

[jira] [Created] (IGNITE-4949) Incorrect behavior CacheJdbcPojoStore if binary marshaller enable

[Dmitriy Govorukhin (JIRA)]

Dmitriy Govorukhin created IGNITE-4949:
--

 Summary: Incorrect behavior CacheJdbcPojoStore if binary 
marshaller enable
 Key: IGNITE-4949
 URL: https://issues.apache.org/jira/browse/IGNITE-4949
 Project: Ignite
  Issue Type: Bug
  Components: general
Reporter: Dmitriy Govorukhin
Assignee: Dmitriy Govorukhin
 Fix For: 2.0






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

[jira] [Commented] (IGNITE-3682) GridFunc: move all inner anonymous classes to separate top-level classes.

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur commented on IGNITE-3682:


Looks like many methods were removed within IGNITE-4733

> GridFunc: move all inner anonymous classes to separate top-level classes.
> -
>
> Key: IGNITE-3682
> URL: https://issues.apache.org/jira/browse/IGNITE-3682
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important
> Fix For: 2.0
>
>
> Otherwise almost any change to class {{GridFunc}} will lead to serialization 
> issues because we have no control over inner class names.
> E.g. if removed single anonymous class, another anonymous class might change 
> it's name from {{GridFunc$4}} to {{GridFunc$3}}.



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

[jira] [Updated] (IGNITE-4626) GridDhtPartitionTopologyImpl refactoring

[Konstantin Dudkov (JIRA)]

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

Konstantin Dudkov updated IGNITE-4626:
--
Fix Version/s: 2.1

> GridDhtPartitionTopologyImpl refactoring
> 
>
> Key: IGNITE-4626
> URL: https://issues.apache.org/jira/browse/IGNITE-4626
> Project: Ignite
>  Issue Type: Task
>Reporter: Konstantin Dudkov
>Assignee: Konstantin Dudkov
> Fix For: 2.1
>
>
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl#nodes(int,
>  org.apache.ignite.internal.processors.affinity.AffinityTopologyVersion)
> Need to refactor this method to use Object[] - partId->List



--
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=15965617#comment-15965617
 ] 

Igor Seliverstov commented on IGNITE-3488:
--

Temporary hold due to works on IGNITE-4946

> 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



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

[jira] [Comment Edited] (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=15965617#comment-15965617
 ] 

Igor Seliverstov edited comment on IGNITE-3488 at 4/12/17 9:41 AM:
---

Temporary on hold due to works on IGNITE-4946


was (Author: gvvinblade):
Temporary hold due to works on IGNITE-4946

> 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



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

[jira] [Updated] (IGNITE-4907) Excessive service instances can be started with dynamic deployment.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-4907:
-
Description: 
More than needed service instances can be started when service deployed 
dynamicly. 

For next service configuration all 3 instances will be started even if cluster 
has 2 ignites nodes only:
  cfg.setMaxPerNodeCount(1);
  cfg.setTotalCount(3);


See for details: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-may-start-more-service-instances-per-node-than-maxPerNodeCount-in-case-of-manual-redeploy-td11661.html

  was:
More than needed service instances can be started when service deployed 
dynamicly. 

For next service configuration all 3 instances will be started even if cluster 
has 2 ignites nodes only:
  cfg.setMaxPerNodeCount(1);
  cfg.setTotalCount(3);



> Excessive service instances can be started with dynamic deployment.
> ---
>
> Key: IGNITE-4907
> URL: https://issues.apache.org/jira/browse/IGNITE-4907
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>  Labels: user-experience
> Fix For: 2.0
>
> Attachments: ServiceDeploymentBug.java
>
>
> More than needed service instances can be started when service deployed 
> dynamicly. 
> For next service configuration all 3 instances will be started even if 
> cluster has 2 ignites nodes only:
>   cfg.setMaxPerNodeCount(1);
>   cfg.setTotalCount(3);
> See for details: 
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-may-start-more-service-instances-per-node-than-maxPerNodeCount-in-case-of-manual-redeploy-td11661.html



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

[jira] [Updated] (IGNITE-4907) Excessive service instances can be started with dynamic deployment.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-4907:
-
Labels: user-experience  (was: )

> Excessive service instances can be started with dynamic deployment.
> ---
>
> Key: IGNITE-4907
> URL: https://issues.apache.org/jira/browse/IGNITE-4907
> Project: Ignite
>  Issue Type: Bug
>  Components: managed services
>Affects Versions: 1.9
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>  Labels: user-experience
> Fix For: 2.0
>
> Attachments: ServiceDeploymentBug.java
>
>
> More than needed service instances can be started when service deployed 
> dynamicly. 
> For next service configuration all 3 instances will be started even if 
> cluster has 2 ignites nodes only:
>   cfg.setMaxPerNodeCount(1);
>   cfg.setTotalCount(3);
> See for details: 
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-may-start-more-service-instances-per-node-than-maxPerNodeCount-in-case-of-manual-redeploy-td11661.html



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

[jira] [Commented] (IGNITE-3682) GridFunc: move all inner anonymous classes to separate top-level classes.

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur commented on IGNITE-3682:


[~agura]
Branch was rebased in order to avoid a merge conflict.

There are two new unused methods:
1. GridFunc#nodeId8s
2. GridFunc#toIntArray

Should I remove them?

> GridFunc: move all inner anonymous classes to separate top-level classes.
> -
>
> Key: IGNITE-3682
> URL: https://issues.apache.org/jira/browse/IGNITE-3682
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.6
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: important
> Fix For: 2.0
>
>
> Otherwise almost any change to class {{GridFunc}} will lead to serialization 
> issues because we have no control over inner class names.
> E.g. if removed single anonymous class, another anonymous class might change 
> it's name from {{GridFunc$4}} to {{GridFunc$3}}.



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

[jira] [Updated] (IGNITE-4945) Web Console: Redesign filter controls for tables.

[Vica Abramova (JIRA)]

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

Vica Abramova updated IGNITE-4945:
--
Attachment: Filtration.png

> Web Console: Redesign filter controls for tables.
> -
>
> Key: IGNITE-4945
> URL: https://issues.apache.org/jira/browse/IGNITE-4945
> Project: Ignite
>  Issue Type: Sub-task
>  Components: UI, wizards
>Affects Versions: 1.9
>Reporter: Andrey Novikov
>Assignee: Vica Abramova
> Attachments: Filtration.png
>
>




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

[jira] [Commented] (IGNITE-2398) .NET: Change default mapper behavior

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-2398:


GitHub user ptupitsyn opened a pull request:

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

IGNITE-2398 .NET: Change default mapper behavior



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

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

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

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


commit 389947517d5a9da82f2957ca6c188abee3ff1950
Author: Pavel Tupitsyn 
Date:   2017-04-06T09:12:28Z

IGNITE-2398 .NET: Change default mapper behavior

commit e8c5eb155b5b3a4ed3438bd07187bffd60da63d2
Author: Pavel Tupitsyn 
Date:   2017-04-07T05:02:22Z

Merge branch 'master' into ignite-2398

commit e3d02ffbd7ed4161208bd7320fc5aa330c795478
Author: Pavel Tupitsyn 
Date:   2017-04-07T05:54:56Z

wip

commit d03b099ad5664cf2fdd7f2fae7cca35ea42ef387
Author: Pavel Tupitsyn 
Date:   2017-04-07T06:10:12Z

Adding tests

commit d16b8e6ef6d1bb84e08a508bfda69c0955b2fcf6
Author: Pavel Tupitsyn 
Date:   2017-04-07T06:12:45Z

wip

commit ff624e11082fbc643ca63571ded2d20424b76bd5
Author: Pavel Tupitsyn 
Date:   2017-04-07T06:22:18Z

wip

commit 1984bfe487e71075ba14475c56d9b8ec11d2f9e0
Author: Pavel Tupitsyn 
Date:   2017-04-07T06:26:32Z

wip

commit 0259adde7701d5139340b27a78f8cf2a35820bca
Author: Pavel Tupitsyn 
Date:   2017-04-07T06:27:42Z

Mapper implemented

commit fdb92dfef0e54dfea405557f957bced17a0cf42c
Author: Pavel Tupitsyn 
Date:   2017-04-07T06:40:54Z

wip

commit dcbabd5e9e2590172acd5447fcf40452724ec98d
Author: Pavel Tupitsyn 
Date:   2017-04-07T06:42:54Z

wip

commit 41e75b7b1a82cc85abbe3d9b30ccb06a6ea5eb33
Author: Pavel Tupitsyn 
Date:   2017-04-07T08:07:59Z

wip

commit f9078a4be71b697146bbfd452eeadcfd6dd54b16
Author: Pavel Tupitsyn 
Date:   2017-04-07T08:27:27Z

wip

commit 62726158cb3ca7092fb9fa20c946f8612b7e50fc
Author: Pavel Tupitsyn 
Date:   2017-04-07T08:44:31Z

wip

commit cf5802362319cd9e2997874107393fd1761221f9
Author: Pavel Tupitsyn 
Date:   2017-04-07T08:57:22Z

wip

commit 48df244e753c998b79b482abeae27b2b4377
Author: Pavel Tupitsyn 
Date:   2017-04-07T09:31:29Z

wip

commit cac10fa6233bd541051c93af0662d52be809ed72
Author: Pavel Tupitsyn 
Date:   2017-04-07T09:45:51Z

wip

commit 1b085dff02469eeb25947ab6064e4fd5108db891
Author: Pavel Tupitsyn 
Date:   2017-04-07T09:49:57Z

wip

commit 283c145ad4251f3fa58d88b0c7b0d7ca3cab0b68
Author: Pavel Tupitsyn 
Date:   2017-04-07T10:26:35Z

wip

commit 93865a970dc60397304ce659ee718f4f13a19936
Author: Pavel Tupitsyn 
Date:   2017-04-07T11:06:37Z

wip

commit 9c053e6d9f7ed25f8784c431a293776649dd8152
Author: Pavel Tupitsyn 
Date:   2017-04-07T11:17:15Z

wip

commit 3c1b38a6979aed4116125a613f058a78dff694dc
Author: Pavel Tupitsyn 
Date:   2017-04-07T11:18:51Z

wip

commit b4f7dd7830207f3fa8b67ccddbe4c4196b1536e5
Author: Pavel Tupitsyn 
Date:   2017-04-07T11:37:36Z

wip

commit 44997da2750d4fea4eabc8777bac3bac0ed354db
Author: Pavel Tupitsyn 
Date:   2017-04-07T11:40:25Z

wip

commit e952c1e3d7a881c9889137970b7cfe1f59b0870e
Author: Pavel Tupitsyn 
Date:   2017-04-07T11:47:18Z

wip type name parser

commit 944e39fb15afee94655666f835723144102283de
Author: Pavel Tupitsyn 
Date:   2017-04-07T11:51:12Z

wip

commit e8df2acde61abd8d853e1ae6b9329736b1f241af
Author: Pavel Tupitsyn 
Date:   2017-04-07T11:56:16Z

wip

commit 5e6ae293e96826131a9dcba2ffa39519df35afd2
Author: Pavel Tupitsyn 
Date:   2017-04-07T11:57:06Z

wip tests

commit d9ec783459b1b87e125ca96c99defad474ff5cb6
Author: Pavel Tupitsyn 
Date:   2017-04-07T11:59:23Z

wip

commit 7c6b6dc6610b5f17fb25e0eba3d20bb45fdb2b84
Author: Pavel Tupitsyn 
Date:   2017-04-07T12:05:59Z

wip

commit 4c8172fba6753749521b58c9c74004ffedde8e7d
Author: Pavel Tupitsyn 
Date:   2017-04-07T12:07:53Z

wip




> .NET: Change default mapper behavior
> 

[jira] [Commented] (IGNITE-2398) .NET: Change default mapper behavior

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-2398:


Currently we always set Simple mapper in Java when starting .NET nodes. We 
should probably do this only when simple mapper is used in .NET.

> .NET: Change default mapper behavior
> 
>
> Key: IGNITE-2398
> URL: https://issues.apache.org/jira/browse/IGNITE-2398
> Project: Ignite
>  Issue Type: Sub-task
>  Components: platforms
>Affects Versions: 1.5.0.final
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>Priority: Minor
>  Labels: .net, important
> Fix For: 2.0
>
>
> We need to mirror changes implemented in IGNITE-2191:
> 1) Default mapper must use full class name (i.e. with package)
> 2) Provide additional mapper implementation which will use simple names.



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