Mark, I used the rpm install. I'll take a look at the plugins. Thanks.
On Thursday, December 19, 2013 5:07:53 PM UTC-5, Mark Walkom wrote: > > Did you install ES via a rpm/deb or using the zip? I ask because your data > store directory is custom.subl > > Check out these plugins for monitoring - elastichq, kopf, bigdesk. They > will give you an overview of your cluster and might give you insight into > where your problem lies. The other best place to check is the ES logs. > > Regards, > Mark Walkom > > Infrastructure Engineer > Campaign Monitor > email: ma...@campaignmonitor.com <javascript:> > web: www.campaignmonitor.com > > > On 20 December 2013 08:52, Eric Luellen <eric.l...@gmail.com <javascript:> > > wrote: > >> I think I made my situation even worse. I tried deleting the shards and >> starting over and now elasticsearch isn't even creating the >> /etc/elasticsearch/data/my-cluster/node folder. >> >> >> On Thursday, December 19, 2013 4:04:41 PM UTC-5, Eric Luellen wrote: >>> >>> Hello, >>> >>> Currently I have my syslog-ng --> logstash --> elasticsearch1 & >>> elastisearch2 setup working pretty good. It's accepting over 300 events per >>> second and hasn't bogged the systems down at all. However I'm running into >>> 2 issues that I don't quite understand. >>> >>> 1. When viewing the information in Kibana, it appears to be anywhere >>> from 15 min to an hr behind on the "all events" view. Sometimes when I >>> search for new logs it shows up correctly but overall it seems like it's >>> lagging behind trying to keep up with what logstash is sending it. That >>> being said, I'm concerned that logs are being dropped and I don't know >>> about it. Are there any commands I can use to validate this type of >>> information or what I can do to make sure elasticsearch/KIbana is keeping >>> up? >>> >>> 2. I've had to restart elasticsearch a few times and every time I do, it >>> completely breaks things. Once it starts back up it doesn't continue to >>> show the logs in Kibana correctly and when I run a health check, it says >>> there are unassigned shards. I've not been able to fix this and in the past >>> I've always just had to delete them and start from scratch again. >>> >>> Any idea what is going on with this or how I can more cleanly restart or >>> reboot the servers and recover from it? >>> >>> Thanks, >>> 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 elasticsearc...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/1f9a1c4a-94cf-49d7-a4d1-22ffb0b64727%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/384e753f-6e9a-49d4-9db9-c03af81d9ba3%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
