TDCH returning 'socket not connected' error when using fast export

Hadoop
The Teradata Portfolio for Hadoop is a flexible offering of products and services for our customers to integrate Hadoop into a Teradata environment and across a broader enterprise architecture, while taking advantage of the world-class Teradata service and support. The Hadoop Channel covers the hardware and software features, tips and best practices on all the components of the Teradata Portfolio for Hadoop.
Highlighted
Tourist

TDCH returning 'socket not connected' error when using fast export

Hi, 

 

We are moving data from Teradata to Hive through TDCH.  # of tables being move are 500+ and we are using internal fast export utility for export.  Since the Hadoop cluster is busy most of the time, We end up with 'socket not connected' issue most of the time. the # of mappers used are less than the nummappers specified in configuration.  As a temp fix, we changed the fast export to 'split by amp' option for failed tables. But split by amp performance is not good for huge tables and taking a long time. Wanted to check if this issue occurs only because of Hadoop cluster being busy or settings within the TDCH that can be changed. The error appears randomly for the fast export and its not during a fixed time limit. the same table was loaded during different times and it returned with socket not connected error. 

 

Thanks