CDH 5.4.4 Sqoop 2 作业开始但从未运行答案

【问题标题】：CDH 5.4.4 Sqoop 2 Job starting but never runsCDH 5.4.4 Sqoop 2 作业开始但从未运行
【发布时间】：2015-10-06 10:33:30
【问题描述】：

Cloudera Community Post

在 Cloudera 5.4.4 中使用 Hue，当尝试运行 Sqoop 2 作业时，它会显示 (i) The job is starting...，但它实际上从未运行过该作业。我在 Job Browser 中看不到任何内容，在作业的 SUBMISSIONS 列表中也看不到任何内容。我也没有在日志中看到任何错误。

这是在库存 Cloudera 5.4.4 (QuickStart VM) 上，我假设所有组件都已正确预配置。不幸的是，我所要做的就是缺少错误消息和有用的报告。

【问题讨论】：

提交作业后有日志小图标吗？您是否在开发者控制台或 Hue 的 /logs 页面中看到任何错误？
当我尝试通过 Hue 查看这些日志时 - 它说找不到日志。但是，在 /var/logs/sqoop2 中似乎有一些日志。

标签： hadoop sqoop cloudera-cdh hue sqoop2

【解决方案1】：

在 CDH5 上，sqoop 2 服务器确实在/var/log/sqoop2/sqoop.log 下提供了一些日志。就我而言，错误是没有提供分区列。这是一个可选参数，但 Hue 界面中的错误报告不会显示任何这些细节。

2015-07-27 07:52:09,728 ERROR server.SqoopProtocolServlet [org.apache.sqoop.server.SqoopProtocolServlet.doPut(SqoopProtocolServlet.java:84)] Exception in PUT http://quickstart.cloudera:12000/sqoop/v1/job/1/start
org.apache.sqoop.common.SqoopException: GENERIC_JDBC_CONNECTOR_0005:No column is found to partition data
        at org.apache.sqoop.connector.jdbc.GenericJdbcFromInitializer.configurePartitionProperties(GenericJdbcFromInitializer.java:147)
        at org.apache.sqoop.connector.jdbc.GenericJdbcFromInitializer.initialize(GenericJdbcFromInitializer.java:51)
        at org.apache.sqoop.connector.jdbc.GenericJdbcFromInitializer.initialize(GenericJdbcFromInitializer.java:40)
        at org.apache.sqoop.driver.JobManager.initializeConnector(JobManager.java:449)
        at org.apache.sqoop.driver.JobManager.createJobRequest(JobManager.java:372)
        at org.apache.sqoop.driver.JobManager.start(JobManager.java:276)
        at org.apache.sqoop.handler.JobRequestHandler.startJob(JobRequestHandler.java:379)
        at org.apache.sqoop.handler.JobRequestHandler.handleEvent(JobRequestHandler.java:115)
        at org.apache.sqoop.server.v1.JobServlet.handlePutRequest(JobServlet.java:96)
        at org.apache.sqoop.server.SqoopProtocolServlet.doPut(SqoopProtocolServlet.java:79)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:723)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:592)
        at org.apache.hadoop.security.token.delegation.web.DelegationTokenAuthenticationFilter.doFilter(DelegationTokenAuthenticationFilter.java:277)
        at org.apache.hadoop.security.authentication.server.AuthenticationFilter.doFilter(AuthenticationFilter.java:555)
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293)
        at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:861)
        at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:620)
        at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
        at java.lang.Thread.run(Thread.java:745)

【讨论】：