January 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-2862) Integrate the Self-tuning Data Placement from CloudTM into Infinispan

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2862?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2862: -------------------------------- Component/s: Core > Integrate the Self-tuning Data Placement from CloudTM into Infinispan > --------------------------------------------------------------------- > > Key: ISPN-2862 > URL: https://issues.jboss.org/browse/ISPN-2862 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Mircea Markus > Assignee: Pedro Ruivo > Attachments: autoplacer.pdf > > > With the same goal as L1 Cache, it applies a different technique to reduce the communication overhead. The self-tunning data placement detects which are the keys most accessed by each node, modifies the ConsistentHash and triggers the State Transfer in order to move the keys for that nodes. > The main difference for L1 Cache is the fact that L1 creates a new copy of the <key,value> in the requestor node, that needs to be invalidated later. The Data Placement, really moves the <key,value> to that requestor. > Both techniques can be enabled at the same time. > This module depends of ISPN-2861, namely the top-key module. -- 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-2877) TOA: review use of message batching and INTERNAL flags

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2877?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2877: -------------------------------- Component/s: Core > TOA: review use of message batching and INTERNAL flags > ------------------------------------------------------ > > Key: ISPN-2877 > URL: https://issues.jboss.org/browse/ISPN-2877 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Reporter: Bela Ban > Assignee: Pedro Ruivo > > Review TOA with focus on > * Implementation of message batching: up(MessageBatch) > * Are INTERNAL, DONT_BUNDLE and OOB flags used correctly ? > ** Note that as of 3.30.Beta1, DONT_BUNDLE is not strictly needed anymore > *** I suggest leave it in though, as I have to verify that [1] doesn't break this. I'll deprecate DONT_BUNDLE once [1] has been implemented and I've verified it doesn't need DONT_BUNDLE anymore. > [1] https://issues.jboss.org/browse/JGRP-1601 -- 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-2902) document exception handling in Infinispan

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-2902?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-2902: -------------------------------- Component/s: Documentation-Core > document exception handling in Infinispan > ----------------------------------------- > > Key: ISPN-2902 > URL: https://issues.jboss.org/browse/ISPN-2902 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Affects Versions: 5.2.3.Final > Reporter: Mircea Markus > Assignee: Mircea Markus > > Map/ConcurrentMap operations, as overridden by Infinispan, might throw various runtime exception to the user. These exceptions should be: > - documented (API) > - the user should be informed about what happens in the case of any such exceptions being thrown (e.g. the operation hasn't succeed an all nodes, the cache might be inconsistent, etc). This again should be added in the javadoc > (ISPN-629 did part of the job for TimeoutException) -- 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-58) Create a TaskQueueExecutorFactory and TaskQueueScheduledExecutorFactory

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-58?page=com.atlassian.jira.plugin.sy... ] Mircea Markus resolved ISPN-58. ------------------------------- Resolution: Rejected > Create a TaskQueueExecutorFactory and TaskQueueScheduledExecutorFactory > ----------------------------------------------------------------------- > > Key: ISPN-58 > URL: https://issues.jboss.org/browse/ISPN-58 > Project: Infinispan > Issue Type: Sub-task > Reporter: Manik Surtani > Assignee: Manik Surtani > Priority: Optional > > These executors will not spawn separate threads, but hook in to Google's TaskQueue API > http://code.google.com/appengine/docs/java/taskqueue/overview.html > This will enable Infinispan to run without spawning any additional threads, thereby enabling it to run on Google's App Engine runtime. > Will need to expose a URI (/taskqueueexecutor ?) which is invoked to process arbitrary Callable/Runnables. May need to use the DataStore to store the actual Callable/Runnable, and pass the taskqueueexecutor the key of the stored object. -- 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-959) Refactor documentation on wiki

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-959?page=com.atlassian.jira.plugin.s... ] Mircea Markus resolved ISPN-959. -------------------------------- Resolution: Out of Date > Refactor documentation on wiki > ------------------------------ > > Key: ISPN-959 > URL: https://issues.jboss.org/browse/ISPN-959 > Project: Infinispan > Issue Type: Task > Affects Versions: 5.0.0.FINAL > Reporter: Manik Surtani > Assignee: Manik Surtani > > This would take into account the new Confluence setup on docs.jboss.org, as well as docbook exporters and the ability to organise documentation as well as wiki pages based on versions of Infinispan. -- 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-1295) Deprecate transport properties and replace with configuration on transport itself

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1295?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1295: -------------------------------- Component/s: Configuration > Deprecate transport properties and replace with configuration on transport itself > --------------------------------------------------------------------------------- > > Key: ISPN-1295 > URL: https://issues.jboss.org/browse/ISPN-1295 > Project: Infinispan > Issue Type: Feature Request > Components: Configuration > Affects Versions: 5.0.0.CR8 > Reporter: Pete Muir > Assignee: Pete Muir > > Currently transport properties are detyped and confusing for users as it sounds like the should actually configure properties of the transport, not properties of 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, 2 months

