ES 1.4.2, Tribe Configuration, And Creating Indices

[Ed_Brown]

Hello,
I have ES 1.4.2 installed on four servers, with one server hosting the ES
tribe node and the other three servers hosting an ES instance. I decided to
have the three servers each being a cluster of one server, to test some
things out.

If I connect to the tribe node, and try to create an index and bulk index,
it fails with an error saying no master can be found. But if I create the
indices on each node and then bulk index using the tribe node, it works.
Additionally, if I create an index template on the three nodes, and then
index using the tribe node, this works. Even if the index doesn't initially
exist.

Reading the documentation, as I understand it, indexing into a new index
via the tribe node should never work.

Is the behavior I'm seeing, expected?

Thanks in advance.

--
Ed Brown,
Software Architect

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/49fb5958-e80e-4de8-888c-3ef4df8aa188%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[warkolm (Mark Walkom)]

Elasticsearch Platform — Find real-time answers at scale

says it can do reads and writes.

But note;

However, there are a few exceptions:

• The merged view cannot handle indices with the same name in multiple
  clusters. By default it will pick one of them, see later for on_conflict
  options.
• Master level read operations (eg Cluster State
  http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-state.html
  , Cluster Health
  http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-health.html)
  will automatically execute with a local flag set to true since there is no
  master.
• Master level write operations (eg Create Index
  http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html)
  are not allowed. These should be performed on a single cluster.

On 6 February 2015 at 14:21, Ed Brown edswarchitect@gmail.com wrote:

Hello,
I have ES 1.4.2 installed on four servers, with one server hosting the ES
tribe node and the other three servers hosting an ES instance. I decided to
have the three servers each being a cluster of one server, to test some
things out.

If I connect to the tribe node, and try to create an index and bulk index,
it fails with an error saying no master can be found. But if I create the
indices on each node and then bulk index using the tribe node, it works.
Additionally, if I create an index template on the three nodes, and then
index using the tribe node, this works. Even if the index doesn't initially
exist.

Reading the documentation, as I understand it, indexing into a new index
via the tribe node should never work.

Is the behavior I'm seeing, expected?

Thanks in advance.

--
Ed Brown,
Software Architect

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/49fb5958-e80e-4de8-888c-3ef4df8aa188%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/49fb5958-e80e-4de8-888c-3ef4df8aa188%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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X9XZ91xGvYts83MBDYZ%2B1_gBck2-aKx%3Det6Q0%2BXUvTErw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.