After upgrade from 1.4.1 to 1.4.2 don't see indices

Elastic Stack Elasticsearch
1

Hello

I did upgrade my ES (OS is linux Centos 6.6) . Config files are proper and
path to indices are good. ES in 1.4.2 dont see indices created by 1.4.1.
When I create new indice from 1.4.2 with name from 1.4.1 old indice is
overwrite.
ES don't report any problem.

Somebody have idea what is going on?

Regards Marek

--
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/883dc935-5860-4d77-8d40-0ef653210e35%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

Are you using by any chance timestamp feature with default set to null?

--
David Pilato | Technical Advocate | Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr https://twitter.com/elasticsearchfr | @scrutmydocs https://twitter.com/scrutmydocs

Le 13 janv. 2015 à 11:36, Marek Dabrowski marek.dabrowski@gmail.com a écrit :

Hello

I did upgrade my ES (OS is linux Centos 6.6) . Config files are proper and path to indices are good. ES in 1.4.2 dont see indices created by 1.4.1. When I create new indice from 1.4.2 with name from 1.4.1 old indice is overwrite.
ES don't report any problem.

Somebody have idea what is going on?

Regards Marek

--
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 mailto:elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/883dc935-5860-4d77-8d40-0ef653210e35%40googlegroups.com https://groups.google.com/d/msgid/elasticsearch/883dc935-5860-4d77-8d40-0ef653210e35%40googlegroups.com?utm_medium=email&utm_source=footer.
For more options, visit https://groups.google.com/d/optout 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/99D69A70-C9BD-466C-A2E8-6F7B75F974CD%40pilato.fr.
For more options, visit https://groups.google.com/d/optout.

3

However it's my mistake. Sorry for post.

W dniu wtorek, 13 stycznia 2015 11:36:34 UTC+1 użytkownik Marek Dabrowski
napisał:

Hello

I did upgrade my ES (OS is linux Centos 6.6) . Config files are proper and
path to indices are good. ES in 1.4.2 dont see indices created by 1.4.1.
When I create new indice from 1.4.2 with name from 1.4.1 old indice is
overwrite.
ES don't report any problem.

Somebody have idea what is going on?

Regards Marek

--
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/853d5cc4-70f7-439b-8913-54e5825d6558%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

4

Hello

My configuration is 2 nodes for master rule and 6 for data. I changed path
in config files for data nodes but I forgot change in 2 master nodes... I
tgought that master after upgrade, collect information about indices from
data nodes. That was mistake. Master node have his one meta data about
indices in path.data: directory. When I changed this param to proper path,
cluster started work ok.

Regards

On Tue, Jan 13, 2015 at 11:51 AM, David Pilato david@pilato.fr wrote:

Are you using by any chance timestamp feature with default set to null?

--
David Pilato | Technical Advocate | Elasticsearch.com
http://Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr | @scrutmydocs
https://twitter.com/scrutmydocs

Le 13 janv. 2015 à 11:36, Marek Dabrowski marek.dabrowski@gmail.com a
écrit :

Hello

I did upgrade my ES (OS is linux Centos 6.6) . Config files are proper and
path to indices are good. ES in 1.4.2 dont see indices created by 1.4.1.
When I create new indice from 1.4.2 with name from 1.4.1 old indice is
overwrite.
ES don't report any problem.

Somebody have idea what is going on?

Regards Marek

--
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/883dc935-5860-4d77-8d40-0ef653210e35%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/883dc935-5860-4d77-8d40-0ef653210e35%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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/BSbuGDbYiyc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/99D69A70-C9BD-466C-A2E8-6F7B75F974CD%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/99D69A70-C9BD-466C-A2E8-6F7B75F974CD%40pilato.fr?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/CAOPKe49COsqyBUBom35EB22YC_bn0H5GdfRxDqDQDAF_AW44-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

5

You really should have an uneven number of masters, it helps achieve easier
quorum which helps to prevent split brain.

On 15 January 2015 at 01:16, Marek Dabrowski marek.dabrowski@gmail.com
wrote:

Hello

My configuration is 2 nodes for master rule and 6 for data. I changed path
in config files for data nodes but I forgot change in 2 master nodes... I
tgought that master after upgrade, collect information about indices from
data nodes. That was mistake. Master node have his one meta data about
indices in path.data: directory. When I changed this param to proper path,
cluster started work ok.

Regards

On Tue, Jan 13, 2015 at 11:51 AM, David Pilato david@pilato.fr wrote:

Are you using by any chance timestamp feature with default set to null?

--
David Pilato | Technical Advocate | Elasticsearch.com
http://Elasticsearch.com
@dadoonet https://twitter.com/dadoonet | @elasticsearchfr
https://twitter.com/elasticsearchfr | @scrutmydocs
https://twitter.com/scrutmydocs

Le 13 janv. 2015 à 11:36, Marek Dabrowski marek.dabrowski@gmail.com a
écrit :

Hello

I did upgrade my ES (OS is linux Centos 6.6) . Config files are proper
and path to indices are good. ES in 1.4.2 dont see indices created by
1.4.1. When I create new indice from 1.4.2 with name from 1.4.1 old indice
is overwrite.
ES don't report any problem.

Somebody have idea what is going on?

Regards Marek

--
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/883dc935-5860-4d77-8d40-0ef653210e35%40googlegroups.com
https://groups.google.com/d/msgid/elasticsearch/883dc935-5860-4d77-8d40-0ef653210e35%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 a topic in the
Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/elasticsearch/BSbuGDbYiyc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/99D69A70-C9BD-466C-A2E8-6F7B75F974CD%40pilato.fr
https://groups.google.com/d/msgid/elasticsearch/99D69A70-C9BD-466C-A2E8-6F7B75F974CD%40pilato.fr?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/CAOPKe49COsqyBUBom35EB22YC_bn0H5GdfRxDqDQDAF_AW44-w%40mail.gmail.com
https://groups.google.com/d/msgid/elasticsearch/CAOPKe49COsqyBUBom35EB22YC_bn0H5GdfRxDqDQDAF_AW44-w%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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAEYi1X81XpZNM_YJ%2BkctAHz2kPajuyei61bCEyyHnaH_92bfUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.