ok. i stopped the entire cluster and started one ES node at a time, and that seemed to do the trick, even though that's one of the first things I did when things went ary. I have no idea how it could have gotten into that state to begin with, but it's all good now. We lost a ton of logs, but it looks like everything is OK now. Alex
On Thursday, April 3, 2014 11:42:41 PM UTC-4, Alexander Gray II wrote: > > I installed elastichq. > Interestingly enough, it doesn't even show that index, but > head/paramedic/bigdesk does. weird. > All the diagnostics of elastichq shows mostly green. There are few > "yellows" under Index Activity for "Get Total", but it doesn't strike me as > something that is related to this. > What I did find was that 2 of the shards have been in the "initializing" > state for quite some time. > Sounds bad, but maybe I should wait. maybe it will just go away. > Note that since this happened, we are pretty much dead in the water, since > no new logs are being ingested at all. > I almost want to say things worked better and with the m1.larges, instead > of the m2.xlarges, but I don't see how that is possible. > I'm open for any wild suggestions to get this cluster back to a working > state. > -- 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/dc353f0a-a136-4fd9-9a6b-d6ded561905e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
