sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abraham Elmahrek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1850) Sqoop2: DerbyProvider retry ping
Date Mon, 08 Dec 2014 15:18:12 GMT

    [ https://issues.apache.org/jira/browse/SQOOP-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14237963#comment-14237963
] 

Abraham Elmahrek commented on SQOOP-1850:
-----------------------------------------

In some sense. I thought the fact it's being ran in a "Future" would limit the number of tries
to the max number of tries possible in 10 seconds.

> Sqoop2: DerbyProvider retry ping
> --------------------------------
>
>                 Key: SQOOP-1850
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1850
>             Project: Sqoop
>          Issue Type: Bug
>          Components: sqoop2-test
>    Affects Versions: 1.99.5
>            Reporter: Abraham Elmahrek
>            Assignee: Abraham Elmahrek
>             Fix For: 1.99.5
>
>         Attachments: SQOOP-1850.0.patch
>
>
> Sometimes if the server doesn't immediately bind to its port, then "ping" command will
throw an exception and the provider will not start. The "ping" method should be caught and
retried "n" times.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message