[jira] [Created] (IGNITE-4908) Reentrant lock looks much slower that cache locks.

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-4908:


 Summary: Reentrant lock looks much slower that cache locks.
 Key: IGNITE-4908
 URL: https://issues.apache.org/jira/browse/IGNITE-4908
 Project: Ignite
  Issue Type: Improvement
  Components: data structures
Affects Versions: 1.8
Reporter: Andrew Mashenkov


We should make a benchmark and investigate this issue.




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

[jira] [Updated] (IGNITE-4908) Reentrant lock looks much slower that cache locks.

[Andrew Mashenkov (JIRA)]

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

Andrew Mashenkov updated IGNITE-4908:
-
Fix Version/s: 2.1

> Reentrant lock looks much slower that cache locks.
> --
>
> Key: IGNITE-4908
> URL: https://issues.apache.org/jira/browse/IGNITE-4908
> Project: Ignite
>  Issue Type: Improvement
>  Components: data structures
>Affects Versions: 1.8
>Reporter: Andrew Mashenkov
> Fix For: 2.1
>
>
> We should make a benchmark and investigate this issue.



--
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:
-
Attachment: ServiceDeploymentBug.java

> 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
> 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);



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

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

[Andrew Mashenkov (JIRA)]

Andrew Mashenkov created IGNITE-4907:


 Summary: 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
 Fix For: 2.0


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);




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

[jira] [Commented] (IGNITE-4906) .NET: Examples tests hang

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4906:


We can copy config file to a temp location and replace config with 
{{TcpDiscoveryStaticIpFinder}} during tests.

> .NET: Examples tests hang
> -
>
> Key: IGNITE-4906
> URL: https://issues.apache.org/jira/browse/IGNITE-4906
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> {{ExamplesTest}} hangs on various stages: 
> http://195.239.208.174/viewType.html?buildTypeId=IgniteTests_IgnitePlatformNetLongRunnin
> Logs show many multicast-related exceptions. We should probably avoid 
> multicast in tests.



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

[jira] [Comment Edited] (IGNITE-1948) ClusterTopologyCheckedException can return null for retryReadyFuture()

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov edited comment on IGNITE-1948 at 4/3/17 4:31 PM:
-

[~sboikov]
Okay I total recalled :) 
In PR I use only checked exception.

It's unclear for me how reach both aims: ensure retry future not null and not 
create new exception class. Do you mean make some default not null value for 
retry future?


was (Author: sharpler):
[~sboikov]
Okay I total recalled :) 
In PR I use only checked exception.

It's not clear for me how reach both: ensure retry future not null and don't 
create new exception class. Do you mean make some default not null value for 
retry future?

> ClusterTopologyCheckedException can return null for retryReadyFuture()
> --
>
> Key: IGNITE-1948
> URL: https://issues.apache.org/jira/browse/IGNITE-1948
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Denis Magda
>Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> It was noted that {{ClusterTopologyCheckedException}} ready future can be 
> null.
> Go though all the places where this kind of exception is being initialized 
> and check why the ready future is not set in some cases.



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

[jira] [Comment Edited] (IGNITE-1948) ClusterTopologyCheckedException can return null for retryReadyFuture()

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov edited comment on IGNITE-1948 at 4/3/17 4:29 PM:
-

[~sboikov]
Okay I total recalled :) 
In PR I use only checked exception.

It's not clear for me how reach both: ensure retry future not null and don't 
create new exception class. Do you mean make some default not null value for 
retry future?


was (Author: sharpler):
[~sboikov]
Okay I total recalled :) 
In PR I use only checked exception.

It's not clear for me how reach both: ensure ensure retry future not null and 
don't create new exception class. Do you mean make some default not null value 
for retry future?

> ClusterTopologyCheckedException can return null for retryReadyFuture()
> --
>
> Key: IGNITE-1948
> URL: https://issues.apache.org/jira/browse/IGNITE-1948
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Denis Magda
>Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> It was noted that {{ClusterTopologyCheckedException}} ready future can be 
> null.
> Go though all the places where this kind of exception is being initialized 
> and check why the ready future is not set in some cases.



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

[jira] [Commented] (IGNITE-1948) ClusterTopologyCheckedException can return null for retryReadyFuture()

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov commented on IGNITE-1948:
-

[~sboikov]
Okay I total recalled :) 
In PR I use only checked exception.

It's not clear for me how reach both: ensure ensure retry future not null and 
don't create new exception class. Do you mean make some default not null value 
for retry future?

> ClusterTopologyCheckedException can return null for retryReadyFuture()
> --
>
> Key: IGNITE-1948
> URL: https://issues.apache.org/jira/browse/IGNITE-1948
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Denis Magda
>Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> It was noted that {{ClusterTopologyCheckedException}} ready future can be 
> null.
> Go though all the places where this kind of exception is being initialized 
> and check why the ready future is not set in some cases.



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

[jira] [Commented] (IGNITE-3582) CPP: Replace pointers with references in function signatures where it's possible.

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-3582:


GitHub user isapego opened a pull request:

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

IGNITE-3582 CPP: Replaced pointers with references in function signatures 
where it's possible



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

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

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

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


commit d729b459c63110b36cf395e858905701e6820875
Author: Igor Sapego 
Date:   2017-04-03T15:09:35Z

IGNITE-3582: Removed IgnireError passing by pointer

commit 1ea13faca27efd9e56ed337ad0bfb109a775924d
Author: Igor Sapego 
Date:   2017-04-03T15:31:36Z

IGNITE-3582: Refactored BinaryMapReader::GetNext




