Slow performance when creating a new client node


(jason) #1

Hi everyone,

I noticed that every time I create a new node, it takes maybe 10 or
more seconds.

        Node node = nodeBuilder().node();
        Client client = node.client();  //this line takes longer than

expected

If I keep adding new documents under the same index, should they be
stored on a single node? At what point I should switch to a new (or
next) client node? Is there a limit of what load a single node or
single index can handle?

Thank you,
Eugene.


(ppearcy) #2

Hey,
Clients should be instantiated once and shared between threads. The
client connects to the entire cluster, so no need to switch the client
in your app.

Indexes can get very large, and with sharding there is no hard limit
other than disk and ram.

Hope this helps,
Paul

On Mar 10, 11:16 am, eugene efur...@gmail.com wrote:

Hi everyone,

I noticed that every time I create a new node, it takes maybe 10 or
more seconds.

            Node node = nodeBuilder().node();
            Client client = node.client();  //this line takes longer than

expected

If I keep adding new documents under the same index, should they be
stored on a single node? At what point I should switch to a new (or
next) client node? Is there a limit of what load a single node or
single index can handle?

Thank you,
Eugene.


(jason) #3

Thank you, Paul. This is really helpful!

On Mar 10, 6:08 pm, Paul ppea...@gmail.com wrote:

Hey,
Clients should be instantiated once and shared between threads. The
client connects to the entire cluster, so no need to switch the client
in your app.

Indexes can get very large, and with sharding there is no hard limit
other than disk and ram.

Hope this helps,
Paul

On Mar 10, 11:16 am, eugene efur...@gmail.com wrote:

Hi everyone,

I noticed that every time I create a new node, it takes maybe 10 or
more seconds.

            Node node = nodeBuilder().node();
            Client client = node.client();  //this line takes longer than

expected

If I keep adding new documents under the same index, should they be
stored on a single node? At what point I should switch to a new (or
next) client node? Is there a limit of what load a single node or
single index can handle?

Thank you,
Eugene.- Hide quoted text -

  • Show quoted text -

(system) #4