Re: elasticsearch deploy on ec2

2015-02-16 Thread Eliran Shlomo
NET committer and PMC member > > On Mon, Feb 16, 2015 at 8:56 PM, Eliran Shlomo > wrote: > >> Hi, made the changes. >> no change in the cluster status and the same response from the servers >> >> { >>"cluster_name": "stress_new&

Re: elasticsearch deploy on ec2

2015-02-16 Thread Eliran Shlomo
ecovered / 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 <ht

Re: elasticsearch deploy on ec2

2015-02-16 Thread Eliran Shlomo
"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 re

Re: elasticsearch deploy on ec2

2015-02-16 Thread Eliran Shlomo
Hi, Since the first moment the cluster in in red The servers are under the same security group and inside the security group i allow any/any between the servers. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group an

elasticsearch deploy on ec2

2015-02-16 Thread Eliran Shlomo
Hi, I'm trying to deploy new elasticsearch environment on aws and the cluster is always at red and i get the following message { "error": "ClusterBlockException[blocked by: [SERVICE_UNAVAILABLE/1/state not recovered / initialized];]", "status": 503 } I'm trying to deploy 3 master nodes,