Re: How to configure max file descriptors on windows OS?
Thanks Mark! On Friday, April 17, 2015 at 6:22:24 AM UTC+8, Mark Walkom wrote: > > -1 means unbound, ie unlimited. > > On 16 April 2015 at 20:54, Xudong You > > wrote: > >> Anyone knows how to change the max_file_descriptors on windows? >> I built ES cluster on Windows and got following process information: >> >> "max_file_descriptors" : -1, >> "open_file_descriptors" : -1, >> >> What does “-1 mean? >> Is it possible to change the max file descriptors on windows platform? >> >> -- >> You received this message because you are subscribed to the Google Groups >> "elasticsearch" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to elasticsearc...@googlegroups.com . >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/aa22c565-80f5-4228-8f03-15d1b1e3f150%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/aa22c565-80f5-4228-8f03-15d1b1e3f150%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/6c87970e-ca32-413b-9333-9ec60a931c9e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to configure max file descriptors on windows OS?
-1 means unbound, ie unlimited. On 16 April 2015 at 20:54, Xudong You wrote: > Anyone knows how to change the max_file_descriptors on windows? > I built ES cluster on Windows and got following process information: > > "max_file_descriptors" : -1, > "open_file_descriptors" : -1, > > What does “-1 mean? > Is it possible to change the max file descriptors on windows platform? > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/aa22c565-80f5-4228-8f03-15d1b1e3f150%40googlegroups.com > <https://groups.google.com/d/msgid/elasticsearch/aa22c565-80f5-4228-8f03-15d1b1e3f150%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_KJHAHgmp%3DdDbsrMGhEXZ4coQifJdZ1_o353ctHQs3DA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
How to configure max file descriptors on windows OS?
Anyone knows how to change the max_file_descriptors on windows? I built ES cluster on Windows and got following process information: "max_file_descriptors" : -1, "open_file_descriptors" : -1, What does “-1 mean? Is it possible to change the max file descriptors on windows platform? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/aa22c565-80f5-4228-8f03-15d1b1e3f150%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: File Descriptors
On Windows I think you can safely ignore the file descriptors value.
> On Dec 16, 2014, at 10:06 PM, Chetan Dev wrote:
>
> Hi,
>
> I am on windows
>
> Thanks
>
> On Wednesday, December 17, 2014 2:12:16 AM UTC+5:30, Andrew Selden wrote:
> What OS are you on? My guess would be that the library (sigar) that reads
> that value can’t find it.
>
>
>> On Dec 16, 2014, at 2:15 AM, Chetan Dev >
>> wrote:
>>
>> Hi,
>>
>> What does file descriptor value of -1 shows?
>> what is the default value for it ?
>>
>> Thanks
>>
>>
>> },
>> "WkgDi0joTYSrs5sO3_bndQ" : {
>> "name" : "AEPLPERF2",
>> "transport_address" : "inet[/192.168.1.13:9300
>> <http://192.168.1.13:9300/>]",
>> "host" : "AEPLPERF1",
>> "ip" : "192.168.1.13",
>> "version" : "1.4.1",
>> "build" : "89d3241",
>> "http_address" : "inet[/192.168.1.13:9200
>> <http://192.168.1.13:9200/>]",
>> "process" : {
>> "refresh_interval_in_millis" : 1000,
>> "id" : 28240,
>> "max_file_descriptors" : -1,
>> "mlockall" : false
>> }
>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/7c08629e-9c6a-42ce-8754-702c0e27be2d%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/elasticsearch/7c08629e-9c6a-42ce-8754-702c0e27be2d%40googlegroups.com?utm_medium=email&utm_source=footer>.
>> For more options, visit https://groups.google.com/d/optout
>> <https://groups.google.com/d/optout>.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com
> <mailto:elasticsearch+unsubscr...@googlegroups.com>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/260d8234-a030-4c6e-81c6-ed48dcf936c2%40googlegroups.com
>
> <https://groups.google.com/d/msgid/elasticsearch/260d8234-a030-4c6e-81c6-ed48dcf936c2%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout
> <https://groups.google.com/d/optout>.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/D1569428-42EF-4FDC-8EBE-FD0D6A1B2FE4%40elasticsearch.com.
For more options, visit https://groups.google.com/d/optout.
Re: File Descriptors
Hi,
I am on windows
Thanks
On Wednesday, December 17, 2014 2:12:16 AM UTC+5:30, Andrew Selden wrote:
>
> What OS are you on? My guess would be that the library (sigar) that reads
> that value can’t find it.
>
>
> On Dec 16, 2014, at 2:15 AM, Chetan Dev > wrote:
>
> Hi,
>
> What does file descriptor value of -1 shows?
> what is the default value for it ?
>
> Thanks
>
>
> },
> "WkgDi0joTYSrs5sO3_bndQ" : {
> "name" : "AEPLPERF2",
> "transport_address" : "inet[/192.168.1.13:9300]",
> "host" : "AEPLPERF1",
> "ip" : "192.168.1.13",
> "version" : "1.4.1",
> "build" : "89d3241",
> "http_address" : "inet[/192.168.1.13:9200]",
> "process" : {
> "refresh_interval_in_millis" : 1000,
> "id" : 28240,
> "max_file_descriptors" : -1,
> "mlockall" : false
> }
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearc...@googlegroups.com .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/7c08629e-9c6a-42ce-8754-702c0e27be2d%40googlegroups.com
>
>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/260d8234-a030-4c6e-81c6-ed48dcf936c2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: File Descriptors
What OS are you on? My guess would be that the library (sigar) that reads that
value can’t find it.
> On Dec 16, 2014, at 2:15 AM, Chetan Dev wrote:
>
> Hi,
>
> What does file descriptor value of -1 shows?
> what is the default value for it ?
>
> Thanks
>
>
> },
> "WkgDi0joTYSrs5sO3_bndQ" : {
> "name" : "AEPLPERF2",
> "transport_address" : "inet[/192.168.1.13:9300]",
> "host" : "AEPLPERF1",
> "ip" : "192.168.1.13",
> "version" : "1.4.1",
> "build" : "89d3241",
> "http_address" : "inet[/192.168.1.13:9200]",
> "process" : {
> "refresh_interval_in_millis" : 1000,
> "id" : 28240,
> "max_file_descriptors" : -1,
> "mlockall" : false
> }
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/7c08629e-9c6a-42ce-8754-702c0e27be2d%40googlegroups.com
>
> .
> For more options, visit https://groups.google.com/d/optout
> .
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/DC20CB93-6027-4361-AC15-09BC49B6C2E5%40elasticsearch.com.
For more options, visit https://groups.google.com/d/optout.
File Descriptors
Hi,
What does file descriptor value of -1 shows?
what is the default value for it ?
Thanks
},
"WkgDi0joTYSrs5sO3_bndQ" : {
"name" : "AEPLPERF2",
"transport_address" : "inet[/192.168.1.13:9300]",
"host" : "AEPLPERF1",
"ip" : "192.168.1.13",
"version" : "1.4.1",
"build" : "89d3241",
"http_address" : "inet[/192.168.1.13:9200]",
"process" : {
"refresh_interval_in_millis" : 1000,
"id" : 28240,
"max_file_descriptors" : -1,
"mlockall" : false
}
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/7c08629e-9c6a-42ce-8754-702c0e27be2d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: File Descriptors
No I did not use RPM used .tar for the installation process and my ulimit
settings are in
/etc/security/limits.conf
* - nofile 65535
/etc/sysctl.conf
fs.file-max = 512000
On Thu, May 22, 2014 at 12:37 PM, Mark Walkom wrote:
> Did you use the RPMs? Where are you setting the ulimit?
>
> Regards,
> Mark Walkom
>
> Infrastructure Engineer
> Campaign Monitor
> email: ma...@campaignmonitor.com
> web: www.campaignmonitor.com
>
>
> On 22 May 2014 20:30, Shawn Ritchie wrote:
>
>> CentOS 6.5 and Java 1.7u55
>>
>>
>> On Thu, May 22, 2014 at 12:28 PM, Shawn Ritchie wrote:
>>
>>> so this issue only occurs on server restart. If I had to restart
>>> elasticsearch service it would load the correct number of file descriptors.
>>>
>>> Regards
>>> Shawn
>>>
>>>
>>> On Thu, May 22, 2014 at 12:19 PM, Shawn Ritchie wrote:
>>>
>>>> Hi guys,
>>>>
>>>> Kind of stuck with a fresh installation of an ElasticSearch cluster.
>>>> everything is installed file descriptor limits are set yet when I run
>>>>
>>>> curl -XGET "
>>>> http://10.0.8.62:9200/_nodes?os=true&process=true&pretty=true"; >
>>>> stats.txt
>>>>
>>>> I get
>>>>
>>>> "process" : {
>>>> "refresh_interval" : 1000,
>>>> "id" : 1200,
>>>> "max_file_descriptors" : 4096,
>>>> "mlockall" : true
>>>> },
>>>>
>>>> yet when I run
>>>>
>>>> ulimit -n I get
>>>>
>>>> 65535
>>>>
>>>> ElasticSearch is installed as a service and running as root? Any idea
>>>> why this is happening?
>>>>
>>>> --
>>>> 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/SIKIWq40MKY/unsubscribe
>>>> .
>>>> To unsubscribe from this group and all its topics, send an email to
>>>> elasticsearch+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/elasticsearch/53e168b5-8834-4b63-98ec-4c5a3080a91b%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/53e168b5-8834-4b63-98ec-4c5a3080a91b%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Thanks
>>> Shawn Ritchie
>>>
>>
>>
>>
>> --
>> Thanks
>> Shawn Ritchie
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to elasticsearch+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/CAP0uL7xtHLT6%2ByjPMSENxQEZKYHJL_31ZuLW%2BUXNrO2GOJsSPw%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAP0uL7xtHLT6%2ByjPMSENxQEZKYHJL_31ZuLW%2BUXNrO2GOJsSPw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> 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/SIKIWq40MKY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/CAEM624bonFrf5V1eK%3D9Ug8SpSiC%3DWL3%3Dc6MRiOSmaK9Hkjz6KA%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAEM624bonFrf5V1eK%3D9Ug8SpSiC%3DWL3%3Dc6MRiOSmaK9Hkjz6KA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
Thanks
Shawn Ritchie
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAP0uL7zxoJe_W80wRU4Kqomv0MBzC67cwo8M%2B0WTmepvgs7CEg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: File Descriptors
Did you use the RPMs? Where are you setting the ulimit?
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 22 May 2014 20:30, Shawn Ritchie wrote:
> CentOS 6.5 and Java 1.7u55
>
>
> On Thu, May 22, 2014 at 12:28 PM, Shawn Ritchie wrote:
>
>> so this issue only occurs on server restart. If I had to restart
>> elasticsearch service it would load the correct number of file descriptors.
>>
>> Regards
>> Shawn
>>
>>
>> On Thu, May 22, 2014 at 12:19 PM, Shawn Ritchie wrote:
>>
>>> Hi guys,
>>>
>>> Kind of stuck with a fresh installation of an ElasticSearch cluster.
>>> everything is installed file descriptor limits are set yet when I run
>>>
>>> curl -XGET "
>>> http://10.0.8.62:9200/_nodes?os=true&process=true&pretty=true"; >
>>> stats.txt
>>>
>>> I get
>>>
>>> "process" : {
>>> "refresh_interval" : 1000,
>>> "id" : 1200,
>>> "max_file_descriptors" : 4096,
>>> "mlockall" : true
>>> },
>>>
>>> yet when I run
>>>
>>> ulimit -n I get
>>>
>>> 65535
>>>
>>> ElasticSearch is installed as a service and running as root? Any idea
>>> why this is happening?
>>>
>>> --
>>> 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/SIKIWq40MKY/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> elasticsearch+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/elasticsearch/53e168b5-8834-4b63-98ec-4c5a3080a91b%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/53e168b5-8834-4b63-98ec-4c5a3080a91b%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Thanks
>> Shawn Ritchie
>>
>
>
>
> --
> Thanks
> Shawn Ritchie
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/CAP0uL7xtHLT6%2ByjPMSENxQEZKYHJL_31ZuLW%2BUXNrO2GOJsSPw%40mail.gmail.com<https://groups.google.com/d/msgid/elasticsearch/CAP0uL7xtHLT6%2ByjPMSENxQEZKYHJL_31ZuLW%2BUXNrO2GOJsSPw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAEM624bonFrf5V1eK%3D9Ug8SpSiC%3DWL3%3Dc6MRiOSmaK9Hkjz6KA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: File Descriptors
CentOS 6.5 and Java 1.7u55
On Thu, May 22, 2014 at 12:28 PM, Shawn Ritchie wrote:
> so this issue only occurs on server restart. If I had to restart
> elasticsearch service it would load the correct number of file descriptors.
>
> Regards
> Shawn
>
>
> On Thu, May 22, 2014 at 12:19 PM, Shawn Ritchie wrote:
>
>> Hi guys,
>>
>> Kind of stuck with a fresh installation of an ElasticSearch cluster.
>> everything is installed file descriptor limits are set yet when I run
>>
>> curl -XGET "http://10.0.8.62:9200/_nodes?os=true&process=true&pretty=true";
>> > stats.txt
>>
>> I get
>>
>> "process" : {
>> "refresh_interval" : 1000,
>> "id" : 1200,
>> "max_file_descriptors" : 4096,
>> "mlockall" : true
>> },
>>
>> yet when I run
>>
>> ulimit -n I get
>>
>> 65535
>>
>> ElasticSearch is installed as a service and running as root? Any idea why
>> this is happening?
>>
>> --
>> 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/SIKIWq40MKY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> elasticsearch+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/53e168b5-8834-4b63-98ec-4c5a3080a91b%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/53e168b5-8834-4b63-98ec-4c5a3080a91b%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Thanks
> Shawn Ritchie
>
--
Thanks
Shawn Ritchie
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAP0uL7xtHLT6%2ByjPMSENxQEZKYHJL_31ZuLW%2BUXNrO2GOJsSPw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: File Descriptors
so this issue only occurs on server restart. If I had to restart
elasticsearch service it would load the correct number of file descriptors.
Regards
Shawn
On Thu, May 22, 2014 at 12:19 PM, Shawn Ritchie wrote:
> Hi guys,
>
> Kind of stuck with a fresh installation of an ElasticSearch cluster.
> everything is installed file descriptor limits are set yet when I run
>
> curl -XGET "http://10.0.8.62:9200/_nodes?os=true&process=true&pretty=true";
> > stats.txt
>
> I get
>
> "process" : {
> "refresh_interval" : 1000,
> "id" : 1200,
> "max_file_descriptors" : 4096,
> "mlockall" : true
> },
>
> yet when I run
>
> ulimit -n I get
>
> 65535
>
> ElasticSearch is installed as a service and running as root? Any idea why
> this is happening?
>
> --
> 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/SIKIWq40MKY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/53e168b5-8834-4b63-98ec-4c5a3080a91b%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/53e168b5-8834-4b63-98ec-4c5a3080a91b%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
Thanks
Shawn Ritchie
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAP0uL7zMEv-dDh1N1ZhY%3D2k9SPDt8bdiBPNqjn%2BPgYHqU0oRrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: File Descriptors
What OS and how did you install it?
(Running as root is a really bad idea by the way!)
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 22 May 2014 20:19, Shawn Ritchie wrote:
> Hi guys,
>
> Kind of stuck with a fresh installation of an ElasticSearch cluster.
> everything is installed file descriptor limits are set yet when I run
>
> curl -XGET "http://10.0.8.62:9200/_nodes?os=true&process=true&pretty=true";
> > stats.txt
>
> I get
>
> "process" : {
> "refresh_interval" : 1000,
> "id" : 1200,
> "max_file_descriptors" : 4096,
> "mlockall" : true
> },
>
> yet when I run
>
> ulimit -n I get
>
> 65535
>
> ElasticSearch is installed as a service and running as root? Any idea why
> this is happening?
>
> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/53e168b5-8834-4b63-98ec-4c5a3080a91b%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAEM624YGJTMJVwfZTea%3DJr4-K77hFvG6hYMoNfLWbTxBa3T4iw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
File Descriptors
Hi guys,
Kind of stuck with a fresh installation of an ElasticSearch cluster.
everything is installed file descriptor limits are set yet when I run
curl -XGET "http://10.0.8.62:9200/_nodes?os=true&process=true&pretty=true";
> stats.txt
I get
"process" : {
"refresh_interval" : 1000,
"id" : 1200,
"max_file_descriptors" : 4096,
"mlockall" : true
},
yet when I run
ulimit -n I get
65535
ElasticSearch is installed as a service and running as root? Any idea why
this is happening?
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/53e168b5-8834-4b63-98ec-4c5a3080a91b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Elasticsearch node under utilising file descriptors
gt;> "primaries" : {
>>>>>>> "docs" : {
>>>>>>> "count" : 28403397,
>>>>>>> "deleted" : 1385142
>>>>>>> },
>>>>>>> "store" : {
>>>>>>> "size" : "465.4gb",
>>>>>>> "size_in_bytes" : 499761991425,
>>>>>>> "throttle_time" : "0s",
>>>>>>> "throttle_time_in_millis" : 0
>>>>>>> },
>>>>>>> "indexing" : {
>>>>>>> "index_total" : 2343265,
>>>>>>> "index_time" : "13.9d",
>>>>>>> "index_time_in_millis" : 1204844492,
>>>>>>> "index_current" : 0,
>>>>>>> "delete_total" : 5,
>>>>>>> "delete_time" : "659ms",
>>>>>>> "delete_time_in_millis" : 659,
>>>>>>> "delete_current" : 0
>>>>>>> },
>>>>>>> "get" : {
>>>>>>> "total" : 9,
>>>>>>> "get_time" : "3.2s",
>>>>>>> "time_in_millis" : 3277,
>>>>>>> "exists_total" : 6,
>>>>>>> "exists_time" : "3.2s",
>>>>>>> "exists_time_in_millis" : 3277,
>>>>>>> "missing_total" : 3,
>>>>>>> "missing_time" : "0s",
>>>>>>> "missing_time_in_millis" : 0,
>>>>>>> "current" : 0
>>>>>>> },
>>>>>>> "search" : {
>>>>>>> "open_contexts" : 32,
>>>>>>> "query_total" : 262779551,
>>>>>>> "query_time" : "430.4d",
>>>>>>> "query_time_in_millis" : 37193583386,
>>>>>>> "query_current" : 3,
>>>>>>> "fetch_total" : 115208512,
>>>>>>> "fetch_time" : "541.6d",
>>>>>>> "fetch_time_in_millis" : 46798459635,
>>>>>>> "fetch_current" : 9
>>>>>>> }
>>>>>>> },
>>>>>>> "total" : {
>>>>>>> "docs" : {
>>>>>>> "count" : 56806794,
>>>>>>> "deleted" : 2770284
>>>>>>> },
>>>>>>> "store" : {
>>>>>>> "size" : "930.8gb",
>>>>>>> "size_in_bytes" : 999509417525,
>>>>>>> "throttle_time" : "0s",
>>>>>>> "throttle_time_in_millis" : 0
>>>>>>> },
>>>>>>> "indexing" : {
>>>>>>> "index_total" : 4682044,
>>>>>>> "index_time" : "34.6d",
>>>>>>> "index_time_in_millis" : 2993312068,
>>>>>>> "index_current" : 2232,
>>>>>>> "delete_total" : 10,
>>>>>>> "delete_time" : "2.4s",
>>>>>>> "delete_time_in_millis" : 2404,
>>>>>>> "delete_current" : 0
>>>>>>> },
>>>>>>> "get" : {
>>>>>>> "total" : 24,
>>>>>>> "get_time" : "9.8s",
>>>>>>> "time_in_millis" : 9855,
>>>>>>> "exists_total" : 15,
>>>>>>> "exists_time" : "9.8s",
>>>>>>> "exists_time_in_millis" : 9855,
>>>>>>> "missing_total" : 9,
>>>>>>> "missing_time" :
Re: Elasticsearch node under utilising file descriptors
d",
>>>>>> "index_time_in_millis" : 1204844492,
>>>>>> "index_current" : 0,
>>>>>> "delete_total" : 5,
>>>>>> "delete_time" : "659ms",
>>>>>> "delete_time_in_millis" : 659,
>>>>>> "delete_current" : 0
>>>>>> },
>>>>>> "get" : {
>>>>>> "total" : 9,
>>>>>> "get_time" : "3.2s",
>>>>>> "time_in_millis" : 3277,
>>>>>> "exists_total" : 6,
>>>>>> "exists_time" : "3.2s",
>>>>>> "exists_time_in_millis" : 3277,
>>>>>> "missing_total" : 3,
>>>>>> "missing_time" : "0s",
>>>>>> "missing_time_in_millis" : 0,
>>>>>> "current" : 0
>>>>>> },
>>>>>> "search" : {
>>>>>> "open_contexts" : 32,
>>>>>> "query_total" : 262779551,
>>>>>> "query_time" : "430.4d",
>>>>>> "query_time_in_millis" : 37193583386,
>>>>>> "query_current" : 3,
>>>>>> "fetch_total" : 115208512,
>>>>>> "fetch_time" : "541.6d",
>>>>>> "fetch_time_in_millis" : 46798459635,
>>>>>> "fetch_current" : 9
>>>>>> }
>>>>>> },
>>>>>> "total" : {
>>>>>> "docs" : {
>>>>>> "count" : 56806794,
>>>>>> "deleted" : 2770284
>>>>>> },
>>>>>> "store" : {
>>>>>> "size" : "930.8gb",
>>>>>> "size_in_bytes" : 999509417525,
>>>>>> "throttle_time" : "0s",
>>>>>> "throttle_time_in_millis" : 0
>>>>>> },
>>>>>> "indexing" : {
>>>>>> "index_total" : 4682044,
>>>>>> "index_time" : "34.6d",
>>>>>> "index_time_in_millis" : 2993312068,
>>>>>> "index_current" : 2232,
>>>>>> "delete_total" : 10,
>>>>>> "delete_time" : "2.4s",
>>>>>> "delete_time_in_millis" : 2404,
>>>>>> "delete_current" : 0
>>>>>> },
>>>>>> "get" : {
>>>>>> "total" : 24,
>>>>>> "get_time" : "9.8s",
>>>>>> "time_in_millis" : 9855,
>>>>>> "exists_total" : 15,
>>>>>> "exists_time" : "9.8s",
>>>>>> "exists_time_in_millis" : 9855,
>>>>>> "missing_total" : 9,
>>>>>> "missing_time" : "0s",
>>>>>> "missing_time_in_millis" : 0,
>>>>>> "current" : 0
>>>>>> },
>>>>>> "search" : {
>>>>>> "open_contexts" : 64,
>>>>>> "query_total" : 525308020,
>>>>>> "query_time" : "816.1d",
>>>>>> "query_time_in_millis" : 70519558277,
>>>>>> "query_current" : 6,
>>>>>> "fetch_total" : 230215915,
>>>>>> "fetch_time" : "939.6d",
>>>>>> "fetch_time_in_millis" : 81182884575,
>>>>>> "fetch_current" : 10
>>>>>> }
>>>>>> }
>>>>>> }
>>>>>>
>>>>>>
>>>>>> I am attaching along the hot_threads output, though I
Re: Elasticsearch node under utilising file descriptors
3.2s",
>>>>> "exists_time_in_millis" : 3277,
>>>>> "missing_total" : 3,
>>>>> "missing_time" : "0s",
>>>>> "missing_time_in_millis" : 0,
>>>>> "current" : 0
>>>>> },
>>>>> "search" : {
>>>>> "open_contexts" : 32,
>>>>> "query_total" : 262779551,
>>>>> "query_time" : "430.4d",
>>>>> "query_time_in_millis" : 37193583386,
>>>>> "query_current" : 3,
>>>>> "fetch_total" : 115208512,
>>>>> "fetch_time" : "541.6d",
>>>>> "fetch_time_in_millis" : 46798459635,
>>>>> "fetch_current" : 9
>>>>> }
>>>>> },
>>>>> "total" : {
>>>>> "docs" : {
>>>>> "count" : 56806794,
>>>>> "deleted" : 2770284
>>>>> },
>>>>> "store" : {
>>>>> "size" : "930.8gb",
>>>>> "size_in_bytes" : 999509417525,
>>>>> "throttle_time" : "0s",
>>>>> "throttle_time_in_millis" : 0
>>>>> },
>>>>> "indexing" : {
>>>>> "index_total" : 4682044,
>>>>> "index_time" : "34.6d",
>>>>> "index_time_in_millis" : 2993312068,
>>>>> "index_current" : 2232,
>>>>> "delete_total" : 10,
>>>>> "delete_time" : "2.4s",
>>>>> "delete_time_in_millis" : 2404,
>>>>> "delete_current" : 0
>>>>> },
>>>>> "get" : {
>>>>> "total" : 24,
>>>>> "get_time" : "9.8s",
>>>>> "time_in_millis" : 9855,
>>>>> "exists_total" : 15,
>>>>> "exists_time" : "9.8s",
>>>>> "exists_time_in_millis" : 9855,
>>>>> "missing_total" : 9,
>>>>> "missing_time" : "0s",
>>>>> "missing_time_in_millis" : 0,
>>>>> "current" : 0
>>>>> },
>>>>> "search" : {
>>>>> "open_contexts" : 64,
>>>>> "query_total" : 525308020,
>>>>> "query_time" : "816.1d",
>>>>> "query_time_in_millis" : 70519558277,
>>>>> "query_current" : 6,
>>>>> "fetch_total" : 230215915,
>>>>> "fetch_time" : "939.6d",
>>>>> "fetch_time_in_millis" : 81182884575,
>>>>> "fetch_current" : 10
>>>>> }
>>>>> }
>>>>> }
>>>>>
>>>>>
>>>>> I am attaching along the hot_threads output, though I couldn't make
>>>>> much sense of it. Pardon me if I sound N00Bish, because I am pretty new to
>>>>> ES.
>>>>>
>>>>>
>>>>> On Wednesday, May 14, 2014 11:27:07 AM UTC+5:30, Mark Walkom wrote:
>>>>>>
>>>>>> ES will use descriptors to open files it needs for general operations
>>>>>> and it can have a lot of those open at one time. But the level you've set
>>>>>> and the level you're using are not related to your slow queries.
>>>>>>
>>>>>> How much data do you have in your cluster? What version of ES, what
>>>>>> version of java? You should also check your slow log
>>>>>> (/var/log/elasticsearch/*_index_search_slowlog.log) and hot threads
>>>>>> (GET /_cluster/nodes/hot_threads) to see what is happening.
>>>>>> Also try installing a plugin like Marvel or ElasticHQ to give you a
>>>>>> better idea of
Re: Elasticsearch node under utilising file descriptors
;fetch_time_in_millis" : 46798459635,
>>>> "fetch_current" : 9
>>>> }
>>>> },
>>>> "total" : {
>>>> "docs" : {
>>>> "count" : 56806794,
>>>> "deleted" : 2770284
>>>> },
>>>> "store" : {
>>>> "size" : "930.8gb",
>>>> "size_in_bytes" : 999509417525,
>>>> "throttle_time" : "0s",
>>>> "throttle_time_in_millis" : 0
>>>> },
>>>> "indexing" : {
>>>> "index_total" : 4682044,
>>>> "index_time" : "34.6d",
>>>> "index_time_in_millis" : 2993312068,
>>>> "index_current" : 2232,
>>>> "delete_total" : 10,
>>>> "delete_time" : "2.4s",
>>>> "delete_time_in_millis" : 2404,
>>>> "delete_current" : 0
>>>> },
>>>> "get" : {
>>>> "total" : 24,
>>>> "get_time" : "9.8s",
>>>> "time_in_millis" : 9855,
>>>> "exists_total" : 15,
>>>> "exists_time" : "9.8s",
>>>> "exists_time_in_millis" : 9855,
>>>> "missing_total" : 9,
>>>> "missing_time" : "0s",
>>>> "missing_time_in_millis" : 0,
>>>> "current" : 0
>>>> },
>>>> "search" : {
>>>> "open_contexts" : 64,
>>>> "query_total" : 525308020,
>>>> "query_time" : "816.1d",
>>>> "query_time_in_millis" : 70519558277,
>>>> "query_current" : 6,
>>>> "fetch_total" : 230215915,
>>>> "fetch_time" : "939.6d",
>>>> "fetch_time_in_millis" : 81182884575,
>>>> "fetch_current" : 10
>>>> }
>>>> }
>>>> }
>>>>
>>>>
>>>> I am attaching along the hot_threads output, though I couldn't make
>>>> much sense of it. Pardon me if I sound N00Bish, because I am pretty new to
>>>> ES.
>>>>
>>>>
>>>> On Wednesday, May 14, 2014 11:27:07 AM UTC+5:30, Mark Walkom wrote:
>>>>>
>>>>> ES will use descriptors to open files it needs for general operations
>>>>> and it can have a lot of those open at one time. But the level you've set
>>>>> and the level you're using are not related to your slow queries.
>>>>>
>>>>> How much data do you have in your cluster? What version of ES, what
>>>>> version of java? You should also check your slow log
>>>>> (/var/log/elasticsearch/*_index_search_slowlog.log) and hot threads
>>>>> (GET /_cluster/nodes/hot_threads) to see what is happening.
>>>>> Also try installing a plugin like Marvel or ElasticHQ to give you a
>>>>> better idea of what your resource usage is like on a cluster level.
>>>>> Bigdesk
>>>>> is good but it limited to a node only view.
>>>>>
>>>>> Regards,
>>>>> Mark Walkom
>>>>>
>>>>> Infrastructure Engineer
>>>>> Campaign Monitor
>>>>> email: ma...@campaignmonitor.com
>>>>> web: www.campaignmonitor.com
>>>>>
>>>>>
>>>>> On 14 May 2014 15:47, Tamanjit Bindra wrote:
>>>>>
>>>>>> Hi,
>>>>>> I have read
>>>>>> here<http://www.elasticsearch.org/tutorials/too-many-open-files/>,
>>>>>> that we should set the soft and hard values of nooffiles for ES to
>>>>>> utilise.
>>>>>>
>>>>>> I have done that, but somehow my BigDesk console shows that even
>>>>>> though the upper limit is 65535, ES is only using about 2K+ file
>>>>>> descriptors at any given moment.
>>>>>>
>>>>>> I have set the ulimit -Hn and ulimit -Sn to 32000.
>>>>>>
>>>>>> Why is this so?
>>>>>>
>>>>>> I ask this because my queries are performing slow.
>>>>>>
>>>>>> We are using 2 nodes. Both servers have 16G RAM with 10G dedicated to
>>>>>> ES.
>>>>>>
>>>>>> Please Help!
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups "elasticsearch" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it,
>>>>>> send an email to elasticsearc...@googlegroups.com.
>>>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>>>> msgid/elasticsearch/c27bd6d3-28a4-470b-96db-08117f554b7d%40goo
>>>>>> glegroups.com<https://groups.google.com/d/msgid/elasticsearch/c27bd6d3-28a4-470b-96db-08117f554b7d%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>> .
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>
>>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "elasticsearch" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to elasticsearc...@googlegroups.com.
>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>> msgid/elasticsearch/d854a1e6-20a0-4424-86b0-2322f18b6047%
>>>> 40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/d854a1e6-20a0-4424-86b0-2322f18b6047%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/d8317d44-f8d9-400f-b72d-089840db0cc7%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/d8317d44-f8d9-400f-b72d-089840db0cc7%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/518692f6-e743-4323-bccf-44e299471c86%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Elasticsearch node under utilising file descriptors
0
>>> },
>>> "indexing" : {
>>> "index_total" : 4682044,
>>> "index_time" : "34.6d",
>>> "index_time_in_millis" : 2993312068,
>>> "index_current" : 2232,
>>> "delete_total" : 10,
>>> "delete_time" : "2.4s",
>>> "delete_time_in_millis" : 2404,
>>> "delete_current" : 0
>>> },
>>> "get" : {
>>> "total" : 24,
>>> "get_time" : "9.8s",
>>> "time_in_millis" : 9855,
>>> "exists_total" : 15,
>>> "exists_time" : "9.8s",
>>> "exists_time_in_millis" : 9855,
>>> "missing_total" : 9,
>>> "missing_time" : "0s",
>>> "missing_time_in_millis" : 0,
>>> "current" : 0
>>> },
>>> "search" : {
>>> "open_contexts" : 64,
>>> "query_total" : 525308020,
>>> "query_time" : "816.1d",
>>> "query_time_in_millis" : 70519558277,
>>> "query_current" : 6,
>>> "fetch_total" : 230215915,
>>> "fetch_time" : "939.6d",
>>> "fetch_time_in_millis" : 81182884575,
>>> "fetch_current" : 10
>>> }
>>> }
>>> }
>>>
>>>
>>> I am attaching along the hot_threads output, though I couldn't make much
>>> sense of it. Pardon me if I sound N00Bish, because I am pretty new to ES.
>>>
>>>
>>> On Wednesday, May 14, 2014 11:27:07 AM UTC+5:30, Mark Walkom wrote:
>>>>
>>>> ES will use descriptors to open files it needs for general operations
>>>> and it can have a lot of those open at one time. But the level you've set
>>>> and the level you're using are not related to your slow queries.
>>>>
>>>> How much data do you have in your cluster? What version of ES, what
>>>> version of java? You should also check your slow log
>>>> (/var/log/elasticsearch/*_index_search_slowlog.log) and hot threads
>>>> (GET /_cluster/nodes/hot_threads) to see what is happening.
>>>> Also try installing a plugin like Marvel or ElasticHQ to give you a
>>>> better idea of what your resource usage is like on a cluster level. Bigdesk
>>>> is good but it limited to a node only view.
>>>>
>>>> Regards,
>>>> Mark Walkom
>>>>
>>>> Infrastructure Engineer
>>>> Campaign Monitor
>>>> email: ma...@campaignmonitor.com
>>>> web: www.campaignmonitor.com
>>>>
>>>>
>>>> On 14 May 2014 15:47, Tamanjit Bindra wrote:
>>>>
>>>>> Hi,
>>>>> I have read
>>>>> here<http://www.elasticsearch.org/tutorials/too-many-open-files/>,
>>>>> that we should set the soft and hard values of nooffiles for ES to
>>>>> utilise.
>>>>>
>>>>> I have done that, but somehow my BigDesk console shows that even
>>>>> though the upper limit is 65535, ES is only using about 2K+ file
>>>>> descriptors at any given moment.
>>>>>
>>>>> I have set the ulimit -Hn and ulimit -Sn to 32000.
>>>>>
>>>>> Why is this so?
>>>>>
>>>>> I ask this because my queries are performing slow.
>>>>>
>>>>> We are using 2 nodes. Both servers have 16G RAM with 10G dedicated to
>>>>> ES.
>>>>>
>>>>> Please Help!
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "elasticsearch" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to elasticsearc...@googlegroups.com.
>>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>>> msgid/elasticsearch/c27bd6d3-28a4-470b-96db-08117f554b7d%40goo
>>>>> glegroups.com<https://groups.google.com/d/msgid/elasticsearch/c27bd6d3-28a4-470b-96db-08117f554b7d%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>
>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "elasticsearch" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to elasticsearc...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/elasticsearch/d854a1e6-20a0-4424-86b0-2322f18b6047%
>>> 40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/d854a1e6-20a0-4424-86b0-2322f18b6047%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "elasticsearch" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to elasticsearch+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/elasticsearch/d8317d44-f8d9-400f-b72d-089840db0cc7%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/d8317d44-f8d9-400f-b72d-089840db0cc7%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/CAEM624YsSgQM5w-in5fdYvGn6d7EhWLa-s0RgQH3TrR%3DxaTG-g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Re: Elasticsearch node under utilising file descriptors
>> "missing_time" : "0s",
>> "missing_time_in_millis" : 0,
>> "current" : 0
>> },
>> "search" : {
>> "open_contexts" : 64,
>> "query_total" : 525308020,
>> "query_time" : "816.1d",
>> "query_time_in_millis" : 70519558277,
>> "query_current" : 6,
>> "fetch_total" : 230215915,
>> "fetch_time" : "939.6d",
>> "fetch_time_in_millis" : 81182884575,
>> "fetch_current" : 10
>> }
>> }
>> }
>>
>>
>> I am attaching along the hot_threads output, though I couldn't make much
>> sense of it. Pardon me if I sound N00Bish, because I am pretty new to ES.
>>
>>
>> On Wednesday, May 14, 2014 11:27:07 AM UTC+5:30, Mark Walkom wrote:
>>>
>>> ES will use descriptors to open files it needs for general operations
>>> and it can have a lot of those open at one time. But the level you've set
>>> and the level you're using are not related to your slow queries.
>>>
>>> How much data do you have in your cluster? What version of ES, what
>>> version of java? You should also check your slow log
>>> (/var/log/elasticsearch/*_index_search_slowlog.log) and hot threads
>>> (GET /_cluster/nodes/hot_threads) to see what is happening.
>>> Also try installing a plugin like Marvel or ElasticHQ to give you a
>>> better idea of what your resource usage is like on a cluster level. Bigdesk
>>> is good but it limited to a node only view.
>>>
>>> Regards,
>>> Mark Walkom
>>>
>>> Infrastructure Engineer
>>> Campaign Monitor
>>> email: ma...@campaignmonitor.com
>>> web: www.campaignmonitor.com
>>>
>>>
>>> On 14 May 2014 15:47, Tamanjit Bindra wrote:
>>>
>>>> Hi,
>>>> I have read
>>>> here<http://www.elasticsearch.org/tutorials/too-many-open-files/>,
>>>> that we should set the soft and hard values of nooffiles for ES to utilise.
>>>>
>>>> I have done that, but somehow my BigDesk console shows that even though
>>>> the upper limit is 65535, ES is only using about 2K+ file descriptors at
>>>> any given moment.
>>>>
>>>> I have set the ulimit -Hn and ulimit -Sn to 32000.
>>>>
>>>> Why is this so?
>>>>
>>>> I ask this because my queries are performing slow.
>>>>
>>>> We are using 2 nodes. Both servers have 16G RAM with 10G dedicated to
>>>> ES.
>>>>
>>>> Please Help!
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "elasticsearch" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to elasticsearc...@googlegroups.com.
>>>> To view this discussion on the web visit https://groups.google.com/d/
>>>> msgid/elasticsearch/c27bd6d3-28a4-470b-96db-08117f554b7d%
>>>> 40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/c27bd6d3-28a4-470b-96db-08117f554b7d%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "elasticsearch" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to elasticsearc...@googlegroups.com .
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/d854a1e6-20a0-4424-86b0-2322f18b6047%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/d854a1e6-20a0-4424-86b0-2322f18b6047%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to elasticsearch+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/d8317d44-f8d9-400f-b72d-089840db0cc7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Elasticsearch node under utilising file descriptors
It's better to put that sort of thing in a gist/pastebin :)
Any reason you aren't running a more recent version of ES? You'll get much
better performance from the new versions.
Also can you be specific about your java, what update, OpenJDK or Oracle?
Regards,
Mark Walkom
Infrastructure Engineer
Campaign Monitor
email: ma...@campaignmonitor.com
web: www.campaignmonitor.com
On 14 May 2014 16:17, Tamanjit Bindra wrote:
> Hi Mark,
> Thanks for the reply. We are using ES 0.90 on Java 7
>
> The stats are as under :
>
>
> "ok" : true,
> "_shards" : {
> "total" : 300,
> "successful" : 300,
> "failed" : 0
> },
> "_all" : {
> "primaries" : {
> "docs" : {
> "count" : 28403397,
> "deleted" : 1385142
> },
> "store" : {
> "size" : "465.4gb",
> "size_in_bytes" : 499761991425,
> "throttle_time" : "0s",
> "throttle_time_in_millis" : 0
> },
> "indexing" : {
> "index_total" : 2343265,
> "index_time" : "13.9d",
> "index_time_in_millis" : 1204844492,
> "index_current" : 0,
> "delete_total" : 5,
> "delete_time" : "659ms",
> "delete_time_in_millis" : 659,
> "delete_current" : 0
> },
> "get" : {
> "total" : 9,
> "get_time" : "3.2s",
> "time_in_millis" : 3277,
> "exists_total" : 6,
> "exists_time" : "3.2s",
> "exists_time_in_millis" : 3277,
> "missing_total" : 3,
> "missing_time" : "0s",
> "missing_time_in_millis" : 0,
> "current" : 0
> },
> "search" : {
> "open_contexts" : 32,
> "query_total" : 262779551,
> "query_time" : "430.4d",
> "query_time_in_millis" : 37193583386,
> "query_current" : 3,
> "fetch_total" : 115208512,
> "fetch_time" : "541.6d",
> "fetch_time_in_millis" : 46798459635,
> "fetch_current" : 9
> }
> },
> "total" : {
> "docs" : {
> "count" : 56806794,
> "deleted" : 2770284
> },
> "store" : {
> "size" : "930.8gb",
> "size_in_bytes" : 999509417525,
> "throttle_time" : "0s",
> "throttle_time_in_millis" : 0
> },
> "indexing" : {
> "index_total" : 4682044,
> "index_time" : "34.6d",
> "index_time_in_millis" : 2993312068,
> "index_current" : 2232,
> "delete_total" : 10,
> "delete_time" : "2.4s",
> "delete_time_in_millis" : 2404,
> "delete_current" : 0
> },
> "get" : {
> "total" : 24,
> "get_time" : "9.8s",
> "time_in_millis" : 9855,
> "exists_total" : 15,
> "exists_time" : "9.8s",
> "exists_time_in_millis" : 9855,
> "missing_total" : 9,
> "missing_time" : "0s",
> "missing_time_in_millis" : 0,
> "current" : 0
> },
> "search" : {
> "open_contexts" : 64,
> "query_total" : 525308020,
> "query_time" : "816.1d",
> "query_time_in_millis" : 70519558277,
> "query_current" : 6,
> "fetch_total" : 230215915,
> "fetch_time" : "939.6d",
> "fetch_time_in_millis" : 81182884575,
> "fetch_current" : 10
> }
> }
> }
>
>
> I am attaching along the hot_threads output, though I couldn't make much
> sense of it. Pardon me if I sound N00Bish, because I am pretty new to ES.
>
>
> On Wednesday, May 14, 2014 11:27:07 AM UTC+5:30, Mark Walkom wrote:
>>
>> ES will use descriptors to open files it needs for gen
Re: Elasticsearch node under utilising file descriptors
Hi Mark,
Thanks for the reply. We are using ES 0.90 on Java 7
The stats are as under :
"ok" : true,
"_shards" : {
"total" : 300,
"successful" : 300,
"failed" : 0
},
"_all" : {
"primaries" : {
"docs" : {
"count" : 28403397,
"deleted" : 1385142
},
"store" : {
"size" : "465.4gb",
"size_in_bytes" : 499761991425,
"throttle_time" : "0s",
"throttle_time_in_millis" : 0
},
"indexing" : {
"index_total" : 2343265,
"index_time" : "13.9d",
"index_time_in_millis" : 1204844492,
"index_current" : 0,
"delete_total" : 5,
"delete_time" : "659ms",
"delete_time_in_millis" : 659,
"delete_current" : 0
},
"get" : {
"total" : 9,
"get_time" : "3.2s",
"time_in_millis" : 3277,
"exists_total" : 6,
"exists_time" : "3.2s",
"exists_time_in_millis" : 3277,
"missing_total" : 3,
"missing_time" : "0s",
"missing_time_in_millis" : 0,
"current" : 0
},
"search" : {
"open_contexts" : 32,
"query_total" : 262779551,
"query_time" : "430.4d",
"query_time_in_millis" : 37193583386,
"query_current" : 3,
"fetch_total" : 115208512,
"fetch_time" : "541.6d",
"fetch_time_in_millis" : 46798459635,
"fetch_current" : 9
}
},
"total" : {
"docs" : {
"count" : 56806794,
"deleted" : 2770284
},
"store" : {
"size" : "930.8gb",
"size_in_bytes" : 999509417525,
"throttle_time" : "0s",
"throttle_time_in_millis" : 0
},
"indexing" : {
"index_total" : 4682044,
"index_time" : "34.6d",
"index_time_in_millis" : 2993312068,
"index_current" : 2232,
"delete_total" : 10,
"delete_time" : "2.4s",
"delete_time_in_millis" : 2404,
"delete_current" : 0
},
"get" : {
"total" : 24,
"get_time" : "9.8s",
"time_in_millis" : 9855,
"exists_total" : 15,
"exists_time" : "9.8s",
"exists_time_in_millis" : 9855,
"missing_total" : 9,
"missing_time" : "0s",
"missing_time_in_millis" : 0,
"current" : 0
},
"search" : {
"open_contexts" : 64,
"query_total" : 525308020,
"query_time" : "816.1d",
"query_time_in_millis" : 70519558277,
"query_current" : 6,
"fetch_total" : 230215915,
"fetch_time" : "939.6d",
"fetch_time_in_millis" : 81182884575,
"fetch_current" : 10
}
}
}
I am attaching along the hot_threads output, though I couldn't make much
sense of it. Pardon me if I sound N00Bish, because I am pretty new to ES.
On Wednesday, May 14, 2014 11:27:07 AM UTC+5:30, Mark Walkom wrote:
>
> ES will use descriptors to open files it needs for general operations and
> it can have a lot of those open at one time. But the level you've set and
> the level you're using are not related to your slow queries.
>
> How much data do you have in your cluster? What version of ES, what
> version of java? You should also check your slow log
> (/var/log/elasticsearch/*_index_search_slowlog.log) and hot threads (GET
> /_cluster/nodes/hot_threads) to see what is happening.
> Also try installing a plugin like Marvel or ElasticHQ to give you a better
> idea of what your resource usage is like on a cluster level. Bigdesk is
> good but it limited to a node only view.
>
> Regards,
> Mark Walkom
>
> Infrastructure Engineer
> Campaign Monitor
> email: ma...@campaignmonitor.com
> web: www.campaignmonitor.com
>
>
> On 14 May 2014 15:47, Tamanjit Bindra >wrote:
>
>> Hi,
>> I have read
>> here<http://www.elasticsearch.org/tutorials/too-many-open
Re: Elasticsearch node under utilising file descriptors
ES will use descriptors to open files it needs for general operations and it can have a lot of those open at one time. But the level you've set and the level you're using are not related to your slow queries. How much data do you have in your cluster? What version of ES, what version of java? You should also check your slow log (/var/log/elasticsearch/*_index_search_slowlog.log) and hot threads (GET /_cluster/nodes/hot_threads) to see what is happening. Also try installing a plugin like Marvel or ElasticHQ to give you a better idea of what your resource usage is like on a cluster level. Bigdesk is good but it limited to a node only view. Regards, Mark Walkom Infrastructure Engineer Campaign Monitor email: ma...@campaignmonitor.com web: www.campaignmonitor.com On 14 May 2014 15:47, Tamanjit Bindra wrote: > Hi, > I have read here<http://www.elasticsearch.org/tutorials/too-many-open-files/>, > that we should set the soft and hard values of nooffiles for ES to utilise. > > I have done that, but somehow my BigDesk console shows that even though > the upper limit is 65535, ES is only using about 2K+ file descriptors at > any given moment. > > I have set the ulimit -Hn and ulimit -Sn to 32000. > > Why is this so? > > I ask this because my queries are performing slow. > > We are using 2 nodes. Both servers have 16G RAM with 10G dedicated to ES. > > Please Help! > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/c27bd6d3-28a4-470b-96db-08117f554b7d%40googlegroups.com<https://groups.google.com/d/msgid/elasticsearch/c27bd6d3-28a4-470b-96db-08117f554b7d%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEM624Z%3DA8FRq-d4rW9nhBsmkx4KDUS0Wyp9Vu%2BzQKM4oPeCxw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Elasticsearch node under utilising file descriptors
Hi, I have read here<http://www.elasticsearch.org/tutorials/too-many-open-files/>, that we should set the soft and hard values of nooffiles for ES to utilise. I have done that, but somehow my BigDesk console shows that even though the upper limit is 65535, ES is only using about 2K+ file descriptors at any given moment. I have set the ulimit -Hn and ulimit -Sn to 32000. Why is this so? I ask this because my queries are performing slow. We are using 2 nodes. Both servers have 16G RAM with 10G dedicated to ES. Please Help! -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c27bd6d3-28a4-470b-96db-08117f554b7d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: problem with file descriptors
THanks a lot :) On Mon, Feb 10, 2014 at 4:06 PM, Binh Ly wrote: > Rondan, > > For Java, should be something like this: > > DeleteIndexResponse deleteIndexResponse = new > 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: > > http://www.elasticsearch.org/webinars/elasticsearch-pre-flight-checklist/ > > > 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 wrote: >> >>> Rondan, >>> >>> If you're using REST/HTTP, you can use the Delete Index API to delete an >>> index easily: >>> >>> http://www.elasticsearch.org/guide/en/elasticsearch/ >>> reference/current/indices-delete-index.html >>> >>> -- >>> 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. >>> >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> >> >> -- >> --- >> Rondan Rino >> Certificado en LPIC-2 <https://cs.lpi.org/caf/Xamman/certification> >> LPI ID:LPI000209832 >> Verification Code:gbblvwyfxu >> Red Hat Certified Engineer -- RHCE -- >> RHCVA<https://www.redhat.com/wapps/training/certification/verify.html?certNumber=120-175-658&verify=Verify> >> >> >> Blog:http://www.itrestauracion.com.ar >> Cv: http://cv.rinorondan.com.ar <http://www.rinorondan.com.ar/> >> http://counter.li.org Linux User -> #517918 >> Viva La Santa Federacion!! >> Mueran Los Salvages Unitarios!! >> ^^^Transcripcion de la epoca ^^^ >> >> >> >> -- > 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 > elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/7a320663-8bab-4f67-b9a4-b8a4c0199823%40googlegroups.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- --- Rondan Rino Certificado en LPIC-2 <https://cs.lpi.org/caf/Xamman/certification> LPI ID:LPI000209832 Verification Code:gbblvwyfxu Red Hat Certified Engineer -- RHCE -- RHCVA<https://www.redhat.com/wapps/training/certification/verify.html?certNumber=120-175-658&verify=Verify> Blog:http://www.itrestauracion.com.ar Cv: http://cv.rinorondan.com.ar <http://www.rinorondan.com.ar/> http://counter.li.org Linux User -> #517918 Viva La Santa Federacion!! Mueran Los Salvages Unitarios!! ^^^Transcripcion de la epoca ^^^ -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAASrp44TZFd0ibuFsvQ0uZvHqnsEh6J_jf5Y%3DhmJO6r-1eH9Rg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: problem with file descriptors
Rondan, For Java, should be something like this: DeleteIndexResponse deleteIndexResponse = new 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: http://www.elasticsearch.org/webinars/elasticsearch-pre-flight-checklist/ 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 >wrote: > >> Rondan, >> >> If you're using REST/HTTP, you can use the Delete Index API to delete an >> index easily: >> >> >> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-delete-index.html >> >> -- >> 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 >> . >> >> For more options, visit https://groups.google.com/groups/opt_out. >> > > > > -- > --- > Rondan Rino > Certificado en LPIC-2 <https://cs.lpi.org/caf/Xamman/certification> > LPI ID:LPI000209832 > Verification Code:gbblvwyfxu > Red Hat Certified Engineer -- RHCE -- > RHCVA<https://www.redhat.com/wapps/training/certification/verify.html?certNumber=120-175-658&verify=Verify> > > > > Blog:http://www.itrestauracion.com.ar > Cv: http://cv.rinorondan.com.ar <http://www.rinorondan.com.ar/> > http://counter.li.org Linux User -> #517918 > Viva La Santa Federacion!! > Mueran Los Salvages Unitarios!! > ^^^Transcripcion de la epoca ^^^ > > > > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7a320663-8bab-4f67-b9a4-b8a4c0199823%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: problem with file descriptors
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 wrote: > Rondan, > > If you're using REST/HTTP, you can use the Delete Index API to delete an > index easily: > > > http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-delete-index.html > > -- > 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 > elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/b2421e6b-3114-4ec8-b417-fd594d7e2612%40googlegroups.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- --- Rondan Rino Certificado en LPIC-2 <https://cs.lpi.org/caf/Xamman/certification> LPI ID:LPI000209832 Verification Code:gbblvwyfxu Red Hat Certified Engineer -- RHCE -- RHCVA<https://www.redhat.com/wapps/training/certification/verify.html?certNumber=120-175-658&verify=Verify> Blog:http://www.itrestauracion.com.ar Cv: http://cv.rinorondan.com.ar <http://www.rinorondan.com.ar/> http://counter.li.org Linux User -> #517918 Viva La Santa Federacion!! Mueran Los Salvages Unitarios!! ^^^Transcripcion de la epoca ^^^ -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAASrp46X__L-MaMg1do%3DKNd1Zf6CLxz8vCUfVZubT8h_Uxxojg%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: problem with file descriptors
Rondan, If you're using REST/HTTP, you can use the Delete Index API to delete an index easily: http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-delete-index.html -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/b2421e6b-3114-4ec8-b417-fd594d7e2612%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: problem with file descriptors
Thanks Binh, I have another question what is the best way to delete an index and the shards that use it to then recreate this index from beginning. Regards On Mon, Feb 10, 2014 at 11:22 AM, Binh Ly wrote: > This might help: > > http://lucene.apache.org/core/3_0_3/fileformats.html#Index%20File%20Formats > > Keep in mind, each shard in ES is a Lucene index so that is while lots of > file descriptors need to be used. In other words, it's normal. > > -- > 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 > elasticsearch+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/e6c59871-6c1f-45c0-8060-e911a2c0609f%40googlegroups.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- --- Rondan Rino Certificado en LPIC-2 <https://cs.lpi.org/caf/Xamman/certification> LPI ID:LPI000209832 Verification Code:gbblvwyfxu Red Hat Certified Engineer -- RHCE -- RHCVA<https://www.redhat.com/wapps/training/certification/verify.html?certNumber=120-175-658&verify=Verify> Blog:http://www.itrestauracion.com.ar Cv: http://cv.rinorondan.com.ar <http://www.rinorondan.com.ar/> http://counter.li.org Linux User -> #517918 Viva La Santa Federacion!! Mueran Los Salvages Unitarios!! ^^^Transcripcion de la epoca ^^^ -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAASrp47_ie1YHbHgS2Tmo70sFN%2BXv4%3D%2B-nS_fY5QJu1zOd8JJQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: problem with file descriptors
This might help: http://lucene.apache.org/core/3_0_3/fileformats.html#Index%20File%20Formats Keep in mind, each shard in ES is a Lucene index so that is while lots of file descriptors need to be used. In other words, it's normal. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e6c59871-6c1f-45c0-8060-e911a2c0609f%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
problem with file descriptors
Hi: 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. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/640dc816-1686-465a-8f5d-1a988c7ebb8b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
