[JBoss JIRA] (ISPN-10428) 7.3 Docs: Document declarative configuration of file-stores
by Donald Naro (Jira)
[ https://issues.redhat.com/browse/ISPN-10428?page=com.atlassian.jira.plugi... ]
Donald Naro updated ISPN-10428:
-------------------------------
Summary: 7.3 Docs: Document declarative configuration of file-stores (was: Document declarative configuration of file-stores)
> 7.3 Docs: Document declarative configuration of file-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
>
> 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)
6 years, 1 month
[JBoss JIRA] (ISPN-11428) Docs: JGroups Config Updates
by Donald Naro (Jira)
[ https://issues.redhat.com/browse/ISPN-11428?page=com.atlassian.jira.plugi... ]
Donald Naro updated ISPN-11428:
-------------------------------
Sprint: DataGrid Sprint #41
> Docs: JGroups Config Updates
> ----------------------------
>
> Key: ISPN-11428
> URL: https://issues.redhat.com/browse/ISPN-11428
> Project: Infinispan
> Issue Type: Enhancement
> Components: Documentation
> Reporter: Donald Naro
> Assignee: Donald Naro
> Priority: Major
>
> From Wolf:
> ISPN docs
> https://infinispan.org/docs/dev/titles/configuring/configuring.html#clust...
> show information about improve performance and mention jgroups-default.xml ....
> but no idea where to find it
> name is confusing should be clarified
> there is no jgroups-defaults for the server it is default-configs/default-jgroups-<stack>.xml
> there is no infinispan-jgroups.xml as well in core.jar
> so the (i) box is just confusion
> 5. Setting up Cluster Transport
> 5.1.2 Default stack
> Confusing as the default-jgroups-[tcp|udp].xml show something more specific and more attributes.
> What is the purpose of this simplified stack? If the default xmls are used I would not include the example here, just point to the ispn-core.jar/default-configs which are listed in 5.1.1
> The (i) box is confusing as there is no heint where to find it.
> Also the ispn-core.jar does not include a jgroups-default.xml or infinspan-jgroups.xml. The embedded stuff seems to point to the same defaults as 5.1.1.
> If there are no real properties which are the default I would remove the box
> 5.2 inline stack
> The hint box “Use inheritance …” should point to 5.3 and here it should mention that this is a fully created stack with the complete configuration.
> 5.3 Adjusting
> For 2. You should mention that this can be “udp” or “tcp” used by default, not only a self created one
> Note that <VERIFY_SUSPECT> is replaced, which means all attributes are back to defaults.
> Example might include RELAY as it can be used without any position to be appended at the end. This is most useful for XSite replication (example is infnispan-xsite.xml)
> Explain that the stack.position is the name of any protocol.
> Not sure what happen if it is not found!
> 5.5.1 system properties default jgroups
> UDP
> Jgroups.udp.* → no udp !
> Missing
> Address → jgroups.bind.address,jgroups.udp.address defaults to SITE_LOCAL
> Port → jgroups.bind.port,jgroups.udp.port defaults to “0” automatically
> TCP
> Address can use jgroups.bind.address and the default is SITE_LOCAL not 127.0.0.1
> Port can use jgroups.bind.port
> Jgroups.udp.* → no udp !
> EC2, kubernetes
> Same here for address and port
> 6 Discovery
> Should we list FILE_PING as well as this is the simple base for discovery and already shared with customers?
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month