> CPP: Replace pointers with references in function signatures where it's 
> possible.
> -
>
> Key: IGNITE-3582
> URL: https://issues.apache.org/jira/browse/IGNITE-3582
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.0
>
>
> Replace passing arguments by pointers with passing by references where it's 
> possible. Places to look at:
> {{BinaryMapReader::GetNext}}.
> The following argument: {{IgniteError* err}}.



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

[jira] [Created] (IGNITE-4906) .NET: Examples tests hang

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-4906:
--

 Summary: .NET: Examples tests hang
 Key: IGNITE-4906
 URL: https://issues.apache.org/jira/browse/IGNITE-4906
 Project: Ignite
  Issue Type: Bug
  Components: platforms
Affects Versions: 2.0
Reporter: Pavel Tupitsyn
Assignee: Pavel Tupitsyn
 Fix For: 2.0


{{ExamplesTest}} hangs on various stages: 
http://195.239.208.174/viewType.html?buildTypeId=IgniteTests_IgnitePlatformNetLongRunnin

Logs show many multicast-related exceptions. We should probably avoid multicast 
in tests.



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

[jira] [Commented] (IGNITE-1948) ClusterTopologyCheckedException can return null for retryReadyFuture()

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov commented on IGNITE-1948:
-

[~sboikov]
Hi Semen, I'm sorry, I real miss your answer for me.

Yes, I read Alexey's message, because he wrote it to me.

There is problem in the phrase "instead of setting a retry ready future in the 
checked exception, you would set a correct affinity topology version here". But 
if you see at code, you will see ready future use not for get affinity topology 
version, but for waiting. So the change breaks logic. I asked Alexey about 
that, but still have not got answer. Maybe you can clarify it for me.

Thank you for information about checked/unchecked. I need some time for recall 
what I did in this ticked :)

> ClusterTopologyCheckedException can return null for retryReadyFuture()
> --
>
> Key: IGNITE-1948
> URL: https://issues.apache.org/jira/browse/IGNITE-1948
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Denis Magda
>Assignee: Alexander Menshikov
> Fix For: 2.0
>
>
> It was noted that {{ClusterTopologyCheckedException}} ready future can be 
> null.
> Go though all the places where this kind of exception is being initialized 
> and check why the ready future is not set in some cases.



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

[jira] [Commented] (IGNITE-4211) Update Spring dependency to latest stable version

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-4211:
--

[~daradurvs]
Please investigate reason of found issues.

> Update Spring dependency to latest stable version
> -
>
> Key: IGNITE-4211
> URL: https://issues.apache.org/jira/browse/IGNITE-4211
> Project: Ignite
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 1.7
>Reporter: Sergey Kozlov
>Assignee: Vyacheslav Daradur
> Fix For: 2.0
>
>
> It seems the Spring dependency looks outdated for now. Apache Ignite still 
> uses 4.1.0 released two years ago. Could we to update to latest stable 
> version (4.3.4 at the moment)?



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

[jira] [Assigned] (IGNITE-3582) CPP: Replace pointers with references in function signatures where it's possible.

[Igor Sapego (JIRA)]

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

Igor Sapego reassigned IGNITE-3582:
---

Assignee: Igor Sapego

> CPP: Replace pointers with references in function signatures where it's 
> possible.
> -
>
> Key: IGNITE-3582
> URL: https://issues.apache.org/jira/browse/IGNITE-3582
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.0
>
>
> Replace passing arguments by pointers with passing by references where it's 
> possible. Places to look at:
> {{BinaryMapReader::GetNext}}.
> The following argument: {{IgniteError* err}}.



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

[jira] [Commented] (IGNITE-4905) ClassCastException in DML benchmarks

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4905:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-4905 DML benchmarks ClassCastException fix



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

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

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

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


commit bae83e6c8700059dda16abc74d70514a655ea8d4
Author: Alexander Paschenko 
Date:   2017-04-03T14:54:10Z

IGNITE-4905 DML benchmarks ClassCastException fix




> ClassCastException in DML benchmarks
> 
>
> Key: IGNITE-4905
> URL: https://issues.apache.org/jira/browse/IGNITE-4905
> Project: Ignite
>  Issue Type: Bug
>  Components: SQL
>Affects Versions: 1.9
>Reporter: Alexander Paschenko
>Assignee: Alexander Paschenko
> Fix For: 2.0
>
>




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

[jira] [Commented] (IGNITE-4625) .NET: MixedClusterTest leaves Java-only node running

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4625:


Looks like stopping Java node from a Java task is not a good idea, this can 
lead to a failure, which leaves "grid2" in the map:
{{No verification for local node leave has been received from coordinator (will 
stop node anyway).}}

> .NET: MixedClusterTest leaves Java-only node running
> 
>
> Key: IGNITE-4625
> URL: https://issues.apache.org/jira/browse/IGNITE-4625
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> MixedClusterTest causes consequent tests to fail in some situations because 
> it leaves java-only "grid2" node running. Looks like ExecuteJavaTask does not 
> stop node properly.



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

[jira] [Created] (IGNITE-4905) ClassCastException in DML benchmarks

[Alexander Paschenko (JIRA)]

Alexander Paschenko created IGNITE-4905:
---

 Summary: ClassCastException in DML benchmarks
 Key: IGNITE-4905
 URL: https://issues.apache.org/jira/browse/IGNITE-4905
 Project: Ignite
  Issue Type: Bug
  Components: SQL
Affects Versions: 1.9
Reporter: Alexander Paschenko
Assignee: Alexander Paschenko
 Fix For: 2.0






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

[jira] [Commented] (IGNITE-4699) Introduce custom configurable executors.

[Alexander Menshikov (JIRA)]

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

