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
command with the `--file` option (or the shorter version `-f`) to supply answers
241
-
to the installer's questions automatically using properties from a
242
-
[TOML](https://toml.io/en/) file:
243
-
244
-
```bash
245
-
./install.sh --file silent.toml
246
-
```
247
-
248
-
### Silent install example
249
-
250
-
The following TOML file example shows the properties for a typical
251
-
silent install configuration:
252
-
253
-
```toml
254
-
title = "RDI Silent Installer Config"
255
-
256
-
scaffold = true
257
-
db_index = 4
258
-
deploy_directory = "/opt/rdi/config"
259
-
260
-
# Upstream DNS servers. This is needed if the installer detects a DNS resolver
261
-
# with a loopback address as an upstream DNS server.
262
-
# nameservers = ["8.8.8.8", "8.8.4.4"]
263
-
264
-
# HTTPS port you want to expose the RDI API on, if different from 443.
265
-
# https_port = 5443
266
-
267
-
[rdi.database]
268
-
host = "localhost"
269
-
port = 12001
270
-
username = "username"
271
-
password = "password"
272
-
ssl = true
273
-
274
-
# Uncomment the properties in this section only if the RDI
275
-
# database uses TLS/mTLS.
276
-
# [rdi.database.certificates]
277
-
# ca = "/home/ubuntu/rdi/certs/ca.crt"
278
-
# cert = "/home/ubuntu/rdi/certs/client.crt"
279
-
# key = "/home/ubuntu/rdi/certs/client.key"
280
-
# passphrase = "foobar"
281
-
```
282
-
283
-
The sections below describe the properties in more detail.
284
-
285
-
### Silent install properties
286
-
287
-
#### Root
288
-
289
-
| Property | Description |
290
-
|-- |-- |
291
-
|`title`| Text to identify the file. RDI doesn't use use this, so you can use any text you like. |
292
-
| `scaffold` | Do you want to enable [scaffolding]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-scaffold" >}}) during the install? (true/false) |
293
-
| `db_index` | Integer to specify the source database type for scaffolding. The options are 2 (MySQL/MariaDB), 3 (Oracle), 4 (PostgreSQL), and 5 (SQL Server). |
294
-
| `deploy_directory` | Path to the directory where you want to store the RDI configuration. |
295
-
| `nameservers` | Upstream DNS servers. This is needed if the installer detects a DNS resolver with a loopback address as an upstream DNS server (for example, `nameservers = ["8.8.8.8", "8.8.4.4"]`). |
296
-
| `https_port` | HTTPS port you want to expose the RDI API on, if different from 443. |
297
-
298
-
#### `rdi.database`
299
-
300
-
Use the properties in this section to specify your RDI database.
301
-
302
-
| Property | Description |
303
-
|-- |-- |
304
-
| `host` | Hostname for the Redis database to store RDI state. |
305
-
| `port` | Port for the RDI database. |
306
-
| `username` | Username for the RDI database. |
307
-
| `password` | Password for the RDI database. |
308
-
| `ssl` | Is SSL enabled for the RDI database (true/false)? If this is false then RDI will ignore the settings in the [`rdi.database.certificates`](#rdidatabasecertificates) section. |
226
+
### Installing with High Availability
309
227
310
-
#### `rdi.database.certificates`
228
+
To install RDI with High Availability (HA), perform the [Installation steps](#installation-steps)
229
+
on two different VMs. The first VM will automatically become the active (primary) instance,
230
+
while the second VM will become the passive (secondary) one.
231
+
When starting the RDI installation on the second VM, the installer will detect that the RDI
232
+
database is already in use and ask you to confirm that you intend to install RDI with HA.
311
233
312
-
Use these properties only if the RDI database requires
313
-
[TLS](https://en.wikipedia.org/wiki/Transport_Layer_Security) or
[`rdi.database`](#rdidatabase) section to enable these properties.
234
+
After the installation is complete, you must set the source and target database secrets
235
+
on both VMs as described in [Deploy a pipeline]({{< relref "/integrate/redis-data-integration/data-pipelines/deploy">}}). If you use `redis-di` to deploy your configuration, you only need to do this on one of the VMs, not both.
317
236
318
-
| Property | Description |
319
-
|-- |-- |
320
-
| `ca` | Path to the CA certificate file. |
321
-
| `cert` | Path to the client certificate file. |
322
-
| `key` | Path to the key file. |
323
-
| `passphrase` | Password for the private key (string). |
237
+
In a High Availability setup, the RDI pipeline is only active on the primary instance (VM).
238
+
The two RDI instances will use the RDI database for leader election. If the primary instance fails
239
+
to renew the lease in the RDI database, it will lose the leadership and a failover to the secondary instance
240
+
will take place. After the failover, the secondary instance will become the primary one,
241
+
and the RDI pipeline will be active on that VM.
324
242
325
243
## Prepare your source database
326
244
327
-
You must also configure your source database to use the CDC connector. See the
245
+
Before deploying a pipeline, you must configure your source database to enableCDC. See the
Copy file name to clipboardExpand all lines: content/integrate/redis-data-integration/quick-start-guide.md
+5-5Lines changed: 5 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -50,10 +50,10 @@ RDI will create the pipeline template for your chosen source database type at
50
50
(see [Prepare the pipeline](#prepare-the-pipeline) below).
51
51
52
52
At the end of the installation, RDI CLI will prompt you to set the access secrets
53
-
for both the source PostgreSQL database and the Redis RDI database. RDI needs these to
53
+
for both the source PostgreSQL database and the target Redis database. RDI needs these to
54
54
run the pipeline.
55
55
56
-
Use the Redis console to create the RDI database with the following requirements:
56
+
Use the Redis Enterprise Cluster Manager UI to create the RDI database with the following requirements:
57
57
58
58
{{< embed-md "rdi-db-reqs.md" >}}
59
59
@@ -90,7 +90,7 @@ To create a context, use the
90
90
command:
91
91
92
92
```bash
93
-
redis-di add-context --rdi-host <host> --rdi-port <port>--cluster-host <Redis DB host> --cluster-api-port <Redis DB API port> --cluster-user <Redis DB username><unique-context-name>
These options are required but there are also a few others you can save, such as TLS credentials, if
@@ -113,7 +113,7 @@ contexts.
113
113
114
114
You can use [Redis Insight]({{< relref "/develop/tools/insight/rdi-connector" >}})
115
115
to deploy the pipeline by adding a connection to the RDI API
116
-
endpoint (which has the same IP address as your RDI VM and uses port 8083) and then clicking the **Deploy** button. You can also deploy it with the following command:
116
+
endpoint (which has the same hostname or IP address as your RDI VM and uses the default HTTPS port 443) and then clicking the **Deploy** button. You can also deploy it with the following command:
117
117
118
118
```bash
119
119
redis-di deploy --dir <path to pipeline folder>
@@ -148,4 +148,4 @@ To see the RDI pipeline working in CDC mode:
148
148
- Run
149
149
[`redis-di status --live`]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-status" >}})
150
150
to see the flow of records.
151
-
-User[Redis Insight]({{< relref "/develop/tools/insight" >}}) to look at the data in the target database.
151
+
-Use[Redis Insight]({{< relref "/develop/tools/insight" >}}) to look at the data in the target database.
0 commit comments