April 2015 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-5264) Optimize PutAll operations (library mode)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5264?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5264: ------------------------------------------ Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1198556, https://bugzilla.redhat.com/show_bug.cgi?id=1194509 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1198556) > Optimize PutAll operations (library mode) > ----------------------------------------- > > Key: ISPN-5264 > URL: https://issues.jboss.org/browse/ISPN-5264 > Project: Infinispan > Issue Type: Enhancement > Reporter: Pedro Zapata > Assignee: William Burns > > - PutAll: to ensure that users can load massive amount of data into the grid quickly in Library mode > - Performance improvement over large data sets. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5263) Optimize Getall operations (library mode)

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5263?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-5263: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1198556, https://bugzilla.redhat.com/show_bug.cgi?id=1194509 > Optimize Getall operations (library mode) > ----------------------------------------- > > Key: ISPN-5263 > URL: https://issues.jboss.org/browse/ISPN-5263 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Reporter: Pedro Zapata > > - GetAll operation: to ensure that there’s a way to batch get multiple objects together. > - Improve performance for large data sets. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5346) QueryInterceptor::shouldRemove is too strict

by Ales Justin (JIRA)

[ https://issues.jboss.org/browse/ISPN-5346?page=com.atlassian.jira.plugin.... ] Ales Justin updated ISPN-5346: ------------------------------ Git Pull Request: https://github.com/infinispan/infinispan/pull/3360 > QueryInterceptor::shouldRemove is too strict > -------------------------------------------- > > Key: ISPN-5346 > URL: https://issues.jboss.org/browse/ISPN-5346 > Project: Infinispan > Issue Type: Task > Components: Embedded Querying > Affects Versions: 7.2.0.Beta2 > Reporter: Ales Justin > Assignee: Sanne Grinovero > Fix For: 7.2.0.CR1 > > > http://lists.jboss.org/pipermail/hibernate-dev/2015-April/012474.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5346) QueryInterceptor::shouldRemove is too strict

by Ales Justin (JIRA)

Ales Justin created ISPN-5346: --------------------------------- Summary: QueryInterceptor::shouldRemove is too strict Key: ISPN-5346 URL: https://issues.jboss.org/browse/ISPN-5346 Project: Infinispan Issue Type: Task Components: Embedded Querying Affects Versions: 7.2.0.Beta2 Reporter: Ales Justin Assignee: Sanne Grinovero Fix For: 7.2.0.CR1 http://lists.jboss.org/pipermail/hibernate-dev/2015-April/012474.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5262) StateTransfer considerably slow with sync indexing

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5262?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5262: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1204938|https://bugzilla.redhat.com/show_bug.cgi?id=1204938] from ON_QA to VERIFIED > StateTransfer considerably slow with sync indexing > -------------------------------------------------- > > Key: ISPN-5262 > URL: https://issues.jboss.org/browse/ISPN-5262 > Project: Infinispan > Issue Type: Enhancement > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Fix For: 7.2.0.Beta1 > > > The {{StateResponseCommand}} applies state sequentially, chunk by chunk. > The sequential cache population by a single thread does not take advantage of the index backend automatic batching capabilities when subjected to multiple threads and consequentially state transfer time can become prohibitive for large number of entries. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-4971) CDI uses default EmbeddedCacheManager producer from infinispan-cdi.jar instead of custom one

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4971?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-4971: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1163040|https://bugzilla.redhat.com/show_bug.cgi?id=1163040] from ON_QA to VERIFIED > CDI uses default EmbeddedCacheManager producer from infinispan-cdi.jar instead of custom one > -------------------------------------------------------------------------------------------- > > Key: ISPN-4971 > URL: https://issues.jboss.org/browse/ISPN-4971 > Project: Infinispan > Issue Type: Bug > Components: CDI Integration > Affects Versions: 7.0.0.CR1, 7.0.0.CR2, 7.0.0.Final > Reporter: Vitalii Chepeliuk > Assignee: Sebastian Łaskawiec > > Custom producer has allowDuplicateDomains set to true look following code > {code} > public class EmbeddedCacheManagerProducer { > /** > * Produces the default embedded cache manager. > * > * @param providedDefaultEmbeddedCacheManager the provided default embedded cache manager. > * @param defaultConfiguration the default configuration produced by the {@link EmbeddedCacheManagerProducer}. > * @return the default embedded cache manager used by the application. > */ > @Produces > @ApplicationScoped > public EmbeddedCacheManager getDefaultEmbeddedCacheManager(@OverrideDefault Instance<EmbeddedCacheManager> providedDefaultEmbeddedCacheManager, Configuration defaultConfiguration) { > GlobalConfiguration globalConfiguration = new GlobalConfigurationBuilder().globalJmxStatistics().allowDuplicateDomains(true).build(); > ConfigurationBuilder builder = new ConfigurationBuilder(); > builder.read(defaultConfiguration); > return new DefaultCacheManager(globalConfiguration, builder.build()); > } > /** > * Stops the default embedded cache manager when the corresponding instance is released. > * > * @param defaultEmbeddedCacheManager the default embedded cache manager. > */ > private void stopCacheManager(@Disposes EmbeddedCacheManager defaultEmbeddedCacheManager) { > defaultEmbeddedCacheManager.stop(); > } > } > {code} > And default ones from infinispan-cdi.jar is > {code} > public class DefaultEmbeddedCacheManagerProducer { > private static final Log log = LogFactory.getLog(DefaultEmbeddedCacheManagerProducer.class, Log.class); > /** > * Produces the default embedded cache manager. > * > * @param providedDefaultEmbeddedCacheManager the provided default embedded cache manager. > * @param defaultConfiguration the default configuration produced by the {@link DefaultEmbeddedCacheConfigurationProducer}. > * @return the default embedded cache manager used by the application. > */ > @Produces > @ApplicationScoped > @DefaultBean(EmbeddedCacheManager.class) > public EmbeddedCacheManager getDefaultEmbeddedCacheManager(@OverrideDefault Instance<EmbeddedCacheManager> providedDefaultEmbeddedCacheManager, Configuration defaultConfiguration) { > if (!providedDefaultEmbeddedCacheManager.isUnsatisfied()) { > log.tracef("Default embedded cache manager overridden by '%s'", providedDefaultEmbeddedCacheManager); > return providedDefaultEmbeddedCacheManager.get(); > } > return new DefaultCacheManager(defaultConfiguration); > } > /** > * Stops the default embedded cache manager when the corresponding instance is released. > * > * @param defaultEmbeddedCacheManager the default embedded cache manager. > */ > private void stopCacheManager(@Disposes EmbeddedCacheManager defaultEmbeddedCacheManager) { > defaultEmbeddedCacheManager.stop(); > } > } > {code} > When tests are deployed to APP server then following ERROR occurs > 10:19:58,494 ERROR [org.infinispan.jmx.JmxUtil] (http-localhost.localdomain/127.0.0.1:8080-1) ISPN000034: There's already an cache manager instance registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element > 10:19:58,526 ERROR [org.infinispan.jmx.JmxUtil] (http-localhost.localdomain/127.0.0.1:8080-1) ISPN000034: There's already an cache manager instance registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element > 10:19:58,598 ERROR [org.infinispan.jmx.JmxUtil] (http-localhost.localdomain/127.0.0.1:8080-1) ISPN000034: There's already an cache manager instance registered under 'org.infinispan' JMX domain. If you want to allow multiple instances configured with same JMX domain enable 'allowDuplicateDomains' attribute in 'globalJmxStatistics' config element > What means that out custom producer is sometimes not used and does not override default produced EmbeddedCacheManager -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5174) Transaction cannot be recommitted after ownership changes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5174?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5174: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1207082|https://bugzilla.redhat.com/show_bug.cgi?id=1207082] from ON_QA to VERIFIED > Transaction cannot be recommitted after ownership changes > --------------------------------------------------------- > > Key: ISPN-5174 > URL: https://issues.jboss.org/browse/ISPN-5174 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.1.0.CR2, 7.1.1.Final > Reporter: Radim Vansa > Assignee: Dan Berindei > Priority: Critical > Fix For: 7.2.0.Beta2, 7.2.0.Final > > > Once transaction is completed, it cannot commit again. If it should commit more keys since it has become an owner of some new keys modified in this transaction, it just ignores the further commit. > There is a race with state transfer which can bring an old value (with StateResponseCommand sent before it is commited) but the value is not set by the ongoing transaction either. > This results with stale value stored on one node. > In my case, The problematic part is transaction <edg-perf01-62141>:15066 (consisting of 10 modifications) which got prepared and committed on edg-perf04 in topology 25. Before the originator finishes, topology changes and 04 requests ongoing transactions: > {code} > 11:06:11,369 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (transport-thread-17) Replication task sending StateRequestCommand{cache=testCache, origin=edg-perf04-35097, type=GET_TRANSACTIONS, topologyId=28, segments=[275, 1, 278, 9, 282, 286, 17, 259, 25, 267, 171, 169, 33, 306, 175, 173, 310, 172, 314, 41, 167, 165, 318, 187, 290, 49, 185, 191, 294, 189, 179, 298, 57, 177, 183, 302, 181, 343, 205, 201, 338, 203, 336, 351, 197, 349, 199, 347, 193, 345, 195, 326, 85, 87, 322, 93, 332, 95, 330, 89, 91, 103, 101, 99, 506, 97, 105, 357, 359, 353, 355, 361]} to single recipient edg-perf01-62141 with response mode GET_ALL > 11:06:11,495 DEBUG [org.infinispan.statetransfer.StateConsumerImpl] (transport-thread-17) Applying 6 transactions for cache testCache transferred from node edg-perf01-62141 > {code} > However I don't see how these are applied, since PrepareCommand is not created again - from the code I see only that backup locks are added. Not sure if the transaction is registered at all, since it was already completed on this node (but at that time it did not own key_00000000000002EB). > After originator stores the entry, it sends one more CommitCommand with topology 28: > {code} > 11:06:11,619 TRACE [org.infinispan.remoting.transport.jgroups.CommandAwareRpcDispatcher] (DefaultStressor-2) Replication task sending CommitCommand {gtx=GlobalTransaction:<edg-perf01-62141>:15066:local, cacheName='testCache', topologyId=28} to addresses [edg-perf03-20530, edg-perf04-35097] with response mode GET_ALL > {code} > 04 receives several CommitCommands (both from originator and forwards), but all of them are ignored as the transaction is completed. > I don't see the logs where state transfer is assembled, but it's probably before the entry is stored on originator as the state transfer contains the old entry: > {code} > 11:06:13,449 TRACE [org.infinispan.statetransfer.StateConsumerImpl] (remote-thread-91) Received chunk with keys [key_000000000000065B, key_00000000000006BE, key_FFFFFFFFFFFFE62F, key_0000000000001F42, key_000000000000027B, key_000000000000159D, key_00000000000002EB, key_00000000000002BB] for segment 343 of cache testCache from node edg-perf01-62141 > 11:06:13,454 TRACE [org.infinispan.container.DefaultDataContainer] (remote-thread-91) Store ImmortalCacheEntry{key=key_00000000000002EB, value=[2 #7: 366, 544, 576, 804, 1061, 1181, 1290, ]} in container > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5232) Entry iterator returns entries created in current TX but does not apply the filter/converter

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5232?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5232: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1197851|https://bugzilla.redhat.com/show_bug.cgi?id=1197851] from ON_QA to VERIFIED > Entry iterator returns entries created in current TX but does not apply the filter/converter > -------------------------------------------------------------------------------------------- > > Key: ISPN-5232 > URL: https://issues.jboss.org/browse/ISPN-5232 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 7.0.0.Final > Reporter: Adrian Nistor > Assignee: William Burns > Fix For: 7.2.0.Beta1, 7.2.0.Final, 7.1.2.Final > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5269) Process and generate component metadata for tests

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5269?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5269: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1202479|https://bugzilla.redhat.com/show_bug.cgi?id=1202479] from ON_QA to VERIFIED > Process and generate component metadata for tests > ------------------------------------------------- > > Key: ISPN-5269 > URL: https://issues.jboss.org/browse/ISPN-5269 > Project: Infinispan > Issue Type: Enhancement > Components: Build process > Affects Versions: 7.2.0.Alpha1 > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta1, 7.1.2.Final > > > Currently it is not possible to use @Inject annotations in test classes because component metadata is not processed for test sources. It would be nice to have this (optionally) generated. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (ISPN-5231) CacheNotifierImpl should wire the listener and converter with dependecies from ComponentRegistry

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-5231?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on ISPN-5231: ----------------------------------------------- Vojtech Juranek <vjuranek(a)redhat.com> changed the Status of [bug 1202479|https://bugzilla.redhat.com/show_bug.cgi?id=1202479] from ON_QA to VERIFIED > CacheNotifierImpl should wire the listener and converter with dependecies from ComponentRegistry > ------------------------------------------------------------------------------------------------ > > Key: ISPN-5231 > URL: https://issues.jboss.org/browse/ISPN-5231 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 7.1.0.Final > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 7.2.0.Beta1, 7.2.0.Final, 7.1.2.Final > > > The wiring is already done for distributed iterators, so the same mechanism should be reused with filters that are used for events. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues April 2015