March 2014 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-4071) Switch to automated generation of RHQ plugin for server

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/ISPN-4071?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated ISPN-4071: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1072349 > Switch to automated generation of RHQ plugin for server > ------------------------------------------------------- > > Key: ISPN-4071 > URL: https://issues.jboss.org/browse/ISPN-4071 > Project: Infinispan > Issue Type: Enhancement > Affects Versions: 7.0.0.Alpha1 > Reporter: Tomas Sykora > Assignee: Mircea Markus > Priority: Minor > > InVM plugin for RHQ is generated automatically. However, the plugin for server is not and therfore, it is easy to miss some of the possible management operations. > The principal intention is to automate server plugin generation and avoid the case when we are missing any of possible operations/metrics/traits due to out of synchronization of code vs rhq-plugin.xml file. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4071) Switch to automated generation of RHQ plugin for server

by Tomas Sykora (JIRA)

Tomas Sykora created ISPN-4071: ---------------------------------- Summary: Switch to automated generation of RHQ plugin for server Key: ISPN-4071 URL: https://issues.jboss.org/browse/ISPN-4071 Project: Infinispan Issue Type: Enhancement Affects Versions: 7.0.0.Alpha1 Reporter: Tomas Sykora Assignee: Mircea Markus Priority: Minor InVM plugin for RHQ is generated automatically. However, the plugin for server is not and therfore, it is easy to miss some of the possible management operations. The principal intention is to automate server plugin generation and avoid the case when we are missing any of possible operations/metrics/traits due to out of synchronization of code vs rhq-plugin.xml file. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4070) Server plugin for RHQ needs extensions in management/monitoring

by Tomas Sykora (JIRA)

Tomas Sykora created ISPN-4070: ---------------------------------- Summary: Server plugin for RHQ needs extensions in management/monitoring Key: ISPN-4070 URL: https://issues.jboss.org/browse/ISPN-4070 Project: Infinispan Issue Type: Bug Components: JMX, reporting and management Affects Versions: 6.0.1.Final Reporter: Tomas Sykora Assignee: Mircea Markus InVM plugin for RHQ is generated automatically. However, the plugin for server is not and those are results of deeper analysis of RHQ ISPN server plugin (missing) possibilities. JCONSOLE is showing number of statistics, traits and operations which are not incorporated in RHQ-plugin (*server* plugin). Some are quite important (start and stop ops for cache for example) and some might be only additional, not necessary - but still pleasant, information about a cluster/cache. *Missing Cache traits:* cacheName version configurationAsProperties statisticsEnabled *Missing from Cache statistics:* averageRemoveTime *Missing cache operations:* START and STOP are missing!! synchronizeData, disconnectSource, recordKnownGlobalKeyset - rolling upgrades related ops *Missing cache manager traits:* definedCacheCount globalConfigurationAsProperties clusterMembers createdCacheCounts definedCacheNames clusterSize version runningCacheCount -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-3338) DistributionManager operations Locate key & Is key local are not working properly

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-3338?page=com.atlassian.jira.plugin.... ] Martin Gencur updated ISPN-3338: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/2412 > DistributionManager operations Locate key & Is key local are not working properly > --------------------------------------------------------------------------------- > > Key: ISPN-3338 > URL: https://issues.jboss.org/browse/ISPN-3338 > Project: Infinispan > Issue Type: Bug > Components: JMX, reporting and management > Environment: Tested localy Fedora16 > Reporter: Tomas Sykora > Assignee: Mircea Markus > > Testing infinispan-rhq-plugin (for InVM). > DistributionManager operations Locate key & Is key local seem not to working properly. For a nonsense key Locate key operation is returning success with result of a label for cache "home node". > Is key local operation for nonsense key is returning TRUE which is obviously wrong. This happens even on totally clear, entry-free, cache. > Operation Could key be affected by a rehash is returning operation success with result false. This is questionable whether it should return failure or not. Again, for nonsense key. > Please can anyone look at it? > I don't think this is directly jon/plugin related. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4069) maxKeysInMemory in infinispan config schema probably wrong

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4069?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4069: ------------------------------------ The schema is incorrect. {{maxKeysInMemory}} is the original name of the attribute, but we decided to rename it because the "extra" keys are removed from the file as well as from memory. > maxKeysInMemory in infinispan config schema probably wrong > ---------------------------------------------------------- > > Key: ISPN-4069 > URL: https://issues.jboss.org/browse/ISPN-4069 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 6.0.0.Final > Environment: jdk 1.7_45 > Infinispan 6.0.0.FInal > Reporter: Stanislav Ivanov > Assignee: Dan Berindei > Labels: configuration > > Probably there is a bug on 1684 line of infinispan-config-6.0.xsd: > {{<xs:attribute name="maxKeysInMemory" type="xs:int" default="-1">}} > When I use this attribute in configuration xml file, I get this: > {code:title=Exception} > javax.xml.stream.XMLStreamException: ParseError at [row,col]:[9,13] > Message: Unexpected attribute 'maxKeysInMemory' encountered > {code} > Actually, {{maxKeysInMemory}} seems very similar to {{maxEntries}}, which was mentioned in user guide and which is missing in the schema. > If I change {{maxKeysInMemory}} to {{maxEntries}}, everything works fine. > Were you planning to change the schema? > Probably you forgot to update the 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4069) maxKeysInMemory in infinispan config schema probably wrong

