July 2016 - infinispan-issues - Jboss List Archives

[JBoss JIRA] (ISPN-6887) Named query parameters user guide

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6887?page=com.atlassian.jira.plugin.... ] Work on ISPN-6887 started by Adrian Nistor. ------------------------------------------- > Named query parameters user guide > --------------------------------- > > Key: ISPN-6887 > URL: https://issues.jboss.org/browse/ISPN-6887 > Project: Infinispan > Issue Type: Task > Components: Documentation-Query > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6887) Query named parameters user guide

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6887: ----------------------------------- Summary: Query named parameters user guide Key: ISPN-6887 URL: https://issues.jboss.org/browse/ISPN-6887 Project: Infinispan Issue Type: Task Components: Documentation-Query Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 9.0.0.Alpha4 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6887) Query named parameters user guide

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6887?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6887: -------------------------------- Status: Open (was: New) > Query named parameters user guide > --------------------------------- > > Key: ISPN-6887 > URL: https://issues.jboss.org/browse/ISPN-6887 > Project: Infinispan > Issue Type: Task > Components: Documentation-Query > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6673) Implement Rolling Upgrades with Kubernetes

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6673?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec updated ISPN-6673: -------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4467 > Implement Rolling Upgrades with Kubernetes > ------------------------------------------ > > Key: ISPN-6673 > URL: https://issues.jboss.org/browse/ISPN-6673 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > There are 2 mechanisms which seems to do the same but are totally different: > * [Kubernetes Rolling Update|http://kubernetes.io/docs/user-guide/rolling-updates/] - replaces Pods in controllable fashon > * [Infinispan Rolling Updgrate|http://infinispan.org/docs/stable/user_guide/user_guide.html#_Ro...] - a procedure for upgrading Infinispan or changing the configuration > Kubernetes Rolling Updates can be used very easily for changing the configuration however if changes are not runtime-compatible, one might loss data. Potential way to avoid this is to use a Cache Store. All other changes must be propagated using Infinispan Rolling Upgrade procedure. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6673) Implement Rolling Upgrades with Kubernetes

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6673?page=com.atlassian.jira.plugin.... ] Work on ISPN-6673 started by Sebastian Łaskawiec. ------------------------------------------------- > Implement Rolling Upgrades with Kubernetes > ------------------------------------------ > > Key: ISPN-6673 > URL: https://issues.jboss.org/browse/ISPN-6673 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > There are 2 mechanisms which seems to do the same but are totally different: > * [Kubernetes Rolling Update|http://kubernetes.io/docs/user-guide/rolling-updates/] - replaces Pods in controllable fashon > * [Infinispan Rolling Updgrate|http://infinispan.org/docs/stable/user_guide/user_guide.html#_Ro...] - a procedure for upgrading Infinispan or changing the configuration > Kubernetes Rolling Updates can be used very easily for changing the configuration however if changes are not runtime-compatible, one might loss data. Potential way to avoid this is to use a Cache Store. All other changes must be propagated using Infinispan Rolling Upgrade procedure. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6886) Continous query user guide

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6886?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6886: -------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/infinispan/infinispan/pull/4466 > Continous query user guide > -------------------------- > > Key: ISPN-6886 > URL: https://issues.jboss.org/browse/ISPN-6886 > Project: Infinispan > Issue Type: Task > Components: Documentation-Query > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6886) Continous query user guide

by Adrian Nistor (JIRA)

Adrian Nistor created ISPN-6886: ----------------------------------- Summary: Continous query user guide Key: ISPN-6886 URL: https://issues.jboss.org/browse/ISPN-6886 Project: Infinispan Issue Type: Task Components: Documentation-Query Reporter: Adrian Nistor Assignee: Adrian Nistor Fix For: 9.0.0.Alpha4 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6886) Continous query user guide

by Adrian Nistor (JIRA)

