[JBoss JIRA] (ISPN-11522) XSDs included in the jars and published to the website don't have the defaults
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-11522:
--------------------------------------
Summary: XSDs included in the jars and published to the website don't have the defaults
Key: ISPN-11522
URL: https://issues.redhat.com/browse/ISPN-11522
Project: Infinispan
Issue Type: Bug
Components: Configuration
Affects Versions: 11.0.0.Dev03, 10.1.5.Final
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 11.0.0.Dev04, 10.1.6.Final
The bundle plugin used to generate the jars is using the raw unfiltered xsds from src/main/resources instead of the filtered ones from target/classes
Additionally, some xsds are referencing invalid properties (soft-index and rocksdb)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11523) XSDs included in the jars and published to the website don't have the defaults
by Tristan Tarrant (Jira)
Tristan Tarrant created ISPN-11523:
--------------------------------------
Summary: XSDs included in the jars and published to the website don't have the defaults
Key: ISPN-11523
URL: https://issues.redhat.com/browse/ISPN-11523
Project: Infinispan
Issue Type: Bug
Components: Configuration
Affects Versions: 10.1.5.Final, 11.0.0.Dev03
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 11.0.0.Dev04, 10.1.6.Final
The bundle plugin used to generate the jars is using the raw unfiltered xsds from src/main/resources instead of the filtered ones from target/classes
Additionally, some xsds are referencing invalid properties (soft-index and rocksdb)
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years
[JBoss JIRA] (ISPN-11428) Docs: JGroups Config Updates
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-11428?page=com.atlassian.jira.plugi... ]
Pedro Ruivo updated ISPN-11428:
-------------------------------
Fix Version/s: 10.1.6.Final
> 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
> Fix For: 11.0.0.Dev04, 10.1.6.Final
>
>
> 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
[JBoss JIRA] (ISPN-11428) Docs: JGroups Config Updates
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-11428?page=com.atlassian.jira.plugi... ]
Pedro Ruivo resolved ISPN-11428.
--------------------------------
Resolution: Done
> 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
> Fix For: 11.0.0.Dev04, 10.1.6.Final
>
>
> 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
[JBoss JIRA] (ISPN-11428) Docs: JGroups Config Updates
by Pedro Ruivo (Jira)
[ https://issues.redhat.com/browse/ISPN-11428?page=com.atlassian.jira.plugi... ]
Pedro Ruivo reopened ISPN-11428:
--------------------------------
> 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
> Fix For: 11.0.0.Dev04, 10.1.6.Final
>
>
> 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