[JBoss JIRA] (ISPN-12221) Add zero-capacity-node support for Replicated caches
by Ryan Emerson (Jira)
Ryan Emerson created ISPN-12221:
-----------------------------------
Summary: Add zero-capacity-node support for Replicated caches
Key: ISPN-12221
URL: https://issues.redhat.com/browse/ISPN-12221
Project: Infinispan
Issue Type: Enhancement
Components: Core
Affects Versions: 12.0.0.Dev01
Reporter: Ryan Emerson
Fix For: 12.0.0.Dev02
Currently if a container is configured to have {{zero-capacity-node=true}} this only applies to distributed caches. To prevent state-transfer for replicated caches, we should modify {{ReplicatedConsistentHashFactory}} and {{ReplicatedConsistentHash}} to allow a node to be a member without also being an owner.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-10503) jgroups config not getting stack name
by Gustavo Lira e Silva (Jira)
[ https://issues.redhat.com/browse/ISPN-10503?page=com.atlassian.jira.plugi... ]
Gustavo Lira e Silva closed ISPN-10503.
---------------------------------------
Resolution: Out of Date
> jgroups config not getting stack name
> -------------------------------------
>
> Key: ISPN-10503
> URL: https://issues.redhat.com/browse/ISPN-10503
> Project: Infinispan
> Issue Type: Bug
> Components: Configuration, Server
> Affects Versions: 10.0.0.Beta5
> Reporter: Gustavo Lira Silva
> Priority: Major
>
> If I use a jgroups configuration like this:
> {code:xml}
> <jgroups>
> <stack-file name='image-tcp' path='jgroups-tcp.xml'/>
> </jgroups>
> <cache-container>
> <transport cluster='infinispan' stack='image-tcp'/>
> </cache-container>
> {code}
> Everything works fine, but I use a configuration like this:
> {code:xml}
> xi:include href="server-configuration/jgroups/default-tcp.xml"/>
> {code}
> default-tcp.xml file
> {code:xml}
> <infinispan
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="urn:infinispan:config:10.0 http://www.infinispan.org/schemas/infinispan-config-10.0.xsd
> urn:org:jgroups http://www.jgroups.org/schema/jgroups-4.0.xsd"
> xmlns="urn:infinispan:config:10.0"
> xmlns:ispn="urn:infinispan:config:10.0">
> <jgroups>
> <stack name="image-tcp">
> <MERGE3 min_interval="1000" max_interval="5000"/>
> <TCP_NIO2
> bind_addr="${jgroups.tcp.address:127.0.0.1}"
> bind_port="${jgroups.tcp.port:7800}"
> port_range="30"
> recv_buf_size="20m"
> send_buf_size="640k"
> enable_diagnostics="false"
> bundler_type="no-bundler"
> thread_naming_pattern="pl"
> thread_pool.min_threads="0"
> thread_pool.max_threads="8"
> thread_pool.keep_alive_time="60000"
> />
> <MPING bind_addr="${jgroups.tcp.address:127.0.0.1}"
> mcast_addr="${jgroups.mping.mcast_addr:228.2.4.6}"
> mcast_port="${jgroups.mping.mcast_port:43366}"
> ip_ttl="${jgroups.udp.ip_ttl:2}"
> />
> </stack>
> </jgroups>
> </infinispan>
> {code}
> I'm receiving the following exception
> {noformat}
> FATAL [org.infinispan.SERVER] (main) Error: org.infinispan.commons.CacheConfigurationException: ISPN000539: Duplicate JGroups stack 'tcp'
> {noformat}
> Looks like the *name* attribute of the <stack> are not working as expected
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12204) Add JDBC Meta Table
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-12204?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-12204:
--------------------------------
Sprint: DataGrid Sprint #47
> Add JDBC Meta Table
> -------------------
>
> Key: ISPN-12204
> URL: https://issues.redhat.com/browse/ISPN-12204
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 12.0.0.Dev01
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 12.0.0.Dev02
>
>
> Currently there is no way to determine what version of Infinispan created a Jdbc store, which makes it difficult/impossible to migrate stored data from one Infinispan version to another if a binary incompatibility is introduced.
> Similarly it's not possible for us to verify that the configured number of segments match those present in an existing store.
> We should add an additional table to store such metadata.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12204) Add JDBC Meta Table
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-12204?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-12204:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8620
> Add JDBC Meta Table
> -------------------
>
> Key: ISPN-12204
> URL: https://issues.redhat.com/browse/ISPN-12204
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 12.0.0.Dev01
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 12.0.0.Dev02
>
>
> Currently there is no way to determine what version of Infinispan created a Jdbc store, which makes it difficult/impossible to migrate stored data from one Infinispan version to another if a binary incompatibility is introduced.
> Similarly it's not possible for us to verify that the configured number of segments match those present in an existing store.
> We should add an additional table to store such metadata.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12204) Add JDBC Meta Table
by Ryan Emerson (Jira)
[ https://issues.redhat.com/browse/ISPN-12204?page=com.atlassian.jira.plugi... ]
Ryan Emerson updated ISPN-12204:
--------------------------------
Status: Open (was: New)
> Add JDBC Meta Table
> -------------------
>
> Key: ISPN-12204
> URL: https://issues.redhat.com/browse/ISPN-12204
> Project: Infinispan
> Issue Type: Enhancement
> Components: Loaders and Stores
> Affects Versions: 12.0.0.Dev01
> Reporter: Ryan Emerson
> Assignee: Ryan Emerson
> Priority: Major
> Fix For: 12.0.0.Dev02
>
>
> Currently there is no way to determine what version of Infinispan created a Jdbc store, which makes it difficult/impossible to migrate stored data from one Infinispan version to another if a binary incompatibility is introduced.
> Similarly it's not possible for us to verify that the configured number of segments match those present in an existing store.
> We should add an additional table to store such metadata.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12220) change default configuration within the ${infinispan.cluster.stack:XXX} does not have an effect
by Wolf-Dieter Fink (Jira)
[ https://issues.redhat.com/browse/ISPN-12220?page=com.atlassian.jira.plugi... ]
Wolf-Dieter Fink updated ISPN-12220:
------------------------------------
Status: Pull Request Sent (was: Coding In Progress)
Git Pull Request: https://github.com/infinispan/infinispan/pull/8619
> change default configuration within the ${infinispan.cluster.stack:XXX} does not have an effect
> -----------------------------------------------------------------------------------------------
>
> Key: ISPN-12220
> URL: https://issues.redhat.com/browse/ISPN-12220
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 11.0.3.Final
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Priority: Minor
>
> If a different stack should be configured within the XML configuration
> <cache-container name="default" statistics="true">
> <transport cluster="${infinispan.cluster.name:MyCluster}" stack="${infinispan.cluster.stack:someDifferent}" node-name="${infinispan.node.name:}"/>
> this will not have any effect, the default tcp stack is used as long as ${infinispan.cluster.stack} is set. The default "tcp" is set hardcoded.
> This is confusing if the stack should be changed inside the configuration with the <jgroups> element.
> Also the cluster.name is set hardcoded instead of using the :default from expression
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12220) change default configuration within the ${infinispan.cluster.stack:XXX} does not have an effect
by Wolf-Dieter Fink (Jira)
[ https://issues.redhat.com/browse/ISPN-12220?page=com.atlassian.jira.plugi... ]
Work on ISPN-12220 started by Wolf-Dieter Fink.
-----------------------------------------------
> change default configuration within the ${infinispan.cluster.stack:XXX} does not have an effect
> -----------------------------------------------------------------------------------------------
>
> Key: ISPN-12220
> URL: https://issues.redhat.com/browse/ISPN-12220
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 11.0.3.Final
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Priority: Minor
>
> If a different stack should be configured within the XML configuration
> <cache-container name="default" statistics="true">
> <transport cluster="${infinispan.cluster.name:MyCluster}" stack="${infinispan.cluster.stack:someDifferent}" node-name="${infinispan.node.name:}"/>
> this will not have any effect, the default tcp stack is used as long as ${infinispan.cluster.stack} is set. The default "tcp" is set hardcoded.
> This is confusing if the stack should be changed inside the configuration with the <jgroups> element.
> Also the cluster.name is set hardcoded instead of using the :default from expression
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12220) change default configuration within the ${infinispan.cluster.stack:XXX} does not have an effect
by Wolf-Dieter Fink (Jira)
[ https://issues.redhat.com/browse/ISPN-12220?page=com.atlassian.jira.plugi... ]
Wolf-Dieter Fink reassigned ISPN-12220:
---------------------------------------
Assignee: Wolf-Dieter Fink
> change default configuration within the ${infinispan.cluster.stack:XXX} does not have an effect
> -----------------------------------------------------------------------------------------------
>
> Key: ISPN-12220
> URL: https://issues.redhat.com/browse/ISPN-12220
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 11.0.3.Final
> Reporter: Wolf-Dieter Fink
> Assignee: Wolf-Dieter Fink
> Priority: Minor
>
> If a different stack should be configured within the XML configuration
> <cache-container name="default" statistics="true">
> <transport cluster="${infinispan.cluster.name:MyCluster}" stack="${infinispan.cluster.stack:someDifferent}" node-name="${infinispan.node.name:}"/>
> this will not have any effect, the default tcp stack is used as long as ${infinispan.cluster.stack} is set. The default "tcp" is set hardcoded.
> This is confusing if the stack should be changed inside the configuration with the <jgroups> element.
> Also the cluster.name is set hardcoded instead of using the :default from expression
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months
[JBoss JIRA] (ISPN-12220) change default configuration within the ${infinispan.cluster.stack:XXX} does not have an effect
by Wolf-Dieter Fink (Jira)
[ https://issues.redhat.com/browse/ISPN-12220?page=com.atlassian.jira.plugi... ]
Wolf-Dieter Fink updated ISPN-12220:
------------------------------------
Description:
If a different stack should be configured within the XML configuration
<cache-container name="default" statistics="true">
<transport cluster="${infinispan.cluster.name:MyCluster}" stack="${infinispan.cluster.stack:someDifferent}" node-name="${infinispan.node.name:}"/>
this will not have any effect, the default tcp stack is used as long as ${infinispan.cluster.stack} is set. The default "tcp" is set hardcoded.
This is confusing if the stack should be changed inside the configuration with the <jgroups> element.
Also the cluster.name is set hardcoded instead of using the :default from expression
was:
If a different stack should be configured within the XML configuration
<cache-container name="default" statistics="true">
<transport cluster="${infinispan.cluster.name}" stack="${infinispan.cluster.stack:someDifferent}" node-name="${infinispan.node.name:}"/>
this will not have any effect, the default tcp stack is used as long as ${infinispan.cluster.stack} is set. The default "tcp" is set hardcoded.
This is confusing if the stack should be changed inside the configuration with the <jgroups> element.
> change default configuration within the ${infinispan.cluster.stack:XXX} does not have an effect
> -----------------------------------------------------------------------------------------------
>
> Key: ISPN-12220
> URL: https://issues.redhat.com/browse/ISPN-12220
> Project: Infinispan
> Issue Type: Enhancement
> Components: Server
> Affects Versions: 11.0.3.Final
> Reporter: Wolf-Dieter Fink
> Priority: Minor
>
> If a different stack should be configured within the XML configuration
> <cache-container name="default" statistics="true">
> <transport cluster="${infinispan.cluster.name:MyCluster}" stack="${infinispan.cluster.stack:someDifferent}" node-name="${infinispan.node.name:}"/>
> this will not have any effect, the default tcp stack is used as long as ${infinispan.cluster.stack} is set. The default "tcp" is set hardcoded.
> This is confusing if the stack should be changed inside the configuration with the <jgroups> element.
> Also the cluster.name is set hardcoded instead of using the :default from expression
>
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 7 months