Can you describe your deployment process? the cluster can't be _always_ red
- it should be green when you first deploy
Other than that, check the obvious - that AWS securty groups are properly
defined for those machines (all of them under the same named security group)
--
Itamar Syn-Hershko
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
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, 3
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.
--
Itamar Syn-Hershko
http://code972.com | @synhershko https://twitter.com/synhershko
Freelance Developer
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:
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
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 and
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
