TransportClient in a JEE container is
better for separation of concerns.
Jörg
On Tue, Sep 9, 2014 at 4:25 PM, Tasha CARL wrote:
>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
t; If you use TransportClient: no, you just connect a client to an existing
> ES cluster which runs outside JEE.
>
> Jörg
>
>
> On Tue, Sep 9, 2014 at 10:32 AM, Tasha CARL wrote:
>
>> Let me ask a different question then:
>>
>> Do you agree when I say that if you
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
ne that for example under heavy load, the ES client (JAR) could create
too many threads of which the container is not aware of that together with
the threads created by the container itself, the OS/VM limits/quota are
hit.
Tasha
On 9 September 2014 09:39, joergpra...@gmail.com
wrote:
> Y
ot likely in this case) and it might
also cause strange side-effects on application servers.
Your opinions?
Best,
Tasha
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails
