[jira] [Closed] (IGNITE-6567) Document JDBC "multipleStatementsAllowed" property

[Denis Magda (JIRA)]

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

Denis Magda closed IGNITE-6567.
---

> Document JDBC "multipleStatementsAllowed" property
> --
>
> Key: IGNITE-6567
> URL: https://issues.apache.org/jira/browse/IGNITE-6567
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
> Fix For: 2.3
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6567) Document JDBC "multipleStatementsAllowed" property

[Prachi Garg (JIRA)]

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

Prachi Garg reassigned IGNITE-6567:
---

Assignee: Denis Magda  (was: Prachi Garg)

> Document JDBC "multipleStatementsAllowed" property
> --
>
> Key: IGNITE-6567
> URL: https://issues.apache.org/jira/browse/IGNITE-6567
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Denis Magda
> Fix For: 2.3
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6567) Document JDBC "multipleStatementsAllowed" property

[Prachi Garg (JIRA)]

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

Prachi Garg commented on IGNITE-6567:
-

Reviewed.

> Document JDBC "multipleStatementsAllowed" property
> --
>
> Key: IGNITE-6567
> URL: https://issues.apache.org/jira/browse/IGNITE-6567
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Prachi Garg
> Fix For: 2.3
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6569) DROP table is frozen in special case

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6569:


Github user asfgit closed the pull request at:

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


> DROP table is frozen in special case
> 
>
> Key: IGNITE-6569
> URL: https://issues.apache.org/jira/browse/IGNITE-6569
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Alexander Paschenko
> Fix For: 2.3
>
> Attachments: DropTableExample2-project.tar.gz
>
>
> In attached project file:
> # Run node with using of DropFrozenTableStartup class.
> Execution is frozen in time of DROP table process.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5608) SQL scripts execution capability

[Oleg Ostanin (JIRA)]

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

Oleg Ostanin commented on IGNITE-5608:
--

[~ntikho...@apache.org],
 Thank you. I think you are right, will fix it.

> SQL scripts execution capability
> 
>
> Key: IGNITE-5608
> URL: https://issues.apache.org/jira/browse/IGNITE-5608
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Denis Magda
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> There should be a way to feed an SQL script to Ignite and execute it right 
> away. A script can consist of DDL command that will define cluster and SQL 
> configuration as well as of DML commands that, for instance, preload data 
> into Ignite.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-5608) SQL scripts execution capability

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov edited comment on IGNITE-5608 at 10/9/17 4:50 PM:
---

[~oleg-ostanin],
Thank you for your contribution! I've reviewed the changes. I have only one 
comment. Let's to use space instead of equals sign. For example:
{code}ignitesql.sh -ch=127.0.0.1 -p=10800 -s=MySchema -dj=true -ej=true 
-ssb=0{code}
I guess the following command looks more consistency with other cli tools:
{code}ignitesql.sh 127.0.0.1 -p 10800 -s MySchema -dj -ej -ssb 0{code}


was (Author: ntikhonov):
[~oleg-ostanin],
Thank you for your contribution! I've reviewed the changes. I have only one 
comment. Let's to use space instead of equals sign. For example:
{code}ignitesql.sh -ch=127.0.0.1 -p=10800 -s=MySchema -dj=true -ej=true 
-ssb=0{code}
I guess the following command looks more consistency with other cli tools:
{code}ignitesql.sh 127.0.0.1 -s MySchema -dj true -ej -ssb 0{code}

> SQL scripts execution capability
> 
>
> Key: IGNITE-5608
> URL: https://issues.apache.org/jira/browse/IGNITE-5608
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Denis Magda
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> There should be a way to feed an SQL script to Ignite and execute it right 
> away. A script can consist of DDL command that will define cluster and SQL 
> configuration as well as of DML commands that, for instance, preload data 
> into Ignite.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5608) SQL scripts execution capability

[Nikolay Tikhonov (JIRA)]

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

Nikolay Tikhonov commented on IGNITE-5608:
--

[~oleg-ostanin],
Thank you for your contribution! I've reviewed the changes. I have only one 
comment. Let's to use space instead of equals sign. For example:
{code}ignitesql.sh -ch=127.0.0.1 -p=10800 -s=MySchema -dj=true -ej=true 
-ssb=0{code}
I guess the following command looks more consistency with other cli tools:
{code}ignitesql.sh 127.0.0.1 -s MySchema -dj true -ej -ssb 0{code}

> SQL scripts execution capability
> 
>
> Key: IGNITE-5608
> URL: https://issues.apache.org/jira/browse/IGNITE-5608
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Denis Magda
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> There should be a way to feed an SQL script to Ignite and execute it right 
> away. A script can consist of DDL command that will define cluster and SQL 
> configuration as well as of DML commands that, for instance, preload data 
> into Ignite.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6585) SVM for Apache Ignite ML module

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko reassigned IGNITE-6585:
--

Assignee: Oleg Ignatenko

> SVM for Apache Ignite ML module
> ---
>
> Key: IGNITE-6585
> URL: https://issues.apache.org/jira/browse/IGNITE-6585
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Yury Babak
>Assignee: Oleg Ignatenko
>
> SVM - support vector machine, is pretty common algorithm and I think that we 
> need it in our module.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6585) SVM for Apache Ignite ML module

[Yury Babak (JIRA)]

Yury Babak created IGNITE-6585:
--

 Summary: SVM for Apache Ignite ML module
 Key: IGNITE-6585
 URL: https://issues.apache.org/jira/browse/IGNITE-6585
 Project: Ignite
  Issue Type: New Feature
  Components: ml
Reporter: Yury Babak


SVM - support vector machine, is pretty common algorithm and I think that we 
need it in our module.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5059) Implement logistic regression

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-5059:


Got it, thanks for your quick update Vladislav!

> Implement logistic regression 
> --
>
> Key: IGNITE-5059
> URL: https://issues.apache.org/jira/browse/IGNITE-5059
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Vladisav Jelisavcic
>Assignee: Vladisav Jelisavcic
>  Labels: important
>
> Implement logistic regression using ignite ml.math. Model should be able to 
> incorporate L1 and L2 regularization. 
> Model should also work with stochastic gradient descent (SGD) as well as 
> batch and mini-batch gradient descent optimization algorithms.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5059) Implement logistic regression

[Vladisav Jelisavcic (JIRA)]

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

Vladisav Jelisavcic commented on IGNITE-5059:
-

Hi Oleg, I recently started working on this, so I would prefer to finish it 
myself. Thanks!

> Implement logistic regression 
> --
>
> Key: IGNITE-5059
> URL: https://issues.apache.org/jira/browse/IGNITE-5059
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Vladisav Jelisavcic
>Assignee: Vladisav Jelisavcic
>  Labels: important
>
> Implement logistic regression using ignite ml.math. Model should be able to 
> incorporate L1 and L2 regularization. 
> Model should also work with stochastic gradient descent (SGD) as well as 
> batch and mini-batch gradient descent optimization algorithms.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5059) Implement logistic regression

[Oleg Ignatenko (JIRA)]

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

Oleg Ignatenko commented on IGNITE-5059:


Hi [~vladisav], this ticket appears dormant for over 5 months now and I would 
like to assign it to myself and try implementing this feature. If you would 
prefer to keep it for yourself, please let me know.

The reason why I picked it among other ML tickets that are currently opened is 
I checked current feature set in Ignite ML Grid and this one looks like quite a 
desired feature because it would nicely complement linear regression that was 
integrated per IGNITE-5012.

I plan to start working on this in a day or two from now, after I complete 
IGNITE-5535.

> Implement logistic regression 
> --
>
> Key: IGNITE-5059
> URL: https://issues.apache.org/jira/browse/IGNITE-5059
> Project: Ignite
>  Issue Type: New Feature
>  Components: ml
>Reporter: Vladisav Jelisavcic
>Assignee: Vladisav Jelisavcic
>  Labels: important
>
> Implement logistic regression using ignite ml.math. Model should be able to 
> incorporate L1 and L2 regularization. 
> Model should also work with stochastic gradient descent (SGD) as well as 
> batch and mini-batch gradient descent optimization algorithms.  



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6569) DROP table is frozen in special case

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6569:


GitHub user alexpaschenko opened a pull request:

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

IGNITE-6569 Exception on DROP TABLE via cache API of cache being dropped



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

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

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

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


commit c3c78b630aa556e95f0dd4ab3c6ed9067cc49ed9
Author: Alexander Paschenko 
Date:   2017-10-09T12:03:20Z

IGNITE-6569 Exception on DROP TABLE via cache API of cache being dropped




> DROP table is frozen in special case
> 
>
> Key: IGNITE-6569
> URL: https://issues.apache.org/jira/browse/IGNITE-6569
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Alexander Paschenko
> Fix For: 2.3
>
> Attachments: DropTableExample2-project.tar.gz
>
>
> In attached project file:
> # Run node with using of DropFrozenTableStartup class.
> Execution is frozen in time of DROP table process.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-6583) Methods of rebalancing progress metrics must obey JavaBean naming conventions

[Andrey Gura (JIRA)]

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

Andrey Gura resolved IGNITE-6583.
-
Resolution: Fixed

Merged to master branch.

