Re: What's the difference between bind_host and publish_host in ElasticSearch?

[flyer]

Thank you, Jörg.

I neglected the client-server model and now I know the purpose of
"bind_host" and "publish_host"。


On Sun, Jun 8, 2014 at 2:27 AM, joergpra...@gmail.com  wrote:

> "bind_host" is the host that an Elasticsearch node uses in the socket bind
> call when starting the network. Due to socket programming model, you can
> "bind" to an address. By referencing an "address", the socket allows access
> to one or all underlying network devices. There are several addresses with
> predefined semantics, e.g. 0.0.0.0 is reserved for "bind to all network
> devices". So the "bind_host" address does not necessarily reflect a single
> unique address.
>
> "publish_host" must be a single unique network address. It is used for
> connect calls by other nodes, not for socket bind call by the node itself.
> By using "publish_host" all nodes and clients can be sure they can connect
> to this node. Declaring this single unique address to the outside can be
> interpreted as "publishing", so it is called "publish_host".
>
> You can not set "bind_host" and "publish_host" to arbitrary values, the
> values must adhere to the underlying socket model.
>
> Jörg
>
>
> On Sat, Jun 7, 2014 at 7:50 PM, flyer  wrote:
>
>>  From this document network settings
>> <http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-network.html>,
>> I know that *publish_host* is the host that other nodes in the cluster
>> will communicate to. But I don't understand the functionality of
>> *bind_host*, which means that:
>>
>> The network.bind_host setting allows to control the host different
>> network components will bind on. By default, the bind host will be
>> anyLocalAddress (typically 0.0.0.0 or ::0).
>>
>> And the *network.host* will set *network.bind_host* and
>> *network.publish_host* to the same value.
>>
>> So I want to know:
>>
>>
>>1.  the difference between *network.bind_host *and
>>*network.publish_host*
>>2.  the consequences of  setting *network.bind_host* and
>>*network.publish_host* to different values
>>
>>
>> Thank you very much.
>>
>>
>> --
>> 宠辱不惊，闲看庭前花开花落；去留无意，漫随天边云卷云舒。
>>
>>  --
>> 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/CAKLbBG_B%3DN449d3MxzqTZu3p5DMnXpg8Vy%2BBS5bcZyVD0natsA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/elasticsearch/CAKLbBG_B%3DN449d3MxzqTZu3p5DMnXpg8Vy%2BBS5bcZyVD0natsA%40mail.gmail.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/CAKdsXoGqGRzHeSFg0%2BuwxxkomdVi%3D5nx9KhGqFHcYw87Xq5pqw%40mail.gmail.com
> <https://groups.google.com/d/msgid/elasticsearch/CAKdsXoGqGRzHeSFg0%2BuwxxkomdVi%3D5nx9KhGqFHcYw87Xq5pqw%40mail.gmail.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/CAKLbBG_KrYccT39fjtpb7tuUswTfUrvZ31RgnPHXouMDymBeXg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

What's the difference between bind_host and publish_host in ElasticSearch?

[flyer]

>From this document network settings
,
I know that *publish_host* is the host that other nodes in the cluster will
communicate to. But I don't understand the functionality of *bind_host*,
which means that:

The network.bind_host setting allows to control the host different network
components will bind on. By default, the bind host will be anyLocalAddress
(typically 0.0.0.0 or ::0).

And the *network.host* will set *network.bind_host* and
*network.publish_host* to the same value.

So I want to know:


   1.  the difference between *network.bind_host *and *network.publish_host*

   2.  the consequences of  setting *network.bind_host* and
   *network.publish_host* to different values


Thank you very much.


-- 
宠辱不惊，闲看庭前花开花落；去留无意，漫随天边云卷云舒。

-- 
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/CAKLbBG_B%3DN449d3MxzqTZu3p5DMnXpg8Vy%2BBS5bcZyVD0natsA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: cluster yellow state

[flyer]

