[docs] Manually migrating Kibana index#13696
Conversation
fcc4c31 to
1fafcf4
Compare
docs/migration/migrate_6_0.asciidoc
Outdated
There was a problem hiding this comment.
we probably want this still?
There was a problem hiding this comment.
Yes, not sure what happened there
1fafcf4 to
7deb526
Compare
There was a problem hiding this comment.
not saying we want to go down this path but a no downtime upgrade without 5.6 could be to stand up two kibana's, one to the reindexed .kibana and update A records to the new IP after
There was a problem hiding this comment.
Yeah, that would be pretty tough to time correctly.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
7deb526 to
ef0857d
Compare
docs/migration/migrate_6_0.asciidoc
Outdated
| === Types removed from Kibana index | ||
| *Details:* With the imminent {es-ref}/removal-of-types.html[removal of types in Elasticsearch], we have updated our index to not rely on types. Kibana 5.6.x can support both of these mappings to minimize downtime. A UI is provided with X-Pack to assist with the migration of the Elastic stack. | ||
|
|
||
| *Impact:* You will need migrate your Kibana index either {kibana-ref}/migrating-6.0-index.html[manually], or through the Migration UI in X-Pack. |
There was a problem hiding this comment.
is there a link a more info link to the migration ui available?
There was a problem hiding this comment.
I believe @archanid is still working on that. We should link when it becomes available.
There was a problem hiding this comment.
I think it shouldn't be called "Migration UI" here--we're calling it "Upgrade Assistant"
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
| "settings" : { | ||
| "number_of_shards" : 1, | ||
| "index.format": 6, | ||
| "index.refresh_interval": -1 |
There was a problem hiding this comment.
we probably want to turn this back on after, right?
There was a problem hiding this comment.
Actually, I am going to remove it. @archanid, is the upgrade UI turning this back on after the migration?
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
|
@debadair, did you want to take a pass over this? |
rhoboat
left a comment
There was a problem hiding this comment.
I left a few comments, including a small typo fix.
docs/migration/migrate_6_0.asciidoc
Outdated
| === Types removed from Kibana index | ||
| *Details:* With the imminent {es-ref}/removal-of-types.html[removal of types in Elasticsearch], we have updated our index to not rely on types. Kibana 5.6.x can support both of these mappings to minimize downtime. A UI is provided with X-Pack to assist with the migration of the Elastic stack. | ||
|
|
||
| *Impact:* You will need migrate your Kibana index either {kibana-ref}/migrating-6.0-index.html[manually], or through the Migration UI in X-Pack. |
There was a problem hiding this comment.
I think it shouldn't be called "Migration UI" here--we're calling it "Upgrade Assistant"
|
|
||
| [IMPORTANT] | ||
| ============================================== | ||
| The following will make transformations to your Kibana index. It is recommended you backup your Kibana index prior to running any of the following commands. |
There was a problem hiding this comment.
Maybe a link to the snapshot/restore docs where you say "backup your Kibana index" ?
https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-snapshots.html
| The following will make transformations to your Kibana index. It is recommended you backup your Kibana index prior to running any of the following commands. | ||
| ============================================== | ||
|
|
||
| In order to migrate to Kibana 6, your Kibana index needs to be re-indexed. This will make transformations to the data model, removing types which are being {es-ref}/removal-of-types.html[removed in Elasticsearch]. |
There was a problem hiding this comment.
I think in other docs, we aren't hyphenating "reindex", so maybe being consistent here would be good.
|
|
||
| In order to migrate to Kibana 6, your Kibana index needs to be re-indexed. This will make transformations to the data model, removing types which are being {es-ref}/removal-of-types.html[removed in Elasticsearch]. | ||
|
|
||
| A UI is available in X-Pack 5.6 to assist with the migration. The following is provided should you be required to run the migration manually. The commands assume your using the default `.kibana` index. If `kibana.index` is set to something different in your `kibana.yml` you will need to modify the commands. |
There was a problem hiding this comment.
The commands assume your using => The commands assume you're using
| // CONSOLE | ||
| -- | ||
|
|
||
| . Re-index `.kibana` into `.kibana-6`: |
| "actions" : [ | ||
| { "add": { "index": ".kibana-6", "alias": ".kibana" } }, | ||
| { "remove_index": { "index": ".kibana" } } | ||
| ] |
There was a problem hiding this comment.
It looks like this command will wipe out any existing aliases on the old kibana index. Right?
There was a problem hiding this comment.
Here's where we're adding the old aliases to the new index: https://github.com/elastic/x-pack-kibana/blob/master/plugins/upgrade/public/lib/util/index.js#L77-L87
There was a problem hiding this comment.
I 38cc25f I have mentioned not using an alias. I would rather keep the commands simple for majority of users and call out the cases where folks have complex setups.
| } | ||
| } | ||
| } | ||
| } |
There was a problem hiding this comment.
This part kind of bothers me. Putting the whole mappings here feels like there could be a typo, or some change to it later (maybe not realistic), but it means it's in more than one place. Is it worth it to link to a mappings object as a central source of truth?
There was a problem hiding this comment.
I believe we could include it, but we would need the whole mapping which I believe this is the first in the OS repo.
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
|
@archanid, thanks for the feedback. I have addressed it - mind giving another look? |
|
Other than that one comma thingy, it LGTM! |
|
Also @tylersmalley to help you link to the Upgrade Assistant docs: The file is But there are these tags at the top of it: I don't know what that means--maybe the link is actually |
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
Signed-off-by: Tyler Smalley <tyler.smalley@elastic.co>
|
6.1/6.x: 220b39f |
|
I will follow-up with adding the link once the other PR is merged. I also need to change the xpack-ref to allow defining the branch, like the other refs. |
|
@tylersmalley I think we'll want this content in master as well, even if it is slightly modified. These steps do not disappear with 7.0 as users will still need to do this reindex if they are beginning in 5.x and trying to go to 7. I know we're a long ways out from dealing directly with upgradability to 7.0, but we should try to keep the docs as current as possible in the meantime. |
|
@epixa, is that something we really want to support? With Elasticsearch, don't users need to go through each of the major versions when upgrading? |
|
@tylersmalley That's a good point |
Documents the process for manually migrating the Kibana index in preparation for a migration to 6.x.