June 2018 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-8242) Utilise Column Families

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8242?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8242: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Utilise Column Families > ----------------------- > > Key: ISPN-8242 > URL: https://issues.jboss.org/browse/ISPN-8242 > Project: Infinispan > Issue Type: Sub-task > Components: Loaders and Stores > Affects Versions: 9.1.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.4.0.Final > > > Currently we utilise two separate databases for the actual data being stored and an expiration queue. Instead we should utilise [Column Families|https://github.com/facebook/rocksdb/wiki/Column-Families] as these allow for atomic updates across columns. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8487) Global MBean registration happens too soon

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8487?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8487: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Global MBean registration happens too soon > ------------------------------------------ > > Key: ISPN-8487 > URL: https://issues.jboss.org/browse/ISPN-8487 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 9.2.0.Alpha2 > Reporter: Dan Berindei > Fix For: 9.4.0.Final > > > Currently {{DefaultCacheManager}} explicitly starts {{CacheManagerJmxRegistration}} before calling {{ModuleLifecycle#cacheManagerStarting}}, which means MBeans in other modules are not registered in JMX. > We should start {{CacheManagerJmxRegistration}} only during global component registry start, after the modules have registered their components. If we want to make the cache manager available in JMX before {{DefaultCacheManager.start()}}, we should only register that particular MBean. Conversely, on shutdown, components other than the cache manager should be removed from JMX on {{DefaultCacheManager.stop()}} (as per ISPN-118). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8486) Make file store work with home relative paths

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8486?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8486: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Make file store work with home relative paths > --------------------------------------------- > > Key: ISPN-8486 > URL: https://issues.jboss.org/browse/ISPN-8486 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > Fix For: 9.4.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8491) Add streaming variant of off heap to not create byte[] instances

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8491?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8491: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.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 > Fix For: 9.4.0.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.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8453) Commit should fail if cache is in degraded mode

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8453?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8453: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Commit should fail if cache is in degraded mode > ----------------------------------------------- > > Key: ISPN-8453 > URL: https://issues.jboss.org/browse/ISPN-8453 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 8.1.9.Final, 8.2.8.Final, 9.1.2.Final, 9.2.0.Alpha2 > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 9.4.0.Final > > > When the originator receives a {{CacheNotFoundResponse}} and the cache is in degraded mode, the transaction is marked as partially completed, but the commit completes successfully. > I believe that is not correct, because the originator could crash after the commit but before the merge, and in that case the transaction will not be applied on all the owners. The transaction manager will ignore any commit exception in {{NON_XA}}/{{useSynchronization}} mode, but at least in {{FULL_XA}}/{{NON_DURABLE_XA}} mode we can signal to the user that the transaction may be lost. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8451) Attributes in AttributeSets should state whether they apply globally or per-node

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8451?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8451: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Attributes in AttributeSets should state whether they apply globally or per-node > -------------------------------------------------------------------------------- > > Key: ISPN-8451 > URL: https://issues.jboss.org/browse/ISPN-8451 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 9.4.0.Final > > > Add an additional boolean to AttributeDefinition that defines whether the attribute is global or local. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8441) The module spec used by server config of indexed-entities/indexed-entity and modules/module accepts only deployments

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8441?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8441: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > The module spec used by server config of indexed-entities/indexed-entity and modules/module accepts only deployments > -------------------------------------------------------------------------------------------------------------------- > > Key: ISPN-8441 > URL: https://issues.jboss.org/browse/ISPN-8441 > Project: Infinispan > Issue Type: Enhancement > Components: Server > Affects Versions: 9.1.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.4.0.Final > > > The module name must start with "deployment." due to the use ServiceModuleLoader.moduleServiceName() method to resolve a service name from a module name. This only knows to handle deployments from 'deployment' dir, regular modules from the 'modules' dir are not handled. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8431) ScatteredSplitAndMergeTest random failures

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8431?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8431: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > ScatteredSplitAndMergeTest random failures > ------------------------------------------ > > Key: ISPN-8431 > URL: https://issues.jboss.org/browse/ISPN-8431 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Affects Versions: 9.2.0.Alpha1 > Environment: Jenkins > Reporter: Tristan Tarrant > Assignee: Radim Vansa > Labels: testsuite_stability > Fix For: 9.4.0.Final > > Attachments: ScatteredSplitAndMergeTest_20180129.log.gz, ScatteredSplitAndMergeTest_ISPN-7919_RpcManager_ResponseCollector_20171212.log.gz > > > http://ci.infinispan.org/job/Infinispan/job/master/214/testReport/junit/o... > java.lang.AssertionError: expected [null] but found [v0] > at org.infinispan.partitionhandling.ScatteredSplitAndMergeTest.testSplitAndMerge(ScatteredSplitAndMergeTest.java:80) > at org.infinispan.partitionhandling.ScatteredSplitAndMergeTest.testSplitAndMerge5(ScatteredSplitAndMergeTest.java:51) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > at java.lang.Thread.run(Thread.java:748) > ... Removed 20 stack frames > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8375) Allow additional HikariCP properties to be passed via PooledConnectionFactoryConfiguration

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8375?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8375: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.Final) > Allow additional HikariCP properties to be passed via PooledConnectionFactoryConfiguration > ------------------------------------------------------------------------------------------ > > Key: ISPN-8375 > URL: https://issues.jboss.org/browse/ISPN-8375 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 9.1.1.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Fix For: 9.4.0.Final > > > Currently the only way to provide additional HikariCP configuration is via a `hikari.properties` file. We should allow users to enter these properties via our xml/config builders. > This will also benefit the new datagrid-infinispan-datasources subsystem, as it will allow users to continue to utilise many of the additional tuning options that we have inherited from the wildfly-connector subsystem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8576) Add authorization to Distributed Locks

by Galder Zamarreño (JIRA)

[ https://issues.jboss.org/browse/ISPN-8576?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-8576: ----------------------------------- Fix Version/s: 9.4.0.Final (was: 9.3.0.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 > Fix For: 9.4.0.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.5.0#75005)

6 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues June 2018