Alexander Menshikov commented on IGNITE-4699:
-

[~vozerov]
Okay. I will think about new future after Taras patch will applied.

> Introduce custom configurable executors.
> 
>
> Key: IGNITE-4699
> URL: https://issues.apache.org/jira/browse/IGNITE-4699
> Project: Ignite
>  Issue Type: Task
>  Components: compute
>Reporter: Vladimir Ozerov
>Assignee: Alexander Menshikov
>  Labels: important
> Fix For: 2.0
>
>
> We need to provide a way to configure custom thread pools for user compute 
> tasks. 
> Proposed API:
> 1) Config
> {code}
> class ExecutorConfiguration {
> String name;
> int size;
> }
> {code}
> 2) Choosing executor for compute task:
> {code}
> IgniteCompute compute = Ignite.compute().withExecutor("my_exec");
> {code}
> 3) Accessing raw executor (could be required for proper execution of future 
> listeners):
> {code}
> ThreadPoolExecutor exec = ignite.compute().localExecutor("my_exec");
> {code}



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

[jira] [Comment Edited] (IGNITE-4535) Add option to store deserialized values on-heap

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-4535 at 4/3/17 2:22 PM:


Removed {{CacheConfiguration.OffheapMaxMemory}}, 
{{CacheConfiguration.SqlOnheapRowCacheSize}} in .NET


was (Author: ptupitsyn):
Removeв {{CacheConfiguration.OffheapMaxMemory}}, 
{{CacheConfiguration.SqlOnheapRowCacheSize}} in .NET

> Add option to store deserialized values on-heap
> ---
>
> Key: IGNITE-4535
> URL: https://issues.apache.org/jira/browse/IGNITE-4535
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>  Labels: important
> Fix For: 2.0
>
>
> Now cache data is always stored in offheap (pagememory). Need implement 
> option to also store deserialised values in heap memory, this should be 
> replacement for existing CacheConfiguration.memoryMode configuration.



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

[jira] [Commented] (IGNITE-4535) Add option to store deserialized values on-heap

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4535:


Removeв {{CacheConfiguration.OffheapMaxMemory}}, 
{{CacheConfiguration.SqlOnheapRowCacheSize}} in .NET

> Add option to store deserialized values on-heap
> ---
>
> Key: IGNITE-4535
> URL: https://issues.apache.org/jira/browse/IGNITE-4535
> Project: Ignite
>  Issue Type: Sub-task
>  Components: cache
>Reporter: Alexey Goncharuk
>Assignee: Alexey Goncharuk
>  Labels: important
> Fix For: 2.0
>
>
> Now cache data is always stored in offheap (pagememory). Need implement 
> option to also store deserialised values in heap memory, this should be 
> replacement for existing CacheConfiguration.memoryMode configuration.



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

[jira] [Updated] (IGNITE-4883) Web Console: Improve the tables on Admin Panel Screen

[Vica Abramova (JIRA)]

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

Vica Abramova updated IGNITE-4883:
--
Description: 
Tab Countries:
- don't show number on Country column
- by default, do sorting by number of users (descendingly), not by alphabet
- show only number on User column (delete the title 'total rows')
- fix the bug: when user click in the Exclude input and then press Enter btn, 
we do not need to download .csv

Companies Tab:
- don't show number on Company column
- by default, do sorting by number of users (descendingly), not by alphabet
- show only number on User column (delete the title 'total rows')

  was:
Tab Countries:
- don't show number on Country column
- by default, do sorting by number of users (descendingly), not by alphabet
- show only number on User column (delete the title 'total rows')
- fix the bug: when user click in the Exclude input and then press Enter btn, 
we do not need to download .csv




> Web Console: Improve the tables on Admin Panel Screen
> -
>
> Key: IGNITE-4883
> URL: https://issues.apache.org/jira/browse/IGNITE-4883
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>
> Tab Countries:
> - don't show number on Country column
> - by default, do sorting by number of users (descendingly), not by alphabet
> - show only number on User column (delete the title 'total rows')
> - fix the bug: when user click in the Exclude input and then press Enter btn, 
> we do not need to download .csv
> Companies Tab:
> - don't show number on Company column
> - by default, do sorting by number of users (descendingly), not by alphabet
> - show only number on User column (delete the title 'total rows')



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

[jira] [Comment Edited] (IGNITE-4839) Remove CacheTypeMetadata

[Taras Ledkov (JIRA)]

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

Taras Ledkov edited comment on IGNITE-4839 at 4/3/17 2:06 PM:
--

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


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

> Remove CacheTypeMetadata
> 
>
> Key: IGNITE-4839
> URL: https://issues.apache.org/jira/browse/IGNITE-4839
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>




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

[jira] [Issue Comment Deleted] (IGNITE-4839) Remove CacheTypeMetadata

[Taras Ledkov (JIRA)]

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

Taras Ledkov updated IGNITE-4839:
-
Comment: was deleted

(was: Tests 
[results|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1667%2Fhead]
 is OK with me.)

> Remove CacheTypeMetadata
> 
>
> Key: IGNITE-4839
> URL: https://issues.apache.org/jira/browse/IGNITE-4839
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>




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

[jira] [Commented] (IGNITE-4839) Remove CacheTypeMetadata

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-4839:
--

Fixed. Waits TC 
[resukts|http://195.239.208.174/project.html?projectId=IgniteTests=projectOverview_IgniteTests=pull%2F1667%2Fhead]
 again.

> Remove CacheTypeMetadata
> 
>
> Key: IGNITE-4839
> URL: https://issues.apache.org/jira/browse/IGNITE-4839
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>




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

[jira] [Commented] (IGNITE-4902) .NET: StartFromApplicationConfiguration does not work in ASP.NET

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-4902:


Fixed in master.

> .NET: StartFromApplicationConfiguration does not work in ASP.NET
> 
>
> Key: IGNITE-4902
> URL: https://issues.apache.org/jira/browse/IGNITE-4902
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> {{Ignition.StartFromApplicationConfiguration()}} fails with {{exePath must be 
> specified when not running inside a stand alone exe}} error. Equivalent call 
> in web environment would be 
> {{System.Web.Configuration.WebConfigurationManager.OpenWebConfiguration("~")}},
>  but we really do not want System.Web dependency.
> {{Ignition.StartFromApplicationConfiguration("igniteConfiguration")}} works, 
> and that is what we should do from the method without arguments.



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

[jira] [Resolved] (IGNITE-4902) .NET: StartFromApplicationConfiguration does not work in ASP.NET

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn resolved IGNITE-4902.

Resolution: Fixed

> .NET: StartFromApplicationConfiguration does not work in ASP.NET
> 
>
> Key: IGNITE-4902
> URL: https://issues.apache.org/jira/browse/IGNITE-4902
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.7
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.0
>
>
> {{Ignition.StartFromApplicationConfiguration()}} fails with {{exePath must be 
> specified when not running inside a stand alone exe}} error. Equivalent call 
> in web environment would be 
> {{System.Web.Configuration.WebConfigurationManager.OpenWebConfiguration("~")}},
>  but we really do not want System.Web dependency.
> {{Ignition.StartFromApplicationConfiguration("igniteConfiguration")}} works, 
> and that is what we should do from the method without arguments.



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

[jira] [Commented] (IGNITE-4839) Remove CacheTypeMetadata

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4839:
-

[~tledkov-gridgain],
I think we should remove two public methods added to {{QueryEntity}}. Note that 
it operates only on {{String}} types in other places, and adding {{Class}} to 
method signatures makes it inconsistent. 
No doubts that {{QueryEntity}} API should be improved, but let's do that in 
another ticket carefully considering overall API consistency.

> Remove CacheTypeMetadata
> 
>
> Key: IGNITE-4839
> URL: https://issues.apache.org/jira/browse/IGNITE-4839
> Project: Ignite
>  Issue Type: Sub-task
>  Components: general
>Affects Versions: 1.9
>Reporter: Taras Ledkov
>Assignee: Taras Ledkov
> Fix For: 2.0
>
>




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

[jira] [Assigned] (IGNITE-4851) IllegalStateException: Tree is being concurrently destroyed in atomic cache

[Ilya Lantukh (JIRA)]

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

Ilya Lantukh reassigned IGNITE-4851:


Assignee: Ilya Lantukh  (was: Alexey Goncharuk)

> IllegalStateException: Tree is being concurrently destroyed in atomic cache
> ---
>
> Key: IGNITE-4851
> URL: https://issues.apache.org/jira/browse/IGNITE-4851
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Reporter: Semen Boikov
>Assignee: Ilya Lantukh
>Priority: Blocker
> Fix For: 2.0
>
> Attachments: Ignite_Tests_Ignite_Binary_Objects_Cache_2_1651.log.zip
>
>
> I observed several hangs on TC in tests with changing topology, most probably 
> reason of hang is this error:
> {noformat}
> [07:26:03]W:   [org.apache.ignite:ignite-core] 
> java.lang.IllegalStateException: Tree is being concurrently destroyed: 
> p-1006##CacheData
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.checkDestroyed(BPlusTree.java:908)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.database.tree.BPlusTree.invoke(BPlusTree.java:1451)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.invoke(IgniteCacheOffheapManagerImpl.java:936)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.invoke(IgniteCacheOffheapManagerImpl.java:338)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.innerUpdate(GridCacheMapEntry.java:1617)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.processDhtAtomicUpdateRequest(GridDhtAtomicCache.java:3276)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache.access$1800(GridDhtAtomicCache.java:126)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$8.apply(GridDhtAtomicCache.java:372)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.distributed.dht.atomic.GridDhtAtomicCache$8.apply(GridDhtAtomicCache.java:367)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:827)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:369)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:293)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$000(GridCacheIoManager.java:95)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:238)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1227)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:855)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager.access$2100(GridIoManager.java:109)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.managers.communication.GridIoManager$6.run(GridIoManager.java:785)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> org.apache.ignite.internal.util.StripedExecutor$Stripe.run(StripedExecutor.java:428)
> [07:26:03]W:   [org.apache.ignite:ignite-core]at 
> java.lang.Thread.run(Thread.java:745)
> {noformat}
> This error was thrown on backup, as result it did not send reply to primary 
> and update hang. I guess this exception is possible when partition is evicted 
> while do GridCacheMapEntry.innerUpdate.
> Attached full log from TC.



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

[jira] [Assigned] (IGNITE-4509) SQL: query with condition on affinity columns and without joins and subqueries can be replaced with GET

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov reassigned IGNITE-4509:
--

Assignee: Sergey Kalashnikov

> SQL: query with condition on affinity columns and without joins and 
> subqueries can be replaced with GET
> ---
>
> Key: IGNITE-4509
> URL: https://issues.apache.org/jira/browse/IGNITE-4509
> Project: Ignite
>  Issue Type: Task
>  Components: SQL
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
>  Labels: performance, sql
> Fix For: 2.0
>
>
> Simple SQL queries usually demonstrate negative scalability when more nodes 
> are added. 
> Consider the following query:
> {code}
> SELECT * FROM Person p
> WHERE p.id = ?
> {code}
> If {{Person.id}} is affinity field, then query can be replaced with plain 
> {{IgniteCache.get}} or some specialized version of GET, which will return 
> only desired fields. This optimization will guarantee smooth scale with any 
> number of nodes.



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

