April 2020 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-10428) Docs: Configuring paths for single file cache stores

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10428?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-10428: ------------------------------- Summary: Docs: Configuring paths for single file cache stores (was: [9.4.x] File Store Examples) > Docs: Configuring paths for single file cache stores > ---------------------------------------------------- > > Key: ISPN-10428 > URL: https://issues.redhat.com/browse/ISPN-10428 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Environment: XSD > jboss-infinispan-core*.xsd > infinispan-config*.xsd > Reporter: Wolf-Dieter Fink > Assignee: Donald Naro > Priority: Minor > Fix For: 9.4.19.Final > > > Embedded and server mode are using a different configuration for file-store > embedded : infinispan-config* > {code} > </xs:attribute> > <xs:attribute name="relative-to" type="xs:string"> > <xs:annotation><xs:documentation>Unused XML attribute</xs:documentation></xs:annotation> > </xs:attribute> > <xs:attribute name="path" type="xs:string"> > <xs:annotation> > <xs:documentation> > The path within "relative-to" in which to store the cache state. > If undefined, the path defaults to the cache container name. > </xs:documentation> > </xs:annotation> > </xs:attribute> > </xs:extension> > </xs:complexContent> > </xs:complexType> > {code} > Here the relative-to is not used but referenced for path. > But path is used relative to PWD if it is not an absolute one, also if defaults to 'Infinispan-SingleFileStore' if not set. > For the server configuration it is > {code} > <xs:attribute name="relative-to" type="xs:string" default="jboss.server.data.dir"> > <xs:annotation> > <xs:documentation>The base directory in which to store the cache state.</xs:documentation> > </xs:annotation> > </xs:attribute> > <xs:attribute name="path" type="xs:string"> > <xs:annotation> > <xs:documentation> > The path within "relative-to" in which to store the cache state. > If undefined, the path defaults to the cache container name. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} > But relative-to is a reference to a path declaration like this > {code} > <paths> > <path name="my.dir" path="/MyCacheStore"/> > </paths> > ... > <distributed-cache name="wolf"> > <persistence> > <file-store shared="false" fetch-state="true" relative-to="my.dir"/> > </persistence> > </distributed-cache> > {code} > If relative-to is set to a real path or env variable the server start will fail with > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.wolf.config: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.wolf.config: Failed to start service > ... > Caused by: java.lang.IllegalArgumentException: WFLYCTL0256: Could not find a path called '/MyCacheStore' > at org.jboss.as.controller.services.path.PathManagerService.resolveRelativePathEntry(PathManagerService.java:110) > at org.jboss.as.clustering.infinispan.subsystem.CacheConfigurationAdd$5.inject(CacheConfigurationAdd.java:765) > at org.jboss.as.clustering.infinispan.subsystem.CacheConfigurationAdd$5.inject(CacheConfigurationAdd.java:760) > at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:58) > at org.jboss.msc.service.ServiceControllerImpl.inject(ServiceControllerImpl.java:1517) > at org.jboss.msc.service.ServiceControllerImpl.inject(ServiceControllerImpl.java:1503) > at org.jboss.msc.service.ServiceControllerImpl.access$2800(ServiceControllerImpl.java:55) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1699) > ... 6 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11673) RemoteStore should allow ClientIntellegience configuration

by Ryan Emerson (Jira)

