Repository: camel
Updated Branches:
  refs/heads/master cbf469e2f -> 4b094993f


Update README of camel-example-hazelcast-kubernetes


Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/4b094993
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/4b094993
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/4b094993

Branch: refs/heads/master
Commit: 4b094993f88d67d3e107f9307185c4b1397882f4
Parents: a71807c
Author: Andrea Cosentino <anco...@gmail.com>
Authored: Fri May 26 14:17:04 2017 +0200
Committer: Andrea Cosentino <anco...@gmail.com>
Committed: Fri May 26 14:17:26 2017 +0200

----------------------------------------------------------------------
 .../ReadMe.md                                   | 140 +++++++++++--------
 1 file changed, 83 insertions(+), 57 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/camel/blob/4b094993/examples/camel-example-hazelcast-kubernetes/ReadMe.md
----------------------------------------------------------------------
diff --git a/examples/camel-example-hazelcast-kubernetes/ReadMe.md 
b/examples/camel-example-hazelcast-kubernetes/ReadMe.md
index d046bb5..20769a9 100644
--- a/examples/camel-example-hazelcast-kubernetes/ReadMe.md
+++ b/examples/camel-example-hazelcast-kubernetes/ReadMe.md
@@ -32,57 +32,72 @@ and check the status of the pod
 ```
 kubectl get pods
 NAME                                        READY     STATUS             
RESTARTS   AGE
-hazelcast-3980717115-x730g                  1/1       Running            0     
     29s
+hazelcast-2400991854-1zk9g                  1/1       Running            0     
     29s
 ```
 
 Now you can decide to scale-up your Hazelcast cluster
 
 ```
-kubectl scale deployment hazelcast --replicas 2
+kubectl scale deployment hazelcast --replicas 4
 ```
 
 and again check the status of your pods
 
 ```
 kubectl get pods
-NAME                                           READY     STATUS    RESTARTS   
AGE
-hazelcast-4195412960-0tl3w                     1/1       Running   0          
7s
-hazelcast-4195412960-mgqtk                     1/1       Running   0          
2m
+NAME                                                  READY     STATUS    
RESTARTS   AGE
+hazelcast-2400991854-1zk9g                            1/1       Running   1    
      8m
+hazelcast-2400991854-4pwn8                            1/1       Running   1    
      6m
+hazelcast-2400991854-fbx4b                            1/1       Running   1    
      6m
+hazelcast-2400991854-wh2sr                            1/1       Running   1    
      6m
 ```
 
 You can also take a look at the logs from the pods:
 
 ```
-kubectl logs hazelcast-3980717115-n1snd
-2017-03-15 09:42:45.046  INFO 7 --- [           main] 
com.github.pires.hazelcast.Application   : Starting Application on 
hazelcast-4195412960-0tl3w with PID 7 (/bootstrapper.jar started by root in /)
-2017-03-15 09:42:45.060  INFO 7 --- [           main] 
com.github.pires.hazelcast.Application   : No active profile set, falling back 
to default profiles: default
-2017-03-15 09:42:45.128  INFO 7 --- [           main] 
s.c.a.AnnotationConfigApplicationContext : Refreshing 
org.springframework.context.annotation.AnnotationConfigApplicationContext@14514713:
 startup date [Wed Mar 15 09:42:45 GMT 2017]; root of context hierarchy
-2017-03-15 09:42:45.989  INFO 7 --- [           main] 
o.s.j.e.a.AnnotationMBeanExporter        : Registering beans for JMX exposure 
on startup
-2017-03-15 09:42:46.001  INFO 7 --- [           main] 
c.g.p.h.HazelcastDiscoveryController     : Asking k8s registry at 
https://kubernetes.default.svc.cluster.local..
-2017-03-15 09:42:46.376  INFO 7 --- [           main] 
c.g.p.h.HazelcastDiscoveryController     : Found 2 pods running Hazelcast.
-2017-03-15 09:42:46.458  INFO 7 --- [           main] 
c.h.instance.DefaultAddressPicker        : [LOCAL] [someGroup] [3.8] Interfaces 
is disabled, trying to pick one address from TCP-IP config addresses: 
[172.17.0.6, 172.17.0.2]
-2017-03-15 09:42:46.458  INFO 7 --- [           main] 
c.h.instance.DefaultAddressPicker        : [LOCAL] [someGroup] [3.8] Prefer 
IPv4 stack is true.
-2017-03-15 09:42:46.464  INFO 7 --- [           main] 
c.h.instance.DefaultAddressPicker        : [LOCAL] [someGroup] [3.8] Picked 
[172.17.0.6]:5701, using socket 
ServerSocket[addr=/0:0:0:0:0:0:0:0,localport=5701], bind any local is true
-2017-03-15 09:42:46.484  INFO 7 --- [           main] com.hazelcast.system     
                : [172.17.0.6]:5701 [someGroup] [3.8] Hazelcast 3.8 (20170217 - 
d7998b4) starting at [172.17.0.6]:5701
-2017-03-15 09:42:46.484  INFO 7 --- [           main] com.hazelcast.system     
                : [172.17.0.6]:5701 [someGroup] [3.8] Copyright (c) 2008-2017, 
Hazelcast, Inc. All Rights Reserved.
-2017-03-15 09:42:46.485  INFO 7 --- [           main] com.hazelcast.system     
                : [172.17.0.6]:5701 [someGroup] [3.8] Configured Hazelcast 
Serialization version : 1
-2017-03-15 09:42:46.679  INFO 7 --- [           main] 
c.h.s.i.o.impl.BackpressureRegulator     : [172.17.0.6]:5701 [someGroup] [3.8] 
Backpressure is disabled
-2017-03-15 09:42:47.069  INFO 7 --- [           main] 
com.hazelcast.instance.Node              : [172.17.0.6]:5701 [someGroup] [3.8] 
Creating TcpIpJoiner
-2017-03-15 09:42:47.182  INFO 7 --- [           main] 
c.h.s.i.o.impl.OperationExecutorImpl     : [172.17.0.6]:5701 [someGroup] [3.8] 
Starting 2 partition threads
-2017-03-15 09:42:47.189  INFO 7 --- [           main] 
c.h.s.i.o.impl.OperationExecutorImpl     : [172.17.0.6]:5701 [someGroup] [3.8] 
Starting 3 generic threads (1 dedicated for priority tasks)
-2017-03-15 09:42:47.197  INFO 7 --- [           main] 
com.hazelcast.core.LifecycleService      : [172.17.0.6]:5701 [someGroup] [3.8] 
[172.17.0.6]:5701 is STARTING
-2017-03-15 09:42:47.253  INFO 7 --- [cached.thread-3] 
c.hazelcast.nio.tcp.InitConnectionTask   : [172.17.0.6]:5701 [someGroup] [3.8] 
Connecting to /172.17.0.2:5701, timeout: 0, bind-any: true
-2017-03-15 09:42:47.262  INFO 7 --- [cached.thread-3] 
c.h.nio.tcp.TcpIpConnectionManager       : [172.17.0.6]:5701 [someGroup] [3.8] 
Established socket connection between /172.17.0.6:58073 and /172.17.0.2:5701
-2017-03-15 09:42:54.260  INFO 7 --- [ration.thread-0] com.hazelcast.system     
                : [172.17.0.6]:5701 [someGroup] [3.8] Cluster version set to 3.8
-2017-03-15 09:42:54.262  INFO 7 --- [ration.thread-0] 
c.h.internal.cluster.ClusterService      : [172.17.0.6]:5701 [someGroup] [3.8] 
-
-Members [2] {
-       Member [172.17.0.2]:5701 - 170f6924-7888-442a-9875-ad4d25659a8a
-       Member [172.17.0.6]:5701 - b1b82bfa-86c2-4931-af57-325c10c03b3b this
+kubectl logs hazelcast-2400991854-1zk9g
+2017-05-26 12:07:40.267  INFO 7 --- [           main] 
com.github.pires.hazelcast.Application   : Starting Application on 
hazelcast-2400991854-1zk9g with PID 7 (/bootstrapper.jar started by root in /)
+2017-05-26 12:07:40.270  INFO 7 --- [           main] 
com.github.pires.hazelcast.Application   : No active profile set, falling back 
to default profiles: default
+2017-05-26 12:07:40.335  INFO 7 --- [           main] 
s.c.a.AnnotationConfigApplicationContext : Refreshing 
org.springframework.context.annotation.AnnotationConfigApplicationContext@14514713:
 startup date [Fri May 26 12:07:40 GMT 2017]; root of context hierarchy
+2017-05-26 12:07:41.083  INFO 7 --- [           main] 
o.s.j.e.a.AnnotationMBeanExporter        : Registering beans for JMX exposure 
on startup
+2017-05-26 12:07:41.091  INFO 7 --- [           main] 
c.g.p.h.HazelcastDiscoveryController     : Asking k8s registry at 
https://kubernetes.default.svc.cluster.local..
+2017-05-26 12:07:41.447  INFO 7 --- [           main] 
c.g.p.h.HazelcastDiscoveryController     : Found 1 pods running Hazelcast.
+2017-05-26 12:07:41.508  INFO 7 --- [           main] 
c.h.instance.DefaultAddressPicker        : [LOCAL] [someGroup] [3.8.2] 
Interfaces is disabled, trying to pick one address from TCP-IP config 
addresses: [172.17.0.4]
+2017-05-26 12:07:41.508  INFO 7 --- [           main] 
c.h.instance.DefaultAddressPicker        : [LOCAL] [someGroup] [3.8.2] Prefer 
IPv4 stack is true.
+2017-05-26 12:07:41.514  INFO 7 --- [           main] 
c.h.instance.DefaultAddressPicker        : [LOCAL] [someGroup] [3.8.2] 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-05-26 12:07:41.528  INFO 7 --- [           main] com.hazelcast.system     
                : [172.17.0.4]:5701 [someGroup] [3.8.2] Hazelcast 3.8.2 
(20170518 - a60f944) starting at [172.17.0.4]:5701
+2017-05-26 12:07:41.529  INFO 7 --- [           main] com.hazelcast.system     
                : [172.17.0.4]:5701 [someGroup] [3.8.2] Copyright (c) 
2008-2016, Hazelcast, Inc. All Rights Reserved.
+2017-05-26 12:07:41.529  INFO 7 --- [           main] com.hazelcast.system     
                : [172.17.0.4]:5701 [someGroup] [3.8.2] Configured Hazelcast 
Serialization version : 1
+2017-05-26 12:07:41.741  INFO 7 --- [           main] 
c.h.s.i.o.impl.BackpressureRegulator     : [172.17.0.4]:5701 [someGroup] 
[3.8.2] Backpressure is disabled
+2017-05-26 12:07:42.187  INFO 7 --- [           main] 
com.hazelcast.instance.Node              : [172.17.0.4]:5701 [someGroup] 
[3.8.2] Creating TcpIpJoiner
+2017-05-26 12:07:42.315  INFO 7 --- [           main] 
c.h.s.i.o.impl.OperationExecutorImpl     : [172.17.0.4]:5701 [someGroup] 
[3.8.2] Starting 2 partition threads
+2017-05-26 12:07:42.318  INFO 7 --- [           main] 
c.h.s.i.o.impl.OperationExecutorImpl     : [172.17.0.4]:5701 [someGroup] 
[3.8.2] Starting 3 generic threads (1 dedicated for priority tasks)
+2017-05-26 12:07:42.324  INFO 7 --- [           main] 
com.hazelcast.core.LifecycleService      : [172.17.0.4]:5701 [someGroup] 
[3.8.2] [172.17.0.4]:5701 is STARTING
+2017-05-26 12:07:42.336  INFO 7 --- [           main] com.hazelcast.system     
                : [172.17.0.4]:5701 [someGroup] [3.8.2] Cluster version set to 
3.8
+2017-05-26 12:07:42.338  INFO 7 --- [           main] 
com.hazelcast.cluster.impl.TcpIpJoiner   : [172.17.0.4]:5701 [someGroup] 
[3.8.2] 
+
+
+Members [1] {
+       Member [172.17.0.4]:5701 - d9f0d2db-ec68-4352-93a3-90b3f264d061 this
+}
+
+2017-05-26 12:07:42.363  INFO 7 --- [           main] 
com.hazelcast.core.LifecycleService      : [172.17.0.4]:5701 [someGroup] 
[3.8.2] [172.17.0.4]:5701 is STARTED
+2017-05-26 12:07:42.365  INFO 7 --- [           main] 
com.github.pires.hazelcast.Application   : Started Application in 2.55 seconds 
(JVM running for 3.014)
+2017-05-26 12:08:36.270  INFO 7 --- [thread-Acceptor] 
c.h.nio.tcp.SocketAcceptorThread         : [172.17.0.4]:5701 [someGroup] 
[3.8.2] Accepting socket connection from /172.17.0.7:43717
+2017-05-26 12:08:36.290  INFO 7 --- [cached.thread-2] 
c.h.nio.tcp.TcpIpConnectionManager       : [172.17.0.4]:5701 [someGroup] 
[3.8.2] Established socket connection between /172.17.0.4:5701 and 
/172.17.0.7:43717
+2017-05-26 12:08:40.117  INFO 7 --- [thread-Acceptor] 
c.h.nio.tcp.SocketAcceptorThread         : [172.17.0.4]:5701 [someGroup] 
[3.8.2] Accepting socket connection from /172.17.0.5:37139
+2017-05-26 12:08:40.120  INFO 7 --- [cached.thread-2] 
c.h.nio.tcp.TcpIpConnectionManager       : [172.17.0.4]:5701 [someGroup] 
[3.8.2] Established socket connection between /172.17.0.4:5701 and 
/172.17.0.5:37139
+2017-05-26 12:08:44.004  INFO 7 --- [thread-Acceptor] 
c.h.nio.tcp.SocketAcceptorThread         : [172.17.0.4]:5701 [someGroup] 
[3.8.2] Accepting socket connection from /172.17.0.6:36975
+2017-05-26 12:08:44.013  INFO 7 --- [cached.thread-2] 
c.h.nio.tcp.TcpIpConnectionManager       : [172.17.0.4]:5701 [someGroup] 
[3.8.2] Established socket connection between /172.17.0.4:5701 and 
/172.17.0.6:36975
+2017-05-26 12:08:50.132  INFO 7 --- [ration.thread-0] 
c.h.internal.cluster.ClusterService      : [172.17.0.4]:5701 [someGroup] 
[3.8.2] 
+
+Members [4] {
+       Member [172.17.0.4]:5701 - d9f0d2db-ec68-4352-93a3-90b3f264d061 this
+       Member [172.17.0.7]:5701 - 7d9a02fb-267e-4dae-92af-c461db0be93b
+       Member [172.17.0.5]:5701 - 15c21689-2aab-4de8-b1ca-ee681b33dfa9
+       Member [172.17.0.6]:5701 - f63fcf65-f477-451a-a805-e68ba7cd1d79
 }
 
-2017-03-15 09:42:56.285  INFO 7 --- [           main] 
com.hazelcast.core.LifecycleService      : [172.17.0.6]:5701 [someGroup] [3.8] 
[172.17.0.6]:5701 is STARTED
-2017-03-15 09:42:56.287  INFO 7 --- [           main] 
com.github.pires.hazelcast.Application   : Started Application in 11.831 
seconds (JVM running for 12.219)
 ```
 
 ### Building and running