[jira] [Assigned] (IGNITE-4871) Web console: Implement possibility to configure Kubernetes IP finder

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-4871:
-

Assignee: Pavel Konstantinov  (was: Vasiliy Sisko)

> Web console: Implement possibility to configure Kubernetes IP finder
> 
>
> Key: IGNITE-4871
> URL: https://issues.apache.org/jira/browse/IGNITE-4871
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Pavel Konstantinov
> Fix For: 2.0
>
>




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

[jira] [Commented] (IGNITE-4871) Web console: Implement possibility to configure Kubernetes IP finder

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-4871:
---

Fixed feedback error on invalid URL.

> Web console: Implement possibility to configure Kubernetes IP finder
> 
>
> Key: IGNITE-4871
> URL: https://issues.apache.org/jira/browse/IGNITE-4871
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 2.0
>
>




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

[jira] [Comment Edited] (IGNITE-4895) TC should fail suite if AssertionError is output to logs

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov edited comment on IGNITE-4895 at 4/3/17 11:02 AM:
---

That's not true,
we have tests causing "positive" assertions 

For example
1) [INFO ][test-runner-#4966%future.GridEmbeddedFutureSelfTest%][root] Failed 
with unhandled error (normal behaviour): java.lang.AssertionError: Test 
assertion (should be ignored).
2) [INFO ][test-runner-#4883%lang.GridByteArrayListSelfTest%][root] Caught 
expected error: java.lang.AssertionError


was (Author: avinogradov):
That's not true,
we have tests causing "positive" assertions 

1) [INFO ][test-runner-#4966%future.GridEmbeddedFutureSelfTest%][root] Failed 
with unhandled error (normal behaviour): java.lang.AssertionError: Test 
assertion (should be ignored).
2) [INFO ][test-runner-#4883%lang.GridByteArrayListSelfTest%][root] Caught 
expected error: java.lang.AssertionError

> TC should fail suite if AssertionError is output to logs
> 
>
> Key: IGNITE-4895
> URL: https://issues.apache.org/jira/browse/IGNITE-4895
> Project: Ignite
>  Issue Type: Test
>Reporter: Yakov Zhdanov
>Assignee: Anton Vinogradov
>Priority: Blocker
> Fix For: 2.0
>
>
> AssertionError is never thrown on purpose during the tests opposite to 
> exceptions which are normal for plenty of scenarios.
> TC should fail if assertion error is output to logs.



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

[jira] [Resolved] (IGNITE-4895) TC should fail suite if AssertionError is output to logs

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov resolved IGNITE-4895.
--
Resolution: Won't Fix

> TC should fail suite if AssertionError is output to logs
> 
>
> Key: IGNITE-4895
> URL: https://issues.apache.org/jira/browse/IGNITE-4895
> Project: Ignite
>  Issue Type: Test
>Reporter: Yakov Zhdanov
>Assignee: Anton Vinogradov
>Priority: Blocker
> Fix For: 2.0
>
>
> AssertionError is never thrown on purpose during the tests opposite to 
> exceptions which are normal for plenty of scenarios.
> TC should fail if assertion error is output to logs.



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

[jira] [Commented] (IGNITE-4895) TC should fail suite if AssertionError is output to logs

[Anton Vinogradov (JIRA)]

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

Anton Vinogradov commented on IGNITE-4895:
--

That's not true,
we have tests causing "positive" assertions 

1) [INFO ][test-runner-#4966%future.GridEmbeddedFutureSelfTest%][root] Failed 
with unhandled error (normal behaviour): java.lang.AssertionError: Test 
assertion (should be ignored).
2) [INFO ][test-runner-#4883%lang.GridByteArrayListSelfTest%][root] Caught 
expected error: java.lang.AssertionError

> TC should fail suite if AssertionError is output to logs
> 
>
> Key: IGNITE-4895
> URL: https://issues.apache.org/jira/browse/IGNITE-4895
> Project: Ignite
>  Issue Type: Test
>Reporter: Yakov Zhdanov
>Assignee: Anton Vinogradov
>Priority: Blocker
> Fix For: 2.0
>
>
> AssertionError is never thrown on purpose during the tests opposite to 
> exceptions which are normal for plenty of scenarios.
> TC should fail if assertion error is output to logs.



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

[jira] [Commented] (IGNITE-3585) CPP: Rework methods that accept containers so any container could be used with them.

[Sergey Kalashnikov (JIRA)]

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

Sergey Kalashnikov commented on IGNITE-3585:


[~isapego], I'm fine with the changes as well.

> CPP: Rework methods that accept containers so any container could be used 
> with them.
> 
>
> Key: IGNITE-3585
> URL: https://issues.apache.org/jira/browse/IGNITE-3585
> Project: Ignite
>  Issue Type: Task
>  Components: platforms
>Affects Versions: 1.6
>Reporter: Igor Sapego
>Assignee: Igor Sapego
>  Labels: cpp
> Fix For: 2.0
>
>
> There are methods that could possibly be used with any container but by some 
> reason they only accept arguments of a single specific container type. It can 
> be non convenient for user and bad from the performance point of view if user 
> uses other container type to store values. Consider using iterators 
> (preferably) or template type for the container.
> Methods of interest:
> - {{QueryCursor::GetAll}}
> - {{Cache::ContainsKeys}}
> - {{Cache::GetAll}}
> - {{Cache::PutAll}}
> - {{Cache::LocalEvict}}
> - {{Cache::ClearAll}}
> - {{Cache::LocalClearAll}}
> - {{Cache::RemoveAll}}.



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

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

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov commented on IGNITE-4052:
--

[~javaller],
For example you can look at cassandra mesos integration 
https://github.com/mesosphere/dcos-cassandra-service/blob/5d6d15e646f1df2fa10fa98d91993d3a6b4719c4/cassandra-commons/src/main/java/com/mesosphere/dcos/cassandra/common/config/ServiceConfig.java.
 List of application which use Mesos not secret and can be found on official 
mesos site http://mesos.apache.org/documentation/latest/frameworks. ;)

I'm really don't understand how the libs can help you. Could you clarify it?

> 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-4812) Disable EventStorageSpi by default

