forked from elastic/built-docs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathupgrading-elastic-stack.html
565 lines (547 loc) · 28.8 KB
/
upgrading-elastic-stack.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
<!DOCTYPE html>
<html lang="en-us">
<head>
<meta charset="UTF-8">
<title>Upgrading the Elastic Stack | Installation and Upgrade Guide [6.4] | Elastic</title>
<meta class="elastic" name="content" content="Upgrading the Elastic Stack | Installation and Upgrade Guide [6.4]">
<link rel="home" href="index.html" title="Installation and Upgrade Guide [6.4]"/>
<link rel="up" href="index.html" title="Installation and Upgrade Guide [6.4]"/>
<link rel="prev" href="installing-elastic-stack.html" title="Installing the Elastic Stack"/>
<meta class="elastic" name="product_version" content="6.4"/>
<meta class="elastic" name="product_name" content="Elastic Stack"/>
<meta class="elastic" name="website_area" content="documentation"/>
<meta name="DC.type" content="Learn/Docs/Elastic Stack/Installation and Upgrade/6.4"/>
<meta name="DC.subject" content="Elastic Stack"/>
<meta name="DC.identifier" content="6.4"/>
<meta name="robots" content="noindex,nofollow"/>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<script src="https://cdn.optimizely.com/js/18132920325.js"></script>
<link rel="apple-touch-icon" sizes="57x57" href="/apple-icon-57x57.png">
<link rel="apple-touch-icon" sizes="60x60" href="/apple-icon-60x60.png">
<link rel="apple-touch-icon" sizes="72x72" href="/apple-icon-72x72.png">
<link rel="apple-touch-icon" sizes="76x76" href="/apple-icon-76x76.png">
<link rel="apple-touch-icon" sizes="114x114" href="/apple-icon-114x114.png">
<link rel="apple-touch-icon" sizes="120x120" href="/apple-icon-120x120.png">
<link rel="apple-touch-icon" sizes="144x144" href="/apple-icon-144x144.png">
<link rel="apple-touch-icon" sizes="152x152" href="/apple-icon-152x152.png">
<link rel="apple-touch-icon" sizes="180x180" href="/apple-icon-180x180.png">
<link rel="icon" type="image/png" href="/favicon-32x32.png" sizes="32x32">
<link rel="icon" type="image/png" href="/android-chrome-192x192.png" sizes="192x192">
<link rel="icon" type="image/png" href="/favicon-96x96.png" sizes="96x96">
<link rel="icon" type="image/png" href="/favicon-16x16.png" sizes="16x16">
<link rel="manifest" href="/manifest.json">
<meta name="apple-mobile-web-app-title" content="Elastic">
<meta name="application-name" content="Elastic">
<meta name="msapplication-TileColor" content="#ffffff">
<meta name="msapplication-TileImage" content="/mstile-144x144.png">
<meta name="theme-color" content="#ffffff">
<meta name="naver-site-verification" content="936882c1853b701b3cef3721758d80535413dbfd" />
<meta name="yandex-verification" content="d8a47e95d0972434" />
<meta name="localized" content="true" />
<meta name="st:robots" content="follow,index" />
<meta property="og:image" content="https://static-www.elastic.co/v3/assets/bltefdd0b53724fa2ce/blt280217a63b82a734/6202d3378b1f312528798412/elastic-logo.svg" />
<meta property="og:image:width" content="500" />
<meta property="og:image:height" content="172" />
<link rel="shortcut icon" href="/favicon.ico" type="image/x-icon">
<link rel="icon" href="/favicon.ico" type="image/x-icon">
<link rel="apple-touch-icon-precomposed" sizes="64x64" href="/favicon_64x64_16bit.png">
<link rel="apple-touch-icon-precomposed" sizes="32x32" href="/favicon_32x32.png">
<link rel="apple-touch-icon-precomposed" sizes="16x16" href="/favicon_16x16.png">
<!-- Give IE8 a fighting chance -->
<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
<![endif]-->
<link rel="stylesheet" type="text/css" href="/guide/static/styles.css" />
</head>
<!--© 2015-2022 Elasticsearch B.V. -->
<!-- All Elastic documentation is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License. -->
<!-- http://creativecommons.org/licenses/by-nc-nd/4.0/ -->
<body>
<!-- Google Tag Manager -->
<script>dataLayer = [];</script><noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-58RLH5" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src= '//www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-58RLH5');</script>
<!-- End Google Tag Manager -->
<!-- Global site tag (gtag.js) - Google Analytics -->
<script async src="https://www.googletagmanager.com/gtag/js?id=UA-12395217-16"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-12395217-16');
</script>
<!-- Google Tag Manager for GA4 -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src='https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);})(window,document,'script','dataLayer','GTM-KNJMG2M');</script>
<noscript><iframe src="https://www.googletagmanager.com/ns.html?id=GTM-KNJMG2M" height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
<!-- End Google Tag Manager for GA4-->
<div id='elastic-nav' style="display:none;"></div>
<script src='https://www.elastic.co/elastic-nav.js'></script>
<div class="main-container">
<section id="content" >
<div class="content-wrapper">
<section id="guide" lang="en">
<div class="container-fluid">
<div class="row pb-3">
<div class="col-12 order-2 col-md-4 order-md-1 col-lg-3 h-almost-full-md sticky-top-md" id="left_col">
<!-- The TOC is appended here -->
</div>
<div class="col-12 order-1 col-md-8 order-md-2 col-lg-7 order-lg-2 guide-section" id="middle_col">
<!-- start body -->
<div class="page_header">
<strong>IMPORTANT</strong>: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
<a href="../current/index.html">current release documentation</a>.
</div>
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="/guide/">Elastic Docs</a></span>
<span class="chevron-right">›</span><span class="breadcrumb-link"><a href="index.html">Installation and Upgrade Guide [6.4]</a></span>
</div>
<div class="navheader">
<span class="prev">
<a href="installing-elastic-stack.html">« Installing the Elastic Stack</a>
</span>
<span class="next">
</span>
</div>
<div class="chapter">
<div class="titlepage"><div><div>
<h1 class="title"><a id="upgrading-elastic-stack"></a>Upgrading the Elastic Stack<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/stack-docs/edit/6.4/docs/en/install-upgrade/upgrading-stack.asciidoc">edit</a></h1>
</div></div></div>
<p>When upgrading to a new version of Elasticsearch, you need to upgrade
each of the products in your Elastic Stack. Beats and Logstash 5.6 are
compatible with Elasticsearch 6.4.3 to give you flexibility in scheduling the
upgrade.</p>
<div class="sidebar">
<div class="titlepage"></div>
<p>The steps you need to take to upgrade differ depending on which products you
are using. Want a list that’s tailored to your stack? Try out our
<a href="/products/upgrade_guide" class="ulink" target="_top">Interactive Upgrade Guide</a>.</p>
</div>
<p>If you are running a pre-6.0 version, we recommend upgrading to the most
recent 5.6 before upgrading to 6.4.3. X-Pack 5.6
provides a free Upgrade Assistant that identifies issues you need to address
before upgrading and simplifies migrating indices that need to be reindexed
before you upgrade. The Upgrade Assistant is enabled with both Trial and
Basic licenses. You can install X-Pack solely for the purpose of upgrading. In
6.3 and later, X-Pack is automatically installed when you install Elasticsearch, Kibana,
and Logstash.</p>
<p>Rolling upgrades are supported when upgrading from Elasticsearch 5.6 and
Elasticsearch 6.0-6.2 to 6.4.3. Upgrading from any
version prior to 5.6 requires a full cluster restart.</p>
<div class="important admon">
<div class="icon"></div>
<div class="admon_content">
<p>2.x indices are not compatible with 6.4.3. You must
remove or reindex them on your 5.n cluster before upgrading to 6.4.3. The internal
Kibana and X-Pack indices and the default Beats and Logstash mapping templates
also need to be updated to work with 6.4.3.</p>
</div>
</div>
<h3><a id="_preparing_to_upgrade"></a>Preparing to upgrade<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/stack-docs/edit/6.4/docs/en/install-upgrade/upgrading-stack.asciidoc">edit</a></h3>
<p>Before upgrading the Elastic Stack to 6.4.3:</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
Back up your data. You <span class="strong strong"><strong>cannot roll back</strong></span> to an earlier version unless
you have a backup of your data. For information about creating snapshots, see
<a href="/guide/en/elasticsearch/reference/6.4/modules-snapshots.html" class="ulink" target="_top">Snapshot and Restore</a>.
</li>
<li class="listitem">
Check the Elasticsearch <a href="/guide/en/elasticsearch/reference/6.4/settings.html" class="ulink" target="_top">deprecation log</a> to see if
you’re using any deprecated features and update your code accordingly.
By default, deprecation log messages are enabled at the <code class="literal">WARN</code> level.
</li>
<li class="listitem">
<p>Review the breaking changes for each product you use
and make the necessary changes so your code is compatible with 6.4.3:</p>
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
<a href="/guide/en/beats/libbeat/6.4/breaking-changes.html" class="ulink" target="_top">Beats 6.4.3 breaking changes</a>
</li>
<li class="listitem">
<a href="/guide/en/elasticsearch/reference/6.4/breaking-changes.html" class="ulink" target="_top">Elasticsearch 6.4.3 breaking changes</a>
</li>
<li class="listitem">
<a href="/guide/en/elasticsearch/hadoop/6.4/breaking-changes.html" class="ulink" target="_top">Elasticsearch Hadoop 6.4.3 breaking changes</a>
</li>
<li class="listitem">
<a href="/guide/en/kibana/6.4/breaking-changes.html" class="ulink" target="_top">Kibana 6.4.3 breaking changes</a>
</li>
<li class="listitem">
<a href="/guide/en/logstash/6.4/breaking-changes.html" class="ulink" target="_top">Logstash 6.4.3 breaking changes</a>
</li>
</ul>
</div>
<div class="important admon">
<div class="icon"></div>
<div class="admon_content">
<div class="ulist itemizedlist">
<ul class="itemizedlist">
<li class="listitem">
If you’re upgrading from 2.n, make sure you check the breaking changes from
2.n to 5.n, as well as from 5.n to 6.n!
</li>
<li class="listitem">
If you are using machine learning datafeeds that contain discontinued search or query
domain specific language (DSL), the upgrade will fail. In 5.6.5 and later, the
Upgrade Assistant provides information about which datafeeds need to be updated.
</li>
</ul>
</div>
</div>
</div>
</li>
<li class="listitem">
<a href="/guide/en/elasticsearch/reference/6.4/docs-reindex.html" class="ulink" target="_top">Reindex</a> or delete any indices created on 2.n. We recommend
upgrading to the most recent 5.6 and using the X-Pack Reindex Helper to reindex 2.n indices.
</li>
<li class="listitem">
If Kibana and X-Pack are part of your stack, upgrade the internal Kibana
and X-Pack indices. We recommend using the X-Pack 5.6 Reindex Helper to
upgrade the internal indices. If you’re performing a full cluster restart upgrade
from an earlier version, you can also <a class="xref" href="upgrading-elastic-stack.html#upgrade-internal-indices" title="Upgrading internal indices for 6.x">use the
<code class="literal">_xpack/migration/upgrade</code> API</a> directly to upgrade the
internal indices after you install Elasticsearch 6.4.3.
</li>
<li class="listitem">
<p>If you use Elastic Stack security features to secure your cluster:</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
<p>Make sure TLS is enabled to encrypt communications between nodes. TLS must
be enabled to upgrade to 6.4.3. For more information, see
<a href="/guide/en/elasticsearch/reference/6.4/encrypting-communications.html" class="ulink" target="_top">Encrypting communications</a>.</p>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>Enabling TLS requires a full cluster restart. Nodes that have TLS
enabled cannot communicate with nodes that do not have TLS enabled. You must
restart all nodes to maintain communication across the cluster.</p>
</div>
</div>
</li>
<li class="listitem">
Make sure real passwords are configured for the built-in <code class="literal">elasticsearch</code>,
<code class="literal">kibana</code>, and <code class="literal">logstash_system</code> users. They cannot use the 5.n default
password (<code class="literal">changeme</code>). For more information, see
<a href="/guide/en/elasticsearch/reference/6.4/built-in-users.html" class="ulink" target="_top">Built-in users</a>.
</li>
</ol>
</div>
</li>
<li class="listitem">
Stop any X-Pack machine learning jobs that are running before starting the
upgrade process. See
<a href="/guide/en/machine-learning/6.4/stopping-ml.html" class="ulink" target="_top">Stopping machine learning</a>.
</li>
</ol>
</div>
<div class="important admon">
<div class="icon"></div>
<div class="admon_content">
<p>Test upgrades in a dev environment before upgrading your
production cluster.</p>
</div>
</div>
<h3><a id="upgrade-order-elastic-stack"></a>Upgrade order<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/stack-docs/edit/6.4/docs/en/install-upgrade/upgrading-stack.asciidoc">edit</a></h3>
<p>Upgrade the Elastic Stack products you use in the following order:</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
Elasticsearch Hadoop: <a href="/guide/en/elasticsearch/hadoop/6.4/install.html" class="ulink" target="_top">install instructions</a>
</li>
<li class="listitem">
Elasticsearch: <a href="/guide/en/elasticsearch/reference/6.4/setup-upgrade.html" class="ulink" target="_top">upgrade instructions</a>
</li>
<li class="listitem">
Kibana: <a href="/guide/en/kibana/6.4/upgrade.html" class="ulink" target="_top">upgrade instructions</a>
</li>
<li class="listitem">
Logstash: <a href="/guide/en/logstash/6.4/upgrading-logstash.html" class="ulink" target="_top">upgrade instructions</a>
</li>
<li class="listitem">
Beats: <a href="/guide/en/beats/libbeat/6.4/upgrading.html" class="ulink" target="_top">upgrade instructions</a>
</li>
</ol>
</div>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>Logstash 5.6 and 6.n and Beats 5.6 and 6.n are compatible with all 6.n versions of
Elasticsearch. This provides flexibility in when you schedule the upgrades
for your Logstash instances and Beats agents. We recommend upgrading Logstash
and Beats as soon as possible to take advantage of performance improvements
and other enhancements.</p>
</div>
</div>
<h3><a id="_upgrading_to_6_3"></a>Upgrading to 6.3<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/stack-docs/edit/6.4/docs/en/install-upgrade/upgrading-stack.asciidoc">edit</a></h3>
<p>Starting in 6.3, the default distributions of Elasticsearch, Logstash, and Kibana
include X-Pack and a free Basic license that never expires.</p>
<p>You can perform rolling upgrades to 6.3 from OSS-only clusters running 5.6
or 6.0-6.2. Basic features are operational once the cluster is fully
upgraded. If you are already using X-Pack, your settings are preserved when
you upgrade.</p>
<p>If you are using X-Pack for the first time, you must explicitly enable data
collection after the upgrade to use monitoring. Set
<code class="literal">xpack.monitoring.collection.enabled</code> to <code class="literal">true</code> with the <code class="literal">_cluster/settings</code>
API:</p>
<div class="pre_wrapper lang-console">
<pre class="programlisting prettyprint lang-console">PUT /_cluster/settings
{
"persistent" : {
"xpack.monitoring.collection.enabled" : "true"
}
}</pre>
</div>
<div class="console_widget" data-snippet="snippets/1.console"></div>
<p>To take more of the Elastic Stack features for a spin, you can start a 30-day trial
from Kibana or with the Start Trial API:</p>
<div class="pre_wrapper lang-console">
<pre class="programlisting prettyprint lang-console">POST _xpack/license/start_trial</pre>
</div>
<div class="console_widget" data-snippet="snippets/2.console"></div>
<p>The 30-day trial enables you to try out the full set of platinum features,
including security, machine learning, alerting, graph capabilities, and more.</p>
<h3><a id="xpack-stack-upgrade"></a><span class="xpack">Upgrading from 5.6</span><a class="xpack_tag" href="/subscriptions"></a><a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/stack-docs/edit/6.4/docs/en/install-upgrade/upgrading-stack.asciidoc">edit</a></h3>
<p>X-Pack 5.6 provides migration and upgrade APIs for Elasticsearch and a
Upgrade Assistant UI for Kibana. These tools are included with the trial
license and the free basic license.</p>
<p>To upgrade to 6.4.3 from 5.6:</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
<p><a href="/guide/en/elasticsearch/reference/6.4/setup-upgrade.html" class="ulink" target="_top">Upgrade Elasticsearch</a> to the most recent 5.6 and
install X-Pack on all nodes in your cluster. If you are upgrading from an
earlier 5.x release, you can perform a rolling upgrade. To upgrade from older
versions you must perform a full cluster restart.</p>
<p>If your trial license expires,
<a href="https://register.elastic.co/" class="ulink" target="_top">register for a free Basic license</a>. To apply the
license, upload the license file with the <code class="literal">license</code> API:</p>
<div class="pre_wrapper lang-json">
<pre class="programlisting prettyprint lang-json">license -d @license.json</pre>
</div>
</li>
<li class="listitem">
<p>If X-Pack <span class="strong strong"><strong>IS NOT</strong></span> normally a part of your Elastic Stack, disable the
Elasticsearch security features in <code class="literal">elasticsearch.yml</code>:</p>
<div class="pre_wrapper lang-yaml">
<pre class="programlisting prettyprint lang-yaml">xpack.security.enabled: false</pre>
</div>
</li>
<li class="listitem">
Upgrade Kibana to the most recent 5.6 and install X-Pack.
</li>
<li class="listitem">
<p>If you disabled the Elasticsearch security features, also disable the Kibana
security features in <code class="literal">kibana.yml</code>:</p>
<div class="pre_wrapper lang-yaml">
<pre class="programlisting prettyprint lang-yaml">xpack.security.enabled: false</pre>
</div>
</li>
<li class="listitem">
<p>Use the Upgrade Assistant in Kibana to
view incompatibilities that you need to fix, identify any 2.x indices that
need to be migrated or deleted, and upgrade the internal indices to the
6.x index format.</p>
<p>You can also call the Elasticsearch migration APIs directly:</p>
<div class="variablelist">
<dl class="variablelist">
<dt>
<span class="term">
<code class="literal">/_xpack/migration/assistance</code>
</span>
</dt>
<dd>
Runs a series of checks on your cluster,
nodes, and indices and returns a list of issues that need to be
fixed before you can upgrade to 6.4.3.
</dd>
<dt>
<span class="term">
<code class="literal">/_xpack/migration/upgrade</code>
</span>
</dt>
<dd>
Upgrades the Watcher and Security indices to a
single-type format compatible with Elasticsearch 6.x.
</dd>
</dl>
</div>
</li>
<li class="listitem">
Once you’ve resolved all of the migration issues, perform
a <a href="/guide/en/elasticsearch/reference/6.4/rolling-upgrades.html" class="ulink" target="_top">rolling upgrade</a> from Elasticsearch 5.6 to 6.4.3.
</li>
</ol>
</div>
<h3><a id="oss-stack-upgrade"></a>Upgrading from a pre-5.6 installation<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/stack-docs/edit/6.4/docs/en/install-upgrade/upgrading-stack.asciidoc">edit</a></h3>
<p>It is possible to upgrade directly to 6.x from a pre-5.6 installation,
but it requires a <a href="/guide/en/elasticsearch/reference/6.4/restart-upgrade.html" class="ulink" target="_top">full cluster restart</a> and you must
manually reindex any 2.x indices you need to carry forward to 6.x.</p>
<div class="important admon">
<div class="icon"></div>
<div class="admon_content">
<p>If you use Kibana or X-Pack, you also need to upgrade the
internal Kibana and X-Pack indices. For information about upgrading them
after you install Elasticsearch 6.4.3, see
<a class="xref" href="upgrading-elastic-stack.html#upgrade-internal-indices" title="Upgrading internal indices for 6.x">Upgrading internal indices</a>.</p>
</div>
</div>
<p>To manually reindex a 2.x index:</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
Create an index with 6.x compatible mappings.
</li>
<li class="listitem">
Use the <a href="/guide/en/elasticsearch/reference/6.4/docs-reindex.html" class="ulink" target="_top">reindex API</a> to copy documents from the
2.x index into the new index. You can use a script to perform any necessary
modifications to the document data and metadata during reindexing.
</li>
<li class="listitem">
Use the <a href="/guide/en/elasticsearch/reference/6.4/indices-aliases.html" class="ulink" target="_top">_aliases</a> API to add the name of the 2.x
index as alias for the new index and delete the 2.x index.
</li>
</ol>
</div>
<h4><a id="upgrade-internal-indices"></a>Upgrading internal indices for 6.x<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/stack-docs/edit/6.4/docs/en/install-upgrade/upgrading-stack.asciidoc">edit</a></h4>
<p>The format used for the internal indices used by Kibana and X-Pack has
changed in 6.x. Before you can run Kibana and X-Pack in 6.4.3,
these indices must be upgraded to the new format. If you are upgrading from a
version prior to 5.6, you must upgrade them after after installing
Elasticsearch 6.4.3.</p>
<p>To get a list of the indices that need to be upgraded, install X-Pack and use
the <a href="/guide/en/elasticsearch/reference/6.4/migration-api-assistance.html" class="ulink" target="_top"><code class="literal">_xpack/migration/assistance</code> API</a>:</p>
<div class="pre_wrapper lang-console">
<pre class="programlisting prettyprint lang-console">GET /_xpack/migration/assistance</pre>
</div>
<div class="console_widget" data-snippet="snippets/3.console"></div>
<p>To upgrade the <code class="literal">.security</code> index:</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
On a single node, add a temporary superuser account to the <code class="literal">file</code> realm.
</li>
<li class="listitem">
<p>Use the <a href="/guide/en/elasticsearch/reference/6.4/migration-api-upgrade.html" class="ulink" target="_top"><code class="literal">_xpack/migration/upgrade</code></a>
API to upgrade the security index, submitting the request with the credentials
for the temporary superuser:</p>
<div class="pre_wrapper lang-console">
<pre class="programlisting prettyprint lang-console">POST /_xpack/migration/upgrade/.security</pre>
</div>
<div class="console_widget" data-snippet="snippets/4.console"></div>
</li>
<li class="listitem">
Delete the temporary superuser account from the file realm.
</li>
</ol>
</div>
<p>You can use your regular administration credentials to upgrade the other
internal indices using the <code class="literal">_xpack/migration/upgrade</code> API.</p>
<div class="tip admon">
<div class="icon"></div>
<div class="admon_content">
<p>Once you upgrade the <code class="literal">.kibana</code> index, you can run Kibana and use the
X-Pack Reindex Helper UI to upgrade the other indices.</p>
</div>
</div>
<h3><a id="upgrade-elastic-stack-for-elastic-cloud"></a>Upgrading on Elastic Cloud<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/stack-docs/edit/6.4/docs/en/install-upgrade/upgrading-stack.asciidoc">edit</a></h3>
<p>A single click in the Elastic Cloud console can upgrade a cluster to a newer
version, add more processing capacity, change plugins, and enable or disable
high availability, all at the same time. During the upgrade process,
Elasticsearch, Kibana, X-Pack and the officially included plugins are
upgraded simultaneously.</p>
<p>Although upgrading your Elastic Cloud clusters is easy, you still need to
address breaking changes that affect your application. Minor version upgrades,
upgrades from 5.6 to 6.x, and all other cluster configuration
changes can be performed with no downtime.</p>
<p>To avoid downtime when a full cluster restart is required:</p>
<div class="olist orderedlist">
<ol class="orderedlist">
<li class="listitem">
Provision an additional cluster with the new Elasticsearch version, reindex
your data, and send index requests to both clusters temporarily.
</li>
<li class="listitem">
Verify that the new cluster performs as expected, fix any problems, and then
permanently swap in the new cluster.
</li>
<li class="listitem">
Delete the old cluster to stop incurring additional costs. You are billed
only for the time that the new cluster runs in parallel with your old cluster.
Usage is billed on an hourly basis.
</li>
</ol>
</div>
<p>To learn more about the upgrade process on Elastic Cloud, see
<a href="/guide/en/cloud/current/ec-upgrade-deployment.html" class="ulink" target="_top">Upgrade versions</a>.</p>
<div class="note admon">
<div class="icon"></div>
<div class="admon_content">
<p>Elastic Cloud only supports upgrades to released versions. Preview
releases and master snapshots are not supported.</p>
</div>
</div>
</div>
<div class="navfooter">
<span class="prev">
<a href="installing-elastic-stack.html">« Installing the Elastic Stack</a>
</span>
<span class="next">
</span>
</div>
</div>
<!-- end body -->
</div>
<div class="col-12 order-3 col-lg-2 order-lg-3 h-almost-full-lg sticky-top-lg" id="right_col">
<div id="sticky_content">
<!-- The OTP is appended here -->
<div class="row">
<div class="col-0 col-md-4 col-lg-0" id="bottom_left_col"></div>
<div class="col-12 col-md-8 col-lg-12">
<div id="rtpcontainer">
<div class="mktg-promo" id="most-popular">
<p class="aside-heading">Most Popular</p>
<div class="pb-2">
<p class="media-type">Video</p>
<a href="https://www.elastic.co/webinars/getting-started-elasticsearch?baymax=default&elektra=docs&storm=top-video">
<p class="mb-0">Get Started with Elasticsearch</p>
</a>
</div>
<div class="pb-2">
<p class="media-type">Video</p>
<a href="https://www.elastic.co/webinars/getting-started-kibana?baymax=default&elektra=docs&storm=top-video">
<p class="mb-0">Intro to Kibana</p>
</a>
</div>
<div class="pb-2">
<p class="media-type">Video</p>
<a href="https://www.elastic.co/webinars/introduction-elk-stack?baymax=default&elektra=docs&storm=top-video">
<p class="mb-0">ELK for Logs & Metrics</p>
</a>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</section>
</div>
<div id='elastic-footer'></div>
<script src='https://www.elastic.co/elastic-footer.js'></script>
<!-- Footer Section end-->
</section>
</div>
<script src="/guide/static/jquery.js"></script>
<script type="text/javascript" src="/guide/static/docs.js"></script>
<script type="text/javascript">
window.initial_state = {}</script>
</body>
</html>