[jira] [Created] (IGNITE-15690) Add a collective metric to log by caches for entries which are removed by expiry policy for time interval.

2021-10-06 Thread Konstantin Sirotkin (Jira) 
Konstantin Sirotkin created IGNITE-15690:


 Summary: Add a collective metric to log by caches for entries 
which are removed by expiry policy for time interval.
 Key: IGNITE-15690
 URL: https://issues.apache.org/jira/browse/IGNITE-15690
 Project: Ignite
  Issue Type: Improvement
  Components: cache
Affects Versions: 2.11
Reporter: Konstantin Sirotkin
Assignee: Konstantin Sirotkin


Within the task [IGNITE-13810 
|https://issues.apache.org/jira/browse/IGNITE-13810 ] was appended additional 
info to log about which expiry policy is applied for cache.

Need to add a collective metric to log by caches for entries which are removed 
by expiry policy for time interval.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13810) Append additional log and metrics info regarding cache expiration.

2021-08-24 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin commented on IGNITE-13810:
--

[~zstan], I'm looking at them right now.

> Append additional log and metrics info regarding cache expiration. 
> ---
>
> Key: IGNITE-13810
> URL: https://issues.apache.org/jira/browse/IGNITE-13810
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.9
>Reporter: Evgeny Stanilovsky
>Assignee: Konstantin Sirotkin
>Priority: Major
>  Time Spent: 2h 40m
>  Remaining Estimate: 0h
>
> Currently we have no any additional information regarding  
> _cache.withExpiryPolicy_ execution. Additionally it would be very useful to 
> have a corresponding metric.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (IGNITE-13810) Append additional log and metrics info regarding cache expiration.

2021-04-14 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin reassigned IGNITE-13810:


Assignee: Konstantin Sirotkin  (was: Stanilovsky Evgeny)

> Append additional log and metrics info regarding cache expiration. 
> ---
>
> Key: IGNITE-13810
> URL: https://issues.apache.org/jira/browse/IGNITE-13810
> Project: Ignite
>  Issue Type: Improvement
>  Components: cache
>Affects Versions: 2.9
>Reporter: Stanilovsky Evgeny
>Assignee: Konstantin Sirotkin
>Priority: Major
>
> Currently we have no any additional information regarding  
> _cache.withExpiryPolicy_ execution. Additionally it would be very useful to 
> have a corresponding metric.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13572) Duplicates in select query during partition eviction for caches with 0 backups

2020-11-25 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin commented on IGNITE-13572:
--

[~ivandasch], please review. I fixed your comments.

> Duplicates in select query during partition eviction for caches with 0 backups
> --
>
> Key: IGNITE-13572
> URL: https://issues.apache.org/jira/browse/IGNITE-13572
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.9, 2.8.1
>Reporter: Ivan Daschinskiy
>Assignee: Konstantin Sirotkin
>Priority: Major
> Fix For: 2.9.1
>
> Attachments: SqlPartitionEvictionTest.java
>
>  Time Spent: 3h 10m
>  Remaining Estimate: 0h
>
> Scenario:
> # Start 2 nodes with indexed atomic partitioned cache with 0 backups.
> # Load sufficient amout of data (or emulate slow removal from idx)
> # Start another node.
> # Perform SELECT * FROM .
> Query result contains duplicates, result size is significantly bigger than 
> expected cache size.
> Reproducer is attached.
> Reproduced on 2.8.1, ongoing 2.9 and master



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (IGNITE-13554) ConcurrentModificationException on node join.

2020-11-25 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin updated IGNITE-13554:
-
Reviewer: Stanilovsky Evgeny  (was: Vyacheslav Koptilin)

