congqixia

Hi @AnandKumarTokopedia. Thanks for the reply. From the code snippet, it seems that you are using 1.X SDK. Are you using 1.X milvus instance?

> @congqixia Can you please help let me know how to check that @AnandKumarTokopedia How did you install Milvus? Using Docker image or just built it from source code?

> It was using docker @congqixia @AnandKumarTokopedia then could you please provide the docker logs from milvus container?

Hi @spookyy, from the error you provided it looks like you're trying to upgrade from sdk v1.1.0 to v2. Note that sdk-v2 is strictly for milvus2.0+, it cannot be used...

Hi @xiyichan , looks like this repo needs the pr sync with master branch. Could you please rebase your pr to latest master commit? I tried in github page but...

Related to https://github.com/milvus-io/milvus/issues/7522

After discussion with @longjiquan , the preliminary conclusions are, there are two parts of implementation which caused this symptom: - When doing `segment.Search` in `QueryNode`, milvus dispatches a new goroutine...

Submit a quick fix to limit cgo call concurrency with GOMAXPROC (cpu number) #18461

@yanliang567 just checked the last standalone run of CI(ms-18745-3). The os threads number(go runtime) is 71 at most. It's expected to have more thread in OpenMP thread pool but still...

@zhuwenxing the log is not complete for second deploy. Also, milvus standalone crashed at very start point of second deploy: ``` [2022/09/05 03:05:47.281 +00:00] [DEBUG] [server/rocksmq_impl.go:157] ["Start rocksmq "] ["max...