1
0
0 / 0

[JBoss JIRA] (ISPN-1242) Add dynamic grouping capabilities for unmodifiable key classes.

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1242?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1242: -------------------------------- Component/s: Core > Add dynamic grouping capabilities for unmodifiable key classes. > --------------------------------------------------------------- > > Key: ISPN-1242 > URL: https://issues.jboss.org/browse/ISPN-1242 > Project: Infinispan > Issue Type: Feature Request > Components: Core > Affects Versions: 5.0.0.CR7 > Reporter: Erik Salter > Assignee: Pete Muir > > The grouping API should be enhanced to add grouping capabilities to a a cache's put() or replace() methods. > This encompasses the following scenario: > Cache A uses a custom key class where the group is dynamically generated. Cache B's key is an unmodifiable String that needs to be grouped with the dynamic value of a key from Cache A. (Cache B's key can't be encapsulated in a custom key class since it needs to be queried from external entities that will not know the group context). > And in pseudo-code: > {code} > Group class InternalResourceKey { > String group; > ... > @Group > String getGroup() { > return group; > } > } > InternalResourceKey key = new InternalResourceKey(); > {code} > ... > {code} > resourceCache.lock( key ); > // Get the previous result. > ResourceResult result = resourceCache.get( key ); > ResourceResult newResult = doWork( key, result ); > resourceCache.put( key, newResult ); > // I also want to group an external identifier that an external client knows about with the result so they will be on the same node > employeeCache.put( "111-111-1111", newResult, key.getGroup() ); > {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-1186) Document different approaches for working with cache statistics for local cache and remote cache (HotRod)

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1186?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1186: -------------------------------- Component/s: Documentation-Core > Document different approaches for working with cache statistics for local cache and remote cache (HotRod) > ---------------------------------------------------------------------------------------------------------- > > Key: ISPN-1186 > URL: https://issues.jboss.org/browse/ISPN-1186 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Affects Versions: 4.2.1.FINAL > Reporter: Martin Gencur > Assignee: Mircea Markus > Priority: Optional > > The documentation for Infinispan should mention different approaches for accessing remote cache (HotRod) and local (default) cache statistics. For example, there is not "evictions" statistics for remote cache. Maybe it would be enough to just mention different classes that hold these statistics (Stats and RemoteStatistics) and the way of getting them. > It should be mentioned most likely somewhere under http://community.jboss.org/wiki/infinispan -- 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-1279) Update links in documentation to point to 5.0 version of API docs

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-1279?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-1279: -------------------------------- Component/s: Documentation-Core > Update links in documentation to point to 5.0 version of API docs > ----------------------------------------------------------------- > > Key: ISPN-1279 > URL: https://issues.jboss.org/browse/ISPN-1279 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Martin Gencur > Assignee: Pete Muir > > Documents at https://docs.jboss.org/author/display/ISPN (user guide, tutorials, etc.) should point (via links) to newer API documentation (http://docs.jboss.org/infinispan/5.0/apidocs/). Now they point to 4.0 API docs. -- 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-3691) Make client side Connection refused error TRACE

by Mircea Markus (JIRA)

[ https://issues.jboss.org/browse/ISPN-3691?page=com.atlassian.jira.plugin.... ] Mircea Markus updated ISPN-3691: -------------------------------- Component/s: Remote protocols > Make client side Connection refused error TRACE > ----------------------------------------------- > > Key: ISPN-3691 > URL: https://issues.jboss.org/browse/ISPN-3691 > Project: Infinispan > Issue Type: Feature Request > Components: Remote protocols > Affects Versions: 6.0.0.CR1, 6.0.0.Final > Reporter: Michal Linhard > Assignee: Mircea Markus > Priority: Minor > > After solving ISPN-3454, it seems that only remaining client-side error during node crashes is "Connection refused": > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JDG/view/RESILIENCE... > This has been reported before as ISPN-1794 or ISPN-1119, but actually it seems like it reappeared in different place. > Sorry for not reporting sooner, I got used to ignoring some of the long-open cosmetic low-prio log message issues, that I forgot about this one... > The issue here is that these "Connection refused" problems are retry-able, so the client log shouldn't contain error. > Maybe only some info level message about failing over to different node. But that's actually already reported by the INFO level messages about the topology changes -- 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