[JBoss JIRA] (ISPN-8491) Add streaming variant of off heap to not create byte[] instances
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8491?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8491:
----------------------------------
Fix Version/s: 9.4.7.Final
(was: 9.4.6.Final)
> Add streaming variant of off heap to not create byte[] instances
> ----------------------------------------------------------------
>
> Key: ISPN-8491
> URL: https://issues.jboss.org/browse/ISPN-8491
> Project: Infinispan
> Issue Type: Sub-task
> Components: Off Heap
> Reporter: William Burns
> Priority: Major
> Fix For: 9.4.7.Final
>
>
> Currently off heap has to create a byte[] to copy memory from off heap. This is a waste of CPU and memory to do so. Instead we should have a streaming variant Output that the GlobalMarshaller can use that doesn't need all of this unnecessary copying. Unfortunately GlobalMarshaller is currently internally hard coded to require the usage of byte[] so we would have to tweak some code there as well to allow this.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (ISPN-8576) Add authorization to Distributed Locks
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8576?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8576:
----------------------------------
Fix Version/s: 9.4.7.Final
(was: 9.4.6.Final)
> Add authorization to Distributed Locks
> --------------------------------------
>
> Key: ISPN-8576
> URL: https://issues.jboss.org/browse/ISPN-8576
> Project: Infinispan
> Issue Type: Enhancement
> Components: Clustered Locks, Security
> Reporter: Tristan Tarrant
> Assignee: Katia Aresti
> Priority: Major
> Fix For: 9.4.7.Final
>
>
> DistributedLocks should support authorization.
> Namely only ADMIN permissions should be allowed to defineLocks and WRITE permissions should be allowed to manipulate them.
> When authorization is enabled, the DistributedLockManager should return SecureClusteredLocks which verify that the user has the required privileges.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (ISPN-8602) ExpirationSingleFileStoreDistListenerFunctionalTest random failures
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8602?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8602:
----------------------------------
Fix Version/s: 9.4.7.Final
(was: 9.4.6.Final)
> ExpirationSingleFileStoreDistListenerFunctionalTest random failures
> -------------------------------------------------------------------
>
> Key: ISPN-8602
> URL: https://issues.jboss.org/browse/ISPN-8602
> Project: Infinispan
> Issue Type: Bug
> Components: Test Suite - Core
> Affects Versions: 9.2.0.Beta1
> Reporter: Dan Berindei
> Assignee: William Burns
> Priority: Major
> Labels: testsuite_stability
> Fix For: 9.4.7.Final
>
>
> Various {{ExpirationSingleFileStoreDistListenerFunctionalTest}} tests are failing in master:
> {noformat}
> [ERROR] testExpirationOfStoreWhenDataNotInMemory[null](org.infinispan.expiration.impl.ExpirationSingleFileStoreDistListenerFunctionalTest) Time elapsed: 0.078 s <<< FAILURE!
> java.lang.AssertionError: expected:<0> but was:<7>
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
> at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252)
> at org.infinispan.expiration.impl.ExpirationStoreListenerFunctionalTest.testExpirationOfStoreWhenDataNotInMemory(ExpirationStoreListenerFunctionalTest.java:55)
> {noformat}
> {noformat}
> [ERROR] testSimpleExpirationLifespan[null](org.infinispan.expiration.impl.ExpirationSingleFileStoreDistListenerFunctionalTest) Time elapsed: 0.045 s <<< FAILURE!
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
> at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252)
> at org.infinispan.expiration.impl.ExpirationFunctionalTest.testSimpleExpirationLifespan(ExpirationFunctionalTest.java:78)
> at org.infinispan.expiration.impl.ExpirationStoreListenerFunctionalTest.testSimpleExpirationLifespan(ExpirationStoreListenerFunctionalTest.java:37)
> {noformat}
> {noformat}
> [ERROR] testSimpleExpirationMaxIdle[null](org.infinispan.expiration.impl.ExpirationSingleFileStoreDistListenerFunctionalTest) Time elapsed: 0 s <<< FAILURE!
> java.lang.AssertionError: expected:<0> but was:<1>
> at org.testng.AssertJUnit.fail(AssertJUnit.java:59)
> at org.testng.AssertJUnit.failNotEquals(AssertJUnit.java:364)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:80)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:245)
> at org.testng.AssertJUnit.assertEquals(AssertJUnit.java:252)
> at org.infinispan.expiration.impl.ExpirationFunctionalTest.testSimpleExpirationMaxIdle(ExpirationFunctionalTest.java:86)
> at org.infinispan.expiration.impl.ExpirationStoreListenerFunctionalTest.testSimpleExpirationMaxIdle(ExpirationStoreListenerFunctionalTest.java:44)
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (ISPN-2575) Key Transformer registration is required on all nodes of the cluster, in case of custom keys
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-2575?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-2575:
----------------------------------
Fix Version/s: 10.0.0.Beta1
(was: 10.0.0.Alpha3)
> Key Transformer registration is required on all nodes of the cluster, in case of custom keys
> --------------------------------------------------------------------------------------------
>
> Key: ISPN-2575
> URL: https://issues.jboss.org/browse/ISPN-2575
> Project: Infinispan
> Issue Type: Enhancement
> Components: Embedded Querying
> Affects Versions: 5.2.0.Beta5
> Reporter: Anna Manukyan
> Assignee: Adrian Nistor
> Priority: Minor
> Fix For: 10.0.0.Beta1
>
> Attachments: ClusteredCacheTest.java
>
>
> The case is the following:
> I have a clustered cache on which I want to perform a search. I'm doing the following:
> I'm initializing SearchManager on node1, I'm registering a custom key transformer for my key using the created searchmanager, but then when I'm trying to put data into the cache on node1 (which is in REPL_SYNC mode with cache on node2), I'm getting the exception:
> java.lang.IllegalArgumentException: Indexing only works with entries keyed on Strings, primitives and classes that have the @Transformable annotation - you passed in a class org.infinispan.query.test.CustomKey3. Alternatively, see org.infinispan.query.SearchManager#registerKeyTransformer
> When I'm initializing the SearchManager using node2 cache and register the keyTransformer on it as well, then everything works perfectly, even though I am not using the second created SearchManager.
> The test which reproduces the issue is attached to the jira. Please see the test case: testSearchKeyTransformer()
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months
[JBoss JIRA] (ISPN-8955) ClusterTopologyManagerImpl should only use non-blocking RPCs
by Tristan Tarrant (Jira)
[ https://issues.jboss.org/browse/ISPN-8955?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-8955:
----------------------------------
Fix Version/s: 10.0.0.Beta1
(was: 10.0.0.Alpha3)
> ClusterTopologyManagerImpl should only use non-blocking RPCs
> ------------------------------------------------------------
>
> Key: ISPN-8955
> URL: https://issues.jboss.org/browse/ISPN-8955
> Project: Infinispan
> Issue Type: Task
> Components: Core
> Affects Versions: 9.2.0.Final
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 10.0.0.Beta1
>
>
> {{ClusterTopologyManagerImpl}} still uses some blocking RPCs, particularly when a node becomes coordinator or after a merge. It should use non-blocking RPCs instead.
> It could also use non-blocking RPCs instead of fire-and-forget messages for things like topology updates, which would allow delivering topology updates in the same order on all the nodes instead of having regular nodes make to with missing topology updates (when the coordinator doesn't change).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 5 months