May 2012 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2044) Optimize marshalling of EnumSet<Flag>

by Sanne Grinovero (JIRA)

Sanne Grinovero created ISPN-2044: ------------------------------------- Summary: Optimize marshalling of EnumSet<Flag> Key: ISPN-2044 URL: https://issues.jboss.org/browse/ISPN-2044 Project: Infinispan Issue Type: Enhancement Components: Marshalling Reporter: Sanne Grinovero Assignee: Galder Zamarreño Fix For: 5.2.0.FINAL It looks like we could encode the whole EnumSet as a bitset, or use a different Marshaller ID for the empty enumset (which I'm assuming is a common case so worth optimizing for) See also thread: http://lists.jboss.org/pipermail/infinispan-dev/2012-May/010635.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
18
0 / 0

[JBoss JIRA] (ISPN-2042) Add easy trace logging facility to the test suite

by Galder Zamarreño (JIRA)

Galder Zamarreño created ISPN-2042: -------------------------------------- Summary: Add easy trace logging facility to the test suite Key: ISPN-2042 URL: https://issues.jboss.org/browse/ISPN-2042 Project: Infinispan Issue Type: Task Components: Test Suite Reporter: Galder Zamarreño Assignee: Galder Zamarreño Priority: Minor Fix For: 5.2.0.FINAL Stuart did some XSLT magic (https://github.com/jbossas/jboss-as/commit/e0c6cdd53068e46a1c9d81d4649cb9...) to enable TRACE logging for categories by simply passing -Dtrace=org.mycategory1,org.mycategory2 when running the tests Very useful stuff. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
1
0 / 0

[JBoss JIRA] (ISPN-1534) Optimise Hot Rod client and server to work with asynchronous distributed caches

by Galder Zamarreño (Created) (JIRA)

Optimise Hot Rod client and server to work with asynchronous distributed caches ------------------------------------------------------------------------------- Key: ISPN-1534 URL: https://issues.jboss.org/browse/ISPN-1534 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreño Assignee: Galder Zamarreño Fix For: 5.2.0.FINAL With Hot Rod clients, we can control where to direct invocations too, so there's a very interesting performance optimization we can apply with distributed caches. We can tolerate, and benefit from the speed of, asynchronous distributed caches very easily if we can get Hot Rod clients to always hit the owner of a key. It's a bit like sticky sessions, but applied to remote distributed caches! I think this would improve performance of our Hot Rod architecture quite notably. I think the Hot Rod client already works this way since I don't think it load balances between owners of a key. So, the aim of this JIRA is to: 1. Verify whether the Hot Rod client works this way 2. Consider whether Hot Rod servers could transform, on the fly, synchronous distributed caches into asynchronous ones, indicating so in the logs (INFO level). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
3
0 / 0

[JBoss JIRA] (ISPN-1698) Lazily start transports until needed

by Manik Surtani (Created) (JIRA)

Lazily start transports until needed ------------------------------------ Key: ISPN-1698 URL: https://issues.jboss.org/browse/ISPN-1698 Project: Infinispan Issue Type: Enhancement Components: Configuration Affects Versions: 5.1.0.FINAL Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.2.0.FINAL Currently if a transport is defined in <global />, and only a local mode cache is started off this configuration, the transport is still started. This is unnecessary and the transport should only be started when the first clustered cache is started. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (ISPN-1146) Improve documentation around transaction and locking

by Mircea Markus (JIRA)

Improve documentation around transaction and locking ---------------------------------------------------- Key: ISPN-1146 URL: https://issues.jboss.org/browse/ISPN-1146 Project: Infinispan Issue Type: Task Components: Transactions Reporter: Mircea Markus Assignee: Mircea Markus Fix For: 5.1.0.Final As suggested by Jonathan Halliday: - preserving some subset of the existing transactional guarantees is all well and good BUT if the user is relying on additional 'guarantees' that are not preserved in all cases then they'll be in trouble. Therefore, it's essential to document not just what the minimum expected guarantees for a given config are, but also that no additional properties that may coincidently be observed are actually guaranteed. Some vendors go further and explicitly document the bad things that may happen with given settings, since in some cases these are not easy to reproduce in testing. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (ISPN-825) Consider staggering remote get requests when using DIST

by Manik Surtani (JIRA)

