故障 排除

使用 RDI 解决和报告简单问题

以下部分说明如何从 Redis 数据集成 （RDI） 可帮助您解决可能遇到的问题。Redis 支持可能会 此外，请提供此信息以帮助您解决问题。

安装过程中的调试信息

如果安装程序失败并出现错误，请尝试使用 Log level 设置为DEBUG:

./install.sh -l DEBUG   # Installer script
redis-di install -l DEBUG    # Install command

This gives you more detail about the installation steps and can often help you to pinpoint the source of the error.

RDI logs

By default, RDI records the following logs in the host VM file system at /opt/rdi/logs (or whichever path you specified during installation);

Filename Phase
rdi_collector-collector-initializer.log Initializing the collector.
rdi_collector-debezium-ssl-init.log Establishing the connector SSL connections to the source and RDI database (if you are using SSL).
rdi_collector-collector-source.log Collector change data capture (CDC) operations.
rdi_rdi-rdi-operator.log Main RDI control plane component.
rdi_processor-processor.log RDI stream processing.

Logs are recorded at the minimum INFO level in a simple format that log analysis tools can use.

Note:
Often during the initial sync phase, the collector source log will contain a message saying RDI is out of memory. This is not an error but an informative message to say that RDI is applying backpressure to the collector. See Backpressure mechanism in the Architecture guide for more information.

Dump support package

If you need to send a comprehensive set of forensics data to Redis support, run the redis-di dump-support-package command from the CLI.

This command gathers the following data:

  • All the internal RDI components and their status
  • All internal RDI configuration
  • List of secret names used by RDI components (but not the secrets themselves)
  • RDI logs
  • RDI component versions
  • Output from the redis-di status command
  • Text of the config.yaml file
  • Text of the Job configuration files
  • [optional] RDI DLQ streams content
  • Rejected records along with the reason for their rejection (should not exist in production)
RATE THIS PAGE
Back to top ↑