> Methods of rebalancing progress metrics must obey JavaBean naming conventions
> -
>
> Key: IGNITE-6583
> URL: https://issues.apache.org/jira/browse/IGNITE-6583
> Project: Ignite
>  Issue Type: Bug
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
> Fix For: 2.4
>
>
> h2. Notes
> Getters for *rebalancingStartTime* and *estimateRebalancingFinishTime* 
> metrics from *CacheMetrics* interface don't follow JavaBean naming 
> conventions; method names don't start with *get* prefix.
> As a result metrics cannot be accessed via MXBean interface.
> h2. Acceptance Criteria
> # Methods *getRebalancingStartTime* and *getEstimateRebalancingFinishTime* 
> are introduced to *CacheMetrics* interface.
> # Existing methods *rebalancingStartTime* and *estimateRebalancingFinishTime* 
> are declared as deprecated and will be deleted in future major release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6024) SQL: execute DML statements on the server when possible

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-6024:
--

[~vozerov], the patch for JDBC drivers are available.
[JDBC 
test|https://ci.ignite.apache.org/project.html?projectId=Ignite20Tests=projectOverview_Ignite20Tests=pull%2F2488%2Fhead]

> SQL: execute DML statements on the server when possible
> ---
>
> Key: IGNITE-6024
> URL: https://issues.apache.org/jira/browse/IGNITE-6024
> Project: Ignite
>  Issue Type: Task
>  Components: sql
>Affects Versions: 2.1
>Reporter: Vladimir Ozerov
>Assignee: Sergey Kalashnikov
>  Labels: important, performance
> Fix For: 2.3
>
>
> Currently we execute DML statements as follows:
> 1) Get query result set to the client
> 2) Construct entry processors and send them to servers in batches
> This approach is inefficient as it causes a lot of unnecessary network 
> communication  Instead, we should execute DML statements directly on server 
> nodes when it is possible.
> Implementation considerations:
> 1) Determine set of queries which could be processed in this way. E.g., 
> {{LIMIT/OFFSET}}, {{GROUP BY}}, {{ORDER BY}}, {{DISTINCT}}, etc. are out of 
> question - they must go through the client anyway. Probably 
> {{skipMergeTable}} flag is a good starting point (good, not precise!)
> 2) Send request to every server and execute local DML right there
> 3) No failover support at the moment - throw "partial update" exception if 
> topology is unstable
> 4) Handle partition reservation carefully
> 5) Transactions: we still have single coordinator - this is a client. When 
> MVCC and TX SQL is ready, client will assign proper counters to server 
> requests.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-6305) Need to add update checker to Ignite

[Andrey Gura (JIRA)]

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

Andrey Gura edited comment on IGNITE-6305 at 10/9/17 3:14 PM:
--

Merged to master and ignite-2.3 branches.


was (Author: agura):
Merged to master branch.

> Need to add update checker to Ignite
> 
>
> Key: IGNITE-6305
> URL: https://issues.apache.org/jira/browse/IGNITE-6305
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Dmitriy Setrakyan
>Assignee: Andrey Gura
>Priority: Critical
>  Labels: important
> Fix For: 2.3
>
>
> # Ignite should provide an update check on node startup, which will report to 
> users if there is a new version available. 
> # We can also use the update-checker to count Ignite starts, which will allow 
> the community to monitor the health of the project.
> The design is specified in this dev@ thread (make sure to read all the way to 
> the end):
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-Update-Checker-td21150.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6305) Need to add update checker to Ignite

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov commented on IGNITE-6305:
-

[~agura], look good to me.

> Need to add update checker to Ignite
> 
>
> Key: IGNITE-6305
> URL: https://issues.apache.org/jira/browse/IGNITE-6305
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Dmitriy Setrakyan
>Assignee: Andrey Gura
>Priority: Critical
>  Labels: important
> Fix For: 2.3
>
>
> # Ignite should provide an update check on node startup, which will report to 
> users if there is a new version available. 
> # We can also use the update-checker to count Ignite starts, which will allow 
> the community to monitor the health of the project.
> The design is specified in this dev@ thread (make sure to read all the way to 
> the end):
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-Update-Checker-td21150.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6397) .NET: Thin client: basic cache operations

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6397:


Github user asfgit closed the pull request at:

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


> .NET: Thin client: basic cache operations
> -
>
> Key: IGNITE-6397
> URL: https://issues.apache.org/jira/browse/IGNITE-6397
> Project: Ignite
>  Issue Type: Bug
>  Components: clients, platforms
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.3
>
>
> We need to implement base cache operations, such as "remove", "replace", 
> "putIfAbsent". 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6584) .NET: Propagate new cache metrics

[Pavel Tupitsyn (JIRA)]

Pavel Tupitsyn created IGNITE-6584:
--

 Summary: .NET: Propagate new cache metrics
 Key: IGNITE-6584
 URL: https://issues.apache.org/jira/browse/IGNITE-6584
 Project: Ignite
  Issue Type: Improvement
  Components: platforms
Reporter: Pavel Tupitsyn
Priority: Trivial


Some properties are missing in {{ICacheMetrics}} that exist in {{CacheMetrics}} 
on Java side, such as rebalancing-related stuff (see IGNITE-6583). Add them.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6305) Need to add update checker to Ignite

[Andrey Gura (JIRA)]

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

Andrey Gura commented on IGNITE-6305:
-

Thanks for comments. PR is updated with fixes.

> Need to add update checker to Ignite
> 
>
> Key: IGNITE-6305
> URL: https://issues.apache.org/jira/browse/IGNITE-6305
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Dmitriy Setrakyan
>Assignee: Andrey Gura
>Priority: Critical
>  Labels: important
> Fix For: 2.3
>
>
> # Ignite should provide an update check on node startup, which will report to 
> users if there is a new version available. 
> # We can also use the update-checker to count Ignite starts, which will allow 
> the community to monitor the health of the project.
> The design is specified in this dev@ thread (make sure to read all the way to 
> the end):
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-Update-Checker-td21150.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6580) Cluster can fail during concurrent re-balancing and cache destruction

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov reassigned IGNITE-6580:
-

Assignee: Alexey Goncharuk

> Cluster can fail during concurrent re-balancing and cache destruction
> -
>
> Key: IGNITE-6580
> URL: https://issues.apache.org/jira/browse/IGNITE-6580
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.2
>Reporter: Mikhail Cherkasov
>Assignee: Alexey Goncharuk
> Fix For: 2.3
>
>
> The following exceptions can be abserved during concurrent re-balancing and 
> cache destruction:
> 1.
> {noformat}
> [00:01:27,135][ERROR][sys-#4375%null%][GridDhtPreloader] Partition eviction 
> failed, this can cause grid hang.
> org.apache.ignite.IgniteException: Runtime failure on search row: 
> Row@6be51c3d[ **REMOVED SENSITIVE INFORMATION** ]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doRemove(BPlusTree.java:1787)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.remove(BPlusTree.java:1578)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.remove(H2TreeIndex.java:226)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.doUpdate(GridH2Table.java:523)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:416)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.remove(IgniteH2Indexing.java:574)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:2172)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:451)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishRemove(IgniteCacheOffheapManagerImpl.java:1462)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1425)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:383)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3224)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.clearInternal(GridDhtCacheEntry.java:588)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.clearAll(GridDhtLocalPartition.java:951)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:809)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:593)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:580)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> [ignite-core-2.1.4.jar:2.1.4]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:1.8.0_131]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:1.8.0_131]
>   at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
> Caused by: java.lang.IllegalStateException: Item not found: 1
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.findIndirectItemIndex(DataPageIO.java:346)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.getDataOffset(DataPageIO.java:446)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> 

[jira] [Updated] (IGNITE-6580) Cluster can fail during concurrent re-balancing and cache destruction

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-6580:
--
Priority: Major  (was: Critical)

> Cluster can fail during concurrent re-balancing and cache destruction
> -
>
> Key: IGNITE-6580
> URL: https://issues.apache.org/jira/browse/IGNITE-6580
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.2
>Reporter: Mikhail Cherkasov
> Fix For: 2.3
>
>
> The following exceptions can be abserved during concurrent re-balancing and 
> cache destruction:
> 1.
> {noformat}
> [00:01:27,135][ERROR][sys-#4375%null%][GridDhtPreloader] Partition eviction 
> failed, this can cause grid hang.
> org.apache.ignite.IgniteException: Runtime failure on search row: 
> Row@6be51c3d[ **REMOVED SENSITIVE INFORMATION** ]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doRemove(BPlusTree.java:1787)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.remove(BPlusTree.java:1578)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.remove(H2TreeIndex.java:226)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.doUpdate(GridH2Table.java:523)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:416)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.remove(IgniteH2Indexing.java:574)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:2172)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:451)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishRemove(IgniteCacheOffheapManagerImpl.java:1462)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1425)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:383)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3224)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.clearInternal(GridDhtCacheEntry.java:588)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.clearAll(GridDhtLocalPartition.java:951)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:809)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:593)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:580)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> [ignite-core-2.1.4.jar:2.1.4]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:1.8.0_131]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:1.8.0_131]
>   at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
> Caused by: java.lang.IllegalStateException: Item not found: 1
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.findIndirectItemIndex(DataPageIO.java:346)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.getDataOffset(DataPageIO.java:446)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.readPayload(DataPageIO.java:488)
>  

[jira] [Updated] (IGNITE-6580) Cluster can fail during concurrent re-balancing and cache destruction

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-6580:
--
Fix Version/s: 2.3

