Community Articles
Find and share helpful community-sourced technical articles
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.
Labels (1)

SYMPTOMS: No visible errors in Resource manager / Node Manager logs for any resource bottleneck.Logs from container/task which is not progressing are as follows:-

Error: java.io.IOException: com.sap.db.jdbc.exceptions.jdbc40.SQLNonTransientConnectionException: Connection to database server lost; 
check server and network status [System error: Socket closed] at 
org.apache.sqoop.mapreduce.db.DBRecordReader.close(DBRecordReader.java:173) at 
org.apache.hadoop.mapred.MapTask$NewTrackingRecordReader.close(MapTask.java:523) at 
org.apache.hadoop.mapred.MapTask.runNewMapper(MapTask.java:791) at 
org.apache.hadoop.mapred.MapTask.run(MapTask.java:341) at 
org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:168) at 
java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.Subject.doAs(Subject.java:422) at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1724) at 
org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:162) 
Caused by: com.sap.db.jdbc.exceptions.jdbc40.SQLNonTransientConnectionException: Connection to database server lost; check server and network status [System error: Socket closed] at 
com.sap.db.jdbc.exceptions.jdbc40.SQLNonTransientConnectionException.createException(SQLNonTransientConnectionException.java:40) at 
com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:252) at 
com.sap.db.jdbc.exceptions.SQLExceptionSapDB.createException(SQLExceptionSapDB.java:214) at 
com.sap.db.jdbc.exceptions.SQLExceptionSapDB.generateSQLException(SQLExceptionSapDB.java:166) at 
com.sap.db.jdbc.exceptions.ConnectionException.createException(ConnectionException.java:22) at 
com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:1117) at 
com.sap.db.jdbc.ConnectionSapDB.execute(ConnectionSapDB.java:877) at 
com.sap.db.jdbc.ConnectionSapDB.commitInternal(ConnectionSapDB.java:353) at 
com.sap.db.jdbc.ConnectionSapDB.commit(ConnectionSapDB.java:340) at 
com.sap.db.jdbc.trace.Connection.commit(Connection.java:126) at 
org.apache.sqoop.mapreduce.db.DBRecordReader.close(DBRecordReader.java:169) ... 8 more Container killed by the ApplicationMaster. Container killed on request. Exit code is 143 Container exited with a non-zero exit code 143

ROOT CAUSE: The issue looks to be at SAP HANA side and not at HDP end. Following URL discusses same error - > https://archive.sap.com/discussions/thread/3675080

NEXT STEPS: Contact SAP HANA support team for further troubleshooting.

951 Views
Don't have an account?
Coming from Hortonworks? Activate your account here
Version history
Revision #:
1 of 1
Last update:
‎12-23-2016 09:02 AM
Updated by:
 
Contributors
Top Kudoed Authors