Hey, a couple of things:
1. Did you check the log files? Most likely in /var/log/elasticsearch if you use the packages. Is there anything suspicious at the time of your outage? Please check your master node as well, if you have one (not sure if it is a master or client node from the cluster health). 2. Why should elasticsearch pull your data? Any special configuration you didnt mention? Or what exactly do you mean here? 3. Happy to debug your issue with the init script. The elasticsearch.yml file should be in /etc/elasticsearch/ and not in /etc - anything manually moved around? Can you still reproduce it? --Alex On Wed, Jan 8, 2014 at 8:10 PM, Eric Luellen <eric.luel...@gmail.com> wrote: > Hello, > > I've had my elasticsearch instance running for about a week with no > issues, but last night it stopped working. When I went to look in Kibana, > it stops logging around 20:45 on 1/7/14. I then restarted the service on > both both elasticsearch servers and it started logging again and back > pulled some logs from 07:10 that morning, even though I restarted the > service around 10:00. So my questions are: > > 1. Why did it stop working? I don't see any obvious errors. > 2. When I restarted it, why didn't it go back and pull all of the data and > not just some of it? I see that there are no unassigned shards. > > curl -XGET 'http://localhost:9200/_cluster/health?pretty=true' > { > "cluster_name" : "my-elasticsearch", > "status" : "green", > "timed_out" : false, > "number_of_nodes" : 3, > "number_of_data_nodes" : 2, > "active_primary_shards" : 40, > "active_shards" : 80, > "relocating_shards" : 0, > "initializing_shards" : 0, > "unassigned_shards" : 0 > > Are there any additional queries or logs I can look at to see what is > going on? > > On a slight side note, when I restarted my 2nd elasticsearch server it > isn't reading from the /etc/elasticsearch.yml file like it should. It isn't > creating the node name correctly or putting the data files in the spot I > have configured. I'm using CentOS and doing everything via > /etc/init.d/elasticsearch on both servers and the elasticsearch1 server > reads everything correctly but elasticsearch2 does not. > > Thanks for your help. > Eric > > -- > 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/fc191ee4-b312-4c52-89d9-de04c4309b65%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- 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/CAGCwEM8EOWdC5esVkfZ5hogocQkgreJBQUbF2zE7s-gGCt4NdQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