[Alper Tekinalp (JIRA)]

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

Alper Tekinalp commented on IGNITE-4812:


[~vkulichenko], I did the changes. Can you check it again?

> Disable EventStorageSpi by default
> --
>
> Key: IGNITE-4812
> URL: https://issues.apache.org/jira/browse/IGNITE-4812
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 1.9
>Reporter: Valentin Kulichenko
>Assignee: Alper Tekinalp
> Fix For: 2.0
>
>
> Current default implementation of {{EventStorageSpi}} is 
> {{MemoryEventStorageSpi}}. It consumes a lot of memory, while is used only 
> for events querying (i.e. not listening), which is a fairly rare use case.
> Need to:
> * Introduce {{NoOpEventStorageSpi}}.
> * Make {{NoOpEventStorageSpi}} the default one.
> * Throw an exception when {{IgniteEvents#localQuery}} or {{#remoteQuery}} 
> method is called with default setting. Exception message should explain how 
> to fix it.



--
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 everybody!

Nikolay, I didn't have experience with ignite-yarn integration and didn't
have idea how fix it, but its interesting for me. Can you write name of
another java application, in which I can see how they connect to mesos.

Also, can you write how correctly to test working of Builder#setRoleBytes
and Builder#setUserBytes without library org.junit.Rule and
org.junit.contrib.java.lang.system.EnvironmentVariables.

Vadim




> 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] [Closed] (IGNITE-4002) Incorrect errors/warnings while odbc driver installation

[Ksenia Rybakova (JIRA)]

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

Ksenia Rybakova closed IGNITE-4002.
---

Verified in master branch

> Incorrect errors/warnings while odbc driver installation
> 
>
> Key: IGNITE-4002
> URL: https://issues.apache.org/jira/browse/IGNITE-4002
> Project: Ignite
>  Issue Type: Bug
>  Components: platforms
>Affects Versions: 1.7
> Environment: Windows 2010 (Rus)
>Reporter: Ksenia Rybakova
>Assignee: Igor Sapego
>Priority: Minor
>  Labels: cpp
> Fix For: 2.0
>
>
> 1) Build x64 odbc driver according to $IGNITE_HOME\platforms\cpp\DEVNOTES.txt
> 2) Install x64 bit driver according to 
> $IGNITE_HOME\platforms\cpp\odbc\README.txt. Don't pass x32 driver as a second 
> parameter:
> {noformat}
> D:\ignite\platforms\cpp\odbc\install>install_amd64.cmd 
> D:\ignite\platforms\cpp\project\vs\x64\Release\ignite.odbc.dll
> Installing 64-bit driver: 
> D:\ignite\platforms\cpp\project\vs\x64\Release\ignite.odbc.dll
> Операция успешно завершена.
> Операция успешно завершена.
> Операция успешно завершена.
> Операция успешно завершена.
> Операция успешно завершена.
> Ошибка в синтаксисе команды.
> {noformat}
> Expected: "warning: 32-bit driver is not specified. If you want to install 
> 32-bit driver please specify path to it as a second argument." message
> Actual: "Ошибка в синтаксисе команды".
> 3) Install x64 bit driver according to 
> $IGNITE_HOME\platforms\cpp\odbc\README.txt. Pass \ (root directory) as a 
> second parameter (x32 driver):
> {noformat}
> D:\ignite\platforms\cpp\odbc\install>install_amd64.cmd 
> D:\ignite\platforms\cpp\project\vs\x64\Release\ignite.odbc.dll \
> Installing 64-bit driver: 
> D:\ignite\platforms\cpp\project\vs\x64\Release\ignite.odbc.dll
> Операция успешно завершена.
> Операция успешно завершена.
> Операция успешно завершена.
> Операция успешно завершена.
> Операция успешно завершена.
> Installing 32-bit driver: \
> Операция успешно завершена.
> Операция успешно завершена.
> Операция успешно завершена.
> Операция успешно завершена.
> Операция успешно завершена.
> {noformat}
> Expected:
> "warning: The path you have specified seems to be a directory. Note that you 
> have to specify path to driver file itself instead." warning before 
> "Installing 32-bit driver: \" 
> Actual: no such a warning (if exist %ODBC_X86%\ -> if exist \ \ -> false. So 
> this check doesn't work in this case).
> Please, consider some changes in error handling.



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

[jira] [Commented] (IGNITE-4815) CollisionSPI.onCollision() method has a confusing javadoc

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-4815:


Github user asfgit closed the pull request at:

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


> CollisionSPI.onCollision() method has a confusing javadoc
> -
>
> Key: IGNITE-4815
> URL: https://issues.apache.org/jira/browse/IGNITE-4815
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Reporter: Andrew Mashenkov
>Assignee: Andrew Mashenkov
>Priority: Trivial
> Fix For: 2.0
>
>
> CollisionSPI calls on every EVT_NODE_METRICS_UPDATED event.
> It looks like CollisionSPI.onCollision() method has a confusing javadoc.



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

[jira] [Updated] (IGNITE-4728) Web Console: Remember the screen from which user has left the previous session.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-4728:
---
Attachment: ignite-4728.png

> Web Console: Remember the screen from which user has left the previous 
> session.
> ---
>
> Key: IGNITE-4728
> URL: https://issues.apache.org/jira/browse/IGNITE-4728
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Dmitriy Shabalin
> Attachments: ignite-4728.png
>
>
> Don't save latest state for demo mode.



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

[jira] [Updated] (IGNITE-4728) Web Console: Remember the screen from which user has left the previous session.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-4728:
---
Attachment: (was: ignite-4728.png)

> Web Console: Remember the screen from which user has left the previous 
> session.
> ---
>
> Key: IGNITE-4728
> URL: https://issues.apache.org/jira/browse/IGNITE-4728
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Dmitriy Shabalin
>
> Don't save latest state for demo mode.



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

[jira] [Assigned] (IGNITE-4871) Web console: Implement possibility to configure Kubernetes IP finder

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-4871:


Assignee: Vasiliy Sisko  (was: Alexey Kuznetsov)

Please fix "Kubernetes server" feedback on error.

> Web console: Implement possibility to configure Kubernetes IP finder
> 
>
> Key: IGNITE-4871
> URL: https://issues.apache.org/jira/browse/IGNITE-4871
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Vasiliy Sisko
> Fix For: 2.0
>
>




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

[jira] [Commented] (IGNITE-4477) Fix IgniteFuture.listen() and IgniteFuture.chain() semantics

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev commented on IGNITE-4477:
-

Vladimir, please review the fix: [PR 
1710|https://github.com/apache/ignite/pull/1710]

Instead of two async methods for listen and chain I've added one with nullable 
Executor. I don't think we need to duplicate methods just without last argument.

> Fix IgniteFuture.listen() and IgniteFuture.chain() semantics
> 
>
> Key: IGNITE-4477
> URL: https://issues.apache.org/jira/browse/IGNITE-4477
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>
> *Problem*
> We allow users to pass continuations to {{IgniteFuture}} which will be 
> executed on future completion. This can be done through {{listen}} or 
> {{chain}} methods.
> However, continuation semantics is broken intrinsically:
> 1) If future is already completed, user code executed in the same thread;
> 2) If future is not completed yet, it will be executed in completion thread.
> Neither of this options are valid because it easily leads to starvation. E.g.:
> {code}
> IgniteFuture fut = cache.getAsync(key2);
> fut.listen(fut0 -> {
>  cache.put(key2, val2); // Possible deadlock, because invoked in sys pool;
> });
> {code}
> *Solution*
> 1) By default callbacks must be executed asynchronously in some common pool 
> (public pool? new "callback pool"? FJP?)
> 2) It should be possible to specify where to execute a callback explicitly:
> {code}
> IgniteFuture.listen(IgniteClosure, ExecutorService);
> {code}
> 3) We may want to expose our public pool on API for convenience.



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

