March 2010 - infinispan-issues - Jboss List Archives

[JBoss JIRA] Created: (ISPN-241) improve test harness to use nice test names for nodes

by Mircea Markus (JIRA)

improve test harness to use nice test names for nodes ----------------------------------------------------- Key: ISPN-241 URL: https://jira.jboss.org/jira/browse/ISPN-241 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Mircea Markus Priority: Minor Fix For: 4.0.0.GA all replicate caches are being created through a TestCacheManagerFactory, TestCacheManagerFactory would make sure to call TransportType.setNodeName on each cache -- 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

13 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (ISPN-368) Remove code duplication in certain JDBC configuration classes

by Manik Surtani (JIRA)

Remove code duplication in certain JDBC configuration classes ------------------------------------------------------------- Key: ISPN-368 URL: https://jira.jboss.org/jira/browse/ISPN-368 Project: Infinispan Issue Type: Task Components: Loaders and Stores Affects Versions: 4.0.0.Final Reporter: Manik Surtani Assignee: Mircea Markus Priority: Minor Fix For: 4.1.0.CR1, 4.1.0.Final JdbcStringBasedCacheStoreConfig, JdbcBinaryCacheStoreConfig and JdbcMixedCacheStoreConfig duplicate a lot of code, including javadocs. Could these not inherit from an abstract superclass? -- 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

13 years, 10 months

1
2
0 / 0

[JBoss JIRA] Created: (ISPN-123) Build demo and blog about using Infinispan on EC2

by Manik Surtani (JIRA)

Build demo and blog about using Infinispan on EC2 ------------------------------------------------- Key: ISPN-123 URL: https://jira.jboss.org/jira/browse/ISPN-123 Project: Infinispan Issue Type: Feature Request Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.0.0.BETA1, 4.0.0.GA This will require the use of FILE_PING in JGroups 2.8 as a discovery mechanism. Critical to show the world that Infinispan + JGroups *can* do auto-discovery on EC2. Potentially also use S3 as a cache store for this demo. -- 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

13 years, 10 months

3
12
0 / 0

[JBoss JIRA] Created: (ISPN-350) Improve evenness of distribution

by Manik Surtani (JIRA)

Improve evenness of distribution -------------------------------- Key: ISPN-350 URL: https://jira.jboss.org/jira/browse/ISPN-350 Project: Infinispan Issue Type: Feature Request Components: Distributed Cache Affects Versions: 4.0.0.CR4 Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.Final On this 8-node run, compare the stats measured on each node when using Infinispan: 2010-02-12 07:03:59,123 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 4 we had 9,739 requests per second 2010-02-12 07:03:59,123 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 7 we had 3,634 requests per second 2010-02-12 07:03:59,123 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 1 we had 2,966 requests per second 2010-02-12 07:03:59,123 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 3 we had 2,935 requests per second 2010-02-12 07:03:59,124 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 2 we had 2,930 requests per second 2010-02-12 07:03:59,124 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 5 we had 2,925 requests per second 2010-02-12 07:03:59,124 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 6 we had 2,922 requests per second 2010-02-12 07:03:59,124 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 0 we had 2,910 requests per second against <a popular proprietary product>: 2010-02-12 06:43:44,747 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 1 we had 12,188 requests per second 2010-02-12 06:43:44,748 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 7 we had 12,001 requests per second 2010-02-12 06:43:44,748 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 0 we had 11,978 requests per second 2010-02-12 06:43:44,748 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 5 we had 11,967 requests per second 2010-02-12 06:43:44,748 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 3 we had 11,994 requests per second 2010-02-12 06:43:44,749 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 6 we had 11,961 requests per second 2010-02-12 06:43:44,749 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 4 we had 11,983 requests per second 2010-02-12 06:43:44,749 [main] INFO [org.cachebench.stages.WebSessionBenchmarkStage] On slave 2 we had 11,814 requests per second This is due to the fact that keys are inequally distributed and some nodes have to deal with greater load than others. We need to revisit the bit spreaders we use as well as the way we place nodes on a hash wheel and try and improve on this. Virtual nodes may help as well, although that adds significant complexity to the distribution implementation. -- 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

13 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (ISPN-232) add service to provide key that would map to the same (Specified) node

by Mircea Markus (JIRA)

