[
https://issues.apache.org/jira/browse/SQOOP-2991?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401789#comment-15401789
]
Benjamin BONNET commented on SQOOP-2991:
----------------------------------------
This issue is due to the fact NetezzaExternalTableImportMapper creates a reader
on a fifo. Such a reader instanciation is blocking until someone writes
something into the fifo.
If an error occurs on Netezza, the NetezzaJDBCStatementRunner will stop without
having written anything into the fifo. Hence the import mapper will wait for
ever.
> Never ending imports from Netezza
> ---------------------------------
>
> Key: SQOOP-2991
> URL: https://issues.apache.org/jira/browse/SQOOP-2991
> Project: Sqoop
> Issue Type: Bug
> Components: connectors
> Affects Versions: 1.4.6
> Reporter: Benjamin BONNET
> Priority: Critical
>
> Hi,
> there are situations where a Netezza import may fail but never end (i.e. the
> map reduce job will run for ever).
> That occurs when Sqoop manages to open a connection to the database and
> executes a query that fails on the Netezza side without writing anything into
> the connection. For instance, that typically occurs for authroization
> problems.
> Then you have to kill the map reuce job by hand if you want to free the
> resource (memory) kept by the MR container.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