> Cluster can fail during concurrent re-balancing and cache destruction
> -
>
> Key: IGNITE-6580
> URL: https://issues.apache.org/jira/browse/IGNITE-6580
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.2
>Reporter: Mikhail Cherkasov
> Fix For: 2.3
>
>
> The following exceptions can be abserved during concurrent re-balancing and 
> cache destruction:
> 1.
> {noformat}
> [00:01:27,135][ERROR][sys-#4375%null%][GridDhtPreloader] Partition eviction 
> failed, this can cause grid hang.
> org.apache.ignite.IgniteException: Runtime failure on search row: 
> Row@6be51c3d[ **REMOVED SENSITIVE INFORMATION** ]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doRemove(BPlusTree.java:1787)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.remove(BPlusTree.java:1578)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.remove(H2TreeIndex.java:226)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.doUpdate(GridH2Table.java:523)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:416)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.remove(IgniteH2Indexing.java:574)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:2172)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:451)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishRemove(IgniteCacheOffheapManagerImpl.java:1462)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1425)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:383)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3224)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.clearInternal(GridDhtCacheEntry.java:588)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.clearAll(GridDhtLocalPartition.java:951)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:809)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:593)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:580)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> [ignite-core-2.1.4.jar:2.1.4]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:1.8.0_131]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:1.8.0_131]
>   at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
> Caused by: java.lang.IllegalStateException: Item not found: 1
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.findIndirectItemIndex(DataPageIO.java:346)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.getDataOffset(DataPageIO.java:446)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.readPayload(DataPageIO.java:488)
>  

[jira] [Updated] (IGNITE-6580) Cluster can fail during concurrent re-balancing and cache destruction

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-6580:
--
Affects Version/s: 2.2

> Cluster can fail during concurrent re-balancing and cache destruction
> -
>
> Key: IGNITE-6580
> URL: https://issues.apache.org/jira/browse/IGNITE-6580
> Project: Ignite
>  Issue Type: Bug
>  Components: cache
>Affects Versions: 2.2
>Reporter: Mikhail Cherkasov
> Fix For: 2.3
>
>
> The following exceptions can be abserved during concurrent re-balancing and 
> cache destruction:
> 1.
> {noformat}
> [00:01:27,135][ERROR][sys-#4375%null%][GridDhtPreloader] Partition eviction 
> failed, this can cause grid hang.
> org.apache.ignite.IgniteException: Runtime failure on search row: 
> Row@6be51c3d[ **REMOVED SENSITIVE INFORMATION** ]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doRemove(BPlusTree.java:1787)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.remove(BPlusTree.java:1578)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.remove(H2TreeIndex.java:226)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.doUpdate(GridH2Table.java:523)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:416)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.remove(IgniteH2Indexing.java:574)
>  ~[ignite-indexing-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:2172)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:451)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishRemove(IgniteCacheOffheapManagerImpl.java:1462)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1425)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:383)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3224)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.clearInternal(GridDhtCacheEntry.java:588)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.clearAll(GridDhtLocalPartition.java:951)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:809)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:593)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:580)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
>  [ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
> [ignite-core-2.1.4.jar:2.1.4]
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  [?:1.8.0_131]
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  [?:1.8.0_131]
>   at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
> Caused by: java.lang.IllegalStateException: Item not found: 1
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.findIndirectItemIndex(DataPageIO.java:346)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.getDataOffset(DataPageIO.java:446)
>  ~[ignite-core-2.1.4.jar:2.1.4]
>   at 
> org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.readPayload(DataPageIO.java:488)
>  

[jira] [Commented] (IGNITE-6483) Entries count in caches' MX Beans not immediately available

[Ilya Kasnacheev (JIRA)]

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

Ilya Kasnacheev commented on IGNITE-6483:
-

[~ntikho...@apache.org] awesome, thanks!

> Entries count in caches' MX Beans not immediately available
> ---
>
> Key: IGNITE-6483
> URL: https://issues.apache.org/jira/browse/IGNITE-6483
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
> Attachments: IgniteCacheMxBeansTest.java
>
>
> When querying properties like
> {code}
> cache.mxBean().getOffHeapPrimaryEntriesCount()
> {code}
> The value is often 0 (zero) initially, even if cache is not empty and located 
> in offheap.
> Local MX Bean returns correct value.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6483) Entries count in caches' MX Beans not immediately available

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6483:


Github user asfgit closed the pull request at:

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


> Entries count in caches' MX Beans not immediately available
> ---
>
> Key: IGNITE-6483
> URL: https://issues.apache.org/jira/browse/IGNITE-6483
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
> Attachments: IgniteCacheMxBeansTest.java
>
>
> When querying properties like
> {code}
> cache.mxBean().getOffHeapPrimaryEntriesCount()
> {code}
> The value is often 0 (zero) initially, even if cache is not empty and located 
> in offheap.
> Local MX Bean returns correct value.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6583) Methods of rebalancing progress metrics must obey JavaBean naming conventions

[Sergey Chugunov (JIRA)]

Sergey Chugunov created IGNITE-6583:
---

 Summary: Methods of rebalancing progress metrics must obey 
JavaBean naming conventions
 Key: IGNITE-6583
 URL: https://issues.apache.org/jira/browse/IGNITE-6583
 Project: Ignite
  Issue Type: Bug
Reporter: Sergey Chugunov
Assignee: Sergey Chugunov
 Fix For: 2.4


h2. Notes
Getters for *rebalancingStartTime* and *estimateRebalancingFinishTime* metrics 
from *CacheMetrics* interface don't follow JavaBean naming conventions; method 
names don't start with *get* prefix.

As a result metrics cannot be accessed via MXBean interface.

h2. Acceptance Criteria
# Methods *getRebalancingStartTime* and *getEstimateRebalancingFinishTime* are 
introduced to *CacheMetrics* interface.
# Existing methods *rebalancingStartTime* and *estimateRebalancingFinishTime* 
are declared as deprecated and will be deleted in future major release.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6582) JDBC thin: supports 'updatedOnServer' connection flag

[Taras Ledkov (JIRA)]

Taras Ledkov created IGNITE-6582:


 Summary: JDBC thin: supports 'updatedOnServer' connection flag
 Key: IGNITE-6582
 URL: https://issues.apache.org/jira/browse/IGNITE-6582
 Project: Ignite
  Issue Type: Bug
  Components: jdbc
Affects Versions: 2.3
Reporter: Taras Ledkov
Assignee: Taras Ledkov
 Fix For: 2.3


JDBC must support  'updateOnServer' connection flag. See more: IGNITE-6024



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6581) clent deadlock in spiStart

[Konstantin Dudkov (JIRA)]

Konstantin Dudkov created IGNITE-6581:
-

 Summary: clent deadlock in spiStart
 Key: IGNITE-6581
 URL: https://issues.apache.org/jira/browse/IGNITE-6581
 Project: Ignite
  Issue Type: Bug
Affects Versions: 1.9
Reporter: Konstantin Dudkov
Assignee: Konstantin Dudkov



{code:java}
"tcp-client-disco-msg-worker-#4%soloots-tg-ManagementFabric%" #50 prio=5 
os_prio=0 tid=0x7fafecd50800 nid=0x469e sleeping[0x7fafc3bfa000]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at 
org.apache.ignite.internal.util.GridSpinReadWriteLock.tryWriteLock(GridSpinReadWriteLock.java:349)
at 
org.apache.ignite.internal.GridKernalGatewayImpl.writeLock(GridKernalGatewayImpl.java:121)
at 
org.apache.ignite.internal.IgniteKernal.onDisconnected(IgniteKernal.java:3427)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:601)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2400)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.notifyDiscovery(ClientImpl.java:2379)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1707)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)

"main" #1 prio=5 os_prio=0 tid=0x7fafec01 nid=0x4644 waiting on 
condition [0x7faff325]
   java.lang.Thread.State: WAITING (parking)
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <0x00068a331ad0> (a 
java.util.concurrent.CountDownLatch$Sync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:836)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(AbstractQueuedSynchronizer.java:997)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(AbstractQueuedSynchronizer.java:1304)
at java.util.concurrent.CountDownLatch.await(CountDownLatch.java:231)
at 
org.apache.ignite.spi.discovery.tcp.ClientImpl.spiStart(ClientImpl.java:265)
at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:1862)
at 
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:268)
at 
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:690)
at 
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1682)
at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:940)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1814)
at 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1605)
- locked <0x0004107210e8> (a 
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance)
at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1042)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:569)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:516)
at org.apache.ignite.Ignition.start(Ignition.java:322)
at 
com.workday.fabric.ignite.IgniteFabric.lambda$start$1(IgniteFabric.java:143)
at 
com.workday.fabric.ignite.IgniteFabric$$Lambda$6/576020159.run(Unknown Source)
at 
com.workday.fabric.util.InvocationInterceptor.invokeRunnable(InvocationInterceptor.java:119)
at com.workday.fabric.ignite.IgniteFabric.start(IgniteFabric.java:138)
- locked <0x0004107212e0> (a 
com.workday.fabric.ignite.IgniteWorkdayFabric)
at com.workday.fabric.FabricManager.ensureFabric(FabricManager.java:146)
- locked <0x000410721368> (a java.util.concurrent.ConcurrentHashMap)
at 
com.workday.fabric.WorkdayFabricManager.ensureFabric(WorkdayFabricManager.java:76)
at 
com.workday.fabric.verifier.FabricVerifier.verify(FabricVerifier.java:347)
at 
com.workday.fabric.verifier.FabricVerifier.main(FabricVerifier.java:276)
{code}




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Comment Edited] (IGNITE-6397) .NET: Thin client: basic cache operations

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn edited comment on IGNITE-6397 at 10/9/17 12:43 PM:
--

