[
https://issues.apache.org/jira/browse/NUTCH-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987757#comment-13987757
]
Rogério Pereira Araújo commented on NUTCH-1768:
-----------------------------------------------
Julien,
When I set the host on nutch-site.xml everything worked as expected, but if I
try to perform the indexing only by resolving the cluster via multicast, I get
the following exception:
failed to send multicast ping request: NullPointerException[null]
and on elasticsearch, even without a firewall running, I always get this
message:
[INFO ][transport] [BMobile 1]bound_address {inet[/192.168.100.110:9300]},
publish_address {inet[/192.168.100.110:9300]}
[INFO ][discovery.zen.ping.multicast] [BMobile 1] multicast failed to start
[SocketException[Invalid argument]], disabling
Maybe this is why my cluster isn't resolved from nutch, just wondering.
> port NUTCH-1745 to Nutch 2.x (Upgrade to ElasticSearch 1.1.0)
> --------------------------------------------------------------
>
> Key: NUTCH-1768
> URL: https://issues.apache.org/jira/browse/NUTCH-1768
> Project: Nutch
> Issue Type: Improvement
> Components: indexer
> Affects Versions: 2.2.1
> Reporter: Julien Nioche
> Labels: elasticsearch
> Fix For: 2.4
>
> Attachments: NUTCH-1768.patch
>
>
> See [https://issues.apache.org/jira/browse/NUTCH-1745]
> ElasticSearch is currently at version 1.1.0. The patch attached upgrades the
> dependencies, fixes a couple of changes required by 1.1.0 and also :
> removes the need for having ES in the main ivy dependency - it is now only
> required at the plugin level
> improves the logic around using the cluster name or an explicit host:port to
> connect to ES : the clustername is not required nor set when using host:port
> uses a more sensible default value for the port
--
This message was sent by Atlassian JIRA
(v6.2#6252)
