We are going to start our battle plans for upgrading from 0.26 to 1.2.2
and I have been reading through this doc:
to help see what things we may need to worry about.
Some specific questions
1 - Can the logging.yml file now be done as json like the elasticsearch
one? Sorry, kind of hate the yml format, and json is much easier. here is
2 - I know our index mappings need to be updated/checked, but anything pop
out as to really look for? Like, on standard analyzer something was set
before, but now it is gone kind of things?
3 - startup. we have just been running ./bin/elasticsearch. I see that
this has now changed. any recommended ways to have similar function as that
4 - index formats? Pretty sure that when we upgrade, the indexes are redone
in a new format, yes? Or, if we had static indexes, and we upgrade, are
some in an older format and new ones in the new format?
4a - if they are being re-written, is the limit more IO than anything else?
So, if we had say 1 TB of indexes to do, we should expect the process to
take while to update/write the new index files
5 - any other gotchas people have experienced? Recommend to just go from
.26 -> 1.2.2? Just making sure!
We are looking forward to finally being able to get to this so we can also
check out Marvel on real work being done. Should be fun and thanks for any
insights everyone has!
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 email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/66ff929d-1f36-406b-a53a-e82545abc98a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.