It's caused by different versions of ES. In my previous test, one node use
ES-1.1.1 and the other uses ES-1.1.2. After every node of the cluster uses
the same version of ES, then the first problem disappears.

Thank you very much!


On Fri, Jun 6, 2014 at 11:46 AM, flyer  wrote:

> I add another node into the cluster and now after I index data, the state
> of the cluster becomes green.
>
> If the replica number is 1, must I have at least 3 nodes to assure that
> the state of the cluster is green?
>
>
> On Fri, Jun 6, 2014 at 9:46 AM, flyer  wrote:
>
>> Because it's difficult to recognize which shards are replica (I haven't
>> installed the head plugin), I removed all of the index data, tried to
>> reindex the data but got the same results that there were still some
>> replica shards not to be allocated.
>>
>> I want to know why there're some replica not to be allocated.
>>
>> "shard allocation filter" seems troublesome. So is there another way to
>> solve this problem other than using shard allocation filter?
>>
>>
>> On Fri, Jun 6, 2014 at 7:57 AM, Mark Walkom 
>> wrote:
>>
>>> Try removing the replicas and then readding them.
>>> You can also force allocation -
>>> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html
>>> - but the first option is an easier one to start with.
>>>
>>> Regards,
>>> Mark Walkom
>>>
>>> Infrastructure Engineer
>>> Campaign Monitor
>>> email: ma...@campaignmonitor.com
>>> web: www.campaignmonitor.com
>>>
>>>
>>> On 6 June 2014 09:35, flyer  wrote:
>>>
>>>>  I have a cluster of two nodes and have the following configs for
>>>> shards and replicas:
>>>>
>>>> index.number_of_shards: 10
>>>>>
>>>> index.number_of_replicas: 1
>>>>
>>>>
>>>> But when I index around 10k data or just one data, I find that there
>>>> are always 4 replica shards not to be allocated.
>>>>
>>>> Is there a method to allocate all replica shards on the two nodes?
>>>> Thanks in advance.
>>>>
>>>> --
>>>> 宠辱不惊，闲看庭前花开花落；去留无意，漫随天边云卷云舒。
>>>>
>>>>  --
>>>> 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/CAKLbBG-%2BKobeupzPhOiF0FZ9Lf0eeWsBOotLEd%2B_v4arR%3DzHwA%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/elasticsearch/CAKLbBG-%2BKobeupzPhOiF0FZ9Lf0eeWsBOotLEd%2B_v4arR%3DzHwA%40mail.gmail.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/CAEM624ZQny1Uy2RwKJ%2BRYi0hLexjFv2%2B8E8jkZccQpsqLrKong%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/elasticsearch/CAEM624ZQny1Uy2RwKJ%2BRYi0hLexjFv2%2B8E8jkZccQpsqLrKong%40mail.gmail.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/CAKLbBG8C9FwazZH0GEgdfRKXEKz2FCaOfDk5xt14%3DwFowieEcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: If I set index.number_of_replica:1, then the minimum number of nodes should be 3 to assure that the status of the cluster is gree?

[flyer]

It's the ES version that causes the first problem.

In my previous test, one node use ES-1.1.1 and the other node use ES-1.1.2.
After I indexed data, the state of the cluster was yellow other than green.
I think there're some compatibility problems between the two versions.

Thank you very much :D


On Fri, Jun 6, 2014 at 4:49 PM, flyer  wrote:

