[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:
-------------------------------
Fix Version/s: 10.1.7.Final
11.0.0.Dev05
> 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, 10.1.7.Final, 11.0.0.Dev05
>
>
> 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
[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: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8240
> 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}
> <!-- Default configuration, heap storage with POJOs -->
> <memory storage="heap">
> <eviction size="20000"/>
> </memory>
> {code}
> {code:xml}
> <!-- Storing java serialized objects, on-heap -->
> <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}
> <!-- Off-heap configuration, in protobuf format -->
> <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
[JBoss JIRA] (ISPN-11706) Use XidImpl internally
by Pedro Ruivo (Jira)
Pedro Ruivo created ISPN-11706:
----------------------------------
Summary: Use XidImpl internally
Key: ISPN-11706
URL: https://issues.redhat.com/browse/ISPN-11706
Project: Infinispan
Issue Type: Enhancement
Components: Core, Transactions
Affects Versions: 11.0.0.Dev04
Reporter: Pedro Ruivo
Assignee: Pedro Ruivo
We can use {{XidImpl}} to store external {{Xid}} in our internals. This way, we only need to handle one implementation internally that makes life easier with protostream.
Action plan:
* Remove {{EmbeddedXid}} and move generator code to {{EmbbededTransaction}}
* Remove {{RemoteXid}} and move generator code to {{RemoteTransaction}}
* Update {{XidImpl.copy()}}
* Create protostream marshaller
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (ISPN-11705) Error and Loading handling
by Katia Aresti (Jira)
Katia Aresti created ISPN-11705:
-----------------------------------
Summary: Error and Loading handling
Key: ISPN-11705
URL: https://issues.redhat.com/browse/ISPN-11705
Project: Infinispan
Issue Type: Enhancement
Components: Console
Affects Versions: 10.1.6.Final
Reporter: Katia Aresti
Assignee: Katia Aresti
Add the first steps for loading and error handling
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months
[JBoss JIRA] (ISPN-11676) Per-cache Hot Rod client configuration
by Katia Aresti (Jira)
[ https://issues.redhat.com/browse/ISPN-11676?page=com.atlassian.jira.plugi... ]
Katia Aresti updated ISPN-11676:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> Per-cache Hot Rod client configuration
> --------------------------------------
>
> Key: ISPN-11676
> URL: https://issues.redhat.com/browse/ISPN-11676
> Project: Infinispan
> Issue Type: Enhancement
> Components: Hot Rod
> Affects Versions: 11.0.0.Dev04, 10.1.6.Final
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Priority: Major
> Fix For: 10.1.7.Final, 11.0.0.Dev05
>
>
> Currently some configuration in the Hot Rod client is global (tx mode, force return values, near cache). We should introduce per-cache configuration. Additionally we should also be able to specify a server-side template/configuration to use if a cache doesn't exist.
> {code:java}
> builder
> .remoteCache(cacheName)
> .templateName("template")
> .nearCacheMode(NearCacheMode.INVALIDATED)
> .nearCacheMaxEntries(100)
> .forceReturnValues(true);
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 11 months