You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -304,11 +283,10 @@ Highlighted breaking changes in 3.6.
304
283
305
284
```
306
285
307
-
# Same flag different defaults
286
+
###Same flag different defaults
308
287
309
288
**Original default flag `etcd --snapshot-count=100000`**
310
289
311
-
312
290
```diff
313
291
314
292
-etcd --snapshot-count=100000
@@ -319,7 +297,6 @@ Highlighted breaking changes in 3.6.
319
297
320
298
**Original default flag `etcd --v2-deprecation='not-yet'`**
321
299
322
-
323
300
```diff
324
301
325
302
-etcd --v2-deprecation='not-yet'
@@ -330,23 +307,22 @@ Highlighted breaking changes in 3.6.
330
307
331
308
**Original default flag `etcd --discovery-fallback='proxy'`**
332
309
333
-
334
310
```diff
335
311
336
312
-etcd --discovery-fallback='proxy'
337
313
338
314
+etcd --discovery-fallback='exit'
339
315
340
316
```
341
-
#### Difference in Prometheus metrics
317
+
318
+
### Difference in Prometheus metrics
342
319
343
320
```diff
344
321
# metrics added in 3.6
345
322
+etcd_network_known_peers
346
323
+etcd_server_feature_enabled
347
324
```
348
325
349
-
350
326
### Server upgrade checklists
351
327
352
328
#### Upgrade requirements
@@ -369,7 +345,7 @@ While upgrading, an etcd cluster supports mixed versions of etcd members, and op
369
345
370
346
If this cluster has been in use since etcd v2, there are some additional requirements.
371
347
372
-
First, if you are upgrading stepwise from etcd v2 to etcd v3.6, you need to take care that the database is initialized with v3 data. See the [v2 data upgrade issue](https://github.com/etcd-io/etcd/issues/9480) for more details.
348
+
First, if you are upgrading stepwise from etcd v2 to etcd v3.6, you need to take care that the database is initialized with v3 data. See the [v2 data upgrade issue](https://github.com/etcd-io/etcd/issues/9480)and [etcd v2 to v3 migration guide](https://etcd.io/docs/v3.6/tutorials/how-to-migrate/)for more details.
373
349
374
350
If the cluster is serving a v2 data set larger than 50MB, each newly upgraded member may take up to two minutes to catch up with the existing cluster. Check the size of a recent snapshot to estimate the total data size. In other words, it is safest to wait for 2 minutes between upgrading each member.
375
351
@@ -512,7 +488,7 @@ Restart the etcd server with same configuration but with the new etcd binary.
0 commit comments