> The configurations on the two nodes are almost the same except the **
> node.name**.
>
> The first question is very strange.
> I I run the same config on another cluster of two nodes and after I index
> data, the state of the cluster is green. I have no idea why this
> happened..Is there something I ignore?
>
> I want to know how ES allocates nodes. Is there some reference? I googled
> but couldn't find it.
>
> Thank you :D
>
>
> On Fri, Jun 6, 2014 at 3:05 PM, joergpra...@gmail.com <
> joergpra...@gmail.com> wrote:
>
>> 1. No. Did you change the configuration? You have two data nodes
>> connected?
>>
>> 2. You do not need to be concerned where primary shards are allocated,
>> secondary shards play the same role (except primaries receive writes first
>> a few milliseconds earlier than secondaries). Elasticsearch randomly
>> allocates shards on all the available nodes. If nodes go away, shards on
>> remaining nodes are promoted to primaries automatically.
>>
>> Jörg
>>
>>
>> On Fri, Jun 6, 2014 at 5:41 AM, flyer  wrote:
>>
>>> I have a cluster of two nodes, and set the configs for shard number and
>>> replica number as following:
>>>
>>> index.number_of_shards: 10
>>>
>>> index.number_of_replicas: 1
>>>
>>>
>>> The master node is elected automatically.
>>>
>>> Before I index data, the state of the cluster is green. After I index
>>> data, the state of the cluster becomes yellow. Some replica shards are not
>>> allocated.
>>>
>>> But if I add another node and now the cluster consists of three nodes,
>>> then I index data and the state of the cluster becomes green.
>>>
>>> The version of ES that I use is 1.1.
>>>
>>> Question 1:
>>> If the replica number is 1, do I have to have at least 3 nodes to
>>> assure the state of the cluster is green?
>>>
>>> Question 2:
>>> I have observed that one (not the master node) of the three nodes
>>> just has primary nodes. What's the mechanism ES uses to allocate
>>> primary/replia shards?
>>>
>>> Thanks anyway.
>>>
>>> --
>>> 宠辱不惊，闲看庭前花开花落；去留无意，漫随天边云卷云舒。
>>>
>>>  --
>>> 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/CAKLbBG-o6JmkbPAAvGBP8t8Bdp-ONEWEFK5kGW%3Dcyn-h-O6dsg%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/elasticsearch/CAKLbBG-o6JmkbPAAvGBP8t8Bdp-ONEWEFK5kGW%3Dcyn-h-O6dsg%40mail.gmail.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/CAKdsXoES%2Bd5gmo_OS-Si2dXLPGbk_q-B554WeL13HC0DfFY1vw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/elasticsearch/CAKdsXoES%2Bd5gmo_OS-Si2dXLPGbk_q-B554WeL13HC0DfFY1vw%40mail.gmail.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/CAKLbBG8o%2BOvM8zOWh58bAmeH1iisq8xERTucw%2BJNktPDNkuuRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: If I set index.number_of_replica:1, then the minimum number of nodes should be 3 to assure that the status of the cluster is gree?

[flyer]

The configurations on the two nodes are almost the same except the **
node.name**.

The first question is very strange.
I I run the same config on another cluster of two nodes and after I index
data, the state of the cluster is green. I have no idea why this
happened..Is there something I ignore?

I want to know how ES allocates nodes. Is there some reference? I googled
but couldn't find it.

Thank you :D


On Fri, Jun 6, 2014 at 3:05 PM, joergpra...@gmail.com  wrote:

