August 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3906) Do not place ProtobufValueWrapper instances in the cache

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3906?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3906: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Do not place ProtobufValueWrapper instances in the cache > -------------------------------------------------------- > > Key: ISPN-3906 > URL: https://issues.jboss.org/browse/ISPN-3906 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 8.1.0.Final > > > ProtobufValueWrapper is only needed in order to provide a classbridge so we can integrate with Hibernate Search. Still, we should not need to wrap the protobuf encoded byte array put in the cache with this class. It should only be created as a temporary wrapper just before we feed the data to Hibernate Search. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3938) AdvancedAsyncCacheLoader.process() concurrency issues

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3938?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3938: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > AdvancedAsyncCacheLoader.process() concurrency issues > ----------------------------------------------------- > > Key: ISPN-3938 > URL: https://issues.jboss.org/browse/ISPN-3938 > Project: Infinispan > Issue Type: Bug > Components: Core, Loaders and Stores > Affects Versions: 6.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Fix For: 8.1.0.Final > > > {{AdvancedAsyncCacheLoader.process()}} calls {{advancedLoader().process()}} to collect all the keys in the store, but the HashSet used to collect the keys it not thread-safe. This can cause problems, e.g. during state transfer: > {noformat} > WARN cheTopologyControlCommand | ISPN000071: Caught exception when handling command CacheTopologyControlCommand{cache=sessions, type=CH_UPDATE, sender=alfie-lt-46127, joinInfo=null, topologyId=3, currentCH=DefaultConsistentHash{numSegments=60, numOwners=1, members=[alfie-lt-46127]}, pendingCH=null, throwable=null, viewId=1}java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:926) > at java.util.HashMap$KeyIterator.next(HashMap.java:960) > at org.infinispan.persistence.async.AdvancedAsyncCacheLoader.process(AdvancedAsyncCacheLoader.java:80) > at org.infinispan.persistence.manager.PersistenceManagerImpl.processOnAllStores(PersistenceManagerImpl.java:414) > at org.infinispan.statetransfer.StateConsumerImpl.invalidateSegments(StateConsumerImpl.java:910) > at org.infinispan.statetransfer.StateConsumerImpl.onTopologyUpdate(StateConsumerImpl.java:393) > at org.infinispan.statetransfer.StateTransferManagerImpl.doTopologyUpdate(StateTransferManagerImpl.java:178) > at org.infinispan.statetransfer.StateTransferManagerImpl.access$000(StateTransferManagerImpl.java:38) > at org.infinispan.statetransfer.StateTransferManagerImpl$1.updateConsistentHash(StateTransferManagerImpl.java:100) > at org.infinispan.topology.LocalTopologyManagerImpl.handleConsistentHashUpdate(LocalTopologyManagerImpl.java:191) > at org.infinispan.topology.CacheTopologyControlCommand.doPerform(CacheTopologyControlCommand.java:152) > at org.infinispan.topology.CacheTopologyControlCommand.perform(CacheTopologyControlCommand.java:124) > at org.infinispan.topology.ClusterTopologyManagerImpl$3.run(ClusterTopologyManagerImpl.java:606) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask.run(FutureTask.java:262) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3905) Murmurhash3 implementation is slow on String keys

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3905?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3905: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Murmurhash3 implementation is slow on String keys > ------------------------------------------------- > > Key: ISPN-3905 > URL: https://issues.jboss.org/browse/ISPN-3905 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 6.0.0.Final, 6.0.1.Final > Reporter: Sanne Grinovero > Assignee: Dan Berindei > Priority: Minor > Fix For: 8.1.0.Final > > > String instances are a common choice for being used as key entries, still the getBytes() operation being performed allocates costly buffers, and the computation to get those bytes looks like expensive too. > I suspect there might be good reasons for not using the String's own hashcode directly as an input to Murmurhash? Still that's what other implementations seem to do. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3891) Tune for batching without transactions

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3891?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3891: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Tune for batching without transactions > -------------------------------------- > > Key: ISPN-3891 > URL: https://issues.jboss.org/browse/ISPN-3891 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Reporter: Sanne Grinovero > Fix For: 8.1.0.Final > > > The usage of batching is a critically important feature, widely used to improve performance in many common scenarios, but while documentation makes it clear that it's built on transactions, it's unclear how these transactions should be configured. > Also, I would challenge the decision of building batching on top of transactions and see if there are opportunities for further optimization. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3835) Index Update command is processed before the registry listener is triggered

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-3835?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-3835: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Index Update command is processed before the registry listener is triggered > --------------------------------------------------------------------------- > > Key: ISPN-3835 > URL: https://issues.jboss.org/browse/ISPN-3835 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 6.0.0.Final > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Priority: Critical > Labels: 64QueryBlockers > Fix For: 8.1.0.Final > > > When using the InfinispanIndexManager backend the master node might receive an index update command about an index which it hasn't defined yet. > Index definitions are triggered by the type registry, which in turn is driven by the ClusterRegistry and an event listener on the ClusterRegistry. It looks like slaves are sending update requests before the master has processed the configuration event. > This leads to index update commands to be lost (with a stacktrace logged) -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4735) Remove TODOs from the documentation

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4735?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4735: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Remove TODOs from the documentation > ----------------------------------- > > Key: ISPN-4735 > URL: https://issues.jboss.org/browse/ISPN-4735 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core, Documentation-Query, Documentation-Servers > Reporter: Mircea Markus > Assignee: Tristan Tarrant > Fix For: 8.1.0.Final > > > ATM the documentation has 38 todos, some of them being empty chapter in User Guide - pretty annoying for a new user trying to get used to Infinispan. Let's fixe all of these before 7.0.0.CR1 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4824) Add complete-timeout and reaper-interval in the server transactions configuration

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4824?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4824: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Add complete-timeout and reaper-interval in the server transactions configuration > --------------------------------------------------------------------------------- > > Key: ISPN-4824 > URL: https://issues.jboss.org/browse/ISPN-4824 > Project: Infinispan > Issue Type: Task > Components: Configuration, Server > Affects Versions: 7.0.0.CR1 > Reporter: Dan Berindei > Fix For: 8.1.0.Final > > > We should allow server users to configure the time after which completed remote txs are cleaned up and how often the cleanup task runs. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4817) Cluster Listener replication of listener to remote dist nodes needs privilege action

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4817?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4817: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Cluster Listener replication of listener to remote dist nodes needs privilege action > ------------------------------------------------------------------------------------ > > Key: ISPN-4817 > URL: https://issues.jboss.org/browse/ISPN-4817 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Affects Versions: 7.0.0.CR1 > Reporter: William Burns > Priority: Critical > Fix For: 8.1.0.Final > > > The ClusterListenerReplicateCallable needs to add the listener in a privileged block so that it can work properly. > I was also thinking if we need to change all of our messages to send along the current Subject so it can be properly applied to remote invocations as well. In this case we wouldn't need to wrap the listener invocation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4624) Allow custom partition handling strategy

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4624?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4624: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Allow custom partition handling strategy > ---------------------------------------- > > Key: ISPN-4624 > URL: https://issues.jboss.org/browse/ISPN-4624 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 7.0.0.Beta1 > Reporter: Dan Berindei > Labels: partition_handling > Fix For: 8.1.0.Final > > > Users should be able to configure a custom PartitionHandlingStrategy. It should be able to specify a behaviour on merge as well. > We might want to merge this with the RebalancePolicy, which was also supposed to be configurable. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ISPN-4596) Avoid index cleanup operations on putIfAbsent

by Pedro Ruivo (JIRA)

[ https://issues.jboss.org/browse/ISPN-4596?page=com.atlassian.jira.plugin.... ] Pedro Ruivo updated ISPN-4596: ------------------------------ Fix Version/s: 8.1.0.Final (was: 8.0.0.Final) > Avoid index cleanup operations on putIfAbsent > --------------------------------------------- > > Key: ISPN-4596 > URL: https://issues.jboss.org/browse/ISPN-4596 > Project: Infinispan > Issue Type: Enhancement > Components: Embedded Querying > Reporter: Sanne Grinovero > Assignee: Gustavo Fernandes > Fix For: 8.1.0.Final > > > when doing a putIfAbsent() operation we can relax some of the internal cleanup operations, such as automatically enabling the Flag.SKIP_INDEX_CLEANUP -- This message was sent by Atlassian JIRA (v6.3.15#6346)

8 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2015