Consider staggering remote get requests when using DIST ------------------------------------------------------- Key: ISPN-825 URL: https://jira.jboss.org/browse/ISPN-825 Project: Infinispan Issue Type: Feature Request Components: RPC Affects Versions: 4.1.0.Final Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 5.0.0.BETA1, 5.0.0.Final In DIST mode, when a request is made on a key that is not mapped locally, a remote get is sent to all data owners of that key and the first response is used. This can add unnecessary load on the network as all nodes still eventually respond, and if values are large this can cause a lot of unnecessary network traffic. The purpose of broadcasting to all data owners is so that (1) if one is down, another could still respond (2) if one is overloaded, others may respond faster. A solution around this could be based on either (or both) of: * Provide a configurable stagger timeout, e.g. 100ms. E.g., RPC to (random) Owner1. Wait for timeout t. If no response, RPC to Owner2. etc. * Always broadcast to a (configurable) subset of owners, e.g., always 2 even if numOwners is 5. Needs careful thought and design. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
10
0 / 0

[JBoss JIRA] Created: (ISPN-647) Remote InboundInvocationHandler should differentiate between various cache inavailabilities

by Manik Surtani (JIRA)

Remote InboundInvocationHandler should differentiate between various cache inavailabilities ------------------------------------------------------------------------------------------- Key: ISPN-647 URL: https://jira.jboss.org/browse/ISPN-647 Project: Infinispan Issue Type: Feature Request Components: RPC Affects Versions: 4.2.0.ALPHA1, 4.1.0.Final Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.2.0.BETA1, 4.2.0.CR1 Currently a RequestIgnoredResponse is returned to any caller if either of these happen: * The cache is not yet started, is in the process of starting, and times out. * The cache doesn't exist. * The cache has been stopped. The latter two should use a different response type - CacheUnavailableResponse ? - that would not trigger a retry or any abort of transactions. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

5
11
0 / 0

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

by Mircea Markus (JIRA)

when unsafeReturnValues is false, combine put, remove, replace, putIfAbsent, to pull back responses in 1 command ---------------------------------------------------------------------------------------------------------------- Key: ISPN-317 URL: https://jira.jboss.org/jira/browse/ISPN-317 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.1.0.CR1 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 contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

7
25
0 / 0

[JBoss JIRA] Created: (ISPN-1345) Dirty reads may occurs on mutable objects

by Christophe Labouisse (JIRA)

Dirty reads may occurs on mutable objects ----------------------------------------- Key: ISPN-1345 URL: https://issues.jboss.org/browse/ISPN-1345 Project: Infinispan Issue Type: Bug Components: Transactions Affects Versions: 5.0.0.FINAL Environment: Windows Java 1.6.0_26 Reporter: Christophe Labouisse Assignee: Manik Surtani In local mode, I create a cache like this: {code} cacheManager = new DefaultCacheManager(); cacheManager.getDefaultConfiguration().fluent().storeAsBinary().transaction().cacheStopTimeout(5000); final Configuration config = new Configuration().fluent().transactionManagerLookup(this.tmLookup).locking() .isolationLevel(IsolationLevel.READ_COMMITED).build(); this.cacheManager.defineConfiguration("Gruik", config); this.cache = this.cacheManager.getCache("Gruik"); {code} When retrieving data using {{cache.get(_key_)}} I find out that Infinispan returns the object instance actually stored in the cache datastore. This is OK when the inserted objects are immutable but fails to achieve isolation when using mutable objects. For instance on a simple Pojo with a {{get/setValue}}. ||Step||Reader||Writer|| |1|Starts transaction| | |2|{{value = cache.get(KEY);}}| | |3|{{System.out.println(value.getValue());}} Prints 42| | |4| |Starts transaction| |5| |{{value = cache.get(KEY);}} Same instance than step 2| |6| |{{value.setValue(666); // Prepare update}}| |7|{{System.out.println(value.getValue());}} Prints 666 !| | |8|{{value = cache.get(KEY);}} Same instance than step 2| | |9| |{{cache.put(KEY,value);}}| |10| |Commits transaction| |11|{{value = cache.get(KEY);}} Same instance than step 2| | |12|{{System.out.println(value.getValue());}} Prints 666| | |13|Commits transaction| | According to the READ_COMMITTED specification, the value returned printed on step 7 should be 42, as the setting to 666 is not committed yes. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

8
18
0 / 0

[JBoss JIRA] Created: (ISPN-1272) Move away from javadoc's aggregate goal

by Galder Zamarreño (JIRA)

Move away from javadoc's aggregate goal --------------------------------------- Key: ISPN-1272 URL: https://issues.jboss.org/browse/ISPN-1272 Project: Infinispan Issue Type: Enhancement Components: Build process Reporter: Galder Zamarreño Assignee: Manik Surtani Priority: Minor Fix For: 5.2.0.FINAL We should move away from maven javadoc's aggregate goal because it creates a lot of pains. For starters, it often spawns a separate process, -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues May 2012