November 2019 - infinispan-issues

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

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-9620?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes edited comment on ISPN-9620 at 11/4/19 2:34 AM: ------------------------------------------------------------------ "Protocol buffers should be utilised as the wire/storage format, with protostream providing the implementation." Not sure I understand this, as a server can store data in any format: JBoss marshalled, UTF-8, protostream, octect-stream, etc. When migrating data from a cluster to another via Rolling Upgrade, it all happens via Hot Rod with "raw" data, that is, data is iterated in the source cluster and stored in the new cluster in the same format as its stored. was (Author: gustavonalle): "Protocol buffers should be utilised as the wire/storage format, with protostream providing the implementation." Not sure I understand this, as a server can store data in any format: jboss marshalled, UTF-8, protostream, octect-stream, etc. When migrating data from a cluster to another via Rolling Upgrade, it all happens via Hot Rod with "raw" data, that is, data is iterated in the source cluster and stored in the new cluster in the same format as its stored. > 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.1.0.Final > > > 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.13.8#713008)

4 years, 5 months

1
0
0 / 0

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

by Gustavo Fernandes (Jira)

[ https://issues.jboss.org/browse/ISPN-9620?page=com.atlassian.jira.plugin.... ] Gustavo Fernandes commented on ISPN-9620: ----------------------------------------- "Protocol buffers should be utilised as the wire/storage format, with protostream providing the implementation." Not sure I understand this, as a server can store data in any format: jboss marshalled, UTF-8, protostream, octect-stream, etc. When migrating data from a cluster to another via Rolling Upgrade, it all happens via Hot Rod with "raw" data, that is, data is iterated in the source cluster and stored in the new cluster in the same format as its stored. > 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.1.0.Final > > > 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.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10884) Expose index details for a cache

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-10884: ---------------------------------------- Summary: Expose index details for a cache Key: ISPN-10884 URL: https://issues.jboss.org/browse/ISPN-10884 Project: Infinispan Issue Type: Enhancement Components: REST Affects Versions: 10.0.1.Final Reporter: Gustavo Fernandes Assignee: Gustavo Fernandes It should provide runtime status together with configuration aspects such as index location, type, etc. Also it should contain all information currently exposes through JMX {code:json} { "size": 1000, "reindexing": false, "provider": { "disk" : { "path": "/path/to/index" } } } {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10883) [REST] Simulataneous call to stop don't stop the servers

by Gustavo Fernandes (Jira)

Gustavo Fernandes created ISPN-10883: ---------------------------------------- Summary: [REST] Simulataneous call to stop don't stop the servers Key: ISPN-10883 URL: https://issues.jboss.org/browse/ISPN-10883 Project: Infinispan Issue Type: Bug Components: REST, Server Reporter: Gustavo Fernandes This was observed in a cluster of 3 servers in the same machine, listening on ports 11222, 11322, 11422. A script would call stop on each of the server individually: http://localhost:11222/rest/v2/server?action=stop http://localhost:11322/rest/v2/server?action=stop http://localhost:11422/rest/v2/server?action=stop All the commands return code 200 but the servers are not stopped, the processes are still alive. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10881) Deprecate GlobalJmxStatisticsConfiguration.allowDuplicateDomains

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10881?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10881: --------------------------------- Status: Open (was: New) > Deprecate GlobalJmxStatisticsConfiguration.allowDuplicateDomains > ---------------------------------------------------------------- > > Key: ISPN-10881 > URL: https://issues.jboss.org/browse/ISPN-10881 > Project: Infinispan > Issue Type: Task > Components: Configuration, Core > Affects Versions: 10.0.0.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 10.1.0.Final > > > {{allowDuplicateDomains}} is just a crutch for tests. Applications rarely start more than one cache manager in the same JVM, and when they (e.g. multiple applications in an application server) do it's always a good idea to give each cache manager a unique name. > Our test suite doesn't really need {{allowDuplicateDomains}} either: {{TestCacheManagerFactory}} adds a UUID to the domain name, unless the test has explicitly set a (presumably unique) domain name. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10863) java.lang.IllegalAccessException logged by PropertyFormatter

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10863?page=com.atlassian.jira.plugin... ] Nistor Adrian updated ISPN-10863: --------------------------------- Git Pull Request: https://github.com/infinispan/infinispan/pull/7512, https://github.com/infinispan/infinispan/pull/7533 (was: https://github.com/infinispan/infinispan/pull/7512) > java.lang.IllegalAccessException logged by PropertyFormatter > ------------------------------------------------------------- > > Key: ISPN-10863 > URL: https://issues.jboss.org/browse/ISPN-10863 > Project: Infinispan > Issue Type: Bug > Components: Configuration > Affects Versions: 10.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1 > > > This is a benign issue being logged by AccessibleObject when PropertyFormatter attempts to accesses via reflection some config methods that are not accessible. JmxStatsFunctionalTest is one good example, and it's not failing because of this. > {code} > java.lang.IllegalAccessException: class org.infinispan.configuration.format.PropertyFormatter cannot access a member of class org.infinispan.configuration.cache.AuthorizationConfiguration with modifiers "static final" > at java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361) > at java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591) > at java.base/java.lang.reflect.Method.invoke(Method.java:558) > at org.infinispan.configuration.format.PropertyFormatter.reflect(PropertyFormatter.java:101) > at org.infinispan.configuration.format.PropertyFormatter.reflect(PropertyFormatter.java:110) > at org.infinispan.configuration.format.PropertyFormatter.reflect(PropertyFormatter.java:101) > at org.infinispan.configuration.format.PropertyFormatter.reflect(PropertyFormatter.java:101) > at org.infinispan.configuration.format.PropertyFormatter.format(PropertyFormatter.java:131) > at org.infinispan.cache.impl.AbstractDelegatingCache.getConfigurationAsProperties(AbstractDelegatingCache.java:616) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base/java.lang.reflect.Method.invoke(Method.java:566) > at org.infinispan.jmx.ResourceDMBean$InvokableSetterBasedMBeanAttributeInfo.invoke(ResourceDMBean.java:378) > at org.infinispan.jmx.ResourceDMBean.getNamedAttribute(ResourceDMBean.java:289) > at org.infinispan.jmx.ResourceDMBean.getAttribute(ResourceDMBean.java:172) > at java.management/com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:641) > at java.management/com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:678) > at org.infinispan.jmx.JmxStatsFunctionalTest.testConfigurationProperties(JmxStatsFunctionalTest.java:307) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8357) Avoid index="LOCAL" in default configurations

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-8357?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated ISPN-8357: -------------------------------- Fix Version/s: 10.1.0.Beta1 > Avoid index="LOCAL" in default configurations > --------------------------------------------- > > Key: ISPN-8357 > URL: https://issues.jboss.org/browse/ISPN-8357 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 9.0.3.Final, 9.1.1.Final > Reporter: Galder Zamarreño > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1 > > > This option is deprecated and should be changed. > The default server configuration comes with configurations that use this deprecated option. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8357) Avoid index="LOCAL" in default configurations

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-8357?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated ISPN-8357: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/7532 > Avoid index="LOCAL" in default configurations > --------------------------------------------- > > Key: ISPN-8357 > URL: https://issues.jboss.org/browse/ISPN-8357 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 9.0.3.Final, 9.1.1.Final > Reporter: Galder Zamarreño > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1 > > > This option is deprecated and should be changed. > The default server configuration comes with configurations that use this deprecated option. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-8357) Avoid index="LOCAL" in default configurations

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-8357?page=com.atlassian.jira.plugin.... ] Nistor Adrian updated ISPN-8357: -------------------------------- Status: Open (was: New) > Avoid index="LOCAL" in default configurations > --------------------------------------------- > > Key: ISPN-8357 > URL: https://issues.jboss.org/browse/ISPN-8357 > Project: Infinispan > Issue Type: Bug > Components: Embedded Querying > Affects Versions: 9.0.3.Final, 9.1.1.Final > Reporter: Galder Zamarreño > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.1.0.Beta1 > > > This option is deprecated and should be changed. > The default server configuration comes with configurations that use this deprecated option. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10860) Attributes with DataType.TRAIT are not metrics

by Nistor Adrian (Jira)

[ https://issues.jboss.org/browse/ISPN-10860?page=com.atlassian.jira.plugin... ] Nistor Adrian closed ISPN-10860. -------------------------------- > Attributes with DataType.TRAIT are not metrics > ---------------------------------------------- > > Key: ISPN-10860 > URL: https://issues.jboss.org/browse/ISPN-10860 > Project: Infinispan > Issue Type: Bug > Affects Versions: 10.0.0.Final > Reporter: Nistor Adrian > Assignee: Nistor Adrian > Priority: Major > Fix For: 10.0.1.Final, 10.1.0.Final > > > They are constant. Exporting them is useless. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues November 2019