[~vozerov]

3) Changed to {{LinkedHashSet}}. {{List}} is not an option, all the related 
APIs (e.g. {{GetAll}}) require {{Set}}.
Everything else fixed.


was (Author: ptupitsyn):
3) Changed to {{LinkedHashSet}}. {{List}} is not an option, all the related 
APIs (e.g. {{GetAll}}) require {{Set}}.
Everything else fixed.

> .NET: Thin client: basic cache operations
> -
>
> Key: IGNITE-6397
> URL: https://issues.apache.org/jira/browse/IGNITE-6397
> Project: Ignite
>  Issue Type: Bug
>  Components: clients, platforms
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.3
>
>
> We need to implement base cache operations, such as "remove", "replace", 
> "putIfAbsent". 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6259) GridServiceProcessor may leave futures hanging on unstable topology

[Evgenii Zhuravlev (JIRA)]

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

Evgenii Zhuravlev reassigned IGNITE-6259:
-

Assignee: Evgenii Zhuravlev

> GridServiceProcessor may leave futures hanging on unstable topology
> ---
>
> Key: IGNITE-6259
> URL: https://issues.apache.org/jira/browse/IGNITE-6259
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7, 1.8, 1.9, 2.0, 2.1
>Reporter: Denis Mekhanikov
>Assignee: Evgenii Zhuravlev
>
> GridServiceProcessor subscribes to updates on the internal cache to get 
> information about new deployments or cancellations of services. Some of such 
> updates may be lost under conditions of unstable topology. It leads to 
> services not being deployed and client futures infinitely hanging.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6397) .NET: Thin client: basic cache operations

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6397:


3) Changed to {{LinkedHashSet}}. {{List}} is not an option, all the related 
APIs (e.g. {{GetAll}}) require {{Set}}.
Everything else fixed.

> .NET: Thin client: basic cache operations
> -
>
> Key: IGNITE-6397
> URL: https://issues.apache.org/jira/browse/IGNITE-6397
> Project: Ignite
>  Issue Type: Bug
>  Components: clients, platforms
>Reporter: Vladimir Ozerov
>Assignee: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.3
>
>
> We need to implement base cache operations, such as "remove", "replace", 
> "putIfAbsent". 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6568) Failed to DROP table created by DDL query after restart

[Alexander Paschenko (JIRA)]

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

Alexander Paschenko commented on IGNITE-6568:
-

Tests are fine, [~agoncharuk] could you please have a look at the code?

> Failed to DROP table created by DDL query after restart
> ---
>
> Key: IGNITE-6568
> URL: https://issues.apache.org/jira/browse/IGNITE-6568
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.1
>Reporter: Vasiliy Sisko
>Assignee: Alexander Paschenko
> Fix For: 2.3
>
> Attachments: DropTableExample-project.tar.gz
>
>
> In attached project:
> # Run node by using of CreateTableStartup class.
> # Stop node.
> # Run node by using of DropTableStartup class.
> On try to stop cache showed next exception:
> {code}
> Exception in thread "main" class 
> org.apache.ignite.internal.processors.query.IgniteSQLException: Unexpected 
> DLL operation failure: class org.apache.ignite.IgniteCheckedException: Only 
> cache created with CREATE TABLE may be removed with DROP TABLE 
> [cacheName=SQL_PUBLIC_CITY]
>   at 
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:280)
>   at 
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.queryDistributedSqlFields(IgniteH2Indexing.java:1385)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1923)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor$6.applyx(GridQueryProcessor.java:1919)
>   at 
> org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2401)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFieldsNoCache(GridQueryProcessor.java:1927)
>   at startup.DropTableStartup.main(DropTableStartup.java:21)
> Caused by: javax.cache.CacheException: class 
> org.apache.ignite.IgniteCheckedException: Only cache created with CREATE 
> TABLE may be removed with DROP TABLE [cacheName=SQL_PUBLIC_CITY]
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheUtils.convertToCacheException(GridCacheUtils.java:1327)
>   at 
> org.apache.ignite.internal.IgniteKernal.destroyCache0(IgniteKernal.java:3118)
>   at 
> org.apache.ignite.internal.processors.query.GridQueryProcessor.dynamicTableDrop(GridQueryProcessor.java:1436)
>   at 
> org.apache.ignite.internal.processors.query.h2.ddl.DdlStatementsProcessor.runDdlStatement(DdlStatementsProcessor.java:212)
>   ... 7 more
> Caused by: class org.apache.ignite.IgniteCheckedException: Only cache created 
> with CREATE TABLE may be removed with DROP TABLE [cacheName=SQL_PUBLIC_CITY]
>   at 
> org.apache.ignite.internal.processors.cache.ClusterCachesInfo.processCacheChangeRequests(ClusterCachesInfo.java:628)
>   at 
> org.apache.ignite.internal.processors.cache.ClusterCachesInfo.onCacheChangeRequested(ClusterCachesInfo.java:392)
>   at 
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.onCustomEvent(GridCacheProcessor.java:2927)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:664)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery(GridDiscoveryManager.java:564)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.notifyDiscoveryListener(ServerImpl.java:5461)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processCustomMessage(ServerImpl.java:5280)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2654)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2445)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6639)
>   at 
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2531)
>   at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4591) File interop_target.h is missing from source-release

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4591:

Fix Version/s: (was: 2.2)
   1.9

> File interop_target.h is missing from source-release
> 
>
> Key: IGNITE-4591
> URL: https://issues.apache.org/jira/browse/IGNITE-4591
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Ilya Suntsov
>  Labels: cpp
> Fix For: 1.9
>
>
> File 
> {{modules\platforms\cpp\core\include\ignite\impl\interop\interop_target.h}} 
> missing from source releases of versions 1.7.0 and 1.8.0. It is present, 
> however, in repository and binary releases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-4591) File interop_target.h is missing from source-release

[Igor Sapego (JIRA)]

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

Igor Sapego updated IGNITE-4591:

Fix Version/s: (was: 2.3)
   2.2

> File interop_target.h is missing from source-release
> 
>
> Key: IGNITE-4591
> URL: https://issues.apache.org/jira/browse/IGNITE-4591
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.7
>Reporter: Igor Sapego
>Assignee: Ilya Suntsov
>  Labels: cpp
> Fix For: 2.2
>
>
> File 
> {{modules\platforms\cpp\core\include\ignite\impl\interop\interop_target.h}} 
> missing from source releases of versions 1.7.0 and 1.8.0. It is present, 
> however, in repository and binary releases.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6580) Cluster can fail during concurrent re-balancing and cache destruction

[Mikhail Cherkasov (JIRA)]

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

Mikhail Cherkasov updated IGNITE-6580:
--
Description: 
The following exceptions can be abserved during concurrent re-balancing and 
cache destruction:
1.
{noformat}

