June 2019 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-9620) Rolling Upgrade Marshaller Changes

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9620?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9620: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, JDG Sprint #29 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, JDG Sprint #31) > Rolling Upgrade Marshaller Changes > ---------------------------------- > > Key: ISPN-9620 > URL: https://issues.jboss.org/browse/ISPN-9620 > Project: Infinispan > Issue Type: Enhancement > Components: Core, Loaders and Stores > Affects Versions: 9.4.0.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta4 > > > In order to allow for compatibility between infinispan versions it is necessary for us to utilise a marshalling implementation at both the cluster (internal node-to-node communication) and persistence layer that is strictly defined but allows for future changes. This is necessary in order to facilitate both rolling and start/stop upgrades. Protocol buffers should be utilised as the wire/storage format, with protostream providing the implementation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-5997) JMX operation ClusterCacheStats.resetStatistics() not working

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-5997?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-5997: ---------------------------------- Sprint: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 9.4.0.Beta1, Sprint 9.4.0.CR1, Sprint 9.4.0.CR3, Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 9.4.0.Final, Sprint 10.0.0.Alpha0, Sprint 10.0.0.Beta1) > JMX operation ClusterCacheStats.resetStatistics() not working > ------------------------------------------------------------- > > Key: ISPN-5997 > URL: https://issues.jboss.org/browse/ISPN-5997 > Project: Infinispan > Issue Type: Bug > Components: Server > Affects Versions: 8.1.0.CR1 > Reporter: Jiří Holuša > Assignee: Vladimir Blagojevic > Priority: Major > > Environment: 2 servers started in domain mode (ISPN 8.1.0.CR1). > Having some clustered cache, inserted/read some entries (just to create some statistics). > When connected via JMX (e.g. through JConsole, see https://issues.jboss.org/browse/ISPN-5983 ) to one of the servers, I execute resetStatistics() operation on ClusterCacheStats MBean (object name: jboss.datagrid-infinispan:type=Cache,name="<cache-name>",manager="<cache-container-name>",component=ClusterCacheStats) and nothing happens, the cluster statistics are not reset. > To actually reset the statistics, I have to connect to each of the servers in domain individually and call resetStatistics() on Statistics MBean, which deletes "a portion" of statistics of that particular server to the cluster stats. > I would expect ClusterCacheStats.resetStatistics() to do exactly the same: call Statistics.resetStatistics() on each server. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8535) Rest API redesign

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-8535?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-8535: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1) > Rest API redesign > ----------------- > > Key: ISPN-8535 > URL: https://issues.jboss.org/browse/ISPN-8535 > Project: Infinispan > Issue Type: Feature Request > Components: Server > Affects Versions: 9.2.0.Final > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > Fix For: 10.0.0.Final > > > Infinispan REST API deals with only one resource, (the cache) and maps all operations on the cache using HTTP verbs and request parameters. The API assumes the URI is related to the cache making it hard to add new kinds of resources without causing ambiguous references. > Since we now have other types of entities, such as counters, scripts, templates, etc, and each one of them can involve different operations, we should make the API more "Restful" by using more than one resource and collections of resources, plus HTTP verbs and operations on them. Examples: > * Create a cache: POST /rest/caches > * Delete a cache: DELETE /rest/caches/myCache > * Create a template: POST /rest/templates > * Delete a template: DELETE /rest/templates/myTemplate > * Create an entry: POST /rest/caches/myCache/1 > * Create a counter: POST /rest/counters > * Get a counter value: GET /rest/counters/mycounter > * Increment a counter: GET /rest/counters/mycounter?action=increment > * Search a cache: GET /rest/caches/myCache?action=search > * Create a script: POST /rest/scripts/ > * Get a script source: GET /rest/scritps/myScript > * Execute a script: GET /rest/scripts/myScript?action=execute&param1=foo > * Stop individual servers and the full cluster > -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9659) Document the Docker image and how to use it in Kubernetes/OpenShift

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9659?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9659: ---------------------------------- Sprint: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Alpha1, Sprint 10.0.0.Alpha2, Sprint 10.0.0.Beta1) > Document the Docker image and how to use it in Kubernetes/OpenShift > ------------------------------------------------------------------- > > Key: ISPN-9659 > URL: https://issues.jboss.org/browse/ISPN-9659 > Project: Infinispan > Issue Type: Task > Components: Documentation-Core > Reporter: Tristan Tarrant > Assignee: Gustavo Fernandes > Priority: Major > > Expand/modernize https://blog.infinispan.org/2016/08/running-infinispan-cluster-on-kuberne... and push it to the main docs. > Also document how to run the simple tutorials against this. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9990) Integrationtests missing java.se module

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9990?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9990: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Beta1) > Integrationtests missing java.se module > --------------------------------------- > > Key: ISPN-9990 > URL: https://issues.jboss.org/browse/ISPN-9990 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 10.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.10.Final, 10.0.0.Beta3 > > > standalone.sh adds the required {{--add-modules java.se}} to the JVM args for most tests, however if the the container is managed by the test this is not present. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9991) infinispan-remote integration tests inconsistent naming

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9991?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9991: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Beta1) > infinispan-remote integration tests inconsistent naming > ------------------------------------------------------- > > Key: ISPN-9991 > URL: https://issues.jboss.org/browse/ISPN-9991 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 10.0.0.Beta1 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta3 > > > RemoteAllTest and JCacheFailoverIT results in tests not being executed together, but as separate lifecycle, results in no logs being saved for RemoteAllTest -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10142) Wildfly modules integrationtests ignore branding

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-10142?page=com.atlassian.jira.plugin... ] Tristan Tarrant updated ISPN-10142: ----------------------------------- Sprint: Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Beta1) > Wildfly modules integrationtests ignore branding > ------------------------------------------------ > > Key: ISPN-10142 > URL: https://issues.jboss.org/browse/ISPN-10142 > Project: Infinispan > Issue Type: Bug > Components: Test Suite - Server > Affects Versions: 9.4.12.Final, 10.0.0.Beta3 > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Labels: testsuite_failure > Fix For: 9.4.14.Final, 10.0.0.Beta4 > > > {{standalone-test.xml}} uses module {{org.infinispan.extension:ispn-${infinispan.core.schema.version}}}, ignoring the branding. The module name should be {{org.infinispan.extension:${infinispan.module.slot}}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9932) Avoid creating MarshallableEntry instances if no CacheWriter enabled

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9932?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9932: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Beta1) > Avoid creating MarshallableEntry instances if no CacheWriter enabled > -------------------------------------------------------------------- > > Key: ISPN-9932 > URL: https://issues.jboss.org/browse/ISPN-9932 > Project: Infinispan > Issue Type: Enhancement > Components: Loaders and Stores > Affects Versions: 10.0.0.Alpha3 > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 10.0.0.Beta1 > > > The (Dist)CacheWriterIntercepter is enabled if any loader/store is configured. The problem, is that the interceptor assumes that a CacheWriter is always configured. However, it is possible that only a CacheLoader has been configured, in which case when a write command visits the interceptor, MarshallableEntry instances are created unnecessarily in order to call the various PersistenceManager write operations. > To avoid unnecessary allocations and the marshalling of key/value/metadata that is never stored, we should ensure that calls to PersistenceManager write methods are only called if a CacheWriter is actually configured. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9962) Feature-packs should optionally depend on jdk-unsupported and sun.jdk

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9962?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9962: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Beta1) > Feature-packs should optionally depend on jdk-unsupported and sun.jdk > --------------------------------------------------------------------- > > Key: ISPN-9962 > URL: https://issues.jboss.org/browse/ISPN-9962 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 10.0.0.Alpha3, 9.4.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final, 10.0.0.Beta1 > > > Currently our feature-packs depend on both "sun.jdk" and "jdk.unsupported" in an inconsistent manner. For the latest versions of Wildfly, we need to use the latter, whilst for older ones we need to use the former. Therefore, for all modules that require access to unsupported classes, we must provide an optional dependency on both of the above modules. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ISPN-9964) Logging incompatibility when deploying modules on older versions of WildFly

