August 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4075) State transfer should preserve the creation timestamp of entries

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-4075?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-4075: ---------------------------------- Sprint: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > State transfer should preserve the creation timestamp of entries > ---------------------------------------------------------------- > > Key: ISPN-4075 > URL: https://issues.jboss.org/browse/ISPN-4075 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1, 10.0.0.Final > > > State transfer inserts values with the current time as the creation time. Since the entries store the expected lifespan and not the expected expiration time, entries on the receiving node could expire much later than intended. > The argument probably doesn't apply to the timestamp of the last usage. Since state transfer process could be interpreted as a reader, it should be fine to extend the update the time of the last usage both on the sending node and on the receiving node. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[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: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > 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: Nistor Adrian > Priority: Minor > Fix For: 10.0.0.Beta5 > > 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)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8234) Add support for @Spatial, @Latitude, @Longitude annotations in protobuf schema

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8234?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8234: ---------------------------------- Sprint: Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 9.3.0.Beta1, Sprint 9.3.0.CR1, Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Add support for @Spatial, @Latitude, @Longitude annotations in protobuf schema > ------------------------------------------------------------------------------ > > Key: ISPN-8234 > URL: https://issues.jboss.org/browse/ISPN-8234 > Project: Infinispan > Issue Type: Feature Request > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > > These annotations must behave identically to their Hibernate Search counterparts defined in org.hibernate.search.annotations package. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9463) Provide API to enlist the resource with TransactionManager

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9463?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9463: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Provide API to enlist the resource with TransactionManager > ---------------------------------------------------------- > > Key: ISPN-9463 > URL: https://issues.jboss.org/browse/ISPN-9463 > Project: Infinispan > Issue Type: Enhancement > Components: Hot Rod, Remote Protocols, Transactions > Reporter: Ramesh Reddy > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Beta3 > > > Currently, Infinispan will automatically enlist the transaction when a transaction is bound to the executing thread. However, in cases like Teiid where remote access to Infinispan access is wrapped with a resource-adapter (RAR) the resource adapter does the explicit enlisting or delisting. For this there needs to be API provided by Infinispan Cache like > {code} > RemoteCacheManager.getXaResource() > {code} > where it can access the XA resource. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9564) Align pom.xml order and versions

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9564?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9564: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Align pom.xml order and versions > -------------------------------- > > Key: ISPN-9564 > URL: https://issues.jboss.org/browse/ISPN-9564 > Project: Infinispan > Issue Type: Enhancement > Components: Build > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Major > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9572) Configuration parser support for multiple cache-containers

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9572?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9572: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Configuration parser support for multiple cache-containers > ---------------------------------------------------------- > > Key: ISPN-9572 > URL: https://issues.jboss.org/browse/ISPN-9572 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > > The embedded configuration parser should allow parsing multiple <cache-container> elements, each one identified by a unique name. > All cache-containers should share the same thread pools and transports. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9366) Cache.size optimizations

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9366?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9366: ---------------------------------- Sprint: Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Cache.size optimizations > ------------------------ > > Key: ISPN-9366 > URL: https://issues.jboss.org/browse/ISPN-9366 > Project: Infinispan > Issue Type: Enhancement > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > Fix For: 10.0.0.Final > > > Now that we have a segmented data container and segmented store we can add optimizations for the Cache.size operation in various configurations. > If a store is configured, passivation must be disabled for any of these optimizations related to stores to work > # Shared store can just invoke Store.size > # No store & no expired entries can invoke DataContainer.sizeIncludingExpired(IntSet) > # Non shared store can invoke Store.size(IntSet) -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9186) Upgrade Protostream to 4.3.0.Alpha8

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9186?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9186: ---------------------------------- Sprint: DataGrid Sprint #31, DataGrid Sprint #32 (was: DataGrid Sprint #31) > Upgrade Protostream to 4.3.0.Alpha8 > ----------------------------------- > > Key: ISPN-9186 > URL: https://issues.jboss.org/browse/ISPN-9186 > Project: Infinispan > Issue Type: Component Upgrade > Components: Remote Querying > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.0.Beta5 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9847) Extend configuration to allow inline JGroups configuration and inheritance

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9847?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9847: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Extend configuration to allow inline JGroups configuration and inheritance > -------------------------------------------------------------------------- > > Key: ISPN-9847 > URL: https://issues.jboss.org/browse/ISPN-9847 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration, Core > Affects Versions: 10.0.0.Alpha2 > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Priority: Major > Fix For: 10.0.0.Beta1, 10.0.0.Final > > > Allowing inline JGroups configurations to increase usability. > Also support the following extra features: > * stack inheritance with protocol replacement/override > * easier xsite configuration > {code:xml} > <jgroups transport="org.infinispan.remoting.transport.jgroups.JGroupsTransport"> >  > <stack-file name="udp" path="stacks/udp.xml"/> > <stack-file name="tcp" path="stacks/tcp.xml"/> >  > <stack name="mping"> > <TCP bind_port="7800" port_range="30" recv_buf_size="20000000" send_buf_size="640000" > sock_conn_timeout="300" bundler_type="no-bundler" > thread_pool.min_threads="0" thread_pool.max_threads="25" thread_pool.keep_alive_time="5000"/> > <MPING bind_addr="127.0.0.1" break_on_coord_rsp="true" > mcast_addr="${jgroups.mping.mcast_addr:228.2.4.6}" > mcast_port="${jgroups.mping.mcast_port:43366}" > ip_ttl="${jgroups.udp.ip_ttl:2}"/> > <MERGE3/> > <FD_SOCK/> > <FD_ALL timeout="3000" > interval="1000" > timeout_check_interval="1000" > /> > <VERIFY_SUSPECT timeout="1000"/> > <pbcast.NAKACK2 > use_mcast_xmit="false" > xmit_interval="100" > xmit_table_num_rows="50" > xmit_table_msgs_per_row="1024" > xmit_table_max_compaction_time="30000"/> > <UNICAST3 > xmit_interval="100" > xmit_table_num_rows="50" > xmit_table_msgs_per_row="1024" > xmit_table_max_compaction_time="30000" > /> > <RSVP /> > <pbcast.STABLE stability_delay="200" > desired_avg_gossip="2000" > max_bytes="1M" > /> > <pbcast.GMS print_local_addr="false" > join_timeout="${jgroups.join_timeout:2000}"/> > <MFC max_credits="2M" min_threshold="0.40"/> > <FRAG3/> > </stack> >  > <stack name="mytcp" extends="tcp"> > <MERGE3 max_interval="20000"/> > </stack> >  > <stack name="tcpgossip" extends="tcp"> > <TCPGOSSIP initial_hosts="${jgroups.tunnel.gossip_router_hosts:localhost[12001]}" stack.combine="replace:TCP_NIO2"/> > </stack> >  > <stack name="xsite" extends="udp"> > <relay site="LON"> > <remote-site name="NYC" stack="tcpgossip"/> > </relay> > </stack> > </jgroups> > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-7624) Change CacheLoaderInterceptor to ignore in memory for certain operations when passivation is not enabled

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-7624?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-7624: ---------------------------------- Sprint: Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31, DataGrid Sprint #32 (was: Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, DataGrid Sprint #31) > Change CacheLoaderInterceptor to ignore in memory for certain operations when passivation is not enabled > -------------------------------------------------------------------------------------------------------- > > Key: ISPN-7624 > URL: https://issues.jboss.org/browse/ISPN-7624 > Project: Infinispan > Issue Type: Bug > Components: Loaders and Stores > Reporter: Will Burns > Assignee: Will Burns > Priority: Major > > CacheLoader currently reads all in memory entries and then the store for bulk operations. This can be changed to only load from the store when passivation is not used as it should contain all entries that aren't in memory. > The only issue is that if Flag.SKIP_CACHE_STORE was used on a write. In this case we could store a boolean in the interceptor so that if this Flag is ever used we always do both. Very few users use this Flag and it should improve performance a bit and entries should be seen more consistently. -- This message was sent by Atlassian Jira (v7.12.1#712002)

4 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues August 2019