@@ -104,28 +119,39 @@ 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] HazelcastClient 3.8 (20170217 - d7998b4) 
is CLIENT_CONNECTED
-2017-03-10 10:05:23,851 [main           ] INFO  SpringCamelContext             
- Apache Camel 2.19.0-SNAPSHOT (CamelContext: camel-1) is starting
-2017-03-10 10:05:23,852 [main           ] INFO  ManagedManagementStrategy      
- JMX is enabled
-2017-03-10 10:05:23,975 [main           ] INFO  DefaultTypeConverter           
- Loaded 192 type converters
-2017-03-10 10:05:23,995 [main           ] INFO  DefaultRuntimeEndpointRegistry 
- Runtime endpoint registry is in extended mode gathering usage statistics of 
all incoming and outgoing endpoints (cache limit: 1000)
-2017-03-10 10:05:24,061 [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
-2017-03-10 10:05:24,114 [main           ] INFO  SpringCamelContext             
- Route: route1 started and consuming from: timer://foo?period=5000
-2017-03-10 10:05:24,115 [main           ] INFO  SpringCamelContext             
- Route: route2 started and consuming from: hazelcast-topic://foo
-2017-03-10 10:05:24,116 [main           ] INFO  SpringCamelContext             
- Total 2 routes, of which 2 are started.
-2017-03-10 10:05:24,119 [main           ] INFO  SpringCamelContext             
- Apache Camel 2.19.0-SNAPSHOT (CamelContext: camel-1) started in 0.265 seconds
-Mar 10, 2017 10:05:24 AM 
com.hazelcast.client.connection.ClientConnectionManager
-INFO: hz.client_0 [someGroup] [3.8] Authenticated with server 
[172.17.0.4]:5701, server version:3.8 Local address: /172.17.0.7:46948
-2017-03-10 10:05:25,125 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
-2017-03-10 10:05:25,139 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
-2017-03-10 10:05:30,120 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
-2017-03-10 10:05:30,127 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
-2017-03-10 10:05:35,116 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
-2017-03-10 10:05:35,118 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
-2017-03-10 10:05:40,117 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
-2017-03-10 10:05:40,118 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
-2017-03-10 10:05:45,117 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
-2017-03-10 10:05:45,119 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
-2017-03-10 10:05:50,117 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
-2017-03-10 10:05:50,118 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
+INFO: hz.client_0 [someGroup] [3.8.2] HazelcastClient 3.8.2 (20170518 - 
a60f944) is CLIENT_CONNECTED
+2017-05-26 12:14:57,135 [main           ] INFO  SpringCamelContext             
- Apache Camel 2.20.0-SNAPSHOT (CamelContext: camel-1) is starting
+2017-05-26 12:14:57,136 [main           ] INFO  ManagedManagementStrategy      
- JMX is enabled
+2017-05-26 12:14:57,271 [main           ] INFO  DefaultTypeConverter           
- Loaded 193 type converters
+2017-05-26 12:14:57,302 [main           ] INFO  DefaultRuntimeEndpointRegistry 
- Runtime endpoint registry is in extended mode gathering usage statistics of 
all incoming and outgoing endpoints (cache limit: 1000)
+2017-05-26 12:14:57,405 [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
+May 26, 2017 12:14:57 PM 
com.hazelcast.client.connection.ClientConnectionManager
+INFO: hz.client_0 [someGroup] [3.8.2] Authenticated with server 
[172.17.0.7]:5701, server version:3.8.2 Local address: /172.17.0.8:37538
+May 26, 2017 12:14:58 PM 
com.hazelcast.client.connection.ClientConnectionManager
+INFO: hz.client_0 [someGroup] [3.8.2] Authenticated with server 
[172.17.0.2]:5701, server version:3.8.2 Local address: /172.17.0.8:59990
+May 26, 2017 12:14:58 PM 
com.hazelcast.client.connection.ClientConnectionManager
+INFO: hz.client_0 [someGroup] [3.8.2] Authenticated with server 
[172.17.0.4]:5701, server version:3.8.2 Local address: /172.17.0.8:38928
+2017-05-26 12:14:59,956 [main           ] INFO  SpringCamelContext             
- Route: route1 started and consuming from: timer://foo?period=5000
+2017-05-26 12:14:59,960 [main           ] INFO  SpringCamelContext             
- Route: route2 started and consuming from: hazelcast-topic://foo
+2017-05-26 12:14:59,961 [main           ] INFO  SpringCamelContext             
- Total 2 routes, of which 2 are started.
+2017-05-26 12:14:59,963 [main           ] INFO  SpringCamelContext             
- Apache Camel 2.20.0-SNAPSHOT (CamelContext: camel-1) started in 2.825 seconds
+2017-05-26 12:15:00,972 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
+2017-05-26 12:15:01,001 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
+2017-05-26 12:15:05,967 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
+2017-05-26 12:15:05,974 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
+2017-05-26 12:15:10,961 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
+2017-05-26 12:15:10,963 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
+2017-05-26 12:15:15,961 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
+2017-05-26 12:15:15,963 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
+2017-05-26 12:15:20,962 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
+2017-05-26 12:15:20,964 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
+2017-05-26 12:15:25,962 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
+2017-05-26 12:15:25,963 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
+2017-05-26 12:15:30,962 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
+2017-05-26 12:15:30,965 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
+2017-05-26 12:15:35,961 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
+2017-05-26 12:15:35,963 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
+2017-05-26 12:15:40,962 [0 - timer://foo] INFO  route1                         
- Producer side: Sending data to Hazelcast topic..
+2017-05-26 12:15:40,964 [lient_0.event-3] INFO  route2                         
- Consumer side: Detected following action: received
+
 ```

Reply via email to