[ https://issues.jboss.org/browse/ISPN-6886?page=com.atlassian.jira.plugin.... ] Adrian Nistor updated ISPN-6886: -------------------------------- Status: Open (was: New) > Continous query user guide > -------------------------- > > Key: ISPN-6886 > URL: https://issues.jboss.org/browse/ISPN-6886 > Project: Infinispan > Issue Type: Task > Components: Documentation-Query > Reporter: Adrian Nistor > Assignee: Adrian Nistor > Fix For: 9.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6885) Add S2I for replacing configuration with OpenShift image

by Sebastian Łaskawiec (JIRA)

Sebastian Łaskawiec created ISPN-6885: ----------------------------------------- Summary: Add S2I for replacing configuration with OpenShift image Key: ISPN-6885 URL: https://issues.jboss.org/browse/ISPN-6885 Project: Infinispan Issue Type: Feature Request Components: Cloud Integrations Reporter: Sebastian Łaskawiec Assignee: Sebastian Łaskawiec Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ISPN-6673) Implement Rolling Upgrades with Kubernetes

by Sebastian Łaskawiec (JIRA)

[ https://issues.jboss.org/browse/ISPN-6673?page=com.atlassian.jira.plugin.... ] Sebastian Łaskawiec edited comment on ISPN-6673 at 7/22/16 8:01 AM: -------------------------------------------------------------------- The procedure for OpenShift looks like the following: # Start OpenShift cluster using: {code} oc cluster up {code} Note you are logged as a developer. # Create new Infinispan cluster using standard configuration. Later on I will use REST interface for playing with data, so turn on compatibility mode: {code} oc new-app slaskawi/infinispan-experiments {code} # Node that you should always be using labels for your clusters. I'll call my cluster=cluster-1 {code} oc env dc/infinispan-experiments OPENSHIFT_KUBE_PING_LABELS=cluster=cluster-1 oc env dc/infinispan-experiments OPENSHIFT_KUBE_PING_NAMESPACE=myproject oc label dc/infinispan-experiments cluster=cluster-1 {code} # Scale up the deployment {code} oc scale dc/infinispan-experiments --replicas=3 {code} # Create a route to the service {code} oc expose svc/infinispan-experiments {code} # Add some entries using REST {code} curl -X POST -H 'Content-type: text/plain' -d 'test' http://infinispan-experiments-myproject.192.168.0.17.xip.io/rest/default/1 {code} # Check if the entry is there {code} curl -X GET -H 'Content-type: text/plain' http://infinispan-experiments-myproject.192.168.0.17.xip.io/rest/default/1 {code} # Now we can spin up a new cluster. Again, it's very important to use labels which will avoid joining those two clusters together. The new Docker image with Infinispan Hot Rod server needs to contain the following Remote Cache Store definition: {code} 212,214d214 < <remote-store cache="default" hotrod-wrapping="false" read-only="true"> < <remote-server outbound-socket-binding="remote-store-hotrod-server" /> < </remote-store> 449,451c449 <  <  < <remote-destination host="172.30.14.112" port="11222"/> {code} # Spinning new cluster involves the following commands: {code} oc new-app slaskawi/infinispan-experiments-2 oc env dc/infinispan-experiments-2 OPENSHIFT_KUBE_PING_LABELS=cluster=cluster-2 oc env dc/infinispan-experiments-2 OPENSHIFT_KUBE_PING_NAMESPACE=myproject oc label dc/infinispan-experiments-2 cluster=cluster-2 oc expose svc infinispan-experiments-2 {code} # At this stage we have 2 clusters (the old one with selector {{cluster=cluster-1}} and the new one with selector {{cluster=cluster-2}}). Both should be up and running (check that with {{oc status -v}}). Cluster-2 has remote stores which point to Cluster-1. # Switch all the clients to the {{cluster=cluster-2}}. Depending on your configuration you probably want to create a new Route (if your clients connect to the cluster using Routes) or modify the Service. # Fetch all remaining keys from {{cluster=cluster-1}} {code} oc get pods --selector=deploymentconfig=infinispan-experiments-2 .. write down oc exec infinispan-experiments-2-3-pc7sg -- '/opt/jboss/infinispan-server/bin/ispn-cli.sh' '-c' '--controller=$(hostname -i):9990' '/subsystem=datagrid-infinispan/cache-container=clustered/distributed-cache=default:synchronize-data(migrator-name=hotrod)' {code} # Disconnect the source cluster {code} oc exec infinispan-experiments-2-3-pc7sg -- '/opt/jboss/infinispan-server/bin/ispn-cli.sh' '-c' '--controller=$(hostname -i):9990' '/subsystem=datagrid-infinispan/cache-container=clustered/distributed-cache=default:disconnect-source(migrator-name=hotrod)' {code} was (Author: sebastian.laskawiec): WARNING - WORK IN PROGRESS NOTES The procedure for OpenShift looks like the following: # Start OpenShift cluster using: {code} oc cluster up {code} Note you are logged as a developer. # Create new Infinispan cluster using standard configuration. Later on I will use REST interface for playing with data, so turn on compatibility mode: {code} oc new-app slaskawi/infinispan-experiments {code} # Node that you should always be using labels for your clusters. I'll call my cluster=cluster-1 {code} oc env dc/infinispan-experiments OPENSHIFT_KUBE_PING_LABELS=cluster=cluster-1 oc env dc/infinispan-experiments OPENSHIFT_KUBE_PING_NAMESPACE=myproject oc label dc/infinispan-experiments cluster=cluster-1 {code} # Scale up the deployment {code} oc scale dc/infinispan-experiments --replicas=3 {code} # Create a route to the service {code} oc expose svc/infinispan-experiments {code} # Add some entries using REST {code} curl -X POST -H 'Content-type: text/plain' -d 'test' http://infinispan-experiments-myproject.192.168.0.17.xip.io/rest/default/1 {code} # Check if the entry is there {code} curl -X GET -H 'Content-type: text/plain' http://infinispan-experiments-myproject.192.168.0.17.xip.io/rest/default/1 {code} # Now we can spin up a new cluster. Again, it's very important to use labels which will avoid joining those two clusters together. The new Docker image with Infinispan Hot Rod server needs to contain the following Remote Cache Store definition: {code} 212,214d214 < <remote-store cache="default" hotrod-wrapping="false" read-only="true"> < <remote-server outbound-socket-binding="remote-store-hotrod-server" /> < </remote-store> 449,451c449 <  <  < <remote-destination host="172.30.14.112" port="11222"/> {code} # Spinning new cluster involves the following commands: {code} oc new-app slaskawi/infinispan-experiments-2 oc env dc/infinispan-experiments-2 OPENSHIFT_KUBE_PING_LABELS=cluster=cluster-2 oc env dc/infinispan-experiments-2 OPENSHIFT_KUBE_PING_NAMESPACE=myproject oc label dc/infinispan-experiments-2 cluster=cluster-2 oc expose svc infinispan-experiments-2 {code} # At this stage we have 2 clusters (the old one with selector {{cluster=cluster-1}} and the new one with selector {{cluster=cluster-2}}). Both should be up and running (check that with {{oc status -v}}). Cluster-2 has remote stores which point to Cluster-1. # Switch all the clients to the {{cluster=cluster-2}}. Depending on your configuration you probably want to create a new Route (if your clients connect to the cluster using Routes) or modify the Service. # Fetch all remaining keys from {{cluster=cluster-1}} {code} oc get pods --selector=deploymentconfig=infinispan-experiments-2 .. write down oc exec infinispan-experiments-2-3-pc7sg -- '/opt/jboss/infinispan-server/bin/ispn-cli.sh' '-c' '--controller=$(hostname -i):9990' '/subsystem=datagrid-infinispan/cache-container=clustered/distributed-cache=default:synchronize-data(migrator-name=hotrod)' {code} > Implement Rolling Upgrades with Kubernetes > ------------------------------------------ > > Key: ISPN-6673 > URL: https://issues.jboss.org/browse/ISPN-6673 > Project: Infinispan > Issue Type: Feature Request > Components: Cloud Integrations > Reporter: Sebastian Łaskawiec > Assignee: Sebastian Łaskawiec > > There are 2 mechanisms which seems to do the same but are totally different: > * [Kubernetes Rolling Update|http://kubernetes.io/docs/user-guide/rolling-updates/] - replaces Pods in controllable fashon > * [Infinispan Rolling Updgrate|http://infinispan.org/docs/stable/user_guide/user_guide.html#_Ro...] - a procedure for upgrading Infinispan or changing the configuration > Kubernetes Rolling Updates can be used very easily for changing the configuration however if changes are not runtime-compatible, one might loss data. Potential way to avoid this is to use a Cache Store. All other changes must be propagated using Infinispan Rolling Upgrade procedure. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

8 years, 5 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

infinispan-issues July 2016