add service to provide key that would map to the same (Specified) node ---------------------------------------------------------------------- Key: ISPN-232 URL: https://jira.jboss.org/jira/browse/ISPN-232 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani background: in order to obtain a hashcode that maps to the current node, the way to go is to generate random keys and pass them to the hashing algorithm until the hash for one of them will match the node. This JIRA is about creating an async service to do that, so that the calling thread won't be blocked while this happens. -------------------- from an email discussion What about adding a service to asynchronously generate and pool a number of ids that map to a certain node (in our use case same node)? Advantage would be that the calling thread won't have to wait until we determine an appropriate value. ----------- -- 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

13 years, 11 months

3
9
0 / 0

[JBoss JIRA] Created: (ISPN-172) Build a Java-based smart client that makes use of the HotRod protocol

by Manik Surtani (JIRA)

Build a Java-based smart client that makes use of the HotRod protocol --------------------------------------------------------------------- Key: ISPN-172 URL: https://jira.jboss.org/jira/browse/ISPN-172 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Manik Surtani Assignee: Manik Surtani Fix For: 4.1.0.BETA1, 4.1.0.GA This will speak the HotRod protocol to communicate with the HotRod server module. Will be used as a reference implementation for clients in other languages as well so needs to be cleanly written and very well commented/documented. -- 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

13 years, 11 months

3
8
0 / 0

[JBoss JIRA] Created: (ISPN-370) clear the store before state transfer

by Mircea Markus (JIRA)

clear the store before state transfer -------------------------------------- Key: ISPN-370 URL: https://jira.jboss.org/jira/browse/ISPN-370 Project: Infinispan Issue Type: Feature Request Reporter: Mircea Markus Assignee: Manik Surtani Fix For: 4.0.1.CR1 Right now, before integrating state (fetch persistent state = true) the cacheStore.clear() is performed within cacheStore. This cacheStore.clear() should be moved outside the store, in StateTransferManager, and state transfer should document that the the store is cleared before integrating remote state. This is in relation to: http://lists.jboss.org/pipermail/infinispan-dev/2010-March/002483.html -- 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

13 years, 11 months

2
3
0 / 0

[JBoss JIRA] Created: (ISPN-384) Implement topology and hash distribution headers in Hot Rod

by Galder Zamarreno (JIRA)

Implement topology and hash distribution headers in Hot Rod ----------------------------------------------------------- Key: ISPN-384 URL: https://jira.jboss.org/jira/browse/ISPN-384 Project: Infinispan Issue Type: Task Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 Implement Topology-Aware Client Topology Change and Hash-Distribution-Aware Client Topology Change headers. -- 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

14 years

1
5
0 / 0

[JBoss JIRA] Created: (ISPN-243) Update developer wiki with Eclipse m2eclipse tips

by Galder Zamarreno (JIRA)

Update developer wiki with Eclipse m2eclipse tips ------------------------------------------------- Key: ISPN-243 URL: https://jira.jboss.org/jira/browse/ISPN-243 Project: Infinispan Issue Type: Task Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.0.0.GA Update http://www.jboss.org/community/wiki/InfinispanQuickStartGuideforDevelopers with the following tips for Eclipse: - Do not use mvn eclipse:eclipse but instead of m2eclipse - Tips for m2eclipse: - Use external maven installation instead of embedded one, otherwise you might get some errors with regards to not understand the jre constraints in the pom.xml - Go to project's classpath and remove excludes for src/test/resources and src/main/resources, otherwise files in these folders won't be loaded and tests will fail. -- 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

14 years

2
4
0 / 0

[JBoss JIRA] Created: (ISPN-388) Cache view rank on a ViewChange listener for Hot Rod version generation

by Galder Zamarreno (JIRA)

Cache view rank on a ViewChange listener for Hot Rod version generation ----------------------------------------------------------------------- Key: ISPN-388 URL: https://jira.jboss.org/jira/browse/ISPN-388 Project: Infinispan Issue Type: Feature Request Components: Cache Server Reporter: Galder Zamarreno Assignee: Galder Zamarreno Fix For: 4.1.0.BETA1 Hot Rod server generates version numbers for cache entries based on the JGroups view id and view rank which is the location of the current server in that view. Currently, this rank is calculated whenever a new version is generated but this is quite wasteful. The view rank could be calculated upon a view change and reused until there's a new view change. This would speed up version generation. -- 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

14 years

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2010