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?
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.
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?
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.
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?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.