You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Veena Basavaraj (JIRA)" <ji...@apache.org> on 2014/10/20 15:51:34 UTC
[jira] [Comment Edited] (SQOOP-1593) If connector registration is
failed, the sqoop2 server cannot startup
[ https://issues.apache.org/jira/browse/SQOOP-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14176902#comment-14176902 ]
Veena Basavaraj edited comment on SQOOP-1593 at 10/20/14 1:50 PM:
------------------------------------------------------------------
I would rather prefer server failing ( HARD failure), unless we have a simple UI/dashboard or a report that says which components ( connectors/ drivers/ or in future other configurable) failed.
It is very annoying to look through the logs and guess what succeeded and failed in this age!
Rather we should fix the server startup to atleast support a blocking mode and fail HARD in front of them. Today if there are any errors /exception while starting the server, it only records the issues in the log files and any novice user thinks the server actually started, when in fact it is running in another thread and failed.
was (Author: vybs):
I would rather prefer server failing ( HARD failure), unless we have a simple UI/dashboard or a report that says which components ( connectors/ drivers/ or in future other configurable) failed.
It is very annoying to look through the logs and guess what succeeded and failed in this age!
> If connector registration is failed, the sqoop2 server cannot startup
> ---------------------------------------------------------------------
>
> Key: SQOOP-1593
> URL: https://issues.apache.org/jira/browse/SQOOP-1593
> Project: Sqoop
> Issue Type: Bug
> Components: connectors
> Affects Versions: 2.0.0
> Reporter: Qian Xu
>
> I noticed that if a connector is failed to registrered (e.g. in case configuration upgrade failed), the sqoop2 server will NOT startup. My expected behaviors would be disable affected connector(s) link(s) and job(s), but server should be able to startup. Is the behavior expected by design?
> {code}
> 2014-10-20 14:15:14,683 ERROR core.SqoopServer [org.apache.sqoop.core.SqoopServer.initialize(SqoopServer.java:56)] Server startup failure
> org.apache.sqoop.common.SqoopException: CONN_0007:Connector registration failed
> at org.apache.sqoop.connector.ConnectorManager.registerConnectors(ConnectorManager.java:206)
> at org.apache.sqoop.connector.ConnectorManager.initialize(ConnectorManager.java:167)
> at org.apache.sqoop.connector.ConnectorManager.initialize(ConnectorMan
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)