linggong2023

not 2.2.4，upgrade to 2.2.6

When a new instance of Milvus version 2.2.6 is created, there are no problems using Attu. However, when upgrading the data based on version 2.2.0, Attu will report the error...

[2023/04/24 08:52:55.373 +00:00] [INFO] [proxy/impl.go:689] ["DescribeCollection done"] [traceID=63be3d4e51a1dd30] [role=proxy] [MsgID=441011765345517569] [BeginTS=441011765345517569] [EndTS=441011765345517569] [db=] [collection=test_json_milvus] [2023/04/24 08:52:55.375 +00:00] [INFO] [proxy/meta_cache.go:682] ["no shard cache for collection, try to get shard leaders from...

[logs.tar.gz](https://github.com/milvus-io/milvus/files/11308582/logs.tar.gz)

[logs.tar.gz](https://github.com/milvus-io/milvus/files/11309732/logs.tar.gz)

[bw_etcd_ALL.230425-031739.bak.gz](https://github.com/milvus-io/milvus/files/11316136/bw_etcd_ALL.230425-031739.bak.gz)

[logs.tar.gz](https://github.com/milvus-io/milvus/files/11624084/logs.tar.gz)

2.2.6 query is not respons [logs.tag.gz](https://github.com/milvus-io/milvus/files/11631540/logs.tag.gz)

[bw_etcd_ALL.230423-070110.bak.gz](https://github.com/milvus-io/milvus/files/11303044/bw_etcd_ALL.230423-070110.bak.gz)

If we upgrade to 2.2.6, can it fix that issue?