You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by ac...@apache.org on 2017/11/23 14:17:55 UTC
[camel] branch master updated (20936b1 -> 85e034b)
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git.
from 20936b1 CAMEL-11656 - add preSort option & update docs
new 4ebeb1f Use latest Hazelcast-Kubernetes 3.9.0 image for the example
new 85e034b Added instructions for Minishift too on the Hazelcast example
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../camel-example-hazelcast-kubernetes/ReadMe.md | 236 +++++++++++++--------
.../resources/fabric8/hazelcast-deployment.yaml | 2 +-
2 files changed, 149 insertions(+), 89 deletions(-)
--
To stop receiving notification emails like this one, please contact
['"commits@camel.apache.org" <co...@camel.apache.org>'].
[camel] 02/02: Added instructions for Minishift too on the
Hazelcast example
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 85e034b36d0c32eab1d4ea37cab08799f9d79f32
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Thu Nov 23 15:17:14 2017 +0100
Added instructions for Minishift too on the Hazelcast example
---
.../camel-example-hazelcast-kubernetes/ReadMe.md | 72 ++++++++++++++++++++--
1 file changed, 67 insertions(+), 5 deletions(-)
diff --git a/examples/camel-example-hazelcast-kubernetes/ReadMe.md b/examples/camel-example-hazelcast-kubernetes/ReadMe.md
index 7a432fd..c4384ed 100644
--- a/examples/camel-example-hazelcast-kubernetes/ReadMe.md
+++ b/examples/camel-example-hazelcast-kubernetes/ReadMe.md
@@ -6,7 +6,7 @@ This quickstart is based on the Kubernetes example here: https://github.com/kube
This example is based on:
-- Minikube (Kubernetes version >= 1.5)
+- Minikube (Kubernetes version >= 1.5) or Minishift (Openshift >= 3.5)
- Fabric8 Maven Plugin (version >= 3.2)
First thing you'll need to do is preparing the environment.
@@ -19,6 +19,13 @@ $ kubectl create -f src/main/resources/fabric8/hazelcast-service.yaml
$ kubectl create -f src/main/resources/fabric8/hazelcast-deployment.yaml
```
+or once your Minishift cluster is up and running:
+
+```
+$ oc create -f src/main/resources/fabric8/hazelcast-service.yaml
+$ oc create -f src/main/resources/fabric8/hazelcast-deployment.yaml
+```
+
To check the correct startup of the Hazelcast instance run the following command:
```
@@ -27,6 +34,14 @@ NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
hazelcast 1 1 1 1 1m
```
+or on Minishift
+
+```
+$ oc get deployment
+NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
+hazelcast 1 1 1 1 1m
+```
+
and check the status of the pod
```
@@ -35,12 +50,26 @@ NAME READY STATUS RESTARTS AGE
hazelcast-1638707704-n64tk 1/1 Running 0 1m
```
+on Minishift:
+
+```
+$ oc get pods
+NAME READY STATUS RESTARTS AGE
+hazelcast-1638707704-n64tk 1/1 Running 0 1m
+```
+
Now you can decide to scale-up your Hazelcast cluster
```
$ kubectl scale deployment hazelcast --replicas 4
```
+on Minishift
+
+```
+$ oc scale deployment hazelcast --replicas=4
+```
+
and again check the status of your pods
```
@@ -53,7 +82,19 @@ hazelcast-1638707704-z1g6r 1/1 Running 0 1m
```
-You can also take a look at the logs from the pods:
+on Minishift
+
+```
+$ oc get pods
+NAME READY STATUS RESTARTS AGE
+hazelcast-1638707704-g8qwh 1/1 Running 0 1m
+hazelcast-1638707704-n64tk 1/1 Running 0 3m
+hazelcast-1638707704-wwwff 1/1 Running 0 1m
+hazelcast-1638707704-z1g6r 1/1 Running 0 1m
+
+```
+
+You can also take a look at the logs from the pods with kubectl or oc
```
kubectl logs hazelcast-414548760-fb5bh
@@ -103,11 +144,19 @@ Navigate to the project folder and the example can be built with
When the example runs in fabric8, you can use the Kubectl command tool to inspect the status
-To list all the running pods:
+To list all the running pods on Minikube:
$ kubectl get pods
-Then find the name of the pod that runs this quickstart, and output the logs from the running pods with:
+Then find the name on Minikube of the pod that runs this quickstart, and output the logs from the running pods with:
+
+ $ kubectl logs <name of pod>
+
+To list all the running pods on Minishift:
+
+ $ oc get pods
+
+Then find the name on Minishift of the pod that runs this quickstart, and output the logs from the running pods with:
$ kubectl logs <name of pod>
@@ -155,7 +204,7 @@ INFO: hz.client_0 [someGroup] [3.9] Authenticated with server [172.17.0.9]:5701,
### Cleanup
-Run following to undeploy
+Run following to undeploy on Minikube
```
$ mvn -Pkubernetes-install fabric8:undeploy
@@ -163,8 +212,21 @@ $ kubectl delete -f src/main/resources/fabric8/hazelcast-deployment.yaml
$ kubectl delete -f src/main/resources/fabric8/hazelcast-service.yaml
```
+Run following to undeploy on Minishift
+
+```
+$ mvn -Pkubernetes-install fabric8:undeploy
+$ oc delete -f src/main/resources/fabric8/hazelcast-deployment.yaml
+$ oc delete -f src/main/resources/fabric8/hazelcast-service.yaml
+```
+
Make sure no pod is running
```
$ kubectl get pods
No resources found.
```
+
+```
+$ oc get pods
+No resources found.
+```
--
To stop receiving notification emails like this one, please contact
"commits@camel.apache.org" <co...@camel.apache.org>.
[camel] 01/02: Use latest Hazelcast-Kubernetes 3.9.0 image for the
example
Posted by ac...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
acosentino pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/camel.git
commit 4ebeb1fcd9cda4a1c189da7015f8b6e6a0522d9e
Author: Andrea Cosentino <an...@gmail.com>
AuthorDate: Thu Nov 23 14:21:59 2017 +0100
Use latest Hazelcast-Kubernetes 3.9.0 image for the example
---
.../camel-example-hazelcast-kubernetes/ReadMe.md | 164 ++++++++++-----------
.../resources/fabric8/hazelcast-deployment.yaml | 2 +-
2 files changed, 82 insertions(+), 84 deletions(-)
diff --git a/examples/camel-example-hazelcast-kubernetes/ReadMe.md b/examples/camel-example-hazelcast-kubernetes/ReadMe.md
index 67f87ed..7a432fd 100644
--- a/examples/camel-example-hazelcast-kubernetes/ReadMe.md
+++ b/examples/camel-example-hazelcast-kubernetes/ReadMe.md
@@ -31,8 +31,8 @@ and check the status of the pod
```
$ kubectl get pods
-NAME READY STATUS RESTARTS AGE
-hazelcast-414548760-fb5bh 1/1 Running 0 29s
+NAME READY STATUS RESTARTS AGE
+hazelcast-1638707704-n64tk 1/1 Running 0 1m
```
Now you can decide to scale-up your Hazelcast cluster
@@ -45,65 +45,53 @@ and again check the status of your pods
```
$ kubectl get pods
-NAME READY STATUS RESTARTS AGE
-hazelcast-414548760-37ktz 1/1 Running 0 23m
-hazelcast-414548760-fb5bh 1/1 Running 0 1d
-hazelcast-414548760-qntg7 1/1 Running 0 24m
-hazelcast-414548760-t38cp 1/1 Running 0 23m
+NAME READY STATUS RESTARTS AGE
+hazelcast-1638707704-g8qwh 1/1 Running 0 1m
+hazelcast-1638707704-n64tk 1/1 Running 0 3m
+hazelcast-1638707704-wwwff 1/1 Running 0 1m
+hazelcast-1638707704-z1g6r 1/1 Running 0 1m
+
```
You can also take a look at the logs from the pods:
```
kubectl logs hazelcast-414548760-fb5bh
-2017-09-12 12:06:17.638 INFO 7 --- [ main] com.github.pires.hazelcast.Application : Starting Application on hazelcast-414548760-fb5bh with PID 7 (/bootstrapper.jar started by root in /)
-2017-09-12 12:06:17.658 INFO 7 --- [ main] com.github.pires.hazelcast.Application : No active profile set, falling back to default profiles: default
-2017-09-12 12:06:17.712 INFO 7 --- [ main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@14514713: startup date [Tue Sep 12 12:06:17 GMT 2017]; root of context hierarchy
-2017-09-12 12:06:18.663 INFO 7 --- [ main] o.s.j.e.a.AnnotationMBeanExporter : Registering beans for JMX exposure on startup
-2017-09-12 12:06:18.675 INFO 7 --- [ main] c.g.p.h.HazelcastDiscoveryController : Asking k8s registry at https://kubernetes.default.svc.cluster.local..
-2017-09-12 12:06:19.103 INFO 7 --- [ main] c.g.p.h.HazelcastDiscoveryController : Found 1 pods running Hazelcast.
-2017-09-12 12:06:19.169 INFO 7 --- [ main] c.h.instance.DefaultAddressPicker : [LOCAL] [someGroup] [3.8.5] Interfaces is disabled, trying to pick one address from TCP-IP config addresses: [172.17.0.4]
-2017-09-12 12:06:19.169 INFO 7 --- [ main] c.h.instance.DefaultAddressPicker : [LOCAL] [someGroup] [3.8.5] Prefer IPv4 stack is true.
-2017-09-12 12:06:19.176 INFO 7 --- [ main] c.h.instance.DefaultAddressPicker : [LOCAL] [someGroup] [3.8.5] Picked [172.17.0.4]:5701, using socket ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=5701], bind any local is true
-2017-09-12 12:06:19.191 INFO 7 --- [ main] com.hazelcast.system : [172.17.0.4]:5701 [someGroup] [3.8.5] Hazelcast 3.8.5 (20170906 - e424927) starting at [172.17.0.4]:5701
-2017-09-12 12:06:19.191 INFO 7 --- [ main] com.hazelcast.system : [172.17.0.4]:5701 [someGroup] [3.8.5] Copyright (c) 2008-2016, Hazelcast, Inc. All Rights Reserved.
-2017-09-12 12:06:19.191 INFO 7 --- [ main] com.hazelcast.system : [172.17.0.4]:5701 [someGroup] [3.8.5] Configured Hazelcast Serialization version : 1
-2017-09-12 12:06:19.423 INFO 7 --- [ main] c.h.s.i.o.impl.BackpressureRegulator : [172.17.0.4]:5701 [someGroup] [3.8.5] Backpressure is disabled
-2017-09-12 12:06:20.048 INFO 7 --- [ main] com.hazelcast.instance.Node : [172.17.0.4]:5701 [someGroup] [3.8.5] Creating TcpIpJoiner
-2017-09-12 12:06:20.242 INFO 7 --- [ main] c.h.s.i.o.impl.OperationExecutorImpl : [172.17.0.4]:5701 [someGroup] [3.8.5] Starting 2 partition threads
-2017-09-12 12:06:20.250 INFO 7 --- [ main] c.h.s.i.o.impl.OperationExecutorImpl : [172.17.0.4]:5701 [someGroup] [3.8.5] Starting 3 generic threads (1 dedicated for priority tasks)
-2017-09-12 12:06:20.270 INFO 7 --- [ main] com.hazelcast.core.LifecycleService : [172.17.0.4]:5701 [someGroup] [3.8.5] [172.17.0.4]:5701 is STARTING
-2017-09-12 12:06:20.296 INFO 7 --- [ main] com.hazelcast.system : [172.17.0.4]:5701 [someGroup] [3.8.5] Cluster version set to 3.8
-2017-09-12 12:06:20.297 INFO 7 --- [ main] com.hazelcast.cluster.impl.TcpIpJoiner : [172.17.0.4]:5701 [someGroup] [3.8.5]
-
-
-Members [1] {
- Member [172.17.0.4]:5701 - 929e9148-870d-4f43-ba1d-fcc8ff973ab3 this
-}
-
-2017-09-12 12:06:20.340 INFO 7 --- [ main] com.hazelcast.core.LifecycleService : [172.17.0.4]:5701 [someGroup] [3.8.5] [172.17.0.4]:5701 is STARTED
-2017-09-12 12:06:20.343 INFO 7 --- [ main] com.github.pires.hazelcast.Application : Started Application in 3.325 seconds (JVM running for 3.747)
-2017-09-12 12:15:05.855 INFO 7 --- [thread-Acceptor] c.h.nio.tcp.SocketAcceptorThread : [172.17.0.4]:5701 [someGroup] [3.8.5] Accepting socket connection from /172.17.0.7:54699
-2017-09-12 12:15:05.863 INFO 7 --- [cached.thread-3] c.h.nio.tcp.TcpIpConnectionManager : [172.17.0.4]:5701 [someGroup] [3.8.5] Established socket connection between /172.17.0.4:5701 and /172.17.0.7:54699
-2017-09-12 12:15:12.856 INFO 7 --- [ration.thread-1] c.h.internal.cluster.ClusterService : [172.17.0.4]:5701 [someGroup] [3.8.5]
-
-Members [2] {
- Member [172.17.0.4]:5701 - 929e9148-870d-4f43-ba1d-fcc8ff973ab3 this
- Member [172.17.0.7]:5701 - 6d05a83b-2960-48b3-8dd2-63f6720115f5
-}
-
-2017-09-12 12:16:51.699 INFO 7 --- [thread-Acceptor] c.h.nio.tcp.SocketAcceptorThread : [172.17.0.4]:5701 [someGroup] [3.8.5] Accepting socket connection from /172.17.0.8:48921
-2017-09-12 12:16:51.736 INFO 7 --- [cached.thread-3] c.h.nio.tcp.TcpIpConnectionManager : [172.17.0.4]:5701 [someGroup] [3.8.5] Established socket connection between /172.17.0.4:5701 and /172.17.0.8:48921
-2017-09-12 12:16:56.258 INFO 7 --- [thread-Acceptor] c.h.nio.tcp.SocketAcceptorThread : [172.17.0.4]:5701 [someGroup] [3.8.5] Accepting socket connection from /172.17.0.9:40459
-2017-09-12 12:16:56.259 INFO 7 --- [cached.thread-4] c.h.nio.tcp.TcpIpConnectionManager : [172.17.0.4]:5701 [someGroup] [3.8.5] Established socket connection between /172.17.0.4:5701 and /172.17.0.9:40459
-2017-09-12 12:17:02.725 INFO 7 --- [ration.thread-0] c.h.internal.cluster.ClusterService : [172.17.0.4]:5701 [someGroup] [3.8.5]
-
-Members [4] {
- Member [172.17.0.4]:5701 - 929e9148-870d-4f43-ba1d-fcc8ff973ab3 this
- Member [172.17.0.7]:5701 - 6d05a83b-2960-48b3-8dd2-63f6720115f5
- Member [172.17.0.8]:5701 - 50ddeb59-8f06-43c6-91a8-c36fd86f825c
- Member [172.17.0.9]:5701 - e79a9a26-971d-4b67-8a46-1a78fee94324
-}
+2017-11-23 13:15:12.243 INFO 7 --- [ main] com.github.pires.hazelcast.Application : Starting Application on hazelcast-1638707704-z1g6r with PID 7 (/bootstrapper.jar started by root in /)
+2017-11-23 13:15:12.248 INFO 7 --- [ main] com.github.pires.hazelcast.Application : No active profile set, falling back to default profiles: default
+2017-11-23 13:15:12.290 INFO 7 --- [ main] s.c.a.AnnotationConfigApplicationContext : Refreshing org.springframework.context.annotation.AnnotationConfigApplicationContext@14514713: startup date [Thu Nov 23 13:15:12 GMT 2017]; root of context hierarchy
+2017-11-23 13:15:13.081 INFO 7 --- [ main] o.s.j.e.a.AnnotationMBeanExporter : Registering beans for JMX exposure on startup
+2017-11-23 13:15:13.089 INFO 7 --- [ main] c.g.p.h.HazelcastDiscoveryController : Asking k8s registry at https://kubernetes.default.svc.cluster.local..
+2017-11-23 13:15:13.442 INFO 7 --- [ main] c.g.p.h.HazelcastDiscoveryController : Found 2 pods running Hazelcast.
+2017-11-23 13:15:13.512 INFO 7 --- [ main] com.hazelcast.instance.AddressPicker : [LOCAL] [someGroup] [3.9] Interfaces is disabled, trying to pick one address from TCP-IP config addresses: [172.17.0.6, 172.17.0.7]
+2017-11-23 13:15:13.513 INFO 7 --- [ main] com.hazelcast.instance.AddressPicker : [LOCAL] [someGroup] [3.9] Prefer IPv4 stack is true.
+2017-11-23 13:15:13.519 INFO 7 --- [ main] com.hazelcast.instance.AddressPicker : [LOCAL] [someGroup] [3.9] Picked [172.17.0.7]:5701, using socket ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=5701], bind any local is true
+2017-11-23 13:15:13.538 INFO 7 --- [ main] com.hazelcast.system : [172.17.0.7]:5701 [someGroup] [3.9] Hazelcast 3.9 (20171023 - b29f549) starting at [172.17.0.7]:5701
+2017-11-23 13:15:13.538 INFO 7 --- [ main] com.hazelcast.system : [172.17.0.7]:5701 [someGroup] [3.9] Copyright (c) 2008-2017, Hazelcast, Inc. All Rights Reserved.
+2017-11-23 13:15:13.538 INFO 7 --- [ main] com.hazelcast.system : [172.17.0.7]:5701 [someGroup] [3.9] Configured Hazelcast Serialization version: 1
+2017-11-23 13:15:13.797 INFO 7 --- [ main] c.h.s.i.o.impl.BackpressureRegulator : [172.17.0.7]:5701 [someGroup] [3.9] Backpressure is disabled
+2017-11-23 13:15:14.293 INFO 7 --- [ main] com.hazelcast.instance.Node : [172.17.0.7]:5701 [someGroup] [3.9] Creating TcpIpJoiner
+2017-11-23 13:15:14.428 INFO 7 --- [ main] c.h.s.i.o.impl.OperationExecutorImpl : [172.17.0.7]:5701 [someGroup] [3.9] Starting 4 partition threads and 3 generic threads (1 dedicated for priority tasks)
+2017-11-23 13:15:14.433 INFO 7 --- [ main] c.h.internal.diagnostics.Diagnostics : [172.17.0.7]:5701 [someGroup] [3.9] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
+2017-11-23 13:15:14.438 INFO 7 --- [ main] com.hazelcast.core.LifecycleService : [172.17.0.7]:5701 [someGroup] [3.9] [172.17.0.7]:5701 is STARTING
+2017-11-23 13:15:14.465 INFO 7 --- [cached.thread-3] com.hazelcast.nio.tcp.TcpIpConnector : [172.17.0.7]:5701 [someGroup] [3.9] Connecting to /172.17.0.6:5701, timeout: 0, bind-any: true
+2017-11-23 13:15:14.468 INFO 7 --- [cached.thread-3] c.h.nio.tcp.TcpIpConnectionManager : [172.17.0.7]:5701 [someGroup] [3.9] Established socket connection between /172.17.0.7:59483 and /172.17.0.6:5701
+2017-11-23 13:15:18.171 INFO 7 --- [thread-Acceptor] com.hazelcast.nio.tcp.TcpIpAcceptor : [172.17.0.7]:5701 [someGroup] [3.9] Accepting socket connection from /172.17.0.8:35427
+2017-11-23 13:15:18.172 INFO 7 --- [cached.thread-3] c.h.nio.tcp.TcpIpConnectionManager : [172.17.0.7]:5701 [someGroup] [3.9] Established socket connection between /172.17.0.7:5701 and /172.17.0.8:35427
+2017-11-23 13:15:21.888 INFO 7 --- [thread-Acceptor] com.hazelcast.nio.tcp.TcpIpAcceptor : [172.17.0.7]:5701 [someGroup] [3.9] Accepting socket connection from /172.17.0.9:45315
+2017-11-23 13:15:21.890 INFO 7 --- [cached.thread-2] c.h.nio.tcp.TcpIpConnectionManager : [172.17.0.7]:5701 [someGroup] [3.9] Established socket connection between /172.17.0.7:5701 and /172.17.0.9:45315
+2017-11-23 13:15:27.900 INFO 7 --- [ration.thread-1] com.hazelcast.system : [172.17.0.7]:5701 [someGroup] [3.9] Cluster version set to 3.9
+2017-11-23 13:15:27.903 INFO 7 --- [ration.thread-1] c.h.internal.cluster.ClusterService : [172.17.0.7]:5701 [someGroup] [3.9]
+
+Members {size:4, ver:2} [
+ Member [172.17.0.6]:5701 - b9cc1fbb-fd27-4b0f-b6c6-9ba693c45e08
+ Member [172.17.0.7]:5701 - bcbbbcb4-7fd8-4a19-a2ed-0a3440b30887 this
+ Member [172.17.0.8]:5701 - 260d1057-d28e-40ff-9a0b-5ed4d23e5576
+ Member [172.17.0.9]:5701 - 6a0450c7-e9ea-4b92-91ee-71462f4362e3
+]
+
+2017-11-23 13:15:29.497 INFO 7 --- [ main] com.hazelcast.core.LifecycleService : [172.17.0.7]:5701 [someGroup] [3.9] [172.17.0.7]:5701 is STARTED
+2017-11-23 13:15:29.498 INFO 7 --- [ main] com.github.pires.hazelcast.Application : Started Application in 17.704 seconds (JVM running for 18.099)
```
@@ -126,45 +114,55 @@ Then find the name of the pod that runs this quickstart, and output the logs fro
and you should see something like this:
```
-INFO: hz.client_0 [someGroup] [3.8.5] HazelcastClient 3.8.5 (20170906 - e424927) is CLIENT_CONNECTED
-2017-09-12 12:42:22,764 [main ] INFO SpringCamelContext - Apache Camel 2.20.0-SNAPSHOT (CamelContext: camel-1) is starting
-2017-09-12 12:42:22,765 [main ] INFO ManagedManagementStrategy - JMX is enabled
-2017-09-12 12:42:22,880 [main ] INFO DefaultTypeConverter - Type converters loaded (core: 192, classpath: 1)
-2017-09-12 12:42:23,012 [main ] INFO SpringCamelContext - StreamCaching is not in use. If using streams then its recommended to enable stream caching. See more details at http://camel.apache.org/stream-caching.html
-Sep 12, 2017 12:42:23 PM com.hazelcast.client.connection.ClientConnectionManager
-INFO: hz.client_0 [someGroup] [3.8.5] Authenticated with server [172.17.0.9]:5701, server version:3.8.5 Local address: /172.17.0.10:37452
-Sep 12, 2017 12:42:23 PM com.hazelcast.client.connection.ClientConnectionManager
-INFO: hz.client_0 [someGroup] [3.8.5] Authenticated with server [172.17.0.7]:5701, server version:3.8.5 Local address: /172.17.0.10:34884
-Sep 12, 2017 12:42:23 PM com.hazelcast.client.connection.ClientConnectionManager
-INFO: hz.client_0 [someGroup] [3.8.5] Authenticated with server [172.17.0.4]:5701, server version:3.8.5 Local address: /172.17.0.10:45126
-2017-09-12 12:42:25,250 [main ] INFO SpringCamelContext - Route: route1 started and consuming from: timer://foo?period=5000
-2017-09-12 12:42:25,251 [main ] INFO SpringCamelContext - Route: route2 started and consuming from: hazelcast-topic://foo
-2017-09-12 12:42:25,258 [main ] INFO SpringCamelContext - Total 2 routes, of which 2 are started
-2017-09-12 12:42:25,260 [main ] INFO SpringCamelContext - Apache Camel 2.20.0-SNAPSHOT (CamelContext: camel-1) started in 2.495 seconds
-2017-09-12 12:42:25,264 [main ] INFO DefaultLifecycleProcessor - Starting beans in phase 2147483646
-2017-09-12 12:42:26,264 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
-2017-09-12 12:42:26,335 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
-2017-09-12 12:42:31,258 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
-2017-09-12 12:42:31,265 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
-2017-09-12 12:42:36,258 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
-2017-09-12 12:42:36,260 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
-2017-09-12 12:42:41,258 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
-2017-09-12 12:42:41,260 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
-2017-09-12 12:42:46,259 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
-2017-09-12 12:42:46,261 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
-2017-09-12 12:42:51,260 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
-2017-09-12 12:42:51,261 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
+INFO: hz.client_0 [someGroup] [3.9] Setting ClientConnection{alive=true, connectionId=1, channel=NioChannel{/172.17.0.10:44111->hazelcast/10.0.0.110:5701}, remoteEndpoint=[172.17.0.8]:5701, lastReadTime=2017-11-23 13:19:30.465, lastWriteTime=2017-11-23 13:19:30.462, closedTime=never, lastHeartbeatRequested=never, lastHeartbeatReceived=never, connected server version=3.9} as owner with principal ClientPrincipal{uuid='72e2102a-e64b-4138-8f6e-7160005533a8', ownerUuid='260d1057-d28e-40ff-9a0 [...]
+Nov 23, 2017 1:19:30 PM com.hazelcast.core.LifecycleService
+INFO: hz.client_0 [someGroup] [3.9] HazelcastClient 3.9 (20171023 - b29f549) is CLIENT_CONNECTED
+Nov 23, 2017 1:19:30 PM com.hazelcast.internal.diagnostics.Diagnostics
+INFO: hz.client_0 [someGroup] [3.9] Diagnostics disabled. To enable add -Dhazelcast.diagnostics.enabled=true to the JVM arguments.
+2017-11-23 13:19:30,503 [main ] INFO SpringCamelContext - Apache Camel 2.21.0-SNAPSHOT (CamelContext: camel-1) is starting
+2017-11-23 13:19:30,515 [main ] INFO ManagedManagementStrategy - JMX is enabled
+2017-11-23 13:19:30,601 [main ] INFO DefaultTypeConverter - Type converters loaded (core: 193, classpath: 1)
+2017-11-23 13:19:30,766 [main ] INFO SpringCamelContext - StreamCaching is not in use. If using streams then its recommended to enable stream caching. See more details at http://camel.apache.org/stream-caching.html
+Nov 23, 2017 1:19:30 PM com.hazelcast.client.connection.ClientConnectionManager
+INFO: hz.client_0 [someGroup] [3.9] Authenticated with server [172.17.0.6]:5701, server version:3.9 Local address: /172.17.0.10:44473
+Nov 23, 2017 1:19:30 PM com.hazelcast.client.connection.ClientConnectionManager
+INFO: hz.client_0 [someGroup] [3.9] Authenticated with server [172.17.0.7]:5701, server version:3.9 Local address: /172.17.0.10:39823
+Nov 23, 2017 1:19:30 PM com.hazelcast.client.connection.ClientConnectionManager
+INFO: hz.client_0 [someGroup] [3.9] Authenticated with server [172.17.0.9]:5701, server version:3.9 Local address: /172.17.0.10:44799
+2017-11-23 13:19:30,933 [main ] INFO SpringCamelContext - Route: route1 started and consuming from: timer://foo?period=5000
+2017-11-23 13:19:30,934 [main ] INFO SpringCamelContext - Route: route2 started and consuming from: hazelcast-topic://foo
+2017-11-23 13:19:30,935 [main ] INFO SpringCamelContext - Total 2 routes, of which 2 are started
+2017-11-23 13:19:30,938 [main ] INFO SpringCamelContext - Apache Camel 2.21.0-SNAPSHOT (CamelContext: camel-1) started in 0.434 seconds
+2017-11-23 13:19:30,941 [main ] INFO DefaultLifecycleProcessor - Starting beans in phase 2147483646
+2017-11-23 13:19:31,943 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
+2017-11-23 13:19:31,957 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
+2017-11-23 13:19:36,936 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
+2017-11-23 13:19:36,941 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
+2017-11-23 13:19:41,937 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
+2017-11-23 13:19:41,939 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
+2017-11-23 13:19:46,936 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
+2017-11-23 13:19:46,938 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
+2017-11-23 13:19:51,936 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
+2017-11-23 13:19:51,939 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
+2017-11-23 13:19:56,936 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
+2017-11-23 13:19:56,938 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
+2017-11-23 13:20:01,936 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
+2017-11-23 13:20:01,938 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
+2017-11-23 13:20:06,936 [2 - timer://foo] INFO route1 - Producer side: Sending data to Hazelcast topic..
+2017-11-23 13:20:06,941 [lient_0.event-3] INFO route2 - Consumer side: Detected following action: received
```
### Cleanup
Run following to undeploy
+
```
$ mvn -Pkubernetes-install fabric8:undeploy
$ kubectl delete -f src/main/resources/fabric8/hazelcast-deployment.yaml
$ kubectl delete -f src/main/resources/fabric8/hazelcast-service.yaml
```
+
Make sure no pod is running
```
$ kubectl get pods
diff --git a/examples/camel-example-hazelcast-kubernetes/src/main/resources/fabric8/hazelcast-deployment.yaml b/examples/camel-example-hazelcast-kubernetes/src/main/resources/fabric8/hazelcast-deployment.yaml
index d4a8ad5..c245d6b 100644
--- a/examples/camel-example-hazelcast-kubernetes/src/main/resources/fabric8/hazelcast-deployment.yaml
+++ b/examples/camel-example-hazelcast-kubernetes/src/main/resources/fabric8/hazelcast-deployment.yaml
@@ -12,7 +12,7 @@ spec:
spec:
containers:
- name: hazelcast
- image: quay.io/pires/hazelcast-kubernetes:3.8.5
+ image: quay.io/pires/hazelcast-kubernetes:3.9.0
imagePullPolicy: Always
env:
- name: "DNS_DOMAIN"
--
To stop receiving notification emails like this one, please contact
"commits@camel.apache.org" <co...@camel.apache.org>.