Tnx for the help Itamar. solved by changing gateway.recover_after_nodes value from 8 to 6 i guess client node shouldn't be count for recover
On Monday, February 16, 2015 at 8:59:48 PM UTC+2, Itamar Syn-Hershko wrote: > > Remove the number of nodes setting, if that doesn't help start looking at > the logs. I seen clusters on AWS that took some time to discover and > stabilize, it may also be that. > > -- > > Itamar Syn-Hershko > http://code972.com | @synhershko <https://twitter.com/synhershko> > Freelance Developer & Consultant > Lucene.NET committer and PMC member > > On Mon, Feb 16, 2015 at 8:56 PM, Eliran Shlomo <eli...@whipclip.com > <javascript:>> wrote: > >> Hi, made the changes. >> no change in the cluster status and the same response from the servers >> >> { >> "cluster_name": "stress_new", >> "status": "red", >> "timed_out": false, >> "number_of_nodes": 8, >> "number_of_data_nodes": 3, >> "active_primary_shards": 0, >> "active_shards": 0, >> "relocating_shards": 0, >> "initializing_shards": 0, >> "unassigned_shards": 0 >> } >> >> get _status >> >> { >> "error": "ClusterBlockException[blocked by: >> [SERVICE_UNAVAILABLE/1/state not recovered / initialized];]", >> "status": 503 >> } >> >> >> On Monday, February 16, 2015 at 8:53:11 PM UTC+2, Itamar Syn-Hershko >> wrote: >>> >>> Master eligible nodes and Data nodes need to have this setting >>> >>> -- >>> >>> Itamar Syn-Hershko >>> http://code972.com | @synhershko <https://twitter.com/synhershko> >>> Freelance Developer & Consultant >>> Lucene.NET committer and PMC member >>> >>> On Mon, Feb 16, 2015 at 8:31 PM, Eliran Shlomo <eli...@whipclip.com> >>> wrote: >>> >>>> "Wait a second, you should use gateway.expected_data_nodes: 3 and >>>> gateway.expected_master_nodes: 3 instead of what you have there now. Also >>>> min master nodes should be 2 in your case." >>>> >>>> Those settings should be in the configuration of all nodes or only in >>>> the external gateway?(client) >>>> >>>> -- >>>> 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/e6914e16-28ac-4d00-96b7-b3b007538aba% >>>> 40googlegroups.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 elasticsearc...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/cd40be93-9b10-4bf1-ac9a-eafe8b98c8fe%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/cd40be93-9b10-4bf1-ac9a-eafe8b98c8fe%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/9473e8bf-def6-4f04-89f3-b957394b4cf4%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