by Tristan Tarrant (Jira)

[ https://issues.jboss.org/browse/ISPN-9964?page=com.atlassian.jira.plugin.... ] Tristan Tarrant updated ISPN-9964: ---------------------------------- Sprint: Sprint 10.0.0.Beta1, JDG Sprint #31 (was: Sprint 10.0.0.Beta1) > Logging incompatibility when deploying modules on older versions of WildFly > --------------------------------------------------------------------------- > > Key: ISPN-9964 > URL: https://issues.jboss.org/browse/ISPN-9964 > Project: Infinispan > Issue Type: Bug > Components: WildFly modules > Affects Versions: 9.4.6.Final > Reporter: Ryan Emerson > Assignee: Ryan Emerson > Priority: Major > Fix For: 9.4.7.Final > > > Older versions of Wildfly 7.1.x still utilise jboss-logging 3.1.x, whereas the 9.4.x branch uses 3.3.x. Jboss-logging 3.3.x introduced several new method signatures, which results in a {{NoSuchMethodError}} being thrown when infinispan is embedded on a older wildfly version. -To overcome this, it is necessary to make sure that only the method signatures found in both jboss-logging 3.1.x and 3.3.x are utilised.- Explicitly including the required version of jboss-logging in the wildfly-modules ensures that no discrepancy exists. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 9 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 June 2019