I want to know why or how works ES, because it needs a lot of file
descriptors, when i doing re indexing it uses a lot. But if someone can
explain me or share some links to understand why open a lot of files and if
it degrade the performance of servers.
Regards
ps: I change on sysctl.conf, and it works, but i want to know why i need to
do that.
THanks, yes we are using this but with java api, but exists any formula
that i can predict how many open file i will have if my indices increase
every week, in order to configure the correct number of file descriptors.
Because when i delete an index and it will create again all (index and all
shards for this index), the quantity of file descriptors is more than that
i have all index working fine.(without delete all)
Regards
On Mon, Feb 10, 2014 at 3:43 PM, Binh Ly binh@hibalo.com wrote:
Rondan,
If you're using REST/HTTP, you can use the Delete Index API to delete an
index easily:
DeleteIndexRequestBuilder(client.admin().indices(),
INDEX_NAME).execute().actionGet();
if (deleteIndexResponse.isAcknowledged()) System.out.println(
"Deleted index" );
Generally, setting the file descriptors to 65535 should suffice. You can
learn more about this and other things here:
On Monday, February 10, 2014 1:57:51 PM UTC-5, Rino Rondan wrote:
THanks, yes we are using this but with java api, but exists any formula
that i can predict how many open file i will have if my indices increase
every week, in order to configure the correct number of file descriptors.
Because when i delete an index and it will create again all (index and all
shards for this index), the quantity of file descriptors is more than that
i have all index working fine.(without delete all)
Regards
On Mon, Feb 10, 2014 at 3:43 PM, Binh Ly <bi...@hibalo.com <javascript:>>wrote:
Rondan,
If you're using REST/HTTP, you can use the Delete Index API to delete an
index easily:
On Monday, February 10, 2014 1:57:51 PM UTC-5, Rino Rondan wrote:
THanks, yes we are using this but with java api, but exists any formula
that i can predict how many open file i will have if my indices increase
every week, in order to configure the correct number of file descriptors.
Because when i delete an index and it will create again all (index and all
shards for this index), the quantity of file descriptors is more than that
i have all index working fine.(without delete all)
Regards
On Mon, Feb 10, 2014 at 3:43 PM, Binh Ly bi...@hibalo.com wrote:
Rondan,
If you're using REST/HTTP, you can use the Delete Index API to delete an
index easily:
--
You received this message because you are subscribed to a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/
topic/elasticsearch/nadGbpBPAQk/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elasticsearc...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/
msgid/elasticsearch/b2421e6b-3114-4ec8-b417-fd594d7e2612% 40googlegroups.com.
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.