[00:01:27,135][ERROR][sys-#4375%null%][GridDhtPreloader] Partition eviction 
failed, this can cause grid hang.
org.apache.ignite.IgniteException: Runtime failure on search row: Row@6be51c3d[ 
**REMOVED SENSITIVE INFORMATION** ]
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doRemove(BPlusTree.java:1787)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.remove(BPlusTree.java:1578)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.remove(H2TreeIndex.java:226)
 ~[ignite-indexing-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.doUpdate(GridH2Table.java:523)
 ~[ignite-indexing-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:416)
 ~[ignite-indexing-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.remove(IgniteH2Indexing.java:574)
 ~[ignite-indexing-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:2172)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:451)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishRemove(IgniteCacheOffheapManagerImpl.java:1462)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1425)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:383)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3224)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.clearInternal(GridDhtCacheEntry.java:588)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.clearAll(GridDhtLocalPartition.java:951)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:809)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:593)
 [ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:580)
 [ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629)
 [ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
 [ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
[ignite-core-2.1.4.jar:2.1.4]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[?:1.8.0_131]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[?:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
Caused by: java.lang.IllegalStateException: Item not found: 1
at 
org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.findIndirectItemIndex(DataPageIO.java:346)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.getDataOffset(DataPageIO.java:446)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.readPayload(DataPageIO.java:488)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:149)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:101)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.query.h2.database.H2RowFactory.getRow(H2RowFactory.java:62)
 ~[ignite-indexing-2.1.4.jar:2.1.4]
at 

[jira] [Created] (IGNITE-6580) Cluster can fail during concurrent re-balancing and cache destruction

[Mikhail Cherkasov (JIRA)]

Mikhail Cherkasov created IGNITE-6580:
-

 Summary: Cluster can fail during concurrent re-balancing and cache 
destruction
 Key: IGNITE-6580
 URL: https://issues.apache.org/jira/browse/IGNITE-6580
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Mikhail Cherkasov
Priority: Critical


The following exceptions can be abserved during concurrent re-balancing and 
cache destruction:
1.
{noformat}

[00:01:27,135][ERROR][sys-#4375%null%][GridDhtPreloader] Partition eviction 
failed, this can cause grid hang.
org.apache.ignite.IgniteException: Runtime failure on search row: Row@6be51c3d[ 
**REMOVED SENSITIVE INFORMATION** ]
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.doRemove(BPlusTree.java:1787)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.persistence.tree.BPlusTree.remove(BPlusTree.java:1578)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.query.h2.database.H2TreeIndex.remove(H2TreeIndex.java:226)
 ~[ignite-indexing-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.doUpdate(GridH2Table.java:523)
 ~[ignite-indexing-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.update(GridH2Table.java:416)
 ~[ignite-indexing-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.remove(IgniteH2Indexing.java:574)
 ~[ignite-indexing-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.remove(GridQueryProcessor.java:2172)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.query.GridCacheQueryManager.remove(GridCacheQueryManager.java:451)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.finishRemove(IgniteCacheOffheapManagerImpl.java:1462)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl$CacheDataStoreImpl.remove(IgniteCacheOffheapManagerImpl.java:1425)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.IgniteCacheOffheapManagerImpl.remove(IgniteCacheOffheapManagerImpl.java:383)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.GridCacheMapEntry.removeValue(GridCacheMapEntry.java:3224)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtCacheEntry.clearInternal(GridDhtCacheEntry.java:588)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.clearAll(GridDhtLocalPartition.java:951)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.tryEvict(GridDhtLocalPartition.java:809)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:593)
 [ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPreloader$3.call(GridDhtPreloader.java:580)
 [ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6629)
 [ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.closure.GridClosureProcessor$2.body(GridClosureProcessor.java:967)
 [ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
[ignite-core-2.1.4.jar:2.1.4]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[?:1.8.0_131]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[?:1.8.0_131]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_131]
Caused by: java.lang.IllegalStateException: Item not found: 1
at 
org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.findIndirectItemIndex(DataPageIO.java:346)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.getDataOffset(DataPageIO.java:446)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.persistence.tree.io.DataPageIO.readPayload(DataPageIO.java:488)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:149)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 
org.apache.ignite.internal.processors.cache.persistence.CacheDataRowAdapter.initFromLink(CacheDataRowAdapter.java:101)
 ~[ignite-core-2.1.4.jar:2.1.4]
at 

[jira] [Resolved] (IGNITE-5418) CPP: Add BINARY SQL type support for SQL queries

[Igor Sapego (JIRA)]

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

Igor Sapego resolved IGNITE-5418.
-
   Resolution: Fixed
Fix Version/s: 2.3

Duplicate of the IGNITE-5621

> CPP: Add BINARY SQL type support for SQL queries
> 
>
> Key: IGNITE-5418
> URL: https://issues.apache.org/jira/browse/IGNITE-5418
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.0
>Reporter: Igor Sapego
>  Labels: cpp
> Fix For: 2.3
>
>
> There are currently no way to add to query argument of type {{BINARY}} (byte 
> array) or read field of this type using C++ API. Consider adding support for 
> this using {{vector}} or some specific API calls.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (IGNITE-6561) Include sqlline in Apache Ignite

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov updated IGNITE-6561:

Fix Version/s: (was: 2.3)

> Include sqlline in Apache Ignite
> 
>
> Key: IGNITE-6561
> URL: https://issues.apache.org/jira/browse/IGNITE-6561
> Project: Ignite
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 2.3
>Reporter: Ilya Suntsov
>Assignee: Oleg Ostanin
>
> I guess we need to include [sqlline|https://github.com/julianhyde/sqlline] in 
> our project.
> Here is overview of internal sqlline commands:
> https://cwiki.apache.org/confluence/display/IGNITE/Overview+sqlline+tool



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6561) Include sqlline in Apache Ignite

[Oleg Ostanin (JIRA)]

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

Oleg Ostanin reassigned IGNITE-6561:


Assignee: Oleg Ostanin

> Include sqlline in Apache Ignite
> 
>
> Key: IGNITE-6561
> URL: https://issues.apache.org/jira/browse/IGNITE-6561
> Project: Ignite
>  Issue Type: Improvement
>  Components: build
>Affects Versions: 2.3
>Reporter: Ilya Suntsov
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> I guess we need to include [sqlline|https://github.com/julianhyde/sqlline] in 
> our project.
> Here is overview of internal sqlline commands:
> https://cwiki.apache.org/confluence/display/IGNITE/Overview+sqlline+tool



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5097) BinaryMarshaller should write ints in "varint" encoding where it makes sense

[Vyacheslav Daradur (JIRA)]

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

Vyacheslav Daradur commented on IGNITE-5097:


Hi, [~vozerov], [~isapego], could you please review Java part changes and port 
the changes to the C++ platform?

> BinaryMarshaller should write ints in "varint" encoding where it makes sense
> 
>
> Key: IGNITE-5097
> URL: https://issues.apache.org/jira/browse/IGNITE-5097
> Project: Ignite
>  Issue Type: Task
>  Components: binary
>Affects Versions: 2.0
>Reporter: Vladimir Ozerov
>Assignee: Vyacheslav Daradur
>  Labels: iep-2, performance
> Fix For: 2.4
>
>
> There are a lot of places in the code where we write integers for some 
> special purposes. Quite often their value will be vary small, so that 
> applying "varint" format could save a lot of space at the cost of very low 
> additional CPU overhead. 
> Specifically:
> 1) Array/collection/map lengths
> 2) BigDecimal's (usually will save ~6 bytes)
> 3) Strings
> 4) Enum ordinals



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Reopened] (IGNITE-5733) Activate/deactivate cluster through http-rest api

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reopened IGNITE-5733:
-

Two tests start to fail after patch was merged:
{{JettyRestProcessorSignedSelfTest.testVisorGateway}}
{{JettyRestProcessorUnsignedSelfTest.testVisorGateway}}

> Activate/deactivate cluster through http-rest api
> -
>
> Key: IGNITE-5733
> URL: https://issues.apache.org/jira/browse/IGNITE-5733
> Project: Ignite
>  Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Alexander Belyak
>Assignee: Alexander Belyak
>Priority: Minor
> Fix For: 2.3
>
>
> Need to add command to get/set cluster active flag into http rest api.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5767) Web console: use byte array type instead of java.lang.Object for binary JDBC types

[Alexey Kuznetsov (JIRA)]

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

Alexey Kuznetsov reassigned IGNITE-5767:


Resolution: Fixed
  Assignee: Pavel Konstantinov  (was: Alexey Kuznetsov)

Looks good.
Merged to master.

> Web console: use byte array type instead of java.lang.Object for binary JDBC 
> types
> --
>
> Key: IGNITE-5767
> URL: https://issues.apache.org/jira/browse/IGNITE-5767
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Denis Kholodov
>Assignee: Pavel Konstantinov
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> Schema importer should use {{[B}} query entity field type instead of 
> {{java.lang.Object}} for the following SQL types: {{BINARY}}, {{VARBINARY}} 
> and {{LONGVARBINARY}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6515) .NET: Enable persistence on per-cache basis

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6515:


Moved metrics to root namespace, everything else to {{Configuration}} namespace.

> .NET: Enable persistence on per-cache basis
> ---
>
> Key: IGNITE-6515
> URL: https://issues.apache.org/jira/browse/IGNITE-6515
> Project: Ignite
>  Issue Type: Improvement
>  Components: platforms
>Affects Versions: 2.3
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>  Labels: .NET, important
> Fix For: 2.3
>
>
> Propagate new configuration to .NET: IGNITE-6030



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6234) [Test failure] GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6234:


GitHub user mcherkasov opened a pull request:

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

IGNITE-6234 Initialize schemaIds to empty set if schemas field is null 
during the deserialization



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

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

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

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


commit 55fe403e9d2fb73cbbf0c89f5cedbe2eb5b8839b
Author: mcherkasov 
Date:   2017-10-09T10:44:06Z

IGNITE-6234 Initialize schemaIds to empty set if schemas field is null 
during the deserialization




