Restarting a Job | Teradata Access Module for Kafka - About Restarting a Job - Access Module

Teradata® Tools and Utilities Access Module Reference - 20.00

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Access Module
Release Number
20.00
Published
October 2023
ft:locale
en-US
ft:lastEdition
2024-05-14
dita:mapPath
cya1691484517272.ditamap
dita:ditavalPath
obe1474387269547.ditaval
dita:id
hjf1479308836950
lifecycle
latest
Product Category
Teradata Tools and Utilities

Restarting a Job is supported in the data import scenario and not in the data export scenario. the Teradata Parallel Transporter DataConnector operator issues a File Set Position command to the Teradata Access Module for Kafka when a Teradata Parallel Transporter job terminates unexpectedly and restarts.

The Teradata Parallel Transporter DataConnector operator provides the Topic name and the offset number of the last message read for each partition to the Teradata Access Module for Kafka.

The Teradata Access Module for Kafka repositions the offsets for each partition based on the information provided by the Teradata Parallel Transporter DataConnector operator, and starts consuming the messages.

To use the checkpoint feature, the user must specify the "tbuild -z" command. When the -z option of tbuild command is used, the TPT-KAFKAAXSMOD import job takes a checkpoint for each set interval (in seconds).

If the TPT-KAFKAAXSMOD import job fails to complete and is later restarted, the only work that will be performed is the work done after the last checkpoint was taken. This feature provides enhanced fault tolerance for jobs that run for an extended period of time and require a large volume of data to be loaded into Analytics Database.