This is a DEV env. I've got 24G of RAM on all 4 machines. 12G for ES and 12G for the OS. I believe the machines are quad core HP Z-800's.
I will not be inserting at this rate very often. My question is more operational. How do you recover from the place I am in? If I kill -9 the ES process on node 2 I believe I will put my cluster in the red state. I did get into this unhappy spot once before. After trying to shut down ES on node 2 I eventually kill -9'd it. At that point my cluster was in the red state and unable to service requests. The "unassigned_shards" number was not changing. I have daily indexes so I simply deleted the most recent daily index and rebuilt it. At this point my cluster had all 4 nodes and was green again. In production this approach is not popular with mgmt. so I'm trying to understand a less heavy handed approach ;-) -Brad On Tuesday, January 21, 2014 2:54:52 PM UTC-7, Ben Hundley wrote: > > 2 questions: > > 1. What size servers are you using? Knowing how much RAM and # cores > would > be very helpful. > > 2. Definitely sounds like a massive load. Are you going to continually be > inserting 3k docs per sec? ~260mil documents a day? > > > > ----- > > -- > View this message in context: > http://elasticsearch-users.115913.n3.nabble.com/Node-will-not-shut-down-tp4047940p4047942.html > > Sent from the ElasticSearch Users mailing list archive at Nabble.com. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/3c667258-6c16-4557-8816-bd98ef0069b5%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
