java的sdk版本：2.2.13
milvus版本：2.2.16

突然sdk报错：

c.e.c.k.b.s.milvus.MilvusHandler -1 – {“exception”:”java.lang.Exception: syncTimestamp Failed:stack trace: /go/src/github.com/milvus-io/milvus/internal/util/trace/stack_trace.go:51 github.com/milvus-io/milvus/internal/util/trace.StackTracen/go/src/github.com/milvus-io/milvus/internal/util/grpcclient/client.go:369 github.com/milvus-io/milvus/internal/util/grpcclient.(*ClientBase[…]).Calln/go/src/github.com/milvus-io/milvus/internal/util/grpcclient/client.go:382 github.com/milvus-io/milvus/internal/util/grpcclient.(*ClientBase[…]).ReCalln/go/src/github.com/milvus-io/milvus/internal/distributed/rootcoord/client/client.go:424 github.com/milvus-io/milvus/internal/distributed/rootcoord/client.(*Client).AllocTimestampn/go/src/github.com/milvus-io/milvus/internal/proxy/timestamp.go:61 github.com/milvus-io/milvus/internal/proxy.(*timestampAllocator).allocn/go/src/github.com/milvus-io/milvus/internal/proxy/timestamp.go:83 github.com/milvus-io/milvus/internal/proxy.(*timestampAllocator).AllocOnen/go/src/github.com/milvus-io/milvus/internal/proxy/task_scheduler.go:174 github.com/milvus-io/milvus/internal/proxy.(*baseTaskQueue).Enqueuen/go/src/github.com/milvus-io/milvus/internal/proxy/impl.go:3063 github.com/milvus-io/milvus/internal/proxy.(*Proxy).Searchn/go/src/github.com/milvus-io/milvus/internal/distributed/proxy/service.go:876 github.com/milvus-io/milvus/internal/distributed/proxy.(*Server).Searchn/go/pkg/mod/github.com/milvus-io/milvus-proto/go-api/[email protected]/milvuspb/milvus.pb.go:11330 github.com/milvus-io/milvus-proto/go-api/v2/milvuspb._MilvusService_Search_Handler.func1: empty grpc client: find no available rootcoord, check rootcoord state”,”status”:1}

没有找到具体的原因，猜测可能是因为混合查询之后，没有releaseCollection，导致内存不够用了，然后attu上的QueryCoord，IndexCoord，DataCoord全都没有了

如果先loadCollection，然后混合查询之后，不releaseCollection会怎么样？