[JBoss JIRA] (ISPN-3750) Configuration.toProperties
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3750?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3750:
--------------------------------
Labels: (was: 630)
> Configuration.toProperties
> --------------------------
>
> Key: ISPN-3750
> URL: https://issues.jboss.org/browse/ISPN-3750
> Project: Infinispan
> Issue Type: Feature Request
> Components: Configuration
> Affects Versions: 6.0.0.Final
> Reporter: Michal Linhard
> Assignee: Michal Linhard
> Fix For: 6.0.1.Final, 7.0.0.Alpha1, 7.0.0.Final
>
>
> I'd like to add methods
> Configuration.toProperties() and
> GlobalConfiguration.toProperties()
> that would return current configuration values in flat key value structure (e.g. java.util.Properties) where property keys would reflect names of configuration fields and structure would be reflected by extending the key prefix and dividing by dot. e.g. clustering.hash.numOwners=2
> The least intrusive and maintenance demanding implementation is via Reflection.
> The flat configuration would be exposed via JMX objects, e.g.
> jboss.infinispan:type=Cache,name="testCache(dist_sync)",manager="default",component=Cache
> attribute "configurationProperties"
> jboss.infinispan:type=CacheManager,name="default",component=CacheManager
> attribute "globalConfigurationProperties"
> This is a diagnostic output feature and doesn't affect the way how Infinispan is configured.
--
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
10 years
[JBoss JIRA] (ISPN-3947) HotRod client keep trying recover connections to a failed cluster
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3947?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3947:
--------------------------------
Labels: 621 630 hotrod hotrod-java-client (was: 621 hotrod hotrod-java-client)
> HotRod client keep trying recover connections to a failed cluster
> -----------------------------------------------------------------
>
> Key: ISPN-3947
> URL: https://issues.jboss.org/browse/ISPN-3947
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote Protocols
> Affects Versions: 6.0.1.Final, 7.0.0.Alpha1
> Reporter: Wolf-Dieter Fink
> Assignee: Galder Zamarreño
> Priority: Critical
> Labels: 621, 630, hotrod, hotrod-java-client
> Fix For: 7.0.0.Alpha1, 7.0.0.Final
>
>
> If an infinispan-server cluster is not longer reachable for some reason, i.e. network disconnect, the hot-rod client try to re-establish the lost connections.
> The client library will retry this by a fixed calculation based on the max numbers of connections from the pool or 10 multiplied with the number of available servers.
> This can lead in a very long time until the application can continue and react as it will wait for the read- or connect-timeout for each try.
> To improve this behaviour there should be a configurable limit of retries per server and/or a timeout in total.
> This will give the application the chance to handle a remote-cache failure and reply to the user instead of hanging for minutes (with the default settings)
--
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
10 years
[JBoss JIRA] (ISPN-3957) Preload with async cache store is not efficient
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3957?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3957:
--------------------------------
Labels: 621 630 (was: 621)
> Preload with async cache store is not efficient
> -----------------------------------------------
>
> Key: ISPN-3957
> URL: https://issues.jboss.org/browse/ISPN-3957
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 5.2.7.Final
> Reporter: Mircea Markus
> Assignee: Dan Berindei
> Labels: 621, 630
> Fix For: 5.2.8.Final, 7.0.0.Alpha1, 7.0.0.Final
>
>
> Configuring on a AdvancedCacheLoader preload=true and asyn=true cause it to load each entry in the store in a loop, each entry being loaded through an store read.
> This is caused by the way loadAll is implemented in the AsynLoader: in order to enforce consistency with whatever is in memory it does some special handling. The thing is, though, that we don't need this advanced async loader logic during the initial preload, as the async cache loader is empty.
--
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
10 years
[JBoss JIRA] (ISPN-2284) Execute Mapper and Reducer tasks in parallel where possible
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-2284?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-2284:
--------------------------------
Labels: 630 roadmap (was: roadmap)
> Execute Mapper and Reducer tasks in parallel where possible
> -----------------------------------------------------------
>
> Key: ISPN-2284
> URL: https://issues.jboss.org/browse/ISPN-2284
> Project: Infinispan
> Issue Type: Feature Request
> Components: Distributed Execution and Map/Reduce
> Affects Versions: 5.2.0.Alpha3
> Reporter: Vladimir Blagojevic
> Assignee: Vladimir Blagojevic
> Labels: 630, roadmap
> Fix For: 7.0.0.Alpha1, 7.0.0.Final
>
> Attachments: Infinispan-MapReduce Job Times.png
>
>
> In our current implementation of Map/Reduce, Mapper and Reducer tasks executed on remote JVMs load and process key/values serially on a single thread. Where and if possible we should use executors to process keys/values in parallel.
--
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
10 years
[JBoss JIRA] (ISPN-3750) Configuration.toProperties
by Mircea Markus (JIRA)
[ https://issues.jboss.org/browse/ISPN-3750?page=com.atlassian.jira.plugin.... ]
Mircea Markus updated ISPN-3750:
--------------------------------
Labels: 630 (was: )
> Configuration.toProperties
> --------------------------
>
> Key: ISPN-3750
> URL: https://issues.jboss.org/browse/ISPN-3750
> Project: Infinispan
> Issue Type: Feature Request
> Components: Configuration
> Affects Versions: 6.0.0.Final
> Reporter: Michal Linhard
> Assignee: Michal Linhard
> Labels: 630
> Fix For: 6.0.1.Final, 7.0.0.Alpha1, 7.0.0.Final
>
>
> I'd like to add methods
> Configuration.toProperties() and
> GlobalConfiguration.toProperties()
> that would return current configuration values in flat key value structure (e.g. java.util.Properties) where property keys would reflect names of configuration fields and structure would be reflected by extending the key prefix and dividing by dot. e.g. clustering.hash.numOwners=2
> The least intrusive and maintenance demanding implementation is via Reflection.
> The flat configuration would be exposed via JMX objects, e.g.
> jboss.infinispan:type=Cache,name="testCache(dist_sync)",manager="default",component=Cache
> attribute "configurationProperties"
> jboss.infinispan:type=CacheManager,name="default",component=CacheManager
> attribute "globalConfigurationProperties"
> This is a diagnostic output feature and doesn't affect the way how Infinispan is configured.
--
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
10 years