July 2013 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2673) maxEntries = 0 support for eviction

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2673?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2673: -------------------------------- Priority: Minor (was: Major) > maxEntries = 0 support for eviction > ----------------------------------- > > Key: ISPN-2673 > URL: https://issues.jboss.org/browse/ISPN-2673 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Affects Versions: 5.2.0.Beta6 > Reporter: Thomas Fromm > Assignee: Mircea Markus > Priority: Minor > > To save memory I'd like to configure maxEntries to 0. > In case I use a Cache to share (possible) big data as entry between nodes. These data are persisted inside store and only used rarely. So I see two ways to realize that: > 1) I can set maxEntries to 0 so that after use the entry is evicted from cache. > 2) Have a cache mode which does not keep data in memory and just work transparent on the store. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-557) support for same transaction touching multiple nodes (multiple VMs)

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-557?page=com.atlassian.jira.plugin.s... ] Mircea Markus resolved ISPN-557. -------------------------------- Resolution: Out of Date we already support a transaction spreading over multiple nodes (embedded) and have a different JIRA to cover the hotrod situation. > support for same transaction touching multiple nodes (multiple VMs) > -------------------------------------------------------------------- > > Key: ISPN-557 > URL: https://issues.jboss.org/browse/ISPN-557 > Project: Infinispan > Issue Type: Feature Request > Components: Transactions > Affects Versions: 4.1.0.Final > Reporter: Mircea Markus > Assignee: Manik Surtani > Priority: Minor > Fix For: 6.0.0.Final > > > E.g. if a distributed transaction managers touches two embedded Infinispan nodes within the same transaction. > Could be implemented using the Hot Rod client approach - but in an embedded fashion! > EmbeddedClient <-- implements logic above > Except comms are in-VM for local entries > And via RpcDispatcher for remote entries > RemoteClient extends EmbeddedClient > Adds proper HotRod layer for comms > Including failover, smart routing, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2673) maxEntries = 0 support for eviction

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2673?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2673: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > maxEntries = 0 support for eviction > ----------------------------------- > > Key: ISPN-2673 > URL: https://issues.jboss.org/browse/ISPN-2673 > Project: Infinispan > Issue Type: Feature Request > Components: Eviction > Affects Versions: 5.2.0.Beta6 > Reporter: Thomas Fromm > Assignee: Mircea Markus > > To save memory I'd like to configure maxEntries to 0. > In case I use a Cache to share (possible) big data as entry between nodes. These data are persisted inside store and only used rarely. So I see two ways to realize that: > 1) I can set maxEntries to 0 so that after use the entry is evicted from cache. > 2) Have a cache mode which does not keep data in memory and just work transparent on the store. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-317) when unsafeReturnValues is false, combine put, remove, replace, putIfAbsent, to pull back responses in 1 command

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-317?page=com.atlassian.jira.plugin.s... ] Mircea Markus updated ISPN-317: ------------------------------- Fix Version/s: (was: 6.0.0.Final) > when unsafeReturnValues is false, combine put, remove, replace, putIfAbsent, to pull back responses in 1 command > ---------------------------------------------------------------------------------------------------------------- > > Key: ISPN-317 > URL: https://issues.jboss.org/browse/ISPN-317 > Project: Infinispan > Issue Type: Feature Request > Affects Versions: 5.1.0.FINAL > Reporter: Mircea Markus > Assignee: Manik Surtani > > at the moment this is split in two operations: a remote get followed by an put. Optimize this to only reside in one operation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1457) try replay prepare if it fails

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1457?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-1457. --------------------------------- Resolution: Out of Date > try replay prepare if it fails > ------------------------------ > > Key: ISPN-1457 > URL: https://issues.jboss.org/browse/ISPN-1457 > Project: Infinispan > Issue Type: Enhancement > Components: Transactions > Affects Versions: 5.0.0.FINAL > Reporter: Mircea Markus > Assignee: Manik Surtani > Fix For: 6.0.0.Final > > Attachments: AbstractCrashTest.java > > > If the prepare fails for whatever reasons the system should automatically try to replay it for several times - the user code would do the same thing. > UT for checking that this is implemented is attached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1757) Use a ConsistentHashFactory for consistent hash configuration

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1757?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1757: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Use a ConsistentHashFactory for consistent hash configuration > ------------------------------------------------------------- > > Key: ISPN-1757 > URL: https://issues.jboss.org/browse/ISPN-1757 > Project: Infinispan > Issue Type: Task > Components: Configuration > Affects Versions: 5.1.0.CR4 > Reporter: Dan Berindei > Assignee: Pete Muir > > The new programmatic configuration allows the user to configure a consistent hash with `HashConfigurationBuilder.consistentHash(ConsistentHash)`. > Since we always create new instances of the consistent hash, I think it would be nicer if we had `HashConfigurationBuilder.consistentHashFactory(ConsistentHashFactory)` instead. > This would also allow us to have a single default factory that can choose between creating a `DefaultconsistentHash` or a `TopologyAwareConsistentHash` based on the transport configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1952) Use RESTEasy's HTTP frontend for the REST server

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1952?page=com.atlassian.jira.plugin.... ] Mircea Markus edited comment on ISPN-1952 at 7/1/13 11:31 PM: -------------------------------------------------------------- [~NadirX] is this still actual now that we have infinispan serveres? was (Author: mircea.markus): [~NadirX] is this still actual now that we have jboss serveres? > Use RESTEasy's HTTP frontend for the REST server > ------------------------------------------------ > > Key: ISPN-1952 > URL: https://issues.jboss.org/browse/ISPN-1952 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Reporter: Tristan Tarrant > Assignee: Tristan Tarrant > Fix For: 6.0.0.Final > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Using RESTEasy's HTTP frontend would allow the following: > - allow starting of a containerless REST Server using the startServer.sh script in the distibution > - drop the need for JBossWeb in JDG > - Give us some noticeable performance improvements -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1600) Use ServiceLoader to load other pluggable services

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1600?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1600: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Use ServiceLoader to load other pluggable services > -------------------------------------------------- > > Key: ISPN-1600 > URL: https://issues.jboss.org/browse/ISPN-1600 > Project: Infinispan > Issue Type: Enhancement > Components: Configuration > Reporter: Galder Zamarreño > Assignee: Galder Zamarreño > > The most interesting services that could benefit from this are most likely: Externalizers and Cache Stores. > Other interesting candidates are maybe transaction manager lookup classes. > This could be extended to other parts such as hash functions...etc, but such extensions are not that common. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1951) Use MERGE3 in the default UDP configuration

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1951?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1951: -------------------------------- Fix Version/s: (was: 6.0.0.Final) > Use MERGE3 in the default UDP configuration > ------------------------------------------- > > Key: ISPN-1951 > URL: https://issues.jboss.org/browse/ISPN-1951 > Project: Infinispan > Issue Type: Task > Components: Configuration > Affects Versions: 5.1.2.FINAL > Reporter: Dan Berindei > Assignee: Dan Berindei > > Bela recommends using MERGE3 instead of MERGE2 in UDP clusters. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-2610) Use Query but disable automatic indexing

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2610?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2610: -------------------------------- Assignee: Adrian Nistor (was: Sanne Grinovero) > Use Query but disable automatic indexing > ---------------------------------------- > > Key: ISPN-2610 > URL: https://issues.jboss.org/browse/ISPN-2610 > Project: Infinispan > Issue Type: Enhancement > Components: Querying > Reporter: Sanne Grinovero > Assignee: Adrian Nistor > Priority: Minor > Labels: stable_embedded_query > Fix For: 6.0.0.Alpha1 > > > The option known in Hibernate Search as > "hibernate.search.default.indexing_strategy" value="manual" > is not applied by Infinispan Query. > Workaround: use the SKIP_INDEXING flag > {code} > org.infinispan.context.Flag.SKIP_INDEXING{code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2013