Documentation: add note for etcd-io#11689 (etcd-io#11759)

Documentation/upgrades/upgrade_3_3.md

@@ -12,6 +12,9 @@ Before [starting an upgrade](#upgrade-procedure), read through the rest of this
 
 **NOTE:** When [migrating from v2 with no v3 data](https://github.com/etcd-io/etcd/issues/9480), etcd server v3.2+ panics when etcd restores from existing snapshots but no v3 `ETCD_DATA_DIR/member/snap/db` file. This happens when the server had migrated from v2 with no previous v3 data. This also prevents accidental v3 data loss (e.g. `db` file might have been moved). etcd requires that post v3 migration can only happen with v3 data. Do not upgrade to newer v3 versions until v3.0 server contains v3 data.
 
+**NOTE:** if you enable auth and use lease(lease ttl is small),it has a high probability to encounter [issue](https://github.com/etcd-io/etcd/issues/11689) that will result in data inconsistency. It is strongly recommended to upgrade to the latest version of 3.2 to fix this problem, and then upgrade to 3.3. The latest version is not yet available, please pay attention to [changelog](https://github.com/etcd-io/etcd/blob/master/CHANGELOG-3.2.md).
+
+
 Highlighted breaking changes in 3.3.
 
 #### Changed value type of `etcd --auto-compaction-retention` flag to `string`