by Stanislav Ivanov (JIRA)

Stanislav Ivanov created ISPN-4069: -------------------------------------- Summary: maxKeysInMemory in infinispan config schema probably wrong Key: ISPN-4069 URL: https://issues.jboss.org/browse/ISPN-4069 Project: Infinispan Issue Type: Bug Components: Configuration Affects Versions: 6.0.0.Final Environment: jdk 1.7_45 Infinispan 6.0.0.FInal Reporter: Stanislav Ivanov Assignee: Dan Berindei Probably there is a bug on 1684 line of infinispan-config-6.0.xsd: {{<xs:attribute name="maxKeysInMemory" type="xs:int" default="-1">}} When I use this attribute in configuration xml file, I get this: {code:title=Exception} javax.xml.stream.XMLStreamException: ParseError at [row,col]:[9,13] Message: Unexpected attribute 'maxKeysInMemory' encountered {code} Actually, {{maxKeysInMemory}} seems very similar to {{maxEntries}}, which was mentioned in user guide and which is missing in the schema. If I change {{maxKeysInMemory}} to {{maxEntries}}, everything works fine. Were you planning to change the schema? Probably you forgot to update the 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

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4011) Make it possible to use 'remote-jmx' protocol inside Karaf

by Martin Gencur (JIRA)

[ https://issues.jboss.org/browse/ISPN-4011?page=com.atlassian.jira.plugin.... ] Martin Gencur commented on ISPN-4011: ------------------------------------- remoting-jmx library uses Xnio which is currently not compatible with OSGi. The linked JIRA describes the issue and already has a fix inmplemented. However, the pull request has been open for a long time without any response. > Make it possible to use 'remote-jmx' protocol inside Karaf > ---------------------------------------------------------- > > Key: ISPN-4011 > URL: https://issues.jboss.org/browse/ISPN-4011 > Project: Infinispan > Issue Type: Feature Request > Reporter: Adrian Nistor > Assignee: Martin Gencur > Fix For: 7.0.0.Final > > > This is needed so remote-query clients can register protobuf schemas via jmx. Currently this was circumvented by creating a separate stand-alone app (ProtofileRegistrar) that runs outside Karaf before the actual test. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4022) M/R: Run the combiner concurrently with the mapper

by Dan Berindei (JIRA)

[ https://issues.jboss.org/browse/ISPN-4022?page=com.atlassian.jira.plugin.... ] Dan Berindei commented on ISPN-4022: ------------------------------------ +1. Shipping the intermediate values to the reducer node after each chunk is produced should help even without a combiner. > M/R: Run the combiner concurrently with the mapper > -------------------------------------------------- > > Key: ISPN-4022 > URL: https://issues.jboss.org/browse/ISPN-4022 > Project: Infinispan > Issue Type: Feature Request > Components: Core, Distributed Execution and Map/Reduce > Affects Versions: 6.0.1.Final > Reporter: Dan Berindei > Assignee: Vladimir Blagojevic > Fix For: 7.0.0.Final > > > Because we only run the combiner after we finished the mapping phase, we need to keep all the results of the mapping phase in memory at once. We should split the output of the mapper into chunks and allow the combiner to process chunks while the mapper is still running, relieving some of the memory pressure. Maybe even block the mapper if there are too many chunks in-flight. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4068) Add support for IncludeCurrentState to listeners

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4068?page=com.atlassian.jira.plugin.... ] Work on ISPN-4068 started by William Burns. > Add support for IncludeCurrentState to listeners > ------------------------------------------------ > > Key: ISPN-4068 > URL: https://issues.jboss.org/browse/ISPN-4068 > Project: Infinispan > Issue Type: Feature Request > Components: Listeners > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Final > > > Cluster listeners were added with ISPN-3355. This didn't cover the includeInitialState support. This should be able to work with both local and cluster listeners. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (ISPN-4068) Add support for IncludeCurrentState to listeners

by William Burns (JIRA)

[ https://issues.jboss.org/browse/ISPN-4068?page=com.atlassian.jira.plugin.... ] William Burns reassigned ISPN-4068: ----------------------------------- Assignee: William Burns (was: Dan Berindei) > Add support for IncludeCurrentState to listeners > ------------------------------------------------ > > Key: ISPN-4068 > URL: https://issues.jboss.org/browse/ISPN-4068 > Project: Infinispan > Issue Type: Feature Request > Components: Listeners > Reporter: William Burns > Assignee: William Burns > Fix For: 7.0.0.Final > > > Cluster listeners were added with ISPN-3355. This didn't cover the includeInitialState support. This should be able to work with both local and cluster listeners. -- 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, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues March 2014