January 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-3522) Upgrade to c3p0 version 0.9.2.1

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3522?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3522: -------------------------------- Component/s: Server > Upgrade to c3p0 version 0.9.2.1 > ------------------------------- > > Key: ISPN-3522 > URL: https://issues.jboss.org/browse/ISPN-3522 > Project: Infinispan > Issue Type: Component Upgrade > Components: Server > Affects Versions: 6.0.0.Alpha4 > Reporter: Dan Berindei > Assignee: Dan Berindei > > We are currently using c3p0 version 0.9.1.2, which is the last version with the {{c3p0}} group id. We should upgrade to the latest stable version, 0.9.2.1: http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22com.mchange%22%20AND%2... > AFAIK version 0.9.2.1 does not solve the concurrency issue in ISPN-3324, but it may solve other problems. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3661) Allow getting entry for key and suggesting it is placed into L1 cache

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3661?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3661: -------------------------------- Assignee: William Burns (was: Mircea Markus) > Allow getting entry for key and suggesting it is placed into L1 cache > --------------------------------------------------------------------- > > Key: ISPN-3661 > URL: https://issues.jboss.org/browse/ISPN-3661 > Project: Infinispan > Issue Type: Enhancement > Components: L1 > Reporter: Randall Hauch > Assignee: William Burns > > When running a distributed cache, some entries are far more popular and keeping them in L1 cache on all/most nodes would enable far better locality. This can be done with a custom hashing algorithm, except when the keys do not have enough information for the algorithm to know which entries should be placed into L1. Therefore, Infinispan should offer a way for clients to get an entry by key and simultaneously request that the resulting entry be placed into the local L1 cache. For example, perhaps {{get(K key, boolean cache)}} or even {{Cache.getL1cache().get(K key)}}. > Here's a concrete example. ModeShape stores a tree structure in Infinispan, with keys that are basically UUIDs + other information. A common access pattern is to navigate from the root node, so it would be very useful to have the top nodes locally cached in L1 on each of the processes in the cluster (as they are accessed). ModeShape knows during access where in the tree the node is, and thus can decide the node is high enough in the tree that the node's entry be cached into L1. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3675) Revisit covariant return type for various implementations

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3675?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3675: -------------------------------- Component/s: Core > Revisit covariant return type for various implementations > --------------------------------------------------------- > > Key: ISPN-3675 > URL: https://issues.jboss.org/browse/ISPN-3675 > Project: Infinispan > Issue Type: Enhancement > Components: Core > Affects Versions: 6.0.0.CR1 > Reporter: William Burns > Assignee: Mircea Markus > > We use interfaces all over the place, which is great. However a lot of implementations currently only define their return types to be that of the type defined in the interface. However we can change the implementation return type of the method to be covariant which allows for direct users of the implementation to use the subclass if desired. > This especially came up in the discussion here: https://github.com/infinispan/infinispan/pull/2177/files#r7375883 as we could remove redundant casts which would provide cleaner 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3661) Allow getting entry for key and suggesting it is placed into L1 cache

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3661?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3661: -------------------------------- Component/s: L1 > Allow getting entry for key and suggesting it is placed into L1 cache > --------------------------------------------------------------------- > > Key: ISPN-3661 > URL: https://issues.jboss.org/browse/ISPN-3661 > Project: Infinispan > Issue Type: Enhancement > Components: L1 > Reporter: Randall Hauch > Assignee: Mircea Markus > > When running a distributed cache, some entries are far more popular and keeping them in L1 cache on all/most nodes would enable far better locality. This can be done with a custom hashing algorithm, except when the keys do not have enough information for the algorithm to know which entries should be placed into L1. Therefore, Infinispan should offer a way for clients to get an entry by key and simultaneously request that the resulting entry be placed into the local L1 cache. For example, perhaps {{get(K key, boolean cache)}} or even {{Cache.getL1cache().get(K key)}}. > Here's a concrete example. ModeShape stores a tree structure in Infinispan, with keys that are basically UUIDs + other information. A common access pattern is to navigate from the root node, so it would be very useful to have the top nodes locally cached in L1 on each of the processes in the cluster (as they are accessed). ModeShape knows during access where in the tree the node is, and thus can decide the node is high enough in the tree that the node's entry be cached into L1. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3119) Cleanup the scripts we ship with the distribution

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3119?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-3119. --------------------------------- Resolution: Rejected we're now using the AS to bootstrap the servers > Cleanup the scripts we ship with the distribution > -------------------------------------------------- > > Key: ISPN-3119 > URL: https://issues.jboss.org/browse/ISPN-3119 > Project: Infinispan > Issue Type: Task > Reporter: Mircea Markus > Assignee: Mircea Markus > > Make sure that all the scripts we ship as part of the distribution are correct. Also update the [release process| https://docspace.corp.redhat.com/docs/DOC-28594] with exact stept to test the scripts we ship, e.g. > {quote} > 1. memcached server > $ ./startServer.sh -r memcached > # from a different console test the client > $ ./memcache.py > - ./bin/startServer.sh -r memcached > 2. Pi approximation demo. Open 3 consoles on the same machine > $ ./runPiApproximationDemo.sh > $ ./runPiApproximationDemo.sh > $ ./runPiApproximationDemo.sh -t master > {quote} > -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3104) org.infinispan.statetransfer.BaseStateTransferManagerImpl#applyState uses local invocation context

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3104?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3104: -------------------------------- Component/s: State transfer > org.infinispan.statetransfer.BaseStateTransferManagerImpl#applyState uses local invocation context > -------------------------------------------------------------------------------------------------- > > Key: ISPN-3104 > URL: https://issues.jboss.org/browse/ISPN-3104 > Project: Infinispan > Issue Type: Feature Request > Components: State transfer > Affects Versions: 5.1.6.FINAL > Reporter: Vitalii Tymchyshyn > Assignee: Mircea Markus > > Currently when remote state is received, it's applied under local invocation context, so every listener receives events with isOriginLocal() == true that is not correct. > We are trying to prevent any cache modification while we are not quorum to prevent split brain problems, but currently it's not working because of the problem. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3110) create tests to show the serialisation protocol at work

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3110?page=com.atlassian.jira.plugin.... ] Mircea Markus resolved ISPN-3110. --------------------------------- Resolution: Rejected > create tests to show the serialisation protocol at work > ------------------------------------------------------- > > Key: ISPN-3110 > URL: https://issues.jboss.org/browse/ISPN-3110 > Project: Infinispan > Issue Type: Sub-task > Reporter: Mircea Markus > Assignee: Mircea Markus > > - e.g. Person class written through a C++/C# hotrod client the read from an embedded Java client or hotrod client > = e.g. Person class written through a Memcached client the read from an embedded Java or Java hotrod client -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3098) Check if TOA is working properly when a node crashes

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3098?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3098: -------------------------------- Component/s: Core > Check if TOA is working properly when a node crashes > ---------------------------------------------------- > > Key: ISPN-3098 > URL: https://issues.jboss.org/browse/ISPN-3098 > Project: Infinispan > Issue Type: Task > Components: Core > Reporter: Pedro Ruivo > Assignee: Pedro Ruivo > Priority: Minor > > Check if TOA is working properly when a node crashes -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3634) Clean up StateTransferDistSharedCacheLoaderFunctionalTest test

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3634?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3634: -------------------------------- Component/s: Test Suite - Core > Clean up StateTransferDistSharedCacheLoaderFunctionalTest test > -------------------------------------------------------------- > > Key: ISPN-3634 > URL: https://issues.jboss.org/browse/ISPN-3634 > Project: Infinispan > Issue Type: Task > Components: Test Suite - Core > Reporter: William Burns > Assignee: William Burns > > There are still some comments on https://github.com/infinispan/infinispan/pull/2157 that need to be addressed. The test itself passes, this just some housekeeping on the test itself. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-3142) RehashAfterPartitionMergeTest.testCachePartition fails intermittently

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3142?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3142: -------------------------------- Component/s: Test Suite - Core > RehashAfterPartitionMergeTest.testCachePartition fails intermittently > ----------------------------------------------------------------------- > > Key: ISPN-3142 > URL: https://issues.jboss.org/browse/ISPN-3142 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Core > Reporter: Mircea Markus > Assignee: Dan Berindei > Labels: testsuite_stability > > As per Dan, this should be fixed indirectly by ISPN-2577. -- 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, 2 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 January 2014