> ConcurrentModificationException on node join.
> -
>
> Key: IGNITE-13554
> URL: https://issues.apache.org/jira/browse/IGNITE-13554
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.8
>Reporter: Stanilovsky Evgeny
>Assignee: Konstantin Sirotkin
>Priority: Major
> Attachments: id.log
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> {noformat}
> java.util.ConcurrentModificationException: null
>   at java.util.HashMap$HashIterator.nextNode(HashMap.java:1445)
>   at java.util.HashMap$EntryIterator.next(HashMap.java:1479)
>   at java.util.HashMap$EntryIterator.next(HashMap.java:1477)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.fillAffinityNodeCaches(GridDiscoveryManager.java:3278)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.createDiscoCache(GridDiscoveryManager.java:2364)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.access$3100(GridDiscoveryManager.java:171)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:723)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:528)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2608)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2646)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13572) Duplicates in select query during partition eviction for caches with 0 backups

2020-11-24 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin commented on IGNITE-13572:
--

[~ivandasch], please take a look.

> Duplicates in select query during partition eviction for caches with 0 backups
> --
>
> Key: IGNITE-13572
> URL: https://issues.apache.org/jira/browse/IGNITE-13572
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.9, 2.8.1
>Reporter: Ivan Daschinskiy
>Assignee: Konstantin Sirotkin
>Priority: Major
> Fix For: 2.9.1
>
> Attachments: SqlPartitionEvictionTest.java
>
>  Time Spent: 2h 20m
>  Remaining Estimate: 0h
>
> Scenario:
> # Start 2 nodes with indexed atomic partitioned cache with 0 backups.
> # Load sufficient amout of data (or emulate slow removal from idx)
> # Start another node.
> # Perform SELECT * FROM .
> Query result contains duplicates, result size is significantly bigger than 
> expected cache size.
> Reproducer is attached.
> Reproduced on 2.8.1, ongoing 2.9 and master



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13572) Duplicates in select query during partition eviction for caches with 0 backups

2020-11-18 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin commented on IGNITE-13572:
--

[~ivandasch], please take a look. I fixed your comments.

> Duplicates in select query during partition eviction for caches with 0 backups
> --
>
> Key: IGNITE-13572
> URL: https://issues.apache.org/jira/browse/IGNITE-13572
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.9, 2.8.1
>Reporter: Ivan Daschinskiy
>Assignee: Konstantin Sirotkin
>Priority: Major
> Fix For: 2.9.1
>
> Attachments: SqlPartitionEvictionTest.java
>
>  Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> Scenario:
> # Start 2 nodes with indexed atomic partitioned cache with 0 backups.
> # Load sufficient amout of data (or emulate slow removal from idx)
> # Start another node.
> # Perform SELECT * FROM .
> Query result contains duplicates, result size is significantly bigger than 
> expected cache size.
> Reproducer is attached.
> Reproduced on 2.8.1, ongoing 2.9 and master



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13700) ConcurrentModificationException on node join.

2020-11-12 Thread Konstantin Sirotkin (Jira) 
Konstantin Sirotkin created IGNITE-13700:


 Summary: ConcurrentModificationException on node join.
 Key: IGNITE-13700
 URL: https://issues.apache.org/jira/browse/IGNITE-13700
 Project: Ignite
  Issue Type: Bug
Reporter: Konstantin Sirotkin
Assignee: Konstantin Sirotkin


This issue was created for more complex investigation of problem IGNITE-13554.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (IGNITE-13572) Duplicates in select query during partition eviction for caches with 0 backups

2020-11-08 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin reassigned IGNITE-13572:


Assignee: Konstantin Sirotkin

> Duplicates in select query during partition eviction for caches with 0 backups
> --
>
> Key: IGNITE-13572
> URL: https://issues.apache.org/jira/browse/IGNITE-13572
> Project: Ignite
>  Issue Type: Bug
>  Components: sql
>Affects Versions: 2.9, 2.8.1
>Reporter: Ivan Daschinskiy
>Assignee: Konstantin Sirotkin
>Priority: Major
> Attachments: SqlPartitionEvictionTest.java
>
>
> Scenario:
> # Start 2 nodes with indexed atomic partitioned cache with 0 backups.
> # Load sufficient amout of data (or emulate slow removal from idx)
> # Start another node.
> # Perform SELECT * FROM .
> Query result contains duplicates, result size is significantly bigger than 
> expected cache size.
> Reproducer is attached.
> Reproduced on 2.8.1, ongoing 2.9 and master



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (IGNITE-13554) ConcurrentModificationException on node join.