> [Test failure] 
> GridCacheClientModesTcpClientDiscoveryAbstractTest$CaseNearReplicatedTransactional.testGetFromClientNode
> ---
>
> Key: IGNITE-6234
> URL: https://issues.apache.org/jira/browse/IGNITE-6234
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Sergey Chugunov
>Assignee: Sergey Chugunov
>  Labels: MakeTeamcityGreenAgain
>
> Test reproducible locally although with a very low probability. 
> I wasn't able to reproduce it starting test in isolation but managed to do it 
> starting *GridCacheClientModesTcpClientDiscoveryAbstractTest* 50 times in a 
> row observing from 1 to 3 failures.
> Test run with failed test is available 
> [here|https://ci.ignite.apache.org/viewLog.html?buildId=798538=buildResultsDiv=Ignite20Tests_IgniteCache].
> It seems that when client requests value of custom class from near cache it 
> may see BinaryMetadata for this class with no schema.
> Test fails with the following exception:
> {noformat}
> java.lang.NullPointerException: null
> at 
> org.apache.ignite.internal.binary.BinaryMetadata.hasSchema(BinaryMetadata.java:189)
> at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl.metadata(CacheObjectBinaryProcessorImpl.java:517)
> at 
> org.apache.ignite.internal.processors.cache.binary.CacheObjectBinaryProcessorImpl$2.metadata(CacheObjectBinaryProcessorImpl.java:185)
> at 
> org.apache.ignite.internal.binary.BinaryContext.metadata(BinaryContext.java:1237)
> at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.getOrCreateSchema(BinaryReaderExImpl.java:2005)
> at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:284)
> at 
> org.apache.ignite.internal.binary.BinaryReaderExImpl.(BinaryReaderExImpl.java:183)
> at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.reader(BinaryObjectImpl.java:830)
> at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.deserializeValue(BinaryObjectImpl.java:794)
> at 
> org.apache.ignite.internal.binary.BinaryObjectImpl.value(BinaryObjectImpl.java:143)
> at 
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinary(CacheObjectUtils.java:161)
> at 
> org.apache.ignite.internal.processors.cache.CacheObjectUtils.unwrapBinaryIfNeeded(CacheObjectUtils.java:41)
> at 
> org.apache.ignite.internal.processors.cache.CacheObjectContext.unwrapBinaryIfNeeded(CacheObjectContext.java:125)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.unwrapBinaryIfNeeded(GridCacheContext.java:1734)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1889)
> at 
> org.apache.ignite.internal.processors.cache.GridCacheContext.addResult(GridCacheContext.java:1828)
> at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.loadEntries(GridNearGetFuture.java:752)
> at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.access$000(GridNearGetFuture.java:68)
> at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture$MiniFuture.onResult(GridNearGetFuture.java:1012)
> at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearGetFuture.onResult(GridNearGetFuture.java:215)
> at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearCacheAdapter.processGetResponse(GridNearCacheAdapter.java:294)
> at 
> org.apache.ignite.internal.processors.cache.distributed.near.GridNearTransactionalCache$1.apply(GridNearTransactionalCache.java:92)
> at 
> 

[jira] [Created] (IGNITE-6579) WAL history does not used when node returns to cluster again

[Vladislav Pyatkov (JIRA)]

Vladislav Pyatkov created IGNITE-6579:
-

 Summary: WAL history does not used when node returns to cluster 
again
 Key: IGNITE-6579
 URL: https://issues.apache.org/jira/browse/IGNITE-6579
 Project: Ignite
  Issue Type: Bug
  Components: persistence
Reporter: Vladislav Pyatkov


When I have set big enough value to "WAL history size" and stop node on 20 
minutes, I got the message from coordinator (order=1):

{noformat}
2017-10-06 15:46:33.429 [WARN 
][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl]
 Partition has been scheduled for rebalancing due to outdated update counter 
[nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7,
 cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2424, 
haveHistory=false]
2017-10-06 15:46:33.429 [WARN 
][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl]
 Partition has been scheduled for rebalancing due to outdated update counter 
[nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7,
 cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2427, 
haveHistory=false]
2017-10-06 15:46:33.429 [WARN 
][sys-#10740%DPL_GRID%DplGridNodeName%][o.a.i.i.p.c.d.d.GridDhtPartitionTopologyImpl]
 Partition has been scheduled for rebalancing due to outdated update counter 
[nodeId=e51a1db2-f49b-44a9-b122-adde4016d9e7,
 cacheOrGroupName=CACHEGROUP_PARTICLE_DServiceZone, partId=2426, 
haveHistory=false]
{noformat}

after start node again.
I think, history size should be enough, but I see it is not by logs 
(haveHistory=false).



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6542) SocketChannel may not be closed in createTcpClient()

[Semen Boikov (JIRA)]

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

Semen Boikov commented on IGNITE-6542:
--

Changes look ok for me.

Thanks

> SocketChannel may not be closed in createTcpClient()
> 
>
> Key: IGNITE-6542
> URL: https://issues.apache.org/jira/browse/IGNITE-6542
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.2
>Reporter: Ilya Kasnacheev
>Assignee: Ilya Kasnacheev
>
> There's no finally() on ch in TcpCommunicationSpi.createTcpClient()
> So there's a long block of code where resource consistency is hanging on a 
> hair. This can lead to file descriptor starvation as well.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Resolved] (IGNITE-6506) Cluster activation hangs if a node was stopped during persistent storage checkpoint

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk resolved IGNITE-6506.
--
Resolution: Cannot Reproduce

> Cluster activation hangs if a node was stopped during persistent storage 
> checkpoint
> ---
>
> Key: IGNITE-6506
> URL: https://issues.apache.org/jira/browse/IGNITE-6506
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.2
>Reporter: Joel Lang
>Assignee: Alexey Goncharuk
>Priority: Critical
>  Labels: important
> Fix For: 2.3
>
>
> I have a cluster with two nodes: A and B.
> On startup, node A and B wait for each other to be connected and then node A 
> will attempt to activate the cluster.
> While testing high availability we find that if a node is stopped during the 
> persistent store checkpoint, we cannot activate the cluster on startup 
> without deleting the persistent storage directory. Specifically in the case 
> where node A is stopped during checkpointing, upon the next startup it will 
> encounter several exceptions during activation and then hang without 
> completing activation.
> Here is the log.
> {noformat}
> 2017-09-26 12:11:24 [tcp-disco-msg-worker-#2%mbe%] INFO  
> o.a.i.i.p.c.GridClusterStateProcessor - Start state transition: true
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.ignite.internal.exchange.time - Started exchange init 
> [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], crd=true, evt=18, 
> node=TcpDiscoveryNode [id=62cf0ccb-e376-4b80-8d2d-98115c3a2990, 
> addrs=[10.5.17.19, 127.0.0.1], 
> sockAddrs=[shouvdevmbe02.petrolink.net/10.5.17.19:47510, /127.0.0.1:47510], 
> discPort=47510, order=1, intOrder=1, lastExchangeTime=1506445884063, 
> loc=true, ver=2.2.0#20170915-sha1:5747ce6b, isClient=false], 
> evtNode=TcpDiscoveryNode [id=62cf0ccb-e376-4b80-8d2d-98115c3a2990, 
> addrs=[10.5.17.19, 127.0.0.1], 
> sockAddrs=[shouvdevmbe02.petrolink.net/10.5.17.19:47510, /127.0.0.1:47510], 
> discPort=47510, order=1, intOrder=1, lastExchangeTime=1506445884063, 
> loc=true, ver=2.2.0#20170915-sha1:5747ce6b, isClient=false], 
> customEvt=ChangeGlobalStateMessage 
> [id=1d0cb2fbe51-7967bd11-40aa-40fe-b0a6-c43302cd4ee7, 
> reqId=f7155dea-fede-4340-b244-7a3b65f167a8, 
> initiatingNodeId=62cf0ccb-e376-4b80-8d2d-98115c3a2990, activate=true]]
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture - Start activation process 
> [nodeId=62cf0ccb-e376-4b80-8d2d-98115c3a2990, client=false, 
> topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1]]
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.f.FilePageStoreManager - Resolved page store work directory: 
> /opt/mbe1/ignite/db/mbe_MBE1
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.w.FileWriteAheadLogManager - Resolved write ahead log work 
> directory: /opt/mbe1/ignite/db/wal/mbe_MBE1
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.w.FileWriteAheadLogManager - Resolved write ahead log archive 
> directory: /opt/mbe1/ignite/db/wal/archive/mbe_MBE1
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] WARN  
> o.a.i.i.p.c.p.GridCacheDatabaseSharedManager - No user-defined default 
> MemoryPolicy found; system default of 1GB size will be used.
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.pagemem.PageMemoryImpl - Started page memory 
> [memoryAllocated=100.0 MiB, pages=48592, tableSize=2.9 MiB, 
> checkpointBuffer=819.4 MiB]
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.pagemem.PageMemoryImpl - Started page memory 
> [memoryAllocated=3.1 GiB, pages=1544064, tableSize=91.0 MiB, 
> checkpointBuffer=819.4 MiB]
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.GridCacheDatabaseSharedManager - Read checkpoint status: start 
> marker = 
> /opt/mbe1/ignite/db/mbe_MBE1/cp/1506444061104-38b80aaa-8c3d-4572-a42e-5b7a3b472505-START.bin,
>  end marker = 
> /opt/mbe1/ignite/db/mbe_MBE1/cp/1506442980839-ff65a0dc-3d83-436a-8329-7b3a31fe5ffc-END.bin
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.GridCacheDatabaseSharedManager - Checking memory state 
> [lastValidPos=FileWALPointer [idx=139, fileOffset=31406805, len=20731, 
> forceFlush=false], lastMarked=FileWALPointer [idx=0, fileOffset=0, len=0, 
> forceFlush=false], lastCheckpointId=38b80aaa-8c3d-4572-a42e-5b7a3b472505]
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] WARN  
> o.a.i.i.p.c.p.GridCacheDatabaseSharedManager - Ignite node stopped in the 
> middle of checkpoint. Will restore memory state and finish checkpoint on node 
> start.
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] ERROR 
> 

[jira] [Commented] (IGNITE-6506) Cluster activation hangs if a node was stopped during persistent storage checkpoint

[Alexey Goncharuk (JIRA)]

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

Alexey Goncharuk commented on IGNITE-6506:
--

I cannot reproduce this on the latest 2.3 nightly build. This most likely was 
fixed by https://issues.apache.org/jira/browse/IGNITE-6096. We need to retest 
this on 2.3 release and reopen the issue with a reproducer if it is still there.