> 1. No. Did you change the configuration? You have two data nodes connected?
>
> 2. You do not need to be concerned where primary shards are allocated,
> secondary shards play the same role (except primaries receive writes first
> a few milliseconds earlier than secondaries). Elasticsearch randomly
> allocates shards on all the available nodes. If nodes go away, shards on
> remaining nodes are promoted to primaries automatically.
>
> Jörg
>
>
> On Fri, Jun 6, 2014 at 5:41 AM, flyer  wrote:
>
>> I have a cluster of two nodes, and set the configs for shard number and
>> replica number as following:
>>
>> index.number_of_shards: 10
>>
>> index.number_of_replicas: 1
>>
>>
>> The master node is elected automatically.
>>
>> Before I index data, the state of the cluster is green. After I index
>> data, the state of the cluster becomes yellow. Some replica shards are not
>> allocated.
>>
>> But if I add another node and now the cluster consists of three nodes,
>> then I index data and the state of the cluster becomes green.
>>
>> The version of ES that I use is 1.1.
>>
>> Question 1:
>> If the replica number is 1, do I have to have at least 3 nodes to
>> assure the state of the cluster is green?
>>
>> Question 2:
>> I have observed that one (not the master node) of the three nodes
>> just has primary nodes. What's the mechanism ES uses to allocate
>> primary/replia shards?
>>
>> Thanks anyway.
>>
>> --
>> 宠辱不惊，闲看庭前花开花落；去留无意，漫随天边云卷云舒。
>>
>>  --
>> 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/CAKLbBG-o6JmkbPAAvGBP8t8Bdp-ONEWEFK5kGW%3Dcyn-h-O6dsg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/elasticsearch/CAKLbBG-o6JmkbPAAvGBP8t8Bdp-ONEWEFK5kGW%3Dcyn-h-O6dsg%40mail.gmail.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/CAKdsXoES%2Bd5gmo_OS-Si2dXLPGbk_q-B554WeL13HC0DfFY1vw%40mail.gmail.com
> <https://groups.google.com/d/msgid/elasticsearch/CAKdsXoES%2Bd5gmo_OS-Si2dXLPGbk_q-B554WeL13HC0DfFY1vw%40mail.gmail.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/CAKLbBG-V0xGEe%3D0gL51-bAcsWMcy-sE8bHwHg_1z7NdEiHt_7w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: cluster yellow state

[flyer]

I add another node into the cluster and now after I index data, the state
of the cluster becomes green.

If the replica number is 1, must I have at least 3 nodes to assure that the
state of the cluster is green?


On Fri, Jun 6, 2014 at 9:46 AM, flyer  wrote:

> Because it's difficult to recognize which shards are replica (I haven't
> installed the head plugin), I removed all of the index data, tried to
> reindex the data but got the same results that there were still some
> replica shards not to be allocated.
>
> I want to know why there're some replica not to be allocated.
>
> "shard allocation filter" seems troublesome. So is there another way to
> solve this problem other than using shard allocation filter?
>
>
> On Fri, Jun 6, 2014 at 7:57 AM, Mark Walkom 
> wrote:
>
>> Try removing the replicas and then readding them.
>> You can also force allocation -
>> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html
>> - but the first option is an easier one to start with.
>>
>> Regards,
>> Mark Walkom
>>
>> Infrastructure Engineer
>> Campaign Monitor
>> email: ma...@campaignmonitor.com
>> web: www.campaignmonitor.com
>>
>>
>> On 6 June 2014 09:35, flyer  wrote:
>>
>>>  I have a cluster of two nodes and have the following configs for
>>> shards and replicas:
>>>
>>> index.number_of_shards: 10
>>>>
>>> index.number_of_replicas: 1
>>>
>>>
>>> But when I index around 10k data or just one data, I find that there are
>>> always 4 replica shards not to be allocated.
>>>
>>> Is there a method to allocate all replica shards on the two nodes?
>>> Thanks in advance.
>>>
>>> --
>>> 宠辱不惊，闲看庭前花开花落；去留无意，漫随天边云卷云舒。
>>>
>>>  --
>>> 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/CAKLbBG-%2BKobeupzPhOiF0FZ9Lf0eeWsBOotLEd%2B_v4arR%3DzHwA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/elasticsearch/CAKLbBG-%2BKobeupzPhOiF0FZ9Lf0eeWsBOotLEd%2B_v4arR%3DzHwA%40mail.gmail.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/CAEM624ZQny1Uy2RwKJ%2BRYi0hLexjFv2%2B8E8jkZccQpsqLrKong%40mail.gmail.com
>> <https://groups.google.com/d/msgid/elasticsearch/CAEM624ZQny1Uy2RwKJ%2BRYi0hLexjFv2%2B8E8jkZccQpsqLrKong%40mail.gmail.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/CAKLbBG-WZZABmG9Ts%3DmbJfjAbMspHDjSSEsTL8C8Yjm3qxxDcg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