Ryan Emerson created ISPN-11673: ----------------------------------- Summary: RemoteStore should allow ClientIntellegience configuration Key: ISPN-11673 URL: https://issues.redhat.com/browse/ISPN-11673 Project: Infinispan Issue Type: Feature Request Components: Hot Rod, Loaders and Stores Affects Versions: 10.1.6.Final, 11.0.0.Dev04 Reporter: Ryan Emerson Assignee: Ryan Emerson Fix For: 10.1.7.Final, 11.0.0.Dev05 In Kubernetes environments, it's not always possible to utilise the default intelligence HASH_DISTRIBUTION_AWARE, therefore it should be possible to configure this. Similarly, long term it would probably be more maintainable to allow the remote-store to utilise a `hotrod-client.properties` file. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10428) [9.4.x] File Store Examples

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-10428?page=com.atlassian.jira.plugi... ] Donald Naro reopened ISPN-10428: -------------------------------- Reopening to clarify path configuration with single file stores with servers. > [9.4.x] File Store Examples > --------------------------- > > Key: ISPN-10428 > URL: https://issues.redhat.com/browse/ISPN-10428 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Environment: XSD > jboss-infinispan-core*.xsd > infinispan-config*.xsd > Reporter: Wolf-Dieter Fink > Assignee: Donald Naro > Priority: Minor > Fix For: 9.4.19.Final > > > Embedded and server mode are using a different configuration for file-store > embedded : infinispan-config* > {code} > </xs:attribute> > <xs:attribute name="relative-to" type="xs:string"> > <xs:annotation><xs:documentation>Unused XML attribute</xs:documentation></xs:annotation> > </xs:attribute> > <xs:attribute name="path" type="xs:string"> > <xs:annotation> > <xs:documentation> > The path within "relative-to" in which to store the cache state. > If undefined, the path defaults to the cache container name. > </xs:documentation> > </xs:annotation> > </xs:attribute> > </xs:extension> > </xs:complexContent> > </xs:complexType> > {code} > Here the relative-to is not used but referenced for path. > But path is used relative to PWD if it is not an absolute one, also if defaults to 'Infinispan-SingleFileStore' if not set. > For the server configuration it is > {code} > <xs:attribute name="relative-to" type="xs:string" default="jboss.server.data.dir"> > <xs:annotation> > <xs:documentation>The base directory in which to store the cache state.</xs:documentation> > </xs:annotation> > </xs:attribute> > <xs:attribute name="path" type="xs:string"> > <xs:annotation> > <xs:documentation> > The path within "relative-to" in which to store the cache state. > If undefined, the path defaults to the cache container name. > </xs:documentation> > </xs:annotation> > </xs:attribute> > {code} > But relative-to is a reference to a path declaration like this > {code} > <paths> > <path name="my.dir" path="/MyCacheStore"/> > </paths> > ... > <distributed-cache name="wolf"> > <persistence> > <file-store shared="false" fetch-state="true" relative-to="my.dir"/> > </persistence> > </distributed-cache> > {code} > If relative-to is set to a real path or env variable the server start will fail with > {code} > ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.datagrid-infinispan.clustered.wolf.config: org.jboss.msc.service.StartException in service jboss.datagrid-infinispan.clustered.wolf.config: Failed to start service > ... > Caused by: java.lang.IllegalArgumentException: WFLYCTL0256: Could not find a path called '/MyCacheStore' > at org.jboss.as.controller.services.path.PathManagerService.resolveRelativePathEntry(PathManagerService.java:110) > at org.jboss.as.clustering.infinispan.subsystem.CacheConfigurationAdd$5.inject(CacheConfigurationAdd.java:765) > at org.jboss.as.clustering.infinispan.subsystem.CacheConfigurationAdd$5.inject(CacheConfigurationAdd.java:760) > at org.jboss.msc.inject.CastingInjector.inject(CastingInjector.java:58) > at org.jboss.msc.service.ServiceControllerImpl.inject(ServiceControllerImpl.java:1517) > at org.jboss.msc.service.ServiceControllerImpl.inject(ServiceControllerImpl.java:1503) > at org.jboss.msc.service.ServiceControllerImpl.access$2800(ServiceControllerImpl.java:55) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1699) > ... 6 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11321) [9.4.x] Update SB Starter Docs

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11321?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11321: ------------------------------- Fix Version/s: 9.4.20.Final (was: 9.4.19.Final) > [9.4.x] Update SB Starter Docs > ------------------------------ > > Key: ISPN-11321 > URL: https://issues.redhat.com/browse/ISPN-11321 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 9.4.20.Final > > > Need to update documentation for DG 8 Spring Boot Starter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-10466) StateConsumerImpl.removeStaleData takes too long with unsegmented stores

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-10466?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-10466: ------------------------------- Fix Version/s: 9.4.20.Final (was: 9.4.19.Final) > StateConsumerImpl.removeStaleData takes too long with unsegmented stores > ------------------------------------------------------------------------ > > Key: ISPN-10466 > URL: https://issues.redhat.com/browse/ISPN-10466 > Project: Infinispan > Issue Type: Bug > Components: Core, State Transfer > Affects Versions: 9.4.16.Final > Reporter: Dan Berindei > Assignee: Dan Berindei > Priority: Major > Fix For: 9.4.20.Final > > > With a segmented data container, {{removeStaleData}} is very fast. But the product doesn't use segmented data containers yet, so it's still important to make {{removeStaleData}} faster with unsegmented data containers. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11424) Deprecate StorageType Configuration in favour of MediaType

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11424?page=com.atlassian.jira.plugi... ] Gustavo Fernandes updated ISPN-11424: ------------------------------------- Status: Open (was: New) > Deprecate StorageType Configuration in favour of MediaType > ---------------------------------------------------------- > > Key: ISPN-11424 > URL: https://issues.redhat.com/browse/ISPN-11424 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 11.0.0.Alpha2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > Currently caches have configuration to specify memory storing aspects that affects eviction, e.g. > {code:xml} > <memory> > <object size="20000"/> > </memory> > {code} > {code:xml} > <memory> > <off-heap size="10000000" eviction="MEMORY"/> > </memory> > {code} > {code:xml} > <memory> > <binary strategy="EXCEPTION" eviction="MEMORY" size="5000"/> > </memory> > {code} > Each of those configurations affect the format that the data will be stored, being {{object}} the default on-heap storage, {{off-heap}} the {{byte[]}} out of heap storage and {{binary}} an on-heap format that mix {{byte[]}}, {{String}} and primitives. > This ticket proposes to have the {{MediaType}} of the keys and values to dictate the storage format, and let the {{<memory>}} element to be responsible to choose between on-heap and off-heap storage, eliminating the {{Binary}} option altogether. The configuration would be something like: > {code:xml} >  > <memory storage="heap"> > <eviction size="20000"/> > </memory> > {code} > {code:xml} >  > <encoding> > <key media-type="application/x-java-serialized-object"/> > <value media-type="application/x-java-serialized-object"/> > </encoding> > <memory storage="heap"> > <eviction size="20000"/> > </memory> > {code} > {code:xml} >  > <encoding> > <key media-type="application/x-protostream"/> > <value media-type="application/x-protostream"/> > </encoding> > <memory storage="off-heap"> > <eviction size="10000000" eviction="MEMORY"/> > </memory> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11424) Deprecate StorageType Configuration in favour of MediaType

