Re: Elasticsearch taking a long time for garbage collection
Okay, I have 10GB and 8GB, will make them same, will make it same. And
another issue I am facing is the ELK stack is choking, and as soon as I
restart elasticsearch it starts up.
Thanks!
Shriyansh
On Friday, December 19, 2014 12:47:43 AM UTC-8, Mark Walkom wrote:
>
> Sorry, I mean you should really have the heap the *same* size on each node.
>
> On 19 December 2014 at 09:16, shriyansh jain > wrote:
>>
>> I have Heap Size on both the nodes.
>>
>> Using openjdk 1.7.0_09-icedtea and elasticsearch : "1.2.2".
>>
>> Thanks!
>> Shriyansh
>>
>> On Thursday, December 18, 2014 11:50:32 PM UTC-8, Mark Walkom wrote:
>>>
>>> You should really have heap the size on both nodes.
>>>
>>> What ES and java versions are you on?
>>>
>>> On 18 December 2014 at 19:54, shriyansh jain
>>> wrote:
>>>>
>>>> Hi All,
>>>>
>>>> I am seeing some warning message in elasticsearh log files which are
>>>> taking pretty long time for garbage collection.
>>>>
>>>> [2014-12-17 10:12:23,789][INFO ][monitor.jvm ] [Node1]
>>>> [gc][young][145219][4796] duration [901ms], collections [1]/[1.5s], total
>>>> [901ms]/[7.1m], memory [7.2gb]->[7.2gb]/[9.9gb], all_pools {[young]
>>>> [104.7mb]->[518.1kb]/[133.1mb]}{[survivor]
>>>> [8.3mb]->[12.6mb]/[16.6mb]}{[old] [7.1gb]->[7.2gb]/[9.8gb]}
>>>> [2014-12-17 10:12:29,172][WARN ][monitor.jvm ] [Node1]
>>>> [gc][young][145220][4797] duration [4.1s], collections [1]/[5s], total
>>>> [4.1s]/[7.2m], memory [7.2gb]->[7.4gb]/[9.9gb], all_pools {[young]
>>>> [518.1kb]->[109.4mb]/[133.1mb]}{[survivor]
>>>> [12.6mb]->[16.6mb]/[16.6mb]}{[old] [7.2gb]->[7.3gb]/[9.8gb]}
>>>> [2014-12-17 10:12:33,188][INFO ][monitor.jvm ] [Node1]
>>>> [gc][young][145224][4798] duration [791ms], collections [1]/[1s], total
>>>> [791ms]/[7.2m], memory [8.9gb]->[8.8gb]/[9.9gb], all_pools {[young]
>>>> [130.2mb]->[2kb]/[133.1mb]}{[survivor] [16.6mb]->[16.6mb]/[16.6mb]}{[old]
>>>> [8.7gb]->[8.8gb]/[9.8gb]}
>>>> [2014-12-17 10:13:18,476][INFO ][monitor.jvm ] [Node1]
>>>> [gc][young][145268][4799] duration [710ms], collections [1]/[1.3s], total
>>>> [710ms]/[7.2m], memory [2.9gb]->[2.8gb]/[9.9gb], all_pools {[young]
>>>> [128.6mb]->[3.5mb]/[133.1mb]}{[survivor] [16.6mb]->[11mb]/[16.6mb]}{[old]
>>>> [2.7gb]->[2.8gb]/[9.8gb]}
>>>>
>>>>
>>>> I have cluster of two elasticsearch nodes, with 10GB and 8GB of Heap.
>>>> Currently 60 shards in elasticsearch with around 2.5GB of data. What can
>>>> be
>>>> a probable reason for GC to take such a along time.
>>>>
>>>>
>>>> Thanks!
>>>> Shriyansh
>>>>
>>>> --
>>>> 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/6a92e329-a8ad-4d8e-96ac-5a9025c647cb%
>>>> 40googlegroups.com
>>>> <https://groups.google.com/d/msgid/elasticsearch/6a92e329-a8ad-4d8e-96ac-5a9025c647cb%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/bf0052a6-aba0-4b7f-b84f-051b5bd7fb44%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/elasticsearch/bf0052a6-aba0-4b7f-b84f-051b5bd7fb44%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/6aa4dbcc-52b6-4703-8ab6-aa9462738849%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Elasticsearch taking a long time for garbage collection
I have Heap Size on both the nodes.
Using openjdk 1.7.0_09-icedtea and elasticsearch : "1.2.2".
Thanks!
Shriyansh
On Thursday, December 18, 2014 11:50:32 PM UTC-8, Mark Walkom wrote:
>
> You should really have heap the size on both nodes.
>
> What ES and java versions are you on?
>
> On 18 December 2014 at 19:54, shriyansh jain > wrote:
>>
>> Hi All,
>>
>> I am seeing some warning message in elasticsearh log files which are
>> taking pretty long time for garbage collection.
>>
>> [2014-12-17 10:12:23,789][INFO ][monitor.jvm ] [Node1]
>> [gc][young][145219][4796] duration [901ms], collections [1]/[1.5s], total
>> [901ms]/[7.1m], memory [7.2gb]->[7.2gb]/[9.9gb], all_pools {[young]
>> [104.7mb]->[518.1kb]/[133.1mb]}{[survivor]
>> [8.3mb]->[12.6mb]/[16.6mb]}{[old] [7.1gb]->[7.2gb]/[9.8gb]}
>> [2014-12-17 10:12:29,172][WARN ][monitor.jvm ] [Node1]
>> [gc][young][145220][4797] duration [4.1s], collections [1]/[5s], total
>> [4.1s]/[7.2m], memory [7.2gb]->[7.4gb]/[9.9gb], all_pools {[young]
>> [518.1kb]->[109.4mb]/[133.1mb]}{[survivor]
>> [12.6mb]->[16.6mb]/[16.6mb]}{[old] [7.2gb]->[7.3gb]/[9.8gb]}
>> [2014-12-17 10:12:33,188][INFO ][monitor.jvm ] [Node1]
>> [gc][young][145224][4798] duration [791ms], collections [1]/[1s], total
>> [791ms]/[7.2m], memory [8.9gb]->[8.8gb]/[9.9gb], all_pools {[young]
>> [130.2mb]->[2kb]/[133.1mb]}{[survivor] [16.6mb]->[16.6mb]/[16.6mb]}{[old]
>> [8.7gb]->[8.8gb]/[9.8gb]}
>> [2014-12-17 10:13:18,476][INFO ][monitor.jvm ] [Node1]
>> [gc][young][145268][4799] duration [710ms], collections [1]/[1.3s], total
>> [710ms]/[7.2m], memory [2.9gb]->[2.8gb]/[9.9gb], all_pools {[young]
>> [128.6mb]->[3.5mb]/[133.1mb]}{[survivor] [16.6mb]->[11mb]/[16.6mb]}{[old]
>> [2.7gb]->[2.8gb]/[9.8gb]}
>>
>>
>> I have cluster of two elasticsearch nodes, with 10GB and 8GB of Heap.
>> Currently 60 shards in elasticsearch with around 2.5GB of data. What can be
>> a probable reason for GC to take such a along time.
>>
>>
>> Thanks!
>> Shriyansh
>>
>> --
>> 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/6a92e329-a8ad-4d8e-96ac-5a9025c647cb%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/elasticsearch/6a92e329-a8ad-4d8e-96ac-5a9025c647cb%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/bf0052a6-aba0-4b7f-b84f-051b5bd7fb44%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Elasticsearch taking a long time for garbage collection
Hi All,
I am seeing some warning message in elasticsearh log files which are taking
pretty long time for garbage collection.
[2014-12-17 10:12:23,789][INFO ][monitor.jvm ] [Node1]
[gc][young][145219][4796] duration [901ms], collections [1]/[1.5s], total
[901ms]/[7.1m], memory [7.2gb]->[7.2gb]/[9.9gb], all_pools {[young]
[104.7mb]->[518.1kb]/[133.1mb]}{[survivor]
[8.3mb]->[12.6mb]/[16.6mb]}{[old] [7.1gb]->[7.2gb]/[9.8gb]}
[2014-12-17 10:12:29,172][WARN ][monitor.jvm ] [Node1]
[gc][young][145220][4797] duration [4.1s], collections [1]/[5s], total
[4.1s]/[7.2m], memory [7.2gb]->[7.4gb]/[9.9gb], all_pools {[young]
[518.1kb]->[109.4mb]/[133.1mb]}{[survivor]
[12.6mb]->[16.6mb]/[16.6mb]}{[old] [7.2gb]->[7.3gb]/[9.8gb]}
[2014-12-17 10:12:33,188][INFO ][monitor.jvm ] [Node1]
[gc][young][145224][4798] duration [791ms], collections [1]/[1s], total
[791ms]/[7.2m], memory [8.9gb]->[8.8gb]/[9.9gb], all_pools {[young]
[130.2mb]->[2kb]/[133.1mb]}{[survivor] [16.6mb]->[16.6mb]/[16.6mb]}{[old]
[8.7gb]->[8.8gb]/[9.8gb]}
[2014-12-17 10:13:18,476][INFO ][monitor.jvm ] [Node1]
[gc][young][145268][4799] duration [710ms], collections [1]/[1.3s], total
[710ms]/[7.2m], memory [2.9gb]->[2.8gb]/[9.9gb], all_pools {[young]
[128.6mb]->[3.5mb]/[133.1mb]}{[survivor] [16.6mb]->[11mb]/[16.6mb]}{[old]
[2.7gb]->[2.8gb]/[9.8gb]}
I have cluster of two elasticsearch nodes, with 10GB and 8GB of Heap.
Currently 60 shards in elasticsearch with around 2.5GB of data. What can be
a probable reason for GC to take such a along time.
Thanks!
Shriyansh
--
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/6a92e329-a8ad-4d8e-96ac-5a9025c647cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Kibana: Historam plotting false values in kibana
Hi, I am collecting system stats per 3 seconds using ELK stack. But while plotting the logs in kibana, I am noticing false values plotted frequently every second in kibana. Some vales are plotted every second. But the logs I am collecting are strictly every 3 seconds. I have attached the screenshot for the same. Has anybody faced the same problem before. What can be causing this.? I will be happy to provide any other information for the same. Thanks! Shriyansh -- 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/821fb795-5231-4b82-9f11-3f4c1db187e1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
kibana saved dashboard not showing up after closing the elasticsearch index
Hello, Are the kibana indexes associated with the elasticsearch indexes in any way. As I closed few elasticsearch indexes, all the kibana saved dashboards disappeared. Is there any way to bring back those indexes. Thanks! Shriyansh -- 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/33df444c-6cf6-4b81-9363-f0008d94bda7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: kibana saved dashboard not showing up after closing the elasticsearch index
Just figured out they are stored in kibana-int index.! Thanks! Shriyansh On Tuesday, November 25, 2014 1:12:20 PM UTC-8, shriyansh jain wrote: > > Hello, > > > > Are the kibana indexes associated with the elasticsearch indexes in any > way. As I closed few elasticsearch indexes, all the kibana saved dashboards > disappeared. > > > > Is there any way to bring back those dashboards. > > > > Thanks! > > Shriyansh > -- 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/00a79817-d750-480f-a06f-bc2ee5d127a6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
kibana saved dashboard not showing up after closing the elasticsearch index
Hello, Are the kibana indexes associated with the elasticsearch indexes in any way. As I closed few elasticsearch indexes, all the kibana saved dashboards disappeared. Is there any way to bring back those dashboards. Thanks! Shriyansh -- 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/11273d98-ddff-4fa0-9668-ca6e1c17ee41%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Error message in elasticsearch log file
Thank you Mark! On Monday, November 24, 2014 4:47:32 PM UTC-8, Mark Walkom wrote: > > You should be able to search for that string in kibana to find more info > about it. > > On 25 November 2014 at 11:04, shriyansh jain > wrote: > >> Thank you mark for your reply. What will be a good way to look at such >> documents. Any particular query or hints, that will help me to dig out such >> logs. >> >> Thanks! >> Shriyansh >> >> On Monday, November 24, 2014 3:50:01 PM UTC-8, Mark Walkom wrote: >>> >>> It means it cannot deal with the data that it has. >>> You'd have to look at the document and find where/what is generating >>> this. >>> >>> On 25 November 2014 at 09:44, shriyansh jain >>> wrote: >>> >>>> Hi, >>>> >>>> I have a setup of ELk stack and using KV filter in logstash to index >>>> logs. >>>> I am getting the following error in the elasticsearch log file. >>>> >>>> http://pastebin.com/TMNQqnqz >>>> >>>> What might be causing this. Any input will really help. >>>> >>>> >>>> Thanks! >>>> Shriyansh >>>> >>>> -- >>>> 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/3f7189f1-7137-49fa-9988-2f630de0c2d5% >>>> 40googlegroups.com >>>> <https://groups.google.com/d/msgid/elasticsearch/3f7189f1-7137-49fa-9988-2f630de0c2d5%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/a2be114d-7891-47b6-bad0-bd79e2ea9e84%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/a2be114d-7891-47b6-bad0-bd79e2ea9e84%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/70f49771-df5e-4724-ad91-68c937a4ee76%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Error message in elasticsearch log file
Thank you mark for your reply. What will be a good way to look at such documents. Any particular query or hints, that will help me to dig out such logs. Thanks! Shriyansh On Monday, November 24, 2014 3:50:01 PM UTC-8, Mark Walkom wrote: > > It means it cannot deal with the data that it has. > You'd have to look at the document and find where/what is generating this. > > On 25 November 2014 at 09:44, shriyansh jain > wrote: > >> Hi, >> >> I have a setup of ELk stack and using KV filter in logstash to index logs. >> I am getting the following error in the elasticsearch log file. >> >> http://pastebin.com/TMNQqnqz >> >> What might be causing this. Any input will really help. >> >> >> Thanks! >> Shriyansh >> >> -- >> 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/3f7189f1-7137-49fa-9988-2f630de0c2d5%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/3f7189f1-7137-49fa-9988-2f630de0c2d5%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/a2be114d-7891-47b6-bad0-bd79e2ea9e84%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Error message in elasticsearch log file
Hi, I have a setup of ELk stack and using KV filter in logstash to index logs. I am getting the following error in the elasticsearch log file. http://pastebin.com/TMNQqnqz What might be causing this. Any input will really help. Thanks! Shriyansh -- 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/3f7189f1-7137-49fa-9988-2f630de0c2d5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Getting Timeout Exceptions with Elasticsearch
will it need a restart to being that info effect.? Thank! Shriyansh On Wednesday, November 12, 2014 1:30:57 PM UTC-8, Mark Walkom wrote: > > You can add that in yourself. > > On 13 November 2014 08:26, shriyansh jain > wrote: > >> Thank you mark for pointing me out with the situation. As I am trying to >> delete the index I am getting timeouts for that. But you suggested me to >> increase discovery.zen.fd.ping_timeout to get rid of that. I am not able to >> see any such variable in elasticsearch.yml file. >> Can you please point me how to increase discovery.zen.fd.ping_timeout. >> >> Thanks! >> Shriyansh >> >> -- >> 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/db816351-88d2-4e18-9863-3e719f2af1ed%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/db816351-88d2-4e18-9863-3e719f2af1ed%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/a1b4fb14-a053-4c9b-ac5f-c6bb22fe3fdb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Getting Timeout Exceptions with Elasticsearch
Thanks! -- 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/b9bf42ad-f55f-4091-99c0-e34125eccaf0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Getting Timeout Exceptions with Elasticsearch
Thank you mark for pointing me out with the situation. As I am trying to delete the index I am getting timeouts for that. But you suggested me to increase discovery.zen.fd.ping_timeout to get rid of that. I am not able to see any such variable in elasticsearch.yml file. Can you please point me how to increase discovery.zen.fd.ping_timeout. Thanks! Shriyansh -- 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/db816351-88d2-4e18-9863-3e719f2af1ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Getting Timeout Exceptions with Elasticsearch
I am also getting Out of Memory exception now in the logs [2014-11-12 13:08:23,157][WARN ][netty.channel.DefaultChannelPipeline] An exception was thrown by a user handler while handling an exception event ([id: 0x40f3788c, /10.18.144.231:52924 => /10.18.144.229:9300] EXCEPTION: java.lang.OutOfMemoryError: Java heap space) java.lang.OutOfMemoryError: Java heap space what will be way out to get out of this situation.? Thanks! Shriyansh -- 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/de51ffc7-7d40-4ced-b37c-84ee68ca7d7c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Getting Timeout Exceptions with Elasticsearch
I have stopped collecting all the data from logstash( as I am using ELK stack), but it still I am getting pretty large GC's (as you mentioned). Can you please point me out what might be the reason for that.? Thank you for the suggestion and pointing me out the error, I appreciate it and will consider increasing the number of nodes of the cluster. Thanks! Shriyansh -- 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/8e005f9a-bb48-4a50-9c94-2c14861dad7d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Getting Timeout Exceptions with Elasticsearch
Hi Mark, The data is around id 150GB. The master node holds : 16 GB RAM with ES_HEAP_SIZE = 8GB The other node holds : 16 GB RAM with ES_HEAP_SIZE = 8 GB I will get the version updated with Oracle Java, will that solve the issue.? Thanks! Shriyansh -- 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/8fc2f714-2c1a-43d4-a67c-2b6869007712%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Getting Timeout Exceptions with Elasticsearch
Hi all,
I am getting timeout exceptions with elastic search while deleting an index
and while looking for logs in kibana its taking lot of time to load logs.
Following are the log details and setup info.
API Call for deleting an Index:
curl -XDELETE 'http://localhost:9200/logstash-2014.08.21'
{"error":"ProcessClusterEventTimeoutException[failed to process cluster
event (delete-index [logstash-2014.08.21]) within 30s]","status":503}
Logs from master node: (setup is cluster of 2 nodes)
http://pastebin.com/hUZEf26d
Logs from other node
http://pastebin.com/HxWppiYL
curl -XGET 'localhost:9200'
{
"status" : 200,
"name" : "Node1",
"version" : {
"number" : "1.2.2",
"build_hash" : "9902f08efc3ad14ce27882b991c4c56b920c9872",
"build_timestamp" : "2014-07-09T12:02:32Z",
"build_snapshot" : false,
"lucene_version" : "4.8"
},
"tagline" : "You Know, for Search"
}
curl -XGET 'http://localhost:9200/_cluster/health?pretty=true'
{
"cluster_name" : "x",
"status" : "green",
"timed_out" : false,
"number_of_nodes" : 2,
"number_of_data_nodes" : 2,
"active_primary_shards" : 270,
"active_shards" : 540,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 0
}
Java version on the system
java version "1.7.0_09-icedtea"
OpenJDK Runtime Environment (rhel-2.3.4.1.el6_3-x86_64)
OpenJDK 64-Bit Server VM (build 23.2-b09, mixed mode)
I am using HQ plugin to visualize the elasticsearch plugin, but that plugin
is taking lot of time to load the cluster info.
what might be causing the timeouts to happen. Any inputs will be greatly
appreciated.
please let me know if any other details are required.
Thanks!
Shriyansh
--
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/89298f22-ec17-49b2-a7fe-c6f110341146%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Error with Elasticsearch
Hi all, I have a setup of ELK stack, and I am experiencing following error with elasticsearch frequently, please suggest me how can I debug this. http://pastebin.com/9j4q1UVd http://pastebin.com/Wj1nXuTt Please let me know if you need any other information. Thanks, Shriyansh -- 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/3ce39fcb-8cfc-4041-bc22-d1a264d2f88b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Facing error and warning messages with ELK stack
which configuration's you will be interested to look at.? -Shriyansh On Friday, September 19, 2014 2:17:16 PM UTC-7, Mark Walkom wrote: > > It looks like networking issues, lots of connection reset/closed/timeout. > > It might help if you can out your configs into a pastebin too. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > On 20 September 2014 04:33, shriyansh jain > wrote: > >> I have a setup of ELK stack with redis as a broker and a cluster of 2 >> Elasticsearch Nodes. The stack was running good and suddenly I started >> facing the following error and warning messages at different levels of the >> stack. >> >> http://pastebin.com/eG7p0PCc >> >> If I restart the redis broker, Logstash and the Elasticsearch node >> showing error message, the stack comes back, with Redis-broker performing >> well, able to allocate memory but I have been seeing the same error >> messages for E.S and Logstash after the restart. Because of which the >> redis-broker start buffering the logs in memory and eventually goes out of >> memory as E.S and logstash stop indexing the data. >> I am trying out figure out what might be the possible cause of this, any >> help will be really appreciated. Please let me know if there is any >> confusion understanding the situation. >> >> Thank you, >> Shriyansh >> >> -- >> 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/99ac902f-c183-4700-9d32-9d23ea0d7c3c%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/99ac902f-c183-4700-9d32-9d23ea0d7c3c%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/ca66b25e-77ab-4339-820e-74e25f5e9e7e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Facing error and warning messages with ELK stack
Which configuration you will be interested to loo at.? -Shriyansh On Friday, September 19, 2014 2:17:16 PM UTC-7, Mark Walkom wrote: > > It looks like networking issues, lots of connection reset/closed/timeout. > > It might help if you can out your configs into a pastebin too. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > On 20 September 2014 04:33, shriyansh jain > wrote: > >> I have a setup of ELK stack with redis as a broker and a cluster of 2 >> Elasticsearch Nodes. The stack was running good and suddenly I started >> facing the following error and warning messages at different levels of the >> stack. >> >> http://pastebin.com/eG7p0PCc >> >> If I restart the redis broker, Logstash and the Elasticsearch node >> showing error message, the stack comes back, with Redis-broker performing >> well, able to allocate memory but I have been seeing the same error >> messages for E.S and Logstash after the restart. Because of which the >> redis-broker start buffering the logs in memory and eventually goes out of >> memory as E.S and logstash stop indexing the data. >> I am trying out figure out what might be the possible cause of this, any >> help will be really appreciated. Please let me know if there is any >> confusion understanding the situation. >> >> Thank you, >> Shriyansh >> >> -- >> 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/99ac902f-c183-4700-9d32-9d23ea0d7c3c%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/99ac902f-c183-4700-9d32-9d23ea0d7c3c%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/624cd024-cc69-4eba-8bf9-d05b21f8d41a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Facing error and warning messages with ELK stack
I have a setup of ELK stack with redis as a broker and a cluster of 2 Elasticsearch Nodes. The stack was running good and suddenly I started facing the following error and warning messages at different levels of the stack. http://pastebin.com/eG7p0PCc If I restart the redis broker, Logstash and the Elasticsearch node showing error message, the stack comes back, with Redis-broker performing well, able to allocate memory but I have been seeing the same error messages for E.S and Logstash after the restart. Because of which the redis-broker start buffering the logs in memory and eventually goes out of memory as E.S and logstash stop indexing the data. I am trying out figure out what might be the possible cause of this, any help will be really appreciated. Please let me know if there is any confusion understanding the situation. Thank you, Shriyansh -- 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/99ac902f-c183-4700-9d32-9d23ea0d7c3c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Received response for a request that has timed out Error
Thank you.! I got that working. On Tuesday, September 16, 2014 7:25:39 AM UTC-7, pawansharma2045 wrote: > > So you need to restart that node. > > On Tue, Sep 16, 2014 at 12:46 AM, shriyansh jain > wrote: > >> Hi, >> >> I am getting the following error in the elasticsearch log file. I have a >> cluster of 2 elasticsearch nodes, and have a setup of ELK stack with redis >> as a buffer. Everything was running fine but suddenly, logstash is not able >> to parse logs (not showing any error messages) and elasticsearch is giving >> the following error message. >> Can anybody guide me on what is this error message about. >> >> [2014-09-15 11:55:30,607][WARN ][transport] [Node1] >> Received response for a request that has timed out, sent [41307ms] ago, >> timed out [11307ms] ago, action [discovery/zen/fd/ping], node >> [[Node2][01qr5MvqQaGhGYgfAZE_IQ][sjain-centos6-3][inet[/10.12.10.235:9300]]], >> >> id [332] >> >> >> Any input is greatly appreciated. >> >> Thank you, >> Shriyansh >> >> -- >> 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/e9a04c4c-be87-4e5a-a2dd-3a76062e4ce1%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/e9a04c4c-be87-4e5a-a2dd-3a76062e4ce1%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/86c9b8e1-b62f-4e5e-9c69-dc43d392edc6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Received response for a request that has timed out Error
Hi, I am getting the following error in the elasticsearch log file. I have a cluster of 2 elasticsearch nodes, and have a setup of ELK stack with redis as a buffer. Everything was running fine but suddenly, logstash is not able to parse logs (not showing any error messages) and elasticsearch is giving the following error message. Can anybody guide me on what is this error message about. [2014-09-15 11:55:30,607][WARN ][transport] [Node1] Received response for a request that has timed out, sent [41307ms] ago, timed out [11307ms] ago, action [discovery/zen/fd/ping], node [[Node2][01qr5MvqQaGhGYgfAZE_IQ][sjain-centos6-3][inet[/10.12.10.235:9300]]], id [332] Any input is greatly appreciated. Thank you, Shriyansh -- 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/e9a04c4c-be87-4e5a-a2dd-3a76062e4ce1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Elasticsearch parse failure error
Hi, I am using ELK stack and have a cluster of 2 elasticsearch nodes. When I am querying Elasticsearch from kibana. I am getting the following log error message in the elasticsearch log file. http://pastebin.com/sD539SNZ I am not able to figure out what is causing the error to happen. Any input will greatly appreciated. Thank you. -Shriyansh -- 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/d7e6b8c4-dc56-4512-854b-081a5aaf88d0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Move Elasticsearch index's from /auto/abc to /auto/def
Thank you sir for your reply back. I appreciate it. Thank you. -Shriyansh On Thursday, September 11, 2014 1:07:46 PM UTC-7, Mark Walkom wrote: > > You should be able to just copy them across and then start ES with your > new path value, yes. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 12 September 2014 03:37, shriyansh jain > wrote: > >> Can someone help me out with this question.? Is there any ambiguity with >> the question.? >> >> Thank you. >> Shriyansh >> >> On Wednesday, September 10, 2014 6:30:30 PM UTC-7, shriyansh jain wrote: >>> >>> Hi, >>> >>> I need an advice on migrating all Elasticsearch indexes from one >>> partition to another partition. Currently, I am using cluster of 2 nodes >>> with Elasticsearch. >>> And both the nodes are pointing to the same partition, which is >>> /auto/abc. How can I point both the nodes to the partition /auto/def and >>> keep all the indexes as they were befrore. >>> Will copying all the index from /auto/abc to /auto/def and pointing both >>> the elasticsearch nodes data path to /auto/def work.? Or I will have to >>> make some other changes which might cause change to happen. >>> >>> Thank you, >>> Shriyash >>> >>> >>> >>> >>> -- >> 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/8d397708-3681-41bc-b422-97fd8a546c00%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/8d397708-3681-41bc-b422-97fd8a546c00%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/f6eb21b2-e379-4ffb-bfc2-8516d341e979%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Move Elasticsearch index's from /auto/abc to /auto/def
Can someone help me out with this question.? Is there any ambiguity with the question.? Thank you. Shriyansh On Wednesday, September 10, 2014 6:30:30 PM UTC-7, shriyansh jain wrote: > > Hi, > > I need an advice on migrating all Elasticsearch indexes from one partition > to another partition. Currently, I am using cluster of 2 nodes with > Elasticsearch. > And both the nodes are pointing to the same partition, which is /auto/abc. > How can I point both the nodes to the partition /auto/def and keep all the > indexes as they were befrore. > Will copying all the index from /auto/abc to /auto/def and pointing both > the elasticsearch nodes data path to /auto/def work.? Or I will have to > make some other changes which might cause change to happen. > > Thank you, > Shriyash > > > > > -- 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/8d397708-3681-41bc-b422-97fd8a546c00%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Move Elasticsearch index's from /auto/abc to /auto/def
Hi, I need an advice on migrating all Elasticsearch indexes from one partition to another partition. Currently, I am using cluster of 2 nodes with Elasticsearch. And both the nodes are pointing to the same partition, which is /auto/abc. How can I point both the nodes to the partition /auto/def and keep all the indexes as they were befrore. Will copying all the index from /auto/abc to /auto/def and pointing both the elasticsearch nodes data path to /auto/def work.? Or I will have to make some other changes which might cause change to happen. Thank you, Shriyash -- 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/1e9ddb09-eac2-462a-b682-165b7c35e055%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
elasticsearch dead but subsys locked
I have a cluster of 2 elasticsearch instance, when I restarted one of the nodes I am getting the error "elasticsearch dead but subsys locked" . What could be causing this.? I am getting the same error for both the nodes.? Thank you, Shriyansh -- 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/c67b91d7-c800-4639-a521-166fdae06657%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: elasticsearch dead but pid file exists
Yes, it was because of the logs being written to /var/log/elasticsearch. I created space in /var/log and the elasticsearch instance was able to restart successfully after that. Thank you very much for you advice. I really appreciate it. Thank you, Shriyansh On Tuesday, August 19, 2014 10:52:45 AM UTC-7, pawansharma2045 wrote: > > /var is 100% so you are getting this issue could you please create some > space in /var and try to start elasticsearch. > > your path.data in elasticsearch.yml inside /var > > Could you provide the full path of path.data. from elasticsearch.yml > > > On Tue, Aug 19, 2014 at 11:32 PM, shriyansh jain > wrote: > >> I am writing the data to /auto/foo, and after going into that directory >> and doing df -h it gives me >> >> >> FilesystemSize Used Avail Use% Mounted on >> /dev/sda3 24G 17G 5.8G 75% / >> tmpfs 7.8G 0 7.8G 0% /dev/shm >> /dev/sda1 97M 82M 9.9M 90% /boot >> /dev/sda6 2.0G 135M 1.8G 7% /tmp >> /dev/sda5 6.0G 5.7G 0 100% /var >> x >>16T 4.2T 11T 28% /auto/home.nas01 >> xx >> 127T 27T 101T 21% /auto/foo >> Thanks, >> Shriyansh >> >> >> >> On Tuesday, August 19, 2014 10:43:35 AM UTC-7, pawansharma2045 wrote: >> >>> it means that you have no space left on root directory. >>> >>> Can you tell me the output of df -h >>> >>> it is is 100% then you have to make some space >>> >>> >>> >>> On Tue, Aug 19, 2014 at 11:24 PM, shriyansh jain >>> wrote: >>> >>>> >>>> >>>> On Tuesday, August 19, 2014 10:37:48 AM UTC-7, shriyansh jain wrote: >>>> >>>>> The command is not giving me any output. Is there any other way to >>>>> find out the problem.? >>>>> >>>>> Thanks, >>>>> Shriyansh >>>>> >>>>> On Tuesday, August 19, 2014 10:33:43 AM UTC-7, pawansharma2045 wrote: >>>>> >>>>>> First grep the pid of existing elasticsearch using >>>>>> *netstat -ntlp | grep 9200 * >>>>>> kill that pid and start the elasticsearch service >>>>>> >>>>>> when i try to execute "sudo service elasticsearch restart". it throws >>>>>> an exception >>>>>> >>>>> >>>> IOException[No space left on device] >>>> java.io.IOException: No space left on device >>>> at java.io.FileOutputStream.writeBytes(Native Method) >>>> at java.io.FileOutputStream.write(FileOutputStream.java:305) >>>> at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java: >>>> 157) >>>> at org.elasticsearch.bootstrap.Elasticsearch.main( >>>> Elasticsearch.java:32) >>>> >>>> >>>>> >>>>>> >>>>>> On Tue, Aug 19, 2014 at 11:08 PM, shriyansh jain < >>>>>> shriyan...@gmail.com> wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> While trying to check the elasticsearch status, I am getting the >>>>>>> message >>>>>>> >>>>>>> elasticsearch dead but pid file exists. >>>>>>> >>>>>>> How can I restart my services.? >>>>>>> >>>>>>> Thank you, >>>>>>> Shriyansh >>>>>>> >>>>>>> -- >>>>>>> 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/b606f43b-c4a >>>>>>> f-4114-9419-88ebe0397616%40googlegroups.com >>>>>>> <https://groups.google.com/d/msgid/elasticsearch/b606f43b-c4af-4114-9419-88ebe0397616%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>> . >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>&
Re: elasticsearch dead but pid file exists
I am writing the data to /auto/foo, and after going into that directory and doing df -h it gives me FilesystemSize Used Avail Use% Mounted on /dev/sda3 24G 17G 5.8G 75% / tmpfs 7.8G 0 7.8G 0% /dev/shm /dev/sda1 97M 82M 9.9M 90% /boot /dev/sda6 2.0G 135M 1.8G 7% /tmp /dev/sda5 6.0G 5.7G 0 100% /var x 16T 4.2T 11T 28% /auto/home.nas01 xx 127T 27T 101T 21% /auto/foo Thanks, Shriyansh On Tuesday, August 19, 2014 10:43:35 AM UTC-7, pawansharma2045 wrote: > > it means that you have no space left on root directory. > > Can you tell me the output of df -h > > it is is 100% then you have to make some space > > > > On Tue, Aug 19, 2014 at 11:24 PM, shriyansh jain > wrote: > >> >> >> On Tuesday, August 19, 2014 10:37:48 AM UTC-7, shriyansh jain wrote: >> >>> The command is not giving me any output. Is there any other way to find >>> out the problem.? >>> >>> Thanks, >>> Shriyansh >>> >>> On Tuesday, August 19, 2014 10:33:43 AM UTC-7, pawansharma2045 wrote: >>> >>>> First grep the pid of existing elasticsearch using >>>> *netstat -ntlp | grep 9200 * >>>> kill that pid and start the elasticsearch service >>>> >>>> when i try to execute "sudo service elasticsearch restart". it throws >>>> an exception >>>> >>> >> IOException[No space left on device] >> java.io.IOException: No space left on device >> at java.io.FileOutputStream.writeBytes(Native Method) >> at java.io.FileOutputStream.write(FileOutputStream.java:305) >> at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:157) >> at >> org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:32) >> >> >>> >>>> >>>> On Tue, Aug 19, 2014 at 11:08 PM, shriyansh jain >>>> wrote: >>>> >>>>> Hi, >>>>> >>>>> While trying to check the elasticsearch status, I am getting the >>>>> message >>>>> >>>>> elasticsearch dead but pid file exists. >>>>> >>>>> How can I restart my services.? >>>>> >>>>> Thank you, >>>>> Shriyansh >>>>> >>>>> -- >>>>> 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/b606f43b-c4af-4114-9419-88ebe0397616% >>>>> 40googlegroups.com >>>>> <https://groups.google.com/d/msgid/elasticsearch/b606f43b-c4af-4114-9419-88ebe0397616%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/4cc2ab13-88b2-4faa-ad0a-f04fd392664a%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/4cc2ab13-88b2-4faa-ad0a-f04fd392664a%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/5a7aa72d-5131-4811-9a76-34f03417aa78%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: elasticsearch dead but pid file exists
On Tuesday, August 19, 2014 10:37:48 AM UTC-7, shriyansh jain wrote: > > The command is not giving me any output. Is there any other way to find > out the problem.? > > Thanks, > Shriyansh > > On Tuesday, August 19, 2014 10:33:43 AM UTC-7, pawansharma2045 wrote: >> >> First grep the pid of existing elasticsearch using >> *netstat -ntlp | grep 9200* >> kill that pid and start the elasticsearch service >> >> when i try to execute "sudo service elasticsearch restart". it throws an >> exception >> > IOException[No space left on device] java.io.IOException: No space left on device at java.io.FileOutputStream.writeBytes(Native Method) at java.io.FileOutputStream.write(FileOutputStream.java:305) at org.elasticsearch.bootstrap.Bootstrap.main(Bootstrap.java:157) at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:32) > >> >> On Tue, Aug 19, 2014 at 11:08 PM, shriyansh jain >> wrote: >> >>> Hi, >>> >>> While trying to check the elasticsearch status, I am getting the message >>> >>> elasticsearch dead but pid file exists. >>> >>> How can I restart my services.? >>> >>> Thank you, >>> Shriyansh >>> >>> -- >>> 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/b606f43b-c4af-4114-9419-88ebe0397616%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/elasticsearch/b606f43b-c4af-4114-9419-88ebe0397616%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/4cc2ab13-88b2-4faa-ad0a-f04fd392664a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: elasticsearch dead but pid file exists
The command is not giving me any output. Is there any other way to find out the problem.? Thanks, Shriyansh On Tuesday, August 19, 2014 10:33:43 AM UTC-7, pawansharma2045 wrote: > > First grep the pid of existing elasticsearch using > *netstat -ntlp | grep 9200* > kill that pid and start the elasticsearch service > > > > > On Tue, Aug 19, 2014 at 11:08 PM, shriyansh jain > wrote: > >> Hi, >> >> While trying to check the elasticsearch status, I am getting the message >> >> elasticsearch dead but pid file exists. >> >> How can I restart my services.? >> >> Thank you, >> Shriyansh >> >> -- >> 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/b606f43b-c4af-4114-9419-88ebe0397616%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/b606f43b-c4af-4114-9419-88ebe0397616%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/941757f7-1186-4eb4-a61c-276b12a90be3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
elasticsearch dead but pid file exists
Hi, While trying to check the elasticsearch status, I am getting the message elasticsearch dead but pid file exists. How can I restart my services.? Thank you, Shriyansh -- 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/b606f43b-c4af-4114-9419-88ebe0397616%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to safely migrate from one mount to another mount in Elasticsearch to store the data
I would like to know one more thing, what would be steps if I want to copy the data from /auto/share to /auto/foo for a particular node.? Thanks, Shriyansh On Monday, August 18, 2014 3:26:39 PM UTC-7, Mark Walkom wrote: > > Do you want to copy the existing data in /auto/share to /auto/foo, or > start with no data? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 19 August 2014 08:23, shriyansh jain > wrote: > >> Hi, >> >> I have a Elasticsearch Cluster of 2 nodes. I have configured them to >> store data at the location which is /auto/share. I want to point one of the >> two nodes in the cluster to some other location to store the data say >> /auto/foo. >> What would be the best way of achieving the above task without loosing >> any data.? And is it possible to do that without loosing any data.? >> >> Thank you, >> Shriyansh >> >> -- >> 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/415f8d41-4fa9-4f6d-86b9-41b2059ab67f%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/415f8d41-4fa9-4f6d-86b9-41b2059ab67f%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/c427919f-b8f1-4286-9302-0869d2aa7b5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to safely migrate from one mount to another mount in Elasticsearch to store the data
Thank you for helping me out. I really appreciate it. Regards, Shriyansh On Monday, August 18, 2014 7:23:50 PM UTC-7, Mark Walkom wrote: > > Apart from replica's, that's really outside the scope of what ES provides. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 19 August 2014 12:12, shriyansh jain > wrote: > >> I got your point sir, but if my entire /auto/share goes down. Then I wont >> have any chance to recover the data in /auto/share. >> Is there any other way to recover the data.? >> >> Thanks, >> Shriyansh >> >> On Monday, August 18, 2014 7:03:34 PM UTC-7, Mark Walkom wrote: >>> >>> This is why you have replicas, they give you redundancy at a higher >>> level that the filesystem, >>> If you are still concerned then you should add another node and increase >>> your replicas. >>> >>> Playing around on the FS to create replicas is only extra management >>> overhead and likely to end up causing more problems than it's worth. >>> >>> Regards, >>> Mark Walkom >>> >>> Infrastructure Engineer >>> Campaign Monitor >>> email: ma...@campaignmonitor.com >>> web: www.campaignmonitor.com >>> >>> >>> On 19 August 2014 11:59, shriyansh jain wrote: >>> >>>> Just to make sure if /auto/share goes down I have data in /auto/foo. >>>> >>>> Thanks, >>>> Shriyansh >>>> >>>> On Monday, August 18, 2014 6:55:59 PM UTC-7, Mark Walkom wrote: >>>>> >>>>> Why do you want to do this if you are worried about data loss? >>>>> >>>>> Regards, >>>>> Mark Walkom >>>>> >>>>> Infrastructure Engineer >>>>> Campaign Monitor >>>>> email: ma...@campaignmonitor.com >>>>> web: www.campaignmonitor.com >>>>> >>>>> >>>>> On 19 August 2014 11:50, shriyansh jain wrote: >>>>> >>>>>> As you mentioned the node will not lose the data completely, is there >>>>>> any possibility that it will lose some data.? >>>>>> >>>>>> Thank you, >>>>>> Shriyansh >>>>>> >>>>>> On Monday, August 18, 2014 4:17:54 PM UTC-7, Mark Walkom wrote: >>>>>>> >>>>>>> If you point the instance to a new data location then yes, it will >>>>>>> startup with no data, but it won't lose the data completely as it will >>>>>>> still be located in your original /auto/share directory. >>>>>>> >>>>>>> However given you have replicas set what will happen is when the >>>>>>> node starts up pointing to the new location it will simply start to >>>>>>> copy >>>>>>> the data from the other node so that you fulfil your replica >>>>>>> requirements. >>>>>>> >>>>>>> Regards, >>>>>>> Mark Walkom >>>>>>> >>>>>>> Infrastructure Engineer >>>>>>> Campaign Monitor >>>>>>> email: ma...@campaignmonitor.com >>>>>>> web: www.campaignmonitor.com >>>>>>> >>>>>>> >>>>>>> On 19 August 2014 08:58, shriyansh jain >>>>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> Yes, I have set *index.number_of_replicas: 1*. If I just point one >>>>>>>> of the 2 nodes to some other location, wont it lose the data stored by >>>>>>>> that >>>>>>>> node.? >>>>>>>> >>>>>>>> >>>>>>>> Thank you, >>>>>>>> Shriyansh >>>>>>>> >>>>>>>> On Monday, August 18, 2014 3:34:48 PM UTC-7, Mark Walkom wrote: >>>>>>>>> >>>>>>>>> If you want no data in /auto/foo then just create the directory, >>>>>>>>> give it the right permissions and then update the config to point to >>>>>>>>> it. >>>>>>>>> It's the same process you did for /auto/share. >>>>>>>>> >
Re: How to safely migrate from one mount to another mount in Elasticsearch to store the data
I got your point sir, but if my entire /auto/share goes down. Then I wont have any chance to recover the data in /auto/share. Is there any other way to recover the data.? Thanks, Shriyansh On Monday, August 18, 2014 7:03:34 PM UTC-7, Mark Walkom wrote: > > This is why you have replicas, they give you redundancy at a higher level > that the filesystem, > If you are still concerned then you should add another node and increase > your replicas. > > Playing around on the FS to create replicas is only extra management > overhead and likely to end up causing more problems than it's worth. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 19 August 2014 11:59, shriyansh jain > wrote: > >> Just to make sure if /auto/share goes down I have data in /auto/foo. >> >> Thanks, >> Shriyansh >> >> On Monday, August 18, 2014 6:55:59 PM UTC-7, Mark Walkom wrote: >>> >>> Why do you want to do this if you are worried about data loss? >>> >>> Regards, >>> Mark Walkom >>> >>> Infrastructure Engineer >>> Campaign Monitor >>> email: ma...@campaignmonitor.com >>> web: www.campaignmonitor.com >>> >>> >>> On 19 August 2014 11:50, shriyansh jain wrote: >>> >>>> As you mentioned the node will not lose the data completely, is there >>>> any possibility that it will lose some data.? >>>> >>>> Thank you, >>>> Shriyansh >>>> >>>> On Monday, August 18, 2014 4:17:54 PM UTC-7, Mark Walkom wrote: >>>>> >>>>> If you point the instance to a new data location then yes, it will >>>>> startup with no data, but it won't lose the data completely as it will >>>>> still be located in your original /auto/share directory. >>>>> >>>>> However given you have replicas set what will happen is when the node >>>>> starts up pointing to the new location it will simply start to copy the >>>>> data from the other node so that you fulfil your replica requirements. >>>>> >>>>> Regards, >>>>> Mark Walkom >>>>> >>>>> Infrastructure Engineer >>>>> Campaign Monitor >>>>> email: ma...@campaignmonitor.com >>>>> web: www.campaignmonitor.com >>>>> >>>>> >>>>> On 19 August 2014 08:58, shriyansh jain wrote: >>>>> >>>>>> >>>>>> Yes, I have set *index.number_of_replicas: 1*. If I just point one >>>>>> of the 2 nodes to some other location, wont it lose the data stored by >>>>>> that >>>>>> node.? >>>>>> >>>>>> >>>>>> Thank you, >>>>>> Shriyansh >>>>>> >>>>>> On Monday, August 18, 2014 3:34:48 PM UTC-7, Mark Walkom wrote: >>>>>>> >>>>>>> If you want no data in /auto/foo then just create the directory, >>>>>>> give it the right permissions and then update the config to point to it. >>>>>>> It's the same process you did for /auto/share. >>>>>>> >>>>>>> >>>>>>> Do you have replicas set on your indexes? >>>>>>> >>>>>>> Regards, >>>>>>> Mark Walkom >>>>>>> >>>>>>> Infrastructure Engineer >>>>>>> Campaign Monitor >>>>>>> email: ma...@campaignmonitor.com >>>>>>> web: www.campaignmonitor.com >>>>>>> >>>>>>> >>>>>>> On 19 August 2014 08:32, shriyansh jain >>>>>>> wrote: >>>>>>> >>>>>>>> I would prefer with no data in /auto/foo.? But would like to go >>>>>>>> with way, which is efficient and more reliable. >>>>>>>> >>>>>>>> >>>>>>>> Thank you, >>>>>>>> Shriyansh >>>>>>>> >>>>>>>> On Monday, August 18, 2014 3:26:39 PM UTC-7, Mark Walkom wrote: >>>>>>>>> >>>>>>>>> Do you want to copy the existing data in /auto/share to /auto/foo, >>>>>>>>> or start with no data? >>>
Re: How to safely migrate from one mount to another mount in Elasticsearch to store the data
To make sure if /auto/share goes down, I have data in /auto/foo. And I am short of space on /auto/share. Mainly bcz of these 2 reasons. Thanks, Shriyansh On Monday, August 18, 2014 6:55:59 PM UTC-7, Mark Walkom wrote: > > Why do you want to do this if you are worried about data loss? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 19 August 2014 11:50, shriyansh jain > wrote: > >> As you mentioned the node will not lose the data completely, is there any >> possibility that it will lose some data.? >> >> Thank you, >> Shriyansh >> >> On Monday, August 18, 2014 4:17:54 PM UTC-7, Mark Walkom wrote: >>> >>> If you point the instance to a new data location then yes, it will >>> startup with no data, but it won't lose the data completely as it will >>> still be located in your original /auto/share directory. >>> >>> However given you have replicas set what will happen is when the node >>> starts up pointing to the new location it will simply start to copy the >>> data from the other node so that you fulfil your replica requirements. >>> >>> Regards, >>> Mark Walkom >>> >>> Infrastructure Engineer >>> Campaign Monitor >>> email: ma...@campaignmonitor.com >>> web: www.campaignmonitor.com >>> >>> >>> On 19 August 2014 08:58, shriyansh jain wrote: >>> >>>> >>>> Yes, I have set *index.number_of_replicas: 1*. If I just point one of >>>> the 2 nodes to some other location, wont it lose the data stored by that >>>> node.? >>>> >>>> >>>> Thank you, >>>> Shriyansh >>>> >>>> On Monday, August 18, 2014 3:34:48 PM UTC-7, Mark Walkom wrote: >>>>> >>>>> If you want no data in /auto/foo then just create the directory, give >>>>> it the right permissions and then update the config to point to it. >>>>> It's the same process you did for /auto/share. >>>>> >>>>> >>>>> Do you have replicas set on your indexes? >>>>> >>>>> Regards, >>>>> Mark Walkom >>>>> >>>>> Infrastructure Engineer >>>>> Campaign Monitor >>>>> email: ma...@campaignmonitor.com >>>>> web: www.campaignmonitor.com >>>>> >>>>> >>>>> On 19 August 2014 08:32, shriyansh jain wrote: >>>>> >>>>>> I would prefer with no data in /auto/foo.? But would like to go with >>>>>> way, which is efficient and more reliable. >>>>>> >>>>>> >>>>>> Thank you, >>>>>> Shriyansh >>>>>> >>>>>> On Monday, August 18, 2014 3:26:39 PM UTC-7, Mark Walkom wrote: >>>>>>> >>>>>>> Do you want to copy the existing data in /auto/share to /auto/foo, >>>>>>> or start with no data? >>>>>>> >>>>>>> Regards, >>>>>>> Mark Walkom >>>>>>> >>>>>>> Infrastructure Engineer >>>>>>> Campaign Monitor >>>>>>> email: ma...@campaignmonitor.com >>>>>>> web: www.campaignmonitor.com >>>>>>> >>>>>>> >>>>>>> On 19 August 2014 08:23, shriyansh jain >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I have a Elasticsearch Cluster of 2 nodes. I have configured them >>>>>>>> to store data at the location which is /auto/share. I want to point >>>>>>>> one of >>>>>>>> the two nodes in the cluster to some other location to store the data >>>>>>>> say >>>>>>>> /auto/foo. >>>>>>>> What would be the best way of achieving the above task without >>>>>>>> loosing any data.? And is it possible to do that without loosing any >>>>>>>> data.? >>>>>>>> >>>>>>>> Thank you, >>>>>>>> Shriyansh >>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are su
Re: How to safely migrate from one mount to another mount in Elasticsearch to store the data
Just to make sure if /auto/share goes down I have data in /auto/foo. Thanks, Shriyansh On Monday, August 18, 2014 6:55:59 PM UTC-7, Mark Walkom wrote: > > Why do you want to do this if you are worried about data loss? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 19 August 2014 11:50, shriyansh jain > wrote: > >> As you mentioned the node will not lose the data completely, is there any >> possibility that it will lose some data.? >> >> Thank you, >> Shriyansh >> >> On Monday, August 18, 2014 4:17:54 PM UTC-7, Mark Walkom wrote: >>> >>> If you point the instance to a new data location then yes, it will >>> startup with no data, but it won't lose the data completely as it will >>> still be located in your original /auto/share directory. >>> >>> However given you have replicas set what will happen is when the node >>> starts up pointing to the new location it will simply start to copy the >>> data from the other node so that you fulfil your replica requirements. >>> >>> Regards, >>> Mark Walkom >>> >>> Infrastructure Engineer >>> Campaign Monitor >>> email: ma...@campaignmonitor.com >>> web: www.campaignmonitor.com >>> >>> >>> On 19 August 2014 08:58, shriyansh jain wrote: >>> >>>> >>>> Yes, I have set *index.number_of_replicas: 1*. If I just point one of >>>> the 2 nodes to some other location, wont it lose the data stored by that >>>> node.? >>>> >>>> >>>> Thank you, >>>> Shriyansh >>>> >>>> On Monday, August 18, 2014 3:34:48 PM UTC-7, Mark Walkom wrote: >>>>> >>>>> If you want no data in /auto/foo then just create the directory, give >>>>> it the right permissions and then update the config to point to it. >>>>> It's the same process you did for /auto/share. >>>>> >>>>> >>>>> Do you have replicas set on your indexes? >>>>> >>>>> Regards, >>>>> Mark Walkom >>>>> >>>>> Infrastructure Engineer >>>>> Campaign Monitor >>>>> email: ma...@campaignmonitor.com >>>>> web: www.campaignmonitor.com >>>>> >>>>> >>>>> On 19 August 2014 08:32, shriyansh jain wrote: >>>>> >>>>>> I would prefer with no data in /auto/foo.? But would like to go with >>>>>> way, which is efficient and more reliable. >>>>>> >>>>>> >>>>>> Thank you, >>>>>> Shriyansh >>>>>> >>>>>> On Monday, August 18, 2014 3:26:39 PM UTC-7, Mark Walkom wrote: >>>>>>> >>>>>>> Do you want to copy the existing data in /auto/share to /auto/foo, >>>>>>> or start with no data? >>>>>>> >>>>>>> Regards, >>>>>>> Mark Walkom >>>>>>> >>>>>>> Infrastructure Engineer >>>>>>> Campaign Monitor >>>>>>> email: ma...@campaignmonitor.com >>>>>>> web: www.campaignmonitor.com >>>>>>> >>>>>>> >>>>>>> On 19 August 2014 08:23, shriyansh jain >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I have a Elasticsearch Cluster of 2 nodes. I have configured them >>>>>>>> to store data at the location which is /auto/share. I want to point >>>>>>>> one of >>>>>>>> the two nodes in the cluster to some other location to store the data >>>>>>>> say >>>>>>>> /auto/foo. >>>>>>>> What would be the best way of achieving the above task without >>>>>>>> loosing any data.? And is it possible to do that without loosing any >>>>>>>> data.? >>>>>>>> >>>>>>>> Thank you, >>>>>>>> Shriyansh >>>>>>>> >>>>>>>> -- >>>>>>>> You received this message because you are subscribed to the Google >>>>>>>> Groups "
Re: How to safely migrate from one mount to another mount in Elasticsearch to store the data
As you mentioned the node will not lose the data completely, is there any possibility that it will lose some data.? Thank you, Shriyansh On Monday, August 18, 2014 4:17:54 PM UTC-7, Mark Walkom wrote: > > If you point the instance to a new data location then yes, it will startup > with no data, but it won't lose the data completely as it will still be > located in your original /auto/share directory. > > However given you have replicas set what will happen is when the node > starts up pointing to the new location it will simply start to copy the > data from the other node so that you fulfil your replica requirements. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 19 August 2014 08:58, shriyansh jain > wrote: > >> >> Yes, I have set *index.number_of_replicas: 1*. If I just point one of >> the 2 nodes to some other location, wont it lose the data stored by that >> node.? >> >> >> Thank you, >> Shriyansh >> >> On Monday, August 18, 2014 3:34:48 PM UTC-7, Mark Walkom wrote: >>> >>> If you want no data in /auto/foo then just create the directory, give it >>> the right permissions and then update the config to point to it. >>> It's the same process you did for /auto/share. >>> >>> >>> Do you have replicas set on your indexes? >>> >>> Regards, >>> Mark Walkom >>> >>> Infrastructure Engineer >>> Campaign Monitor >>> email: ma...@campaignmonitor.com >>> web: www.campaignmonitor.com >>> >>> >>> On 19 August 2014 08:32, shriyansh jain wrote: >>> >>>> I would prefer with no data in /auto/foo.? But would like to go with >>>> way, which is efficient and more reliable. >>>> >>>> >>>> Thank you, >>>> Shriyansh >>>> >>>> On Monday, August 18, 2014 3:26:39 PM UTC-7, Mark Walkom wrote: >>>>> >>>>> Do you want to copy the existing data in /auto/share to /auto/foo, or >>>>> start with no data? >>>>> >>>>> Regards, >>>>> Mark Walkom >>>>> >>>>> Infrastructure Engineer >>>>> Campaign Monitor >>>>> email: ma...@campaignmonitor.com >>>>> web: www.campaignmonitor.com >>>>> >>>>> >>>>> On 19 August 2014 08:23, shriyansh jain wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I have a Elasticsearch Cluster of 2 nodes. I have configured them to >>>>>> store data at the location which is /auto/share. I want to point one of >>>>>> the >>>>>> two nodes in the cluster to some other location to store the data say >>>>>> /auto/foo. >>>>>> What would be the best way of achieving the above task without >>>>>> loosing any data.? And is it possible to do that without loosing any >>>>>> data.? >>>>>> >>>>>> Thank you, >>>>>> Shriyansh >>>>>> >>>>>> -- >>>>>> 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/415f8d41-4fa9-4f6d-86b9-41b2059ab67f%40goo >>>>>> glegroups.com >>>>>> <https://groups.google.com/d/msgid/elasticsearch/415f8d41-4fa9-4f6d-86b9-41b2059ab67f%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/2dbadd5f-5e23-4e6b-8cf5-9a8bb31c4328% >>>> 40googlegroups.com >>>&g
Re: How to safely migrate from one mount to another mount in Elasticsearch to store the data
Yes, I have set *index.number_of_replicas: 1*. If I just point one of the 2 nodes to some other location, wont it lose the data stored by that node.? Thank you, Shriyansh On Monday, August 18, 2014 3:34:48 PM UTC-7, Mark Walkom wrote: > > If you want no data in /auto/foo then just create the directory, give it > the right permissions and then update the config to point to it. > It's the same process you did for /auto/share. > > > Do you have replicas set on your indexes? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 19 August 2014 08:32, shriyansh jain > wrote: > >> I would prefer with no data in /auto/foo.? But would like to go with way, >> which is efficient and more reliable. >> >> >> Thank you, >> Shriyansh >> >> On Monday, August 18, 2014 3:26:39 PM UTC-7, Mark Walkom wrote: >>> >>> Do you want to copy the existing data in /auto/share to /auto/foo, or >>> start with no data? >>> >>> Regards, >>> Mark Walkom >>> >>> Infrastructure Engineer >>> Campaign Monitor >>> email: ma...@campaignmonitor.com >>> web: www.campaignmonitor.com >>> >>> >>> On 19 August 2014 08:23, shriyansh jain wrote: >>> >>>> Hi, >>>> >>>> I have a Elasticsearch Cluster of 2 nodes. I have configured them to >>>> store data at the location which is /auto/share. I want to point one of >>>> the >>>> two nodes in the cluster to some other location to store the data say >>>> /auto/foo. >>>> What would be the best way of achieving the above task without loosing >>>> any data.? And is it possible to do that without loosing any data.? >>>> >>>> Thank you, >>>> Shriyansh >>>> >>>> -- >>>> 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/415f8d41-4fa9-4f6d-86b9-41b2059ab67f% >>>> 40googlegroups.com >>>> <https://groups.google.com/d/msgid/elasticsearch/415f8d41-4fa9-4f6d-86b9-41b2059ab67f%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/2dbadd5f-5e23-4e6b-8cf5-9a8bb31c4328%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/2dbadd5f-5e23-4e6b-8cf5-9a8bb31c4328%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/01d32d9d-3041-4fb7-babe-0e73e3908b31%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to safely migrate from one mount to another mount in Elasticsearch to store the data
Yes, I have set *index.number_of_replicas: 1*. If I just point one of the 2 nodes to some other location, wont it loose the data stored by that node.? Thank you, Shriyansh On Monday, August 18, 2014 3:34:48 PM UTC-7, Mark Walkom wrote: > > If you want no data in /auto/foo then just create the directory, give it > the right permissions and then update the config to point to it. > It's the same process you did for /auto/share. > > > Do you have replicas set on your indexes? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 19 August 2014 08:32, shriyansh jain > wrote: > >> I would prefer with no data in /auto/foo.? But would like to go with way, >> which is efficient and more reliable. >> >> >> Thank you, >> Shriyansh >> >> On Monday, August 18, 2014 3:26:39 PM UTC-7, Mark Walkom wrote: >>> >>> Do you want to copy the existing data in /auto/share to /auto/foo, or >>> start with no data? >>> >>> Regards, >>> Mark Walkom >>> >>> Infrastructure Engineer >>> Campaign Monitor >>> email: ma...@campaignmonitor.com >>> web: www.campaignmonitor.com >>> >>> >>> On 19 August 2014 08:23, shriyansh jain wrote: >>> >>>> Hi, >>>> >>>> I have a Elasticsearch Cluster of 2 nodes. I have configured them to >>>> store data at the location which is /auto/share. I want to point one of >>>> the >>>> two nodes in the cluster to some other location to store the data say >>>> /auto/foo. >>>> What would be the best way of achieving the above task without loosing >>>> any data.? And is it possible to do that without loosing any data.? >>>> >>>> Thank you, >>>> Shriyansh >>>> >>>> -- >>>> 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/415f8d41-4fa9-4f6d-86b9-41b2059ab67f% >>>> 40googlegroups.com >>>> <https://groups.google.com/d/msgid/elasticsearch/415f8d41-4fa9-4f6d-86b9-41b2059ab67f%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/2dbadd5f-5e23-4e6b-8cf5-9a8bb31c4328%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/2dbadd5f-5e23-4e6b-8cf5-9a8bb31c4328%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/eb602b14-4d3e-430c-93d8-935da98af66a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to safely migrate from one mount to another mount in Elasticsearch to store the data
I would prefer with no data in /auto/foo.? But would like to go with way, which is efficient and more reliable. Thank you, Shriyansh On Monday, August 18, 2014 3:26:39 PM UTC-7, Mark Walkom wrote: > > Do you want to copy the existing data in /auto/share to /auto/foo, or > start with no data? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 19 August 2014 08:23, shriyansh jain > wrote: > >> Hi, >> >> I have a Elasticsearch Cluster of 2 nodes. I have configured them to >> store data at the location which is /auto/share. I want to point one of the >> two nodes in the cluster to some other location to store the data say >> /auto/foo. >> What would be the best way of achieving the above task without loosing >> any data.? And is it possible to do that without loosing any data.? >> >> Thank you, >> Shriyansh >> >> -- >> 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/415f8d41-4fa9-4f6d-86b9-41b2059ab67f%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/415f8d41-4fa9-4f6d-86b9-41b2059ab67f%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/2dbadd5f-5e23-4e6b-8cf5-9a8bb31c4328%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
How to safely migrate from one mount to another mount in Elasticsearch to store the data
Hi, I have a Elasticsearch Cluster of 2 nodes. I have configured them to store data at the location which is /auto/share. I want to point one of the two nodes in the cluster to some other location to store the data say /auto/foo. What would be the best way of achieving the above task without loosing any data.? And is it possible to do that without loosing any data.? Thank you, Shriyansh -- 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/415f8d41-4fa9-4f6d-86b9-41b2059ab67f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Problem Plotting Zero values with Kibana
Hi, Thank you for your reply back. I am aware of the zero fill settings in kibana. But my problem is I have some log values which are zero at particular timestamp and don't have any values at some timestamp. So if I select zero fill it plots zero for both the actual zero values and the values where there are gaps. I want to plot the values where I am actually getting zero and plot nothing where I have gaps. Is that possible .? Thank you, Shriyansh On Monday, August 11, 2014 4:54:17 PM UTC-7, Mark Walkom wrote: > > This was just answered on your post to the LS list, but you can set zero > fill under panel settings. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 12 August 2014 09:50, shriyansh jain > wrote: > >> Hi, >> >> I am using a ELK stack for log processing. One of the problem I am facing >> with kibana is that, I have some fields in my log whose values is zero, and >> zero is considered as legitimate value in my case. But when I plot those >> fields in kibana, if zero field is enabled it plots zero in the graph >> including the gaps. But I dont want to plot the zero values in the gaps, I >> just want to plot my actual log values in the graph, but kibana doent seem >> to be able to do that. Am I going anywhere wrong or is kibana really not >> able to visualize that.? >> >> >> Thank you, >> Shriyansh >> >> -- >> 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/cd54f92f-737a-4af1-b6cb-5b2f00a75fc2%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/cd54f92f-737a-4af1-b6cb-5b2f00a75fc2%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/c654db5f-10f5-4c8c-9389-8ff847cf8914%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Problem Plotting Zero values with Kibana
Hi, I am using a ELK stack for log processing. One of the problem I am facing with kibana is that, I have some fields in my log whose values is zero, and zero is considered as legitimate value in my case. But when I plot those fields in kibana, if zero field is enabled it plots zero in the graph including the gaps. But I dont want to plot the zero values in the gaps, I just want to plot my actual log values in the graph, but kibana doent seem to be able to do that. Am I going anywhere wrong or is kibana really not able to visualize that.? Thank you, Shriyansh -- 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/cd54f92f-737a-4af1-b6cb-5b2f00a75fc2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Issue Mapping Elasticsearch
Hey I started the conversation on logstash list as suggested by you. I
tried testing to telnet from the Logstash central server to ES server.
Following is the output I am getting.
$ telnet 10.12.7.2 9200
Trying 10.12.7.2...
Connected to (10.12.7.2).
Escape character is '^]'.
Here is the link to the discussion,
https://groups.google.com/forum/#!topic/logstash-users/9IPSEtCwrNc
Any input will be greatly appreciated.
-Shriyansh
On Tuesday, July 15, 2014 3:22:43 PM UTC-7, Mark Walkom wrote:
>
> You should probably start this conversation on the logstash list.
> However if you are using the http output then you don't need cluster or
> node_name. It'd be worth testing that you can telnet from your LS host to
> your ES host on port 9200, and also try enabling verbose logging in LS with
> -v.
>
> Regards,
> Mark Walkom
>
> Infrastructure Engineer
> Campaign Monitor
> email: ma...@campaignmonitor.com
> web: www.campaignmonitor.com
>
>
> On 16 July 2014 07:15, Voc Austin > wrote:
>
>> Hey,
>>
>> I am using ELK stack for log processing. Logstash 1.4.2 (Single Instance)
>> and Elasticsearch 1.2.2(Cluster of 2 nodes), and redis as broker between
>> logstash and elasticsearch.
>>
>> I am able to parse my logs using Logstash, get the parsed document in
>> Redis. But not able to get the documents inside Elasticsearch.
>>
>> The following is my Central logstash server configuration file.
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *input { redis {host => "xx.xx.xx.xx"type =>
>> "redis-input"data_type => "list"key => "logstash"
>> threads => 5 }redis {host => "xx.xx.xx.xx"type =>
>> "redis-input"data_type => "list"key => "logstash"
>> threads => 5 }} filter { date { match =>
>> ["timestamp_nsstats",%{YEAR}-%{MONTHNUM}-%{MONTHDAY}[,]%{HOUR}:?%{MINUTE}(?::?%{SECOND})?"]
>>
>> } } output {stdout { } elasticsearch
>> {cluster => "logstash"host =>
>> "xx.xx.xx.xx"protocol => "http"node_name =>
>> "Node1" index => "logstash-%{+.MM.dd}"}}*
>> The following is the health of Elasticsearch Instances.
>>
>>
>>1. {
>>
>>2. "cluster_name": "logstash",
>>
>>
>>3. "status": "green",
>>
>>
>>4. "timed_out": false,
>>
>>
>>5. "number_of_nodes": 2,
>>
>>
>>6. "number_of_data_nodes": 2,
>>
>>
>>7. "active_primary_shards": 3,
>>
>>
>>8. "active_shards": 6,
>>
>>
>>9. "relocating_shards": 0,
>>
>>
>>10. "initializing_shards": 0,
>>
>>
>>11. "unassigned_shards": 0
>>
>>12. }
>>
>>
>>
>> I am not able to find out the reason, that is causing logstash being not
>> able to reach elasticsearch. Do I need to make any changes in configuration
>> file, which might make logstash aware of the elasticsearch server.
>>
>>
>>
>> Please let me know what you think, that might be causing the issue. If you
>> need any other information please let me know.
>>
>>
>>
>> Thank you
>>
>> --
>> 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/CAKKFHoG3_rY%3Dtx6x7ibmXVRk7btXw_Xaxv_S-FEMHX0b_g8-oA%40mail.gmail.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/e6605cd3-8571-47ae-b4fc-f3bce5af7fa9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Elasticsearch Mapping Issue
Hey,
I am using ELK stack for log processing. Logstash 1.4.2 (Single Instance)
and Elasticsearch 1.2.2(Cluster of 2 nodes), and redis as broker between
logstash and elasticsearch.
I am able to parse my logs using Logstash, get the parsed document in
Redis. But not able to get the documents inside Elasticsearch.
The following is my Central logstash server configuration file.
*input {redis {host => "xx.xx.xx.xx"type =>
"redis-input"data_type => "list" key => "logstash"
threads => 5}redis {host => "xx.xx.xx.xx"type =>
"redis-input"data_type => "list" key => "logstash"
threads => 5}} filter { date { match =>
["timestamp_nsstats",%{YEAR}-%{MONTHNUM}-%{MONTHDAY}[,]%{HOUR}:?%{MINUTE}(?::?%{SECOND})?"]
} } output { stdout { }
elasticsearch {cluster => "logstash"host =>
"xx.xx.xx.xx"protocol => "http" node_name
=> "Node1"index => "logstash-%{+.MM.dd}"}}*
The following is the health of Elasticsearch Instances.
1. {
2. "cluster_name": "logstash",
3. "status": "green",
4. "timed_out": false,
5. "number_of_nodes": 2,
6. "number_of_data_nodes": 2,
7. "active_primary_shards": 3,
8. "active_shards": 6,
9. "relocating_shards": 0,
10. "initializing_shards": 0,
11. "unassigned_shards": 0
12. }
I am not able to find out the reason, that is causing logstash being not able
to reach elasticsearch. Do I need to make any changes in configuration file,
which might make logstash aware of the elasticsearch server.
Please let me know what you think, that might be causing the issue. If you need
any other information please let me know.
Thank you,
Shriyansh
--
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/1c586b5d-c53e-4899-b9cb-57ce0f57a262%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Issue redirecting output to Elasticsearch
Hey,
I am using losgstash 1.4.2 and Elasticsearch 1.2.2. I am trying to output
my logs on Elasticsearch cluster which is running on different machine from
logstash server. The issue is my logs are not able to reach to
ealsticsearch instance. Though I am able to get my logs in redis.
What can be possible issue I should look for to solve the problem. I have
not defined any elasticsearch indices, do i have to define the indexes
explicitly.
Following is my logstash server configuration file
input {
redis {
host => "xx.xx.xx.xx"
type => "redis-input"
data_type => "list"
key => "logstash"
}
redis {
host => "xx.xx.xx.xx"
type => "redis-input"
data_type => "list"
key => "logstash"
}
}
filter {
date {
match =>
["timestamp_nsstats",%{YEAR}-%{MONTHNUM}-%{MONTHDAY}[,]%{HOUR}:?%{MINUTE}(?::?%{SECOND})?"]
}
}
output {
stdout { }
elasticsearch {
cluster => "logstash"
host => "xx.xx.xx.xx"
protocol => http
port => "9200"
}
}
Any input will really help.
Thank you,
Shriyansh
--
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/51fff7eb-e0b9-4d43-b2a1-6d695b9de51e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: Elasticsearch Not Working
Hi, Thank you very much Hai. It worked. Thanks, Shriyansh On Tuesday, July 8, 2014 5:58:53 AM UTC-7, Hai S. Ha wrote: > > Hi, > Here is the way to solve it: > > You have to set the variables in /etc/elasticsearch/elasticsearch.yml: > path.data: path/to/data > path.work: path/to/work > path.logs: /var/log/elasticsearch > path.conf: /etc/elasticsearch > > And remember to give access to user "elasticsearch" for folder that > elasticsearch uses: > chown -R elasticsearch /path/to/data > chown -R elasticsearch /path/to/work > > Regards. > > On Tuesday, July 8, 2014 1:59:50 PM UTC+2, Hai S. Ha wrote: >> >> I got exactly the same problem like Shriyansh Jain. Anyone knows what >> happened? >> Thanks a lot for helping. >> >> On Tuesday, July 8, 2014 2:03:44 AM UTC+2, shriyansh jain wrote: >>> >>> When I am verifying the elastic-search status, its giving me the >>> following error message. >>> >>> *elasticsearch dead but subsys locked* >>> >>> Please help me out solving this. >>> >>> Thank you. >>> Shriyansh Jain >>> >> -- 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/2ddafa18-d118-409d-98f3-60124e757595%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Elasticsearch Not Working
Hey, I tried executing the above commands specified by you. But still not getting the elastic-search working. Still giving the same status message, "elasticsearch dead but subsys locked" Thanks, Shriyansh On Monday, July 7, 2014 5:29:00 PM UTC-7, arshpreet singh wrote: > > On Tue, Jul 8, 2014 at 5:53 AM, shriyansh jain > wrote: > > Hey Arshpreet, > > > > I am not getting anything in output. > > Please avoid top posting and RTF while replying in mailing lists. > IMHO your service is blocked and you need to kill the demon. > > sudo /etc/init.d/elasticsearch restart > or > sudo /etc/init.d/elasticsearch stop > sudo /etc/init.d/elasticsearch start > > > -- > > Thanks > Arshpreet singh > http://arshpreetsingh.wordpress.com/ > I have no special talents. Only passionately curious > -- 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/bc85faa2-406e-4fac-ac75-06649d1bf075%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Elasticsearch Not Working
Hey, I am running the following command from terminal to verify the status *sudo /etc/init.d/elasticsearch status*Thanks, Shriyansh On Monday, July 7, 2014 5:07:04 PM UTC-7, Mark Walkom wrote: > > You need to provide more details for people to be able to effectively help. > > How are you verifying this, what method are you using? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 8 July 2014 10:03, shriyansh jain > > wrote: > >> When I am verifying the elastic-search status, its giving me the >> following error message. >> >> *elasticsearch dead but subsys locked* >> >> Please help me out solving this. >> >> Thank you. >> Shriyansh Jain >> >> -- >> 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/bbbf214b-909b-4819-a6ca-508e76c7af7b%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/bbbf214b-909b-4819-a6ca-508e76c7af7b%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/a37913e3-fd5a-45b1-85c1-9d20fad05c6b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Elasticsearch Not Working
I am just running a command from terminal. Thanks, Shriyansh On Monday, July 7, 2014 5:07:04 PM UTC-7, Mark Walkom wrote: > > You need to provide more details for people to be able to effectively help. > > How are you verifying this, what method are you using? > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com > web: www.campaignmonitor.com > > > On 8 July 2014 10:03, shriyansh jain > > wrote: > >> When I am verifying the elastic-search status, its giving me the >> following error message. >> >> *elasticsearch dead but subsys locked* >> >> Please help me out solving this. >> >> Thank you. >> Shriyansh Jain >> >> -- >> 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/bbbf214b-909b-4819-a6ca-508e76c7af7b%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/bbbf214b-909b-4819-a6ca-508e76c7af7b%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/269395b9-7d48-4f0c-93de-4d7b275dff6d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Elasticsearch Not Working
Hey Arshpreet, I am not getting anything in output. Thank you, Shriyansh On Monday, July 7, 2014 5:12:05 PM UTC-7, arshpreet singh wrote: > > On Tue, Jul 8, 2014 at 5:33 AM, shriyansh jain > wrote: > > When I am verifying the elastic-search status, its giving me the > following > > error message. > > > > elasticsearch dead but subsys locked > > ipcs -s | grep elasticsearch > > Can you post output for the above command? > > -- > > Thanks > Arshpreet singh > http://arshpreetsingh.wordpress.com/ > I have no special talents. Only passionately curious > -- 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/e48f5f1e-dfe8-4f25-b9f0-b787762b631b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Elasticsearch Not Working
When I am verifying the elastic-search status, its giving me the following error message. *elasticsearch dead but subsys locked* Please help me out solving this. Thank you. Shriyansh Jain -- 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/bbbf214b-909b-4819-a6ca-508e76c7af7b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
