In a test scenario, I used stunnel for connections between some
zookeeper observers and the central ensemble, as well as between a SolrJ
4.9.0 client and the central zookeepers. This is entirely transparent
modulo performance penalties due to network latency and ssl overhead. I
finally ended up with placing the observer node close to the SolrJ client.
Depending on what kind of network connection is between the SolrJ client
and the cluster, you may run into TCP MTU issues or packet fragmentation
problems. Hard to say what's happening without knowing any details on
the nature of the tunnel.
Try testing some four-letter commands from the SolrJ client machine,
e.g. "echo ruok | nc localhost 2181". Does that work?
Best regards,
--Jürgen
On 16.09.2014 21:25, Michael Joyner wrote:
> I am in a situation where I need to access a solrcloud behind a firewall.
>
> I have a tunnel enabled to one of the zookeeper as a starting points
> and the following test code:
>
> CloudSolrServer server = new CloudSolrServer("localhost:2181");
> server.setDefaultCollection("test");
> SolrPingResponse p = server.ping();
> System.out.println(p.getRequestUrl());
>
> Right now it just "hangs" without any errors... what additional ports
> need forwarding and other configurations need setting to access a
> solrcloud over a ssh tunnel or tunnels?
--
Mit freundlichen Grüßen/Kind regards/Cordialement vôtre/Atentamente/С
уважением
*i.A. Jürgen Wagner*
Head of Competence Center "Intelligence"
& Senior Cloud Consultant
Devoteam GmbH, Industriestr. 3, 70565 Stuttgart, Germany
Phone: +49 6151 868-8725, Fax: +49 711 13353-53, Mobile: +49 171 864 1543
E-Mail: juergen.wag...@devoteam.com
<mailto:juergen.wag...@devoteam.com>, URL: www.devoteam.de
<http://www.devoteam.de/>
------------------------------------------------------------------------
Managing Board: Jürgen Hatzipantelis (CEO)
Address of Record: 64331 Weiterstadt, Germany; Commercial Register:
Amtsgericht Darmstadt HRB 6450; Tax Number: DE 172 993 071