[jira] [Comment Edited] (IGNITE-4477) Fix IgniteFuture.listen() and IgniteFuture.chain() semantics

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev edited comment on IGNITE-4477 at 4/3/17 7:48 AM:
-

Vladimir, please review the fix: [PR 
1710|https://github.com/apache/ignite/pull/1710]

Instead of two async methods for listen and chain I've added one with nullable 
Executor. I don't think we need to duplicate methods just without last argument.

Here is a link to upsource: 
[IGNT-CR-151|http://reviews.ignite.apache.org/ignite/review/IGNT-CR-151]


was (Author: dkarachentsev):
Vladimir, please review the fix: [PR 
1710|https://github.com/apache/ignite/pull/1710]

Instead of two async methods for listen and chain I've added one with nullable 
Executor. I don't think we need to duplicate methods just without last argument.

> Fix IgniteFuture.listen() and IgniteFuture.chain() semantics
> 
>
> Key: IGNITE-4477
> URL: https://issues.apache.org/jira/browse/IGNITE-4477
> Project: Ignite
>  Issue Type: Task
>  Components: general
>Affects Versions: 1.8
>Reporter: Vladimir Ozerov
>Assignee: Dmitry Karachentsev
> Fix For: 2.0
>
>
> *Problem*
> We allow users to pass continuations to {{IgniteFuture}} which will be 
> executed on future completion. This can be done through {{listen}} or 
> {{chain}} methods.
> However, continuation semantics is broken intrinsically:
> 1) If future is already completed, user code executed in the same thread;
> 2) If future is not completed yet, it will be executed in completion thread.
> Neither of this options are valid because it easily leads to starvation. E.g.:
> {code}
> IgniteFuture fut = cache.getAsync(key2);
> fut.listen(fut0 -> {
>  cache.put(key2, val2); // Possible deadlock, because invoked in sys pool;
> });
> {code}
> *Solution*
> 1) By default callbacks must be executed asynchronously in some common pool 
> (public pool? new "callback pool"? FJP?)
> 2) It should be possible to specify where to execute a callback explicitly:
> {code}
> IgniteFuture.listen(IgniteClosure, ExecutorService);
> {code}
> 3) We may want to expose our public pool on API for convenience.



--
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

[Dmitry Karachentsev (JIRA)]

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

Dmitry Karachentsev commented on IGNITE-4891:
-

Valentin, please review the fix: [PR 
1715|https://github.com/apache/ignite/pull/1715]

> 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] [Commented] (IGNITE-4699) Introduce custom configurable executors.

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-4699:
-

