You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
gfsh>start server --name=server1 --bind-address=127.0.0.1 --cache-xml-file=~/redis-connect-gemfire/config/samples/cdc/gemfire2redis/cache.xml
43
+
gfsh>start server --name=server1 --bind-address=127.0.0.1 --cache-xml-file=/home/viragtripathi/redis-connect-gemfire/demo/config/samples/cdc/gemfire2redis/cache.xml
44
44
45
45
Start server2
46
-
gfsh>start server --name=server2 --bind-address=127.0.0.1 --cache-xml-file=~/redis-connect-gemfire/config/samples/cdc/gemfire2redis/cache1.xml
46
+
gfsh>start server --name=server2 --bind-address=127.0.0.1 --cache-xml-file=/home/viragtripathi/redis-connect-gemfire/demo/config/samples/cdc/gemfire2redis/cache1.xml
Staging Redis Connect redis-connect-gemfire v1.0.2.151 job using Java 11.0.12 on 16229e5715a1 started by root in /opt/redislabs/redis-connect-gemfire/bin
141
-
Loading Redis Connect redis-connect-gemfire Configurations from /opt/redislabs/redis-connect-gemfire/config/samples/loader
142
-
.....
143
-
.....
144
-
12:31:38.726 [main] INFO startup - Setup Completed.
145
-
-------------------------------
146
-
```
147
-
148
-
</p>
149
-
</details>
150
-
151
-
<details><summary><b>Start pre configured loader job</b></summary>
Staging Redis Connect redis-connect-gemfire v1.0.2.151 job using Java 11.0.12 on virag-cdc started by root in /opt/redislabs/redis-connect-gemfire/bin.
219
-
Loading Redis Connect redis-connect-gemfire Configurations from /opt/redislabs/redis-connect-gemfire/config/samples/gemfire.
220
-
.....
221
-
.....
222
-
20:15:06.819 [main] INFO startup - Setup Completed.
128
+
Staging Redis Connect redis-connect-gemfire v0.5.0.135 job using Java 11.0.13 on virag-cdc started by root in /opt/redislabs/redis-connect-gemfire/bin
129
+
Loading Redis Connect redis-connect-gemfire Configurations from /opt/redislabs/redis-connect-gemfire/config/samples/cdc/gemfire2redis
130
+
....
131
+
17:39:43.212 [main] INFO startup - ##################################################################
132
+
17:39:43.214 [main] INFO startup -
133
+
17:39:43.214 [main] INFO startup - REDIS CONNECT SETUP CLEAN - Deletes metadata related to Redis Connect from Job Management Database
134
+
135
+
17:39:43.214 [main] INFO startup -
136
+
17:39:43.214 [main] INFO startup - ##################################################################
137
+
....
138
+
17:39:45.566 [main] INFO startup - ##################################################################
139
+
17:39:45.569 [main] INFO startup -
140
+
17:39:45.569 [main] INFO startup - REDIS CONNECT SETUP CREATE - Seed metadata related to Redis Connect to Job Management Database
141
+
17:39:45.569 [main] INFO startup -
142
+
17:39:45.569 [main] INFO startup - ##################################################################
143
+
....
144
+
17:39:47.250 [main] INFO startup - Instance: 100@virag-cdc successfully seeded Metrics related metadata
145
+
17:39:47.250 [main] INFO startup - Instance: 100@virag-cdc successfully staged Job Management Database (Redis) with all the configurations and scripts, if applicable, needed to execute jobs
Starting Redis Connect redis-connect-gemfire v0.5.0.135 instance using Java 11.0.13 on virag-cdc started by root in /opt/redislabs/redis-connect-gemfire/bin
178
+
Loading Redis Connect redis-connect-gemfire Configurations from /opt/redislabs/redis-connect-gemfire/config/samples/gemfire2redis
179
+
17:40:09,940 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [/opt/redislabs/redis-connect-gemfire/config/logback.xml] at [file:/opt/redislabs/redis-connect-gemfire/config/logback.xml]
180
+
....
181
+
17:40:10.222 [main] INFO startup -
182
+
17:40:10.225 [main] INFO startup - /$$$$$$$ /$$ /$$ /$$$$$$ /$$
183
+
17:40:10.225 [main] INFO startup - |$$__ $$|$$|__/ /$$__ $$|$$
17:40:10.227 [main] INFO startup - ##################################################################
192
+
17:40:10.227 [main] INFO startup -
193
+
17:40:10.227 [main] INFO startup - Initializing Redis Connect Instance
194
+
17:40:10.227 [main] INFO startup -
195
+
17:40:10.227 [main] INFO startup - ##################################################################
196
+
....
197
+
17:40:26.854 [JobManager-1] INFO startup - Instance: 30@virag-cdc successfully established Redis connection for HeartbeatManager service
198
+
17:40:26.855 [JobManager-1] INFO startup - Instance: 30@virag-cdc was successfully elected Redis Connect cluster leader
199
+
17:40:36.901 [JobManager-1] INFO startup - Getting instance of EventHandler for: REDIS_KV_TO_STRING_WRITER
200
+
17:40:36.919 [JobManager-1] WARN startup - metricsKey not set - Metrics collection will be disabled
201
+
17:40:36.929 [JobManager-1] INFO startup - Instance: 30@virag-cdc successfully established Redis connection for RedisConnectorEventHandler service
202
+
17:40:36.933 [JobManager-1] INFO startup - Getting instance of EventHandler for: REDIS_STRING_CHECKPOINT_WRITER
203
+
17:40:36.933 [JobManager-1] WARN startup - metricsKey not set - Metrics collection will be disabled
204
+
17:40:36.943 [JobManager-1] INFO startup - Instance: 30@virag-cdc successfully established Redis connection for RedisCheckpointReader service
205
+
17:40:38.237 [JobManager-1] INFO startup - Client with clientId : {connect}:job:job1 connecting for the first time
206
+
17:40:38.240 [JobManager-1] INFO startup - Instance: 30@virag-cdc successfully started job execution for JobId: {connect}:job:job1
207
+
17:40:38.241 [JobManager-1] INFO startup - Instance: 30@virag-cdc has successfully claimed ownership of JobId: {connect}:job:job1
208
+
17:40:38.241 [JobManager-1] INFO startup - Instance: 30@virag-cdc has claimed 1 job(s) from its 2 max allowable capacity
209
+
17:40:38.254 [JobManager-1] INFO startup - JobId: {connect}:job:job1 claim request with ID: 1641490787024-0 has been fully processed and all metadata has been updated
210
+
17:40:38.258 [JobManager-1] INFO startup - Instance: 30@virag-cdc published Job Claim Transition Event to Channel: REDIS.CONNECT.JOB.CLAIM.TRANSITION.EVENTS Message: {"jobId":"{connect}:job:job1","instanceName":"30@virag-cdc","transitionEvent":"CLAIMED","serviceName":"JobClaimer"}
211
+
17:40:38.258 [lettuce-nioEventLoop-4-3] INFO startup - Instance: 30@virag-cdc consumed Job Claim Transition Event on Channel: REDIS.CONNECT.JOB.CLAIM.TRANSITION.EVENTS Message: {"jobId":"{connect}:job:job1","instanceName":"30@virag-cdc","transitionEvent":"CLAIMED","serviceName":"JobClaimer"}
253
212
```
254
213
255
214
</p>
256
215
</details>
257
216
258
-
<details><summary><b>INSERT a record into gemfire table (source)</b></summary>
217
+
<details><summary><b>INSERT a record into gemfire region (source)</b></summary>
259
218
<p>
260
219
261
220
```bash
262
-
221
+
gfsh> put --key='redis123' --value='Hello Redis!!' --region=/session
Review the Custom Stage Demo then use the pre-built CustomStage function by passing it as an external library then follow the same [Initial Loader Steps](#initial-loader-steps) and [CDC Steps](#cdc-steps).
286
-
287
-
Add the `CustomStage``handlerId` in JobConfig.yml as explained in the Custom Stage Demo i.e.
288
-
```yml
289
-
stages:
290
-
CustomStage:
291
-
handlerId: TO_UPPER_CASE
292
-
```
293
-
<details><summary><b>Stage pre-configured loader job with Custom Stage</b></summary>
240
+
<details><summary><b>UPDATE a record into gemfire region (source)</b></summary>
0 commit comments