Wares Plugin Questions

Elastic Stack Elasticsearch
1

Hi, I have a few questions about the Wares plugin:

i) Do I have to use REST / http to query ES, or can I still use the
java client, which will be deployed in the same application server
(Weblogic).

ii) Does Wares automatically encrypt the Java port (Netty) cluster
communication using SSL. If not how is this done, Shay seem to
indicate that this is possible in his comment here:

  • David.
2

On Wednesday, February 8, 2012 at 8:22 PM, davrob2 wrote:

Hi, I have a few questions about the Wares plugin:

i) Do I have to use REST / http to query ES, or can I still use the
java client, which will be deployed in the same application server
(Weblogic).

If its embedded, then you can just use the Node itself to talk to the cluster. You can get it from the servlet context attribute: https://github.com/elasticsearch/elasticsearch-transport-wares/blob/master/src/main/java/org/elasticsearch/wares/NodeServlet.java#L89.

ii) Does Wares automatically encrypt the Java port (Netty) cluster
communication using SSL. If not how is this done, Shay seem to
indicate that this is possible in his comment here:
Add HTTPS and basic authentication support to elasticsearch · Issue #664 · elastic/elasticsearch · GitHub

It does not use netty for HTTP in this case, it will plug (based on the path you provide) as a Servlet and use it to do the communication.

  • David.
3

Hi Shay,

On point ii), does this mean that the Servlet is used to do all inter-
node communication? Is that less efficient than using Java Sockets?

If the above is true then implementing SSL is just a matter of
plugging in the default application server SSL for servlets?

-David

On Feb 9, 8:15 am, Shay Banon kim...@gmail.com wrote:

On Wednesday, February 8, 2012 at 8:22 PM, davrob2 wrote:

Hi, I have a few questions about the Wares plugin:

i) Do I have to use REST / http to query ES, or can I still use the
java client, which will be deployed in the same application server
(Weblogic).

If its embedded, then you can just use the Node itself to talk to the cluster. You can get it from the servlet context attribute:https://github.com/elasticsearch/elasticsearch-transport-wares/blob/m....

ii) Does Wares automatically encrypt the Java port (Netty) cluster
communication using SSL. If not how is this done, Shay seem to
indicate that this is possible in his comment here:
Add HTTPS and basic authentication support to elasticsearch · Issue #664 · elastic/elasticsearch · GitHub...

It does not use netty for HTTP in this case, it will plug (based on the path you provide) as a Servlet and use it to do the communication.

  • David.
4

Yes, the servlet uses to the embedded Node started to do all its "work". Exposing it is up to you, if you expose it through HTTP through the servlet container, then you can use the container SSL for it.

On Thursday, February 9, 2012 at 1:09 PM, davrob2 wrote:

Hi Shay,

On point ii), does this mean that the Servlet is used to do all inter-
node communication? Is that less efficient than using Java Sockets?

If the above is true then implementing SSL is just a matter of
plugging in the default application server SSL for servlets?

-David

On Feb 9, 8:15 am, Shay Banon <kim...@gmail.com (http://gmail.com)> wrote:

On Wednesday, February 8, 2012 at 8:22 PM, davrob2 wrote:

Hi, I have a few questions about the Wares plugin:

i) Do I have to use REST / http to query ES, or can I still use the
java client, which will be deployed in the same application server
(Weblogic).

If its embedded, then you can just use the Node itself to talk to the cluster. You can get it from the servlet context attribute:https://github.com/elasticsearch/elasticsearch-transport-wares/blob/m....

ii) Does Wares automatically encrypt the Java port (Netty) cluster
communication using SSL. If not how is this done, Shay seem to
indicate that this is possible in his comment here:
Add HTTPS and basic authentication support to elasticsearch · Issue #664 · elastic/elasticsearch · GitHub...

It does not use netty for HTTP in this case, it will plug (based on the path you provide) as a Servlet and use it to do the communication.

  • David.