camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-5433) camel-hdfs - Allow to startup async as hdfs file system has hardcoded 15 min retry in case no connection
Date Mon, 09 Jul 2012 09:16:33 GMT

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

Claus Ibsen commented on CAMEL-5433:
------------------------------------

Logs where you can see the retry happening
{code}
2012-07-05 14:50:17,708 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 0 time(s).
2012-07-05 14:50:38,708 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 1 time(s).
2012-07-05 14:50:59,708 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 2 time(s).
2012-07-05 14:51:20,709 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 3 time(s).
2012-07-05 14:51:41,709 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 4 time(s).
2012-07-05 14:52:02,709 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 5 time(s).
2012-07-05 14:52:23,709 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 6 time(s).
2012-07-05 14:52:44,710 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 7 time(s).
2012-07-05 14:53:05,710 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 8 time(s).
2012-07-05 14:53:26,710 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 9 time(s).
2012-07-05 14:53:47,710 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 10 time(s).
2012-07-05 14:54:08,710 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 11 time(s).
2012-07-05 14:54:29,693 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 12 time(s).
2012-07-05 14:54:50,694 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 13 time(s).
2012-07-05 14:55:11,695 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 14 time(s).
2012-07-05 14:55:32,696 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 15 time(s).
2012-07-05 14:55:53,697 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 16 time(s).
2012-07-05 14:56:14,698 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 17 time(s).
2012-07-05 14:56:35,699 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 18 time(s).
2012-07-05 14:56:56,700 | INFO  | FelixStartLevel  | org.apache.hadoop.ipc.Client     |  
                                       | Retrying connect to server: 192.168.240.129/192.168.240.129:9000.
Already tried 19 time(s).
{code}
                
> camel-hdfs - Allow to startup async as hdfs file system has hardcoded 15 min retry in
case no connection
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-5433
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5433
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-hdfs
>    Affects Versions: 2.10.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.10.1, 2.11
>
>
> When start a Camel app with camel-hdfs (either as producer or consumer), then getting
a hdfs file system object may have Hadoop block for up till 15 minutes where it tries to obtain
a connection to the cluster.
> This makes the app appear as blocking and people dont want their apps to block for 15
min on startup.
> We should let the hadoop hdfs connection happing in an async thread, so the app can startup.
Configurable so you can turn back the old behavior.
> Hadoop dosn't allow to configure a lower timeout etc this as its hardcoded.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message