[~sharpler],
There are two main problems which I expect to be covered once ticket is ready:
1) Execution of nested compute calls. In this case you can make decision on 
per-job basis. Say, if you created a re-usable component, you could do 
something like:
{code}
compute.withExecutor("component_executor").[run_job]
{code}
And any code on top of this component will be able to use it safely without a 
risk of deadlock.
2) Execution of chained calls, especially {{IgniteFuture.chain}} and 
{{IgniteFuture.listen}}. Currently user has no control on where continuation is 
to be executed, so he can inadvertently run something in public pool, causing 
exhaustion of public pool threads. Once user has access to predefined 
executors, he will be able to control this behavior.

Regarding simplicity of configuration, for other thread pools we allow users to 
configure only number of threads (e.g. 
{{IgniteConfiguration.publicThreadPoolSize}}. And I am not aware of any 
complains on insufficient flexibility of this approach. This is why I propose 
to start with as simple config as possible. We will always be able to extend it 
in future if needed.

One more important reason why we need to have this feature ready ASAP is 2.0 
release, which is expected to happen in April. This feature will require 
message protocol changes, and hence broke binary compatibility. 

Having said that I'd prefer to go ahead with Taras patch at the moment, while 
keeping in mind all proposed improvement for future releases. Ideally, it would 
be cool to materialize them into JIRA tickets, and plan their implementation in 
AI 2.1 release or so.

> Introduce custom configurable executors.
> 
>
> Key: IGNITE-4699
> URL: https://issues.apache.org/jira/browse/IGNITE-4699
> Project: Ignite
>  Issue Type: Task
>  Components: compute
>Reporter: Vladimir Ozerov
>Assignee: Alexander Menshikov
>  Labels: important
> Fix For: 2.0
>
>
> We need to provide a way to configure custom thread pools for user compute 
> tasks. 
> Proposed API:
> 1) Config
> {code}
> class ExecutorConfiguration {
> String name;
> int size;
> }
> {code}
> 2) Choosing executor for compute task:
> {code}
> IgniteCompute compute = Ignite.compute().withExecutor("my_exec");
> {code}
> 3) Accessing raw executor (could be required for proper execution of future 
> listeners):
> {code}
> ThreadPoolExecutor exec = ignite.compute().localExecutor("my_exec");
> {code}



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

[jira] [Assigned] (IGNITE-4728) Web Console: Remember the screen from which user has left the previous session.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov reassigned IGNITE-4728:
--

Assignee: Dmitriy Shabalin  (was: Pavel Konstantinov)

> Web Console: Remember the screen from which user has left the previous 
> session.
> ---
>
> Key: IGNITE-4728
> URL: https://issues.apache.org/jira/browse/IGNITE-4728
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Dmitriy Shabalin
> Attachments: ignite-4728.png
>
>
> Don't save latest state for demo mode.



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

[jira] [Updated] (IGNITE-4728) Web Console: Remember the screen from which user has left the previous session.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov updated IGNITE-4728:
---
Attachment: ignite-4728.png

> Web Console: Remember the screen from which user has left the previous 
> session.
> ---
>
> Key: IGNITE-4728
> URL: https://issues.apache.org/jira/browse/IGNITE-4728
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Pavel Konstantinov
> Attachments: ignite-4728.png
>
>
> Don't save latest state for demo mode.



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

[jira] [Commented] (IGNITE-4728) Web Console: Remember the screen from which user has left the previous session.

[Pavel Konstantinov (JIRA)]

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

Pavel Konstantinov commented on IGNITE-4728:


Top-level menu become invisible after I was redirected to Configuration


> Web Console: Remember the screen from which user has left the previous 
> session.
> ---
>
> Key: IGNITE-4728
> URL: https://issues.apache.org/jira/browse/IGNITE-4728
> Project: Ignite
>  Issue Type: Task
>  Components: UI, wizards
>Reporter: Vica Abramova
>Assignee: Pavel Konstantinov
>
> Don't save latest state for demo mode.



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

[jira] [Updated] (IGNITE-4871) Web console: Implement possibility to configure Kubernetes IP finder

[Alexey Kuznetsov (JIRA)]

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

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

> Web console: Implement possibility to configure Kubernetes IP finder
> 
>
> Key: IGNITE-4871
> URL: https://issues.apache.org/jira/browse/IGNITE-4871
> Project: Ignite
>  Issue Type: Task
>  Components: wizards
>Affects Versions: 1.8
>Reporter: Vasiliy Sisko
>Assignee: Alexey Kuznetsov
> Fix For: 2.0
>
>




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

[jira] [Closed] (IGNITE-4877) Add test covers get(key, type) in direct way (via SpringCache)

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur closed IGNITE-4877.
--

> Add test covers get(key, type) in direct way (via SpringCache)
> --
>
> Key: IGNITE-4877
> URL: https://issues.apache.org/jira/browse/IGNITE-4877
> Project: Ignite
>  Issue Type: Test
>Reporter: Vyacheslav Daradur
>  Labels: test
> Fix For: 2.0
>
>




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

[jira] [Resolved] (IGNITE-4877) Add test covers get(key, type) in direct way (via SpringCache)

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur resolved IGNITE-4877.

Resolution: Duplicate
  Assignee: (was: Vyacheslav Daradur)

Method was covered with unit tests in the IGNITE-4823.

> Add test covers get(key, type) in direct way (via SpringCache)
> --
>
> Key: IGNITE-4877
> URL: https://issues.apache.org/jira/browse/IGNITE-4877
> Project: Ignite
>  Issue Type: Test
>Reporter: Vyacheslav Daradur
>  Labels: test
> Fix For: 2.0
>
>




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