[jira] [Created] (IGNITE-7596) Add Functionality for data structures to be able to remove any failed node on data structure creation

2018-01-31 Thread Tim Onyschak (JIRA) 
Tim Onyschak created IGNITE-7596:


 Summary: Add Functionality for data structures to be able to 
remove any failed node on data structure creation
 Key: IGNITE-7596
 URL: https://issues.apache.org/jira/browse/IGNITE-7596
 Project: Ignite
  Issue Type: Improvement
  Components: cache, data structures
Affects Versions: 2.4
Reporter: Tim Onyschak


Improvement of IGNITE-7090 to allow any data structure the ability to fix state 
when new instances are created. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-7090) Semaphore Stuck when no acquirers to assign permit

2017-12-01 Thread Tim Onyschak (JIRA) 
Tim Onyschak created IGNITE-7090:


 Summary: Semaphore Stuck when no acquirers to assign permit
 Key: IGNITE-7090
 URL: https://issues.apache.org/jira/browse/IGNITE-7090
 Project: Ignite
  Issue Type: Bug
  Components: cache
Affects Versions: 2.1, 2.4
Reporter: Tim Onyschak


If no acquirers are available to take permit of semaphore, the permit never 
gets release and any further acquirerers will wait forever. 





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

[jira] [Created] (IGNITE-6756) Primary Node Change causes invalidation of GridNearCacheEntry topVer

2017-10-25 Thread Tim Onyschak (JIRA) 
Tim Onyschak created IGNITE-6756:


 Summary: Primary Node Change causes invalidation of 
GridNearCacheEntry topVer
 Key: IGNITE-6756
 URL: https://issues.apache.org/jira/browse/IGNITE-6756
 Project: Ignite
  Issue Type: Bug
  Security Level: Public (Viewable by anyone)
  Components: general
Affects Versions: 2.2, 2.1, 2.3
Reporter: Tim Onyschak


When using a near cache after a cache exists in a cluster, their appears to be 
a bug which causes the GridNearCacheEntry.topVer to be set to NONE on a check 
of the primaryNode after a topology change when the 
!nodeId.equals(primary.id(). This will prevent the topVer from being updated to 
the latest, which then cause the GridNearCacheEntry.valid to return false and 
force a hard hit to the cluster. 

Steps to reproduce: 
# Create 2 node
# create cache on 1 node
# populate cache 1
# create client
# create nearCache of original cache
# warm nearCache
# Cause topolgy change

Expected: 
Topology change cause 1 hard hit to cluster to make sure value value is up to 
date (guessing on this) 
All future request will be retrived from near cache

Actual
All request are to cluster since the GridNearCacheEntry.valid method return 
false. 



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