> Cluster activation hangs if a node was stopped during persistent storage 
> checkpoint
> ---
>
> Key: IGNITE-6506
> URL: https://issues.apache.org/jira/browse/IGNITE-6506
> Project: Ignite
>  Issue Type: Bug
>  Components: persistence
>Affects Versions: 2.2
>Reporter: Joel Lang
>Assignee: Alexey Goncharuk
>Priority: Critical
>  Labels: important
> Fix For: 2.3
>
>
> I have a cluster with two nodes: A and B.
> On startup, node A and B wait for each other to be connected and then node A 
> will attempt to activate the cluster.
> While testing high availability we find that if a node is stopped during the 
> persistent store checkpoint, we cannot activate the cluster on startup 
> without deleting the persistent storage directory. Specifically in the case 
> where node A is stopped during checkpointing, upon the next startup it will 
> encounter several exceptions during activation and then hang without 
> completing activation.
> Here is the log.
> {noformat}
> 2017-09-26 12:11:24 [tcp-disco-msg-worker-#2%mbe%] INFO  
> o.a.i.i.p.c.GridClusterStateProcessor - Start state transition: true
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.ignite.internal.exchange.time - Started exchange init 
> [topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1], crd=true, evt=18, 
> node=TcpDiscoveryNode [id=62cf0ccb-e376-4b80-8d2d-98115c3a2990, 
> addrs=[10.5.17.19, 127.0.0.1], 
> sockAddrs=[shouvdevmbe02.petrolink.net/10.5.17.19:47510, /127.0.0.1:47510], 
> discPort=47510, order=1, intOrder=1, lastExchangeTime=1506445884063, 
> loc=true, ver=2.2.0#20170915-sha1:5747ce6b, isClient=false], 
> evtNode=TcpDiscoveryNode [id=62cf0ccb-e376-4b80-8d2d-98115c3a2990, 
> addrs=[10.5.17.19, 127.0.0.1], 
> sockAddrs=[shouvdevmbe02.petrolink.net/10.5.17.19:47510, /127.0.0.1:47510], 
> discPort=47510, order=1, intOrder=1, lastExchangeTime=1506445884063, 
> loc=true, ver=2.2.0#20170915-sha1:5747ce6b, isClient=false], 
> customEvt=ChangeGlobalStateMessage 
> [id=1d0cb2fbe51-7967bd11-40aa-40fe-b0a6-c43302cd4ee7, 
> reqId=f7155dea-fede-4340-b244-7a3b65f167a8, 
> initiatingNodeId=62cf0ccb-e376-4b80-8d2d-98115c3a2990, activate=true]]
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.d.d.p.GridDhtPartitionsExchangeFuture - Start activation process 
> [nodeId=62cf0ccb-e376-4b80-8d2d-98115c3a2990, client=false, 
> topVer=AffinityTopologyVersion [topVer=2, minorTopVer=1]]
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.f.FilePageStoreManager - Resolved page store work directory: 
> /opt/mbe1/ignite/db/mbe_MBE1
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.w.FileWriteAheadLogManager - Resolved write ahead log work 
> directory: /opt/mbe1/ignite/db/wal/mbe_MBE1
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.w.FileWriteAheadLogManager - Resolved write ahead log archive 
> directory: /opt/mbe1/ignite/db/wal/archive/mbe_MBE1
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] WARN  
> o.a.i.i.p.c.p.GridCacheDatabaseSharedManager - No user-defined default 
> MemoryPolicy found; system default of 1GB size will be used.
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.pagemem.PageMemoryImpl - Started page memory 
> [memoryAllocated=100.0 MiB, pages=48592, tableSize=2.9 MiB, 
> checkpointBuffer=819.4 MiB]
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.pagemem.PageMemoryImpl - Started page memory 
> [memoryAllocated=3.1 GiB, pages=1544064, tableSize=91.0 MiB, 
> checkpointBuffer=819.4 MiB]
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.GridCacheDatabaseSharedManager - Read checkpoint status: start 
> marker = 
> /opt/mbe1/ignite/db/mbe_MBE1/cp/1506444061104-38b80aaa-8c3d-4572-a42e-5b7a3b472505-START.bin,
>  end marker = 
> /opt/mbe1/ignite/db/mbe_MBE1/cp/1506442980839-ff65a0dc-3d83-436a-8329-7b3a31fe5ffc-END.bin
> 2017-09-26 12:11:24 [exchange-worker-#34%mbe%] INFO  
> o.a.i.i.p.c.p.GridCacheDatabaseSharedManager - Checking memory state 
> [lastValidPos=FileWALPointer [idx=139, fileOffset=31406805, len=20731, 
> forceFlush=false], lastMarked=FileWALPointer [idx=0, fileOffset=0, len=0, 
> forceFlush=false], lastCheckpointId=38b80aaa-8c3d-4572-a42e-5b7a3b472505]
> 2017-09-26 12:11:24 

[jira] [Assigned] (IGNITE-5608) SQL scripts execution capability

[Oleg Ostanin (JIRA)]

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

Oleg Ostanin reassigned IGNITE-5608:


Assignee: Oleg Ostanin

> SQL scripts execution capability
> 
>
> Key: IGNITE-5608
> URL: https://issues.apache.org/jira/browse/IGNITE-5608
> Project: Ignite
>  Issue Type: New Feature
>  Components: sql
>Reporter: Denis Magda
>Assignee: Oleg Ostanin
> Fix For: 2.3
>
>
> There should be a way to feed an SQL script to Ignite and execute it right 
> away. A script can consist of DDL command that will define cluster and SQL 
> configuration as well as of DML commands that, for instance, preload data 
> into Ignite.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-6305) Need to add update checker to Ignite

[Vladimir Ozerov (JIRA)]

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

Vladimir Ozerov reassigned IGNITE-6305:
---

Assignee: Andrey Gura  (was: Vladimir Ozerov)

[~agura], my comments:
1) {{ClusterProcessor.ctor}} - looks like update checker should be enabled by 
default and no new property is needed: 
{{IgniteSystemProperties.getBoolean(IGNITE_UPDATE_NOTIFIER, true)}}
2) {{GridUpdateNotifier#reportStatus}} - implementation is incorrect, as it 
checks for {{equals}}. As a result, if site reports 2.2.0, but I have 2.3.0, I 
still will be notified about "new" version. Instead, we should check for 
{{IgniteProductVersion#greaterThanEqual}}.

> Need to add update checker to Ignite
> 
>
> Key: IGNITE-6305
> URL: https://issues.apache.org/jira/browse/IGNITE-6305
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Reporter: Dmitriy Setrakyan
>Assignee: Andrey Gura
>Priority: Critical
>  Labels: important
> Fix For: 2.3
>
>
> # Ignite should provide an update check on node startup, which will report to 
> users if there is a new version available. 
> # We can also use the update-checker to count Ignite starts, which will allow 
> the community to monitor the health of the project.
> The design is specified in this dev@ thread (make sure to read all the way to 
> the end):
> http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSS-Ignite-Update-Checker-td21150.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6380) Exception should be thrown on cache creation attempt inside transaction

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on IGNITE-6380:


GitHub user xtern opened a pull request:

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

IGNITE-6380 Reject compute task execution if deadlock possible.



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

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

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

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


commit 403d2e7b071d56d67f9a960176ef94f634da1b59
Author: Pereslegin Pavel 
Date:   2017-10-08T16:30:01Z

IGNITE-6380 Reject compute task execution if deadlock possible.

commit 8abb43916e27f7b651cd63511ef759bf8cd343f5
Author: Pavel Pereslegin <30606288+xt...@users.noreply.github.com>
Date:   2017-10-09T08:46:51Z

IGNITE-6380 Exception message correction.

commit ff44e7d8056c5f53ec51e63a65ea9a81119ecfa5
Author: Pavel Pereslegin <30606288+xt...@users.noreply.github.com>
Date:   2017-10-09T08:51:23Z

IGNITE-6380 Test was renamed.

commit b617d4c41ebb3948d5c770f5369c283f60fe5c4c
Author: Pavel Pereslegin <30606288+xt...@users.noreply.github.com>
Date:   2017-10-09T08:54:29Z

IGNITE-6380 Test was included to test suit.




> Exception should be thrown on cache creation attempt inside transaction
> ---
>
> Key: IGNITE-6380
> URL: https://issues.apache.org/jira/browse/IGNITE-6380
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Yakov Zhdanov
>Assignee: Pavel Pereslegin
>  Labels: newbie, usability
>
> Exception should be thrown on cache creation attempt inside transaction to 
> prevent deadlocks since cache start triggers exchange and exchange cannot 
> finish until all txs are finished.
> We need to check if thread owns a tx before starting cache and if it does 
> then IllegalStateException should be thrown.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Assigned] (IGNITE-5767) Web console: use byte array type instead of java.lang.Object for binary JDBC types

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko reassigned IGNITE-5767:
-

Assignee: Alexey Kuznetsov  (was: Vasiliy Sisko)

> Web console: use byte array type instead of java.lang.Object for binary JDBC 
> types
> --
>
> Key: IGNITE-5767
> URL: https://issues.apache.org/jira/browse/IGNITE-5767
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Denis Kholodov
>Assignee: Alexey Kuznetsov
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> Schema importer should use {{[B}} query entity field type instead of 
> {{java.lang.Object}} for the following SQL types: {{BINARY}}, {{VARBINARY}} 
> and {{LONGVARBINARY}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5767) Web console: use byte array type instead of java.lang.Object for binary JDBC types

[Vasiliy Sisko (JIRA)]

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

Vasiliy Sisko commented on IGNITE-5767:
---

Not reproduced. 
Tested. Virbinary columns of TimesTen DB imported as byte[] columns.

> Web console: use byte array type instead of java.lang.Object for binary JDBC 
> types
> --
>
> Key: IGNITE-5767
> URL: https://issues.apache.org/jira/browse/IGNITE-5767
> Project: Ignite
>  Issue Type: Bug
>  Components: wizards
>Affects Versions: 2.0
>Reporter: Denis Kholodov
>Assignee: Vasiliy Sisko
> Fix For: 2.4
>
> Attachments: screenshot-1.png
>
>
> Schema importer should use {{[B}} query entity field type instead of 
> {{java.lang.Object}} for the following SQL types: {{BINARY}}, {{VARBINARY}} 
> and {{LONGVARBINARY}}.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6567) Document JDBC "multipleStatementsAllowed" property

[Taras Ledkov (JIRA)]

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

Taras Ledkov commented on IGNITE-6567:
--

[~dmagda], It's right. The multiple statements are always enabled for the thin 
driver in case the ignite node to which the client is connected supports 
multiple statements query.

> Document JDBC "multipleStatementsAllowed" property
> --
>
> Key: IGNITE-6567
> URL: https://issues.apache.org/jira/browse/IGNITE-6567
> Project: Ignite
>  Issue Type: Task
>  Components: documentation
>Reporter: Vladimir Ozerov
>Assignee: Prachi Garg
> Fix For: 2.3
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5798) Logging Ignite configuration at startup

[Vladislav Pyatkov (JIRA)]

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

Vladislav Pyatkov commented on IGNITE-5798:
---

Hi, 
Just I have faced with the same issue.
I can not able to verify "WAL history size" after grid is had been started.
We should to show this configuration at start (may by only if it is different 
from default).

{{org.apache.ignite.configuration.PersistentStoreConfiguration#walHistSize}}


> Logging Ignite configuration at startup
> ---
>
> Key: IGNITE-5798
> URL: https://issues.apache.org/jira/browse/IGNITE-5798
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexandr Kuramshin
>Assignee: Ivan Fedotov
>  Labels: easyfix, newbie
>
> I've found that IgniteConfiguration is not logged even when 
> -DIGNITE_QUIET=false
> When we starting Ignite with path to the xml, or InputStream, we have to 
> ensure, that all configuration options were properly read. And also we would 
> like to know actual values of uninitialized configuration properties (default 
> values), which will be set only after Ignite get started.
> Monitoring tools, like Visor or WebConsole, do not show all configuration 
> options. And even though they will be updated to show all properties, when 
> new configuration options appear, then tools update will be needed.
> Logging IgniteConfiguration at startup gives a possibility to ensure that the 
> right grid configuration has been applied and leads to better user support 
> based on log analyzing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5798) Logging Ignite configuration at startup

[Alexandr Kuramshin (JIRA)]

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

Alexandr Kuramshin commented on IGNITE-5798:


Hi, [~ivanan.fed]

1. I think we should use output of {{IgniteConfiguration.toString()}} which 
implemented by standard call to 
{{GridToStringBuilder#toString(java.lang.Class, T)}}. The maximum 
inheritance level will be used. Every object being logged takes own 
responsibility to have right {{toString()}} implementation. You may check 
proper {{@GridToStringInclude}} and {{@GridToStringExclude}} annotation usage 
on all enclosed configuration objects.

2. Null values also should be logged.

3. Relates to question #1.

4. When {{IgniteLogger.quiet == true}} we should not log 
{{IgniteConfiguration}}. Only when {{IgniteLogger.quiet == false}}.

> Logging Ignite configuration at startup
> ---
>
> Key: IGNITE-5798
> URL: https://issues.apache.org/jira/browse/IGNITE-5798
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexandr Kuramshin
>Assignee: Ivan Fedotov
>  Labels: easyfix, newbie
>
> I've found that IgniteConfiguration is not logged even when 
> -DIGNITE_QUIET=false
> When we starting Ignite with path to the xml, or InputStream, we have to 
> ensure, that all configuration options were properly read. And also we would 
> like to know actual values of uninitialized configuration properties (default 
> values), which will be set only after Ignite get started.
> Monitoring tools, like Visor or WebConsole, do not show all configuration 
> options. And even though they will be updated to show all properties, when 
> new configuration options appear, then tools update will be needed.
> Logging IgniteConfiguration at startup gives a possibility to ensure that the 
> right grid configuration has been applied and leads to better user support 
> based on log analyzing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-5798) Logging Ignite configuration at startup

[Alexander Belyak (JIRA)]

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

Alexander Belyak commented on IGNITE-5798:
--

1) I think you should log as many configuration options as you can
2) Don't sure, I prefer to log such fields for simplify grep for some parameter 
value
3) -
4) Yes, IMHO