If I set index.number_of_replica:1, then the minimum number of nodes should be 3 to assure that the status of the cluster is gree?

[flyer]

I have a cluster of two nodes, and set the configs for shard number and
replica number as following:

index.number_of_shards: 10

index.number_of_replicas: 1


The master node is elected automatically.

Before I index data, the state of the cluster is green. After I index data,
the state of the cluster becomes yellow. Some replica shards are not
allocated.

But if I add another node and now the cluster consists of three nodes, then
I index data and the state of the cluster becomes green.

The version of ES that I use is 1.1.

Question 1:
If the replica number is 1, do I have to have at least 3 nodes to
assure the state of the cluster is green?

Question 2:
I have observed that one (not the master node) of the three nodes just
has primary nodes. What's the mechanism ES uses to allocate primary/replia
shards?

Thanks anyway.

-- 
宠辱不惊，闲看庭前花开花落；去留无意，漫随天边云卷云舒。

-- 
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/CAKLbBG-o6JmkbPAAvGBP8t8Bdp-ONEWEFK5kGW%3Dcyn-h-O6dsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: cluster yellow state

[flyer]

Because it's difficult to recognize which shards are replica (I haven't
installed the head plugin), I removed all of the index data, tried to
reindex the data but got the same results that there were still some
replica shards not to be allocated.

I want to know why there're some replica not to be allocated.

"shard allocation filter" seems troublesome. So is there another way to
solve this problem other than using shard allocation filter?


On Fri, Jun 6, 2014 at 7:57 AM, Mark Walkom 
wrote:

> Try removing the replicas and then readding them.
> You can also force allocation -
> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-allocation.html
> - but the first option is an easier one to start with.
>
> Regards,
> Mark Walkom
>
> Infrastructure Engineer
> Campaign Monitor
> email: ma...@campaignmonitor.com
> web: www.campaignmonitor.com
>
>
> On 6 June 2014 09:35, flyer  wrote:
>
>> I have a cluster of two nodes and have the following configs for shards
>> and replicas:
>>
>> index.number_of_shards: 10
>>>
>> index.number_of_replicas: 1
>>
>>
>> But when I index around 10k data or just one data, I find that there are
>> always 4 replica shards not to be allocated.
>>
>> Is there a method to allocate all replica shards on the two nodes? Thanks
>> in advance.
>>
>> --
>> 宠辱不惊，闲看庭前花开花落；去留无意，漫随天边云卷云舒。
>>
>>  --
>> 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/CAKLbBG-%2BKobeupzPhOiF0FZ9Lf0eeWsBOotLEd%2B_v4arR%3DzHwA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/elasticsearch/CAKLbBG-%2BKobeupzPhOiF0FZ9Lf0eeWsBOotLEd%2B_v4arR%3DzHwA%40mail.gmail.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/CAEM624ZQny1Uy2RwKJ%2BRYi0hLexjFv2%2B8E8jkZccQpsqLrKong%40mail.gmail.com
> <https://groups.google.com/d/msgid/elasticsearch/CAEM624ZQny1Uy2RwKJ%2BRYi0hLexjFv2%2B8E8jkZccQpsqLrKong%40mail.gmail.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/CAKLbBG9MwJ4xNhouWmOUAhj3B5%3DNujcOSsRvChmYyOL-k3POYA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

cluster yellow state

[flyer]

I have a cluster of two nodes and have the following configs for shards and
replicas:

index.number_of_shards: 10
>
index.number_of_replicas: 1


But when I index around 10k data or just one data, I find that there are
always 4 replica shards not to be allocated.

Is there a method to allocate all replica shards on the two nodes? Thanks
in advance.

-- 
宠辱不惊，闲看庭前花开花落；去留无意，漫随天边云卷云舒。

-- 
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/CAKLbBG-%2BKobeupzPhOiF0FZ9Lf0eeWsBOotLEd%2B_v4arR%3DzHwA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.