Sebastian Nagel commented on NUTCH-1499:

Thanks! That's a plausible reason: (let's call it) "administrative constraints".
+1 (lean patch, look's good, I'll try to test it on a machine with suitable 
network settings)
> Usage of multiple ipv4 addresses and network cards on fetcher machines
> ----------------------------------------------------------------------
>                 Key: NUTCH-1499
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1499
>             Project: Nutch
>          Issue Type: New Feature
>          Components: fetcher
>    Affects Versions: 1.5.1
>            Reporter: Walter Tietze
>            Priority: Minor
>         Attachments: apache-nutch-1.5.1.NUTCH-1499.patch
> Adds for the fetcher threads the ability to use multiple configured ipv4 
> addresses.
> On some cluster machines there are several ipv4 addresses configured where 
> each ip address is associated with its own network interface.
> This patch enables to configure the protocol-http and the protocol-httpclient 
>  to use these network interfaces in a round robin style.
> If the feature is enabled, a helper class reads at *startup* the network 
> configuration. In each http network connection the next ip address is taken. 
> This method is synchronized, but this should be no bottleneck for the overall 
> performance of the fetcher threads.
> This feature is tested on our cluster for the protocol-http and the 
> protocol-httpclient protocol.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to