> Logging Ignite configuration at startup
> ---
>
> Key: IGNITE-5798
> URL: https://issues.apache.org/jira/browse/IGNITE-5798
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Alexandr Kuramshin
>Assignee: Ivan Fedotov
>  Labels: easyfix, newbie
>
> I've found that IgniteConfiguration is not logged even when 
> -DIGNITE_QUIET=false
> When we starting Ignite with path to the xml, or InputStream, we have to 
> ensure, that all configuration options were properly read. And also we would 
> like to know actual values of uninitialized configuration properties (default 
> values), which will be set only after Ignite get started.
> Monitoring tools, like Visor or WebConsole, do not show all configuration 
> options. And even though they will be updated to show all properties, when 
> new configuration options appear, then tools update will be needed.
> Logging IgniteConfiguration at startup gives a possibility to ensure that the 
> right grid configuration has been applied and leads to better user support 
> based on log analyzing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (IGNITE-6030) Allow enabling persistence per-cache

[Pavel Tupitsyn (JIRA)]

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

Pavel Tupitsyn commented on IGNITE-6030:


{code}
DefaultRegionConfiguration
DataRegions
{code}

Looks inconsistent to me. In one case we call it RegionConfiguration, in 
another case DataRegion.

> Allow enabling persistence per-cache
> 
>
> Key: IGNITE-6030
> URL: https://issues.apache.org/jira/browse/IGNITE-6030
> Project: Ignite
>  Issue Type: New Feature
>  Components: persistence
>Affects Versions: 2.1
>Reporter: Alexey Goncharuk
>Assignee: Ivan Rakov
>Priority: Critical
>  Labels: important
> Fix For: 2.3
>
>
> Also, when cache native persistence is disabled, we need to make sure that 
> different {{CacheStores}} can be configured on per-cache basis.
> New storage configuration design draft:
> {noformat}
> DataStorageConfiguration
>   // memory configuration
>   getConcurrencyLevel
>   getDefaultRegionConfiguration
>   getDataRegions
>   getPageSize
>   getSystemRegionInitialSize
>   getSystemRegionMaxSize
>   // persistence coniguration
>   getCheckpointingFrequency
>   getCheckpointingPageBufferSize
>   getCheckpointingThreads
>   getCheckpointWriteOrder
>   getFileIOFactory
>   getLockWaitTime
>   getPersistentStorePath
>   getRateTimeInterval
>   getSubIntervals
>   getTlbSize
>   getWalArchivePath
>   getWalAutoArchiveAfterInactivity
>   getWalFlushFrequency
>   getWalFsyncDelayNanos
>   getWalHistorySize
>   getWalMode
>   getWalRecordIteratorBufferSize
>   getWalSegments
>   getWalSegmentSize
>   getWalStorePath
>   isAlwaysWriteFullPages
>   isMetricsEnabled
>   isWriteThrottlingEnabled
> DataRegionConfiguration
>   // memory policy configuration
>   isPersistenceEnabled (default = false)
>   getEmptyPagesPoolSize
>   getEvictionThreshold
>   getInitialSize
>   getMaxSize
>   getName
>   getPageEvictionMode
>   getRateTimeInterval
>   getSubIntervals
>   getSwapFilePath
>   isMetricsEnabled
> {noformat}
> New metrics and MBean classes:
> {noformat}
> PersistenceMetrics -> DataStorageMetrics
> PersistenceMetricsMXBean -> DataStorageMetricsMXBean
> MemoryMetrics -> DataRegionMetrics
> MemoryMetricsMXBean -> DataRegionMetricsMXBean
> {noformat}
> Please note that old versions of all classes and methods are retained in 
> codebase as deprecated.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Created] (IGNITE-6578) Too many diagnostic: Found long running cache future

[Alexander Belyak (JIRA)]

Alexander Belyak created IGNITE-6578:


 Summary: Too many diagnostic: Found long running cache future
 Key: IGNITE-6578
 URL: https://issues.apache.org/jira/browse/IGNITE-6578
 Project: Ignite
  Issue Type: Bug
  Components: general
Affects Versions: 2.1
Reporter: Alexander Belyak
Priority: Critical


Get about 100Mb of message:
 [WARN][grid-timeout-worker-...][o.apache.ignite.internal.diagnostic] 
Found long running cache future 
few equals message per ms! Can loose logs by rotating! Can't read logs without 
prefiltering!



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)