[
https://issues.jboss.org/browse/ISPN-7494?page=com.atlassian.jira.plugin....
]
Sebastian Łaskawiec updated ISPN-7494:
--------------------------------------
Comment: was deleted
(was: It seems the new Rollout API behaves better:
{noformat}
oc rollout status dc/transactions-repository
1 ↵
Waiting for rollout to finish: 1 out of 3 new replicas have been updated...
Waiting for rollout to finish: 1 out of 3 new replicas have been updated...
Waiting for rollout to finish: 1 out of 3 new replicas have been updated...
Waiting for rollout to finish: 1 out of 3 new replicas have been updated...
Waiting for rollout to finish: 1 out of 3 new replicas have been updated...
Waiting for rollout to finish: 2 out of 3 new replicas have been updated...
Waiting for rollout to finish: 2 out of 3 new replicas have been updated...
Waiting for rollout to finish: 2 out of 3 new replicas have been updated...
Waiting for rollout to finish: 2 out of 3 new replicas have been updated...
Waiting for rollout to finish: 2 out of 3 new replicas have been updated...
Waiting for rollout to finish: 2 out of 3 new replicas have been updated...
Waiting for rollout to finish: 2 out of 3 new replicas have been updated...
Waiting for rollout to finish: 1 old replicas are pending termination...
Waiting for rollout to finish: 1 old replicas are pending termination...
Waiting for rollout to finish: 1 old replicas are pending termination...
Waiting for rollout to finish: 1 old replicas are pending termination...
Waiting for rollout to finish: 1 old replicas are pending termination...
Waiting for rollout to finish: 2 of 3 updated replicas are available...
replication controller "transactions-repository-2" successfully rolled out
{noformat}
{noformat}
oc logs transactions-repository-2-deploy -f
--> Scaling up transactions-repository-2 from 0 to 3, scaling down
transactions-repository-1 from 3 to 0 (keep 2 pods available, don't exceed 4 pods)
Scaling transactions-repository-2 up to 1
Scaling transactions-repository-1 down to 2
Scaling transactions-repository-2 up to 2
Scaling transactions-repository-1 down to 1
Scaling transactions-repository-2 up to 3
Scaling transactions-repository-1 down to 0
--> Success
{noformat})
Prevent Kubernetes from killing 2 nodes at the same time
--------------------------------------------------------
Key: ISPN-7494
URL:
https://issues.jboss.org/browse/ISPN-7494
Project: Infinispan
Issue Type: Sub-task
Components: Cloud Integrations
Affects Versions: 9.0.0.Beta2
Environment: * OpenShift {{v1.5.0-alpha.2+e4b43ee}}
* Infinispan Server 9.0.0.Beta2
Reporter: Sebastian Łaskawiec
Assignee: Sebastian Łaskawiec
Priority: Blocker
When I was performing [Spring Session and Kubernetes Rolling Update
demo|https://bluejeans.com/s/pYKUg/] I encountered a couple of problems.
One of the is this:
{noformat}
[transactions-repository-1-hqz3v] *** JBossAS process (83) received TERM signal ***
[transactions-repository-1-dwl81] 09:52:09,522 INFO [org.jboss.as.server] (Thread-2)
WFLYSRV0220: Server shutdown has been requested via an OS signal
[transactions-repository-1-dwl81] *** JBossAS process (80) received TERM signal ***
[transactions-repository-1-hqz3v] 09:52:09,526 INFO [org.jboss.as.server] (Thread-2)
WFLYSRV0220: Server shutdown has been requested via an OS signal
{noformat}
Full logs from Rolling Update process might be found here:
https://gist.github.com/slaskawi/2308b4c5e9bbf523fb3e02a7cc45fa24
Steps to reproduce:
* Start local OpenShift Cluster
* invoke `./init_infrastructure.sh` from
https://github.com/slaskawi/presentations/tree/ISPN-7487-reproducer
* invoke `cd transaction-creator && mvn fabric8:run`
* Start Spring Session Demo `cd session-demo && mvn fabric8:run`
* Create a client which inserts data (`watch -n 0.5 curl
http://<spring-session-demo-pod-ip>/sessions`) and at the same time invoke the
rolling update: `oc deploy transactions-repository --latest -n myproject`
* Observe logs `kubetail -l environment=infrastructure`
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)