by Gustavo Fernandes (Jira)

[ https://issues.redhat.com/browse/ISPN-11424?page=com.atlassian.jira.plugi... ] Work on ISPN-11424 started by Gustavo Fernandes. ------------------------------------------------ > Deprecate StorageType Configuration in favour of MediaType > ---------------------------------------------------------- > > Key: ISPN-11424 > URL: https://issues.redhat.com/browse/ISPN-11424 > Project: Infinispan > Issue Type: Bug > Components: Core > Affects Versions: 11.0.0.Alpha2 > Reporter: Gustavo Fernandes > Assignee: Gustavo Fernandes > Priority: Major > > Currently caches have configuration to specify memory storing aspects that affects eviction, e.g. > {code:xml} > <memory> > <object size="20000"/> > </memory> > {code} > {code:xml} > <memory> > <off-heap size="10000000" eviction="MEMORY"/> > </memory> > {code} > {code:xml} > <memory> > <binary strategy="EXCEPTION" eviction="MEMORY" size="5000"/> > </memory> > {code} > Each of those configurations affect the format that the data will be stored, being {{object}} the default on-heap storage, {{off-heap}} the {{byte[]}} out of heap storage and {{binary}} an on-heap format that mix {{byte[]}}, {{String}} and primitives. > This ticket proposes to have the {{MediaType}} of the keys and values to dictate the storage format, and let the {{<memory>}} element to be responsible to choose between on-heap and off-heap storage, eliminating the {{Binary}} option altogether. The configuration would be something like: > {code:xml} >  > <memory storage="heap"> > <eviction size="20000"/> > </memory> > {code} > {code:xml} >  > <encoding> > <key media-type="application/x-java-serialized-object"/> > <value media-type="application/x-java-serialized-object"/> > </encoding> > <memory storage="heap"> > <eviction size="20000"/> > </memory> > {code} > {code:xml} >  > <encoding> > <key media-type="application/x-protostream"/> > <value media-type="application/x-protostream"/> > </encoding> > <memory storage="off-heap"> > <eviction size="10000000" eviction="MEMORY"/> > </memory> > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11321) [9.4.x] Update SB Starter Docs

by Donald Naro (Jira)

[ https://issues.redhat.com/browse/ISPN-11321?page=com.atlassian.jira.plugi... ] Donald Naro updated ISPN-11321: ------------------------------- Status: Pull Request Sent (was: Reopened) > [9.4.x] Update SB Starter Docs > ------------------------------ > > Key: ISPN-11321 > URL: https://issues.redhat.com/browse/ISPN-11321 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 9.4.19.Final > > > Need to update documentation for DG 8 Spring Boot Starter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11321) [9.4.x] Update SB Starter Docs

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11321?page=com.atlassian.jira.plugi... ] Pedro Ruivo updated ISPN-11321: ------------------------------- Git Pull Request: https://github.com/infinispan/infinispan-spring-boot/pull/144, https://github.com/infinispan/infinispan/pull/8209 (was: https://github.com/infinispan/infinispan-spring-boot/pull/144) > [9.4.x] Update SB Starter Docs > ------------------------------ > > Key: ISPN-11321 > URL: https://issues.redhat.com/browse/ISPN-11321 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 9.4.19.Final > > > Need to update documentation for DG 8 Spring Boot Starter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ISPN-11321) [9.4.x] Update SB Starter Docs

by Pedro Ruivo (Jira)

[ https://issues.redhat.com/browse/ISPN-11321?page=com.atlassian.jira.plugi... ] Pedro Ruivo reopened ISPN-11321: -------------------------------- > [9.4.x] Update SB Starter Docs > ------------------------------ > > Key: ISPN-11321 > URL: https://issues.redhat.com/browse/ISPN-11321 > Project: Infinispan > Issue Type: Enhancement > Components: Documentation > Reporter: Donald Naro > Assignee: Donald Naro > Priority: Major > Fix For: 9.4.19.Final > > > Need to update documentation for DG 8 Spring Boot Starter. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 April 2020