2020-10-15 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin reassigned IGNITE-13554:


Assignee: Konstantin Sirotkin

> ConcurrentModificationException on node join.
> -
>
> Key: IGNITE-13554
> URL: https://issues.apache.org/jira/browse/IGNITE-13554
> Project: Ignite
>  Issue Type: Bug
>  Components: general
>Affects Versions: 2.8
>Reporter: Stanilovsky Evgeny
>Assignee: Konstantin Sirotkin
>Priority: Major
> Attachments: id.log
>
>
> {noformat}
> java.util.ConcurrentModificationException: null
>   at java.util.HashMap$HashIterator.nextNode(HashMap.java:1445)
>   at java.util.HashMap$EntryIterator.next(HashMap.java:1479)
>   at java.util.HashMap$EntryIterator.next(HashMap.java:1477)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.fillAffinityNodeCaches(GridDiscoveryManager.java:3278)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.createDiscoCache(GridDiscoveryManager.java:2364)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.access$3100(GridDiscoveryManager.java:171)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.onDiscovery0(GridDiscoveryManager.java:723)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$4.lambda$onDiscovery$0(GridDiscoveryManager.java:528)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body0(GridDiscoveryManager.java:2608)
>   at 
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$DiscoveryMessageNotifierWorker.body(GridDiscoveryManager.java:2646)
>   at 
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
>   at java.lang.Thread.run(Thread.java:748)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Comment Edited] (IGNITE-13420) Add assertion message to assert in CachedDeploymentInfo private constructor

2020-09-13 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin edited comment on IGNITE-13420 at 9/13/20, 11:13 AM:
-

[~mmuzaf] 


Initial problem was fixed in https://issues.apache.org/jira/browse/IGNITE-12760.

Here I add assertion message for debug in case if assertion will be triggered 
by another reason.


was (Author: ksirotkin):
[Maxim Muzafarov
|file:///jira/secure/ViewProfile.jspa%3fname=mmuzaf]

Initial problem was fixed in 
[https://issues.apache.org/jira/browse/IGNITE-12760].

Here I add assertion message for debug in case if assertion will be triggered 
by another reason.

> Add assertion message to assert in CachedDeploymentInfo private constructor
> ---
>
> Key: IGNITE-13420
> URL: https://issues.apache.org/jira/browse/IGNITE-13420
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Konstantin Sirotkin
>Assignee: Konstantin Sirotkin
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We have an assertion in 
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.CachedDeploymentInfo#CachedDeploymentInfo:
>  
> {code:java}
> private CachedDeploymentInfo(UUID sndId, IgniteUuid ldrId, String userVer, 
> DeploymentMode depMode,
> Map participants) {
> assert sndId.equals(ldrId.globalId()) || participants != null;
> this.sndId = sndId;
> this.ldrId = ldrId;
> this.userVer = userVer;
> this.depMode = depMode;
> this.participants = participants == null || 
> participants.isEmpty() ? null :
> new ConcurrentLinkedHashMap<>(participants);
> }
> {code}
> Now we can't define assertion reason. We should add assertion message to that 
> place.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13420) Add assertion message to assert in CachedDeploymentInfo private constructor

2020-09-13 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin commented on IGNITE-13420:
--

[Maxim Muzafarov
|file:///jira/secure/ViewProfile.jspa%3fname=mmuzaf]

Initial problem was fixed in 
[https://issues.apache.org/jira/browse/IGNITE-12760].

Here I add assertion message for debug in case if assertion will be triggered 
by another reason.

> Add assertion message to assert in CachedDeploymentInfo private constructor
> ---
>
> Key: IGNITE-13420
> URL: https://issues.apache.org/jira/browse/IGNITE-13420
> Project: Ignite
>  Issue Type: Improvement
>Reporter: Konstantin Sirotkin
>Assignee: Konstantin Sirotkin
>Priority: Minor
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> We have an assertion in 
> org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.CachedDeploymentInfo#CachedDeploymentInfo:
>  
> {code:java}
> private CachedDeploymentInfo(UUID sndId, IgniteUuid ldrId, String userVer, 
> DeploymentMode depMode,
> Map participants) {
> assert sndId.equals(ldrId.globalId()) || participants != null;
> this.sndId = sndId;
> this.ldrId = ldrId;
> this.userVer = userVer;
> this.depMode = depMode;
> this.participants = participants == null || 
> participants.isEmpty() ? null :
> new ConcurrentLinkedHashMap<>(participants);
> }
> {code}
> Now we can't define assertion reason. We should add assertion message to that 
> place.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13420) Add assertion message to assert in CachedDeploymentInfo private constructor

2020-09-09 Thread Konstantin Sirotkin (Jira) 
Konstantin Sirotkin created IGNITE-13420:


 Summary: Add assertion message to assert in CachedDeploymentInfo 
private constructor
 Key: IGNITE-13420
 URL: https://issues.apache.org/jira/browse/IGNITE-13420
 Project: Ignite
  Issue Type: Improvement
Reporter: Konstantin Sirotkin
Assignee: Konstantin Sirotkin


We have an assertion in 
org.apache.ignite.internal.processors.cache.GridCacheDeploymentManager.CachedDeploymentInfo#CachedDeploymentInfo:

 
{code:java}
private CachedDeploymentInfo(UUID sndId, IgniteUuid ldrId, String userVer, 
DeploymentMode depMode,
Map participants) {
assert sndId.equals(ldrId.globalId()) || participants != null;

this.sndId = sndId;
this.ldrId = ldrId;
this.userVer = userVer;
this.depMode = depMode;
this.participants = participants == null || participants.isEmpty() 
? null :
new ConcurrentLinkedHashMap<>(participants);
}
{code}
Now we can't define assertion reason. We should add assertion message to that 
place.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (IGNITE-13102) IgniteCache#isClosed() returns false on server node even if the cache had been closed before.

2020-08-12 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin updated IGNITE-13102:
-
Release Note: Fixed problem when IgniteCache#isClosed() return false after 
IgniteCache#close()

> IgniteCache#isClosed() returns false on server node even if the cache had 
> been closed before.
> -
>
> Key: IGNITE-13102
> URL: https://issues.apache.org/jira/browse/IGNITE-13102
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.8, 2.8.1
>Reporter: Sergey Antonov
>Assignee: Konstantin Sirotkin
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 40m
>  Remaining Estimate: 0h
>
> IgniteCache#isClosed() still returns {{false}} even after 
> {{IgniteCache#close()}}. Only server nodes affect by this problem. 
> Simple reproducer:
> {code:java}
> @Test
> public void test() throws Exception {
> IgniteEx node = startGrid(0);
> IgniteCache cache = 
> node.getOrCreateCache(DEFAULT_CACHE_NAME);
> assertFalse(cache.isClosed());
> cache.close();
> // java.lang.AssertionError
> assertTrue(cache.isClosed());
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13102) IgniteCache#isClosed() returns false on server node even if the cache had been closed before.

2020-08-10 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin commented on IGNITE-13102:
--

[~zstan], done.

> IgniteCache#isClosed() returns false on server node even if the cache had 
> been closed before.
> -
>
> Key: IGNITE-13102
> URL: https://issues.apache.org/jira/browse/IGNITE-13102
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.8, 2.8.1
>Reporter: Sergey Antonov
>Assignee: Konstantin Sirotkin
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> IgniteCache#isClosed() still returns {{false}} even after 
> {{IgniteCache#close()}}. Only server nodes affect by this problem. 
> Simple reproducer:
> {code:java}
> @Test
> public void test() throws Exception {
> IgniteEx node = startGrid(0);
> IgniteCache cache = 
> node.getOrCreateCache(DEFAULT_CACHE_NAME);
> assertFalse(cache.isClosed());
> cache.close();
> // java.lang.AssertionError
> assertTrue(cache.isClosed());
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13102) IgniteCache#isClosed() returns false on server node even if the cache had been closed before.

2020-08-07 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin commented on IGNITE-13102:
--

[~zstan], can you review please?

> IgniteCache#isClosed() returns false on server node even if the cache had 
> been closed before.
> -
>
> Key: IGNITE-13102
> URL: https://issues.apache.org/jira/browse/IGNITE-13102
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.8, 2.8.1
>Reporter: Sergey Antonov
>Assignee: Konstantin Sirotkin
>Priority: Major
> Fix For: 2.10
>
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> IgniteCache#isClosed() still returns {{false}} even after 
> {{IgniteCache#close()}}. Only server nodes affect by this problem. 
> Simple reproducer:
> {code:java}
> @Test
> public void test() throws Exception {
> IgniteEx node = startGrid(0);
> IgniteCache cache = 
> node.getOrCreateCache(DEFAULT_CACHE_NAME);
> assertFalse(cache.isClosed());
> cache.close();
> // java.lang.AssertionError
> assertTrue(cache.isClosed());
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13315) Uninformative TxDumpsThrottling toString output.

2020-07-30 Thread Konstantin Sirotkin (Jira) 
Konstantin Sirotkin created IGNITE-13315:


 Summary: Uninformative TxDumpsThrottling toString output.
 Key: IGNITE-13315
 URL: https://issues.apache.org/jira/browse/IGNITE-13315
 Project: Ignite
  Issue Type: Improvement
  Components: general
Affects Versions: 2.8.1
Reporter: Konstantin Sirotkin
Assignee: Konstantin Sirotkin


looks like e need additional @GridToStringExclude for:
GridNearTxLocal#txDumpsThrottling

{noformat} 

2020-07-27 18:38:06.983[WARN 
][exchange-worker-#155%DPL_GRID%DplGridNodeName%][o.apache.ignite.internal.diagnostic]
 >>> [txVer=null, exchWait=false, tx=GridNearTxLocal 
[mappings=IgniteTxMappingsSingleImpl [mapping=null], nearLocallyMapped=false, 
colocatedLocallyMapped=false, needCheckBackup=null, hasRemoteLocks=false, 
trackTimeout=false, systemTime=0, systemStartTime=0, prepareStartTime=0, 
prepareTime=0, commitOrRollbackStartTime=0, commitOrRollbackTime=0, 
*txDumpsThrottling=o.a.i.i.processors.cache.transactions.IgniteTxManager$TxDumpsThrottling@66ede293*,
 lb=null, thread=, 
mappings=IgniteTxMappingsSingleImpl [mapping=null], super=GridDhtTxLocalAdapter 
[nearOnOriginatingNode=false, nearNodes=KeySetView [], dhtNodes=KeySetView [], 
explicitLock=false, super=IgniteTxLocalAdapter [completedBase=null, 
sndTransformedVals=false, depEnabled=false, 
txState=IgniteTxImplicitSingleStateImpl [init=false, recovery=false], 
super=IgniteTxAdapter [xidVer=GridCacheVersion [topVer=206004504, 
order=1595859218447, nodeOrder=1], writeVer=null, implicit=true, loc=true, 
threadId=997408, startTime=1595863641166, 
nodeId=1227c1de-f539-47ef-baef-5d04e259d590, startVer=GridCacheVersion 
[topVer=206004504, order=1595859218447, nodeOrder=1], endVer=null, 
isolation=READ_COMMITTED, concurrency=OPTIMISTIC, timeout=0, 
sysInvalidate=false, sys=true, plc=5, commitVer=null, finalizing=NONE, 
invalidParts=null, state=ACTIVE, timedOut=false, topVer=AffinityTopologyVersion 
[topVer=-1, minorTopVer=0], skipCompletedVers=false, duration=645816ms, 
onePhaseCommit=false], size=0

{noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13307) need update documentation in part of baseline-topology

2020-07-28 Thread Konstantin Sirotkin (Jira) 
Konstantin Sirotkin created IGNITE-13307:


 Summary: need update documentation in part of baseline-topology
 Key: IGNITE-13307
 URL: https://issues.apache.org/jira/browse/IGNITE-13307
 Project: Ignite
  Issue Type: Improvement
  Components: documentation
Reporter: Konstantin Sirotkin


Need to update documentation 
[baseline-topology|https://apacheignite.readme.io/docs/baseline-topology]

Documentation says that the baseline topology is built only for server nodes 
with enabled persistence

At the moment, the basic topology is being built for all server nodes, 
including in-memory



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13305) if create topologyValidator as lambda then get error "Cache topology validator mismatch"

2020-07-28 Thread Konstantin Sirotkin (Jira) 
Konstantin Sirotkin created IGNITE-13305:


 Summary: if create topologyValidator as lambda then get error 
"Cache topology validator mismatch"
 Key: IGNITE-13305
 URL: https://issues.apache.org/jira/browse/IGNITE-13305
 Project: Ignite
  Issue Type: Bug
  Components: cache
Reporter: Konstantin Sirotkin


Check of cache topology validator fails if create it as lambda.

For reproducing: 

In 
org.apache.ignite.internal.processors.cache.IgniteTopologyValidatorCacheGroupsAbstractTest#getConfiguration

{{{code:java|borderStyle=solid}}}

{{}}

TopologyValidator val1 = new TopologyValidator() {
    @Override public boolean validate(Collection nodes) {
        return nodes.size() == 2;
    }
};

{{}}

{{{code}}}

replace on {{}}

{{}}

{{{code:java|borderStyle=solid}}}

TopologyValidator val1 = nodes -> nodes.size() == 2;

{{{code}}}

{{Check fails in }}

{{org.apache.ignite.internal.processors.cache.ClusterCachesInfo#checkCache}}

{{when compare local and remote topologyValidators by class name }}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (IGNITE-13102) IgniteCache#isClosed() returns false on server node even if the cache had been closed before.

2020-07-24 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin reassigned IGNITE-13102:


Assignee: Konstantin Sirotkin

> IgniteCache#isClosed() returns false on server node even if the cache had 
> been closed before.
> -
>
> Key: IGNITE-13102
> URL: https://issues.apache.org/jira/browse/IGNITE-13102
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 2.8, 2.8.1
>Reporter: Sergey Antonov
>Assignee: Konstantin Sirotkin
>Priority: Major
> Fix For: 2.10
>
>
> IgniteCache#isClosed() still returns {{false}} even after 
> {{IgniteCache#close()}}. Only server nodes affect by this problem. 
> Simple reproducer:
> {code:java}
> @Test
> public void test() throws Exception {
> IgniteEx node = startGrid(0);
> IgniteCache cache = 
> node.getOrCreateCache(DEFAULT_CACHE_NAME);
> assertFalse(cache.isClosed());
> cache.close();
> // java.lang.AssertionError
> assertTrue(cache.isClosed());
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13069) Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression

2020-07-24 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin commented on IGNITE-13069:
--

[~agoncharuk], can you review?

> Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression
> -
>
> Key: IGNITE-13069
> URL: https://issues.apache.org/jira/browse/IGNITE-13069
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.8.1
>Reporter: Nikolay Izhikov
>Assignee: Konstantin Sirotkin
>Priority: Trivial
>  Labels: newbie
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We can use lambda expression instead of direct instantiation of 
> IgniteInClosure, IgniteOutClosure.
> This:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, new 
> IgniteOutClosure() {
> @Override public StateItem apply() {
> return new StateItem(msgFactory, protoVer);
> }
> });
> {code}
> Can be replaced with:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, () -> new 
> StateItem(msgFactory, protoVer));
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (IGNITE-13069) Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression

2020-07-22 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin updated IGNITE-13069:
-
Issue Type: Improvement  (was: New Feature)

> Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression
> -
>
> Key: IGNITE-13069
> URL: https://issues.apache.org/jira/browse/IGNITE-13069
> Project: Ignite
>  Issue Type: Improvement
>  Components: general
>Affects Versions: 2.8.1
>Reporter: Nikolay Izhikov
>Assignee: Konstantin Sirotkin
>Priority: Trivial
>  Labels: newbie
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We can use lambda expression instead of direct instantiation of 
> IgniteInClosure, IgniteOutClosure.
> This:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, new 
> IgniteOutClosure() {
> @Override public StateItem apply() {
> return new StateItem(msgFactory, protoVer);
> }
> });
> {code}
> Can be replaced with:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, () -> new 
> StateItem(msgFactory, protoVer));
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Updated] (IGNITE-13069) Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression

2020-07-22 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin updated IGNITE-13069:
-
Component/s: general

> Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression
> -
>
> Key: IGNITE-13069
> URL: https://issues.apache.org/jira/browse/IGNITE-13069
> Project: Ignite
>  Issue Type: New Feature
>  Components: general
>Affects Versions: 2.8.1
>Reporter: Nikolay Izhikov
>Assignee: Konstantin Sirotkin
>Priority: Trivial
>  Labels: newbie
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We can use lambda expression instead of direct instantiation of 
> IgniteInClosure, IgniteOutClosure.
> This:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, new 
> IgniteOutClosure() {
> @Override public StateItem apply() {
> return new StateItem(msgFactory, protoVer);
> }
> });
> {code}
> Can be replaced with:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, () -> new 
> StateItem(msgFactory, protoVer));
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (IGNITE-13069) Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression

2020-07-22 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin commented on IGNITE-13069:
--

[~nizhikov], can you review?

> Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression
> -
>
> Key: IGNITE-13069
> URL: https://issues.apache.org/jira/browse/IGNITE-13069
> Project: Ignite
>  Issue Type: New Feature
>Affects Versions: 2.8.1
>Reporter: Nikolay Izhikov
>Assignee: Konstantin Sirotkin
>Priority: Trivial
>  Labels: newbie
>  Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> We can use lambda expression instead of direct instantiation of 
> IgniteInClosure, IgniteOutClosure.
> This:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, new 
> IgniteOutClosure() {
> @Override public StateItem apply() {
> return new StateItem(msgFactory, protoVer);
> }
> });
> {code}
> Can be replaced with:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, () -> new 
> StateItem(msgFactory, protoVer));
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (IGNITE-13069) Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression

2020-07-17 Thread Konstantin Sirotkin (Jira) 


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

Konstantin Sirotkin reassigned IGNITE-13069:


Assignee: Konstantin Sirotkin

> Rewrite creation of IgniteInClosure and IgniteOutClosure as lambda expression
> -
>
> Key: IGNITE-13069
> URL: https://issues.apache.org/jira/browse/IGNITE-13069
> Project: Ignite
>  Issue Type: New Feature
>Affects Versions: 2.8
>Reporter: Nikolay Izhikov
>Assignee: Konstantin Sirotkin
>Priority: Trivial
>  Labels: newbie
>  Time Spent: 20m
>  Remaining Estimate: 0h
>
> We can use lambda expression instead of direct instantiation of 
> IgniteInClosure, IgniteOutClosure.
> This:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, new 
> IgniteOutClosure() {
> @Override public StateItem apply() {
> return new StateItem(msgFactory, protoVer);
> }
> });
> {code}
> Can be replaced with:
> {code:java}
> state = new DirectMessageState<>(StateItem.class, () -> new 
> StateItem(msgFactory, protoVer));
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)