2014 16:51
À : elasticsearch@googlegroups.com
Objet : Re: ElasticSearch multi-threading and the Java EE specifications
Again: why do you want ES respect the JEE specs? It is not a JEE component at
all and will never be.
You can run anything in a JEE container, also software which i
Again: why do you want ES respect the JEE specs? It is not a JEE component
at all and will never be.
You can run anything in a JEE container, also software which is not a JEE
component.
Running a NodeClient (with or without data) means the node is becoming a
part of the ES cluster, i.e. the JVM o
>If you use NodeClient in JEE container with data, but being part of an ES
cluster: yes and no.
(think you mean without data)
That's what I do. Why yes and no? IMHO it's yes and if this is the case, it
should respect the Java EE specs :)
On 9 September 2014 16:14, joergpra...@gmail.com
wrote:
It depends.
With ES engine you mean the machinery to search and index I presume.
If you use embedded single node in a JEE container: yes.
If you use NodeClient in JEE container with data, but being part of an ES
cluster: yes and no.
If you use TransportClient: no, you just connect a client to a
Let me ask a different question then:
Do you agree when I say that if you include ES in your Java EE application
(JAR file) and you create a single tone to manage the ES connection to the
cluster. That in this case, the ES engine runs inside of your Java EE
application container?
Tasha
On 9 Sept
I think you confuse two things:
- the Java platform (Java Language, Java Virtual Machine)
- the Java EE specification
These two things are different.
As the Java EE specification is community-driven and defined, it does not
mean to put any burden or restrictions on the Java platform, or on any
>Elasticsearch was never designed to run as a container managed Java EE
>component in a Java EE container, so the question about thread creation
>is unrelated.
That's exactly my point and that's why I ask this question.
>If you want to use an ES client from within a Java EE container,
>sta
Your question is not very clear, but maybe you refer to JSR 236 for Java
EE.
Elasticsearch was never designed to run as a container managed Java EE
component in a Java EE container, so the question about thread creation is
unrelated.
If you want to use an ES client from within a Java EE container
I've heard of this rule but never seen anyone follow it. They'd mostly
make threads/thread pools and just make sure they were shut down when the
application was shut down. So my advice is to follow the intent of the law
(shutdown your threads) rather than follow the letter of the law.
Nik
On Mo
Hi all,
As you know, ElasticSearch relies a lot on multi-threading.
I'm currently using ES in a Java EE 6 application (using the node client as
pure client node) and the Java EE specifications state that classic thread
creation (à la "new Thread() { @Override public void run() {}}") i
10 matches
Mail list logo
