[Bug]: filter indexed segments failed about milvus HOT 9 OPEN

@TonyAnn How did you deploy milvus? According to the log of index node, it seems that some permissions are missing.

from milvus.

@SimFG hi sim, milvus cluster deployed via helm in kubernetes

from milvus.

You also need to confirm whether the etcd service is normal, because etcd also has failed operations during the indexnode startup process.

from milvus.

@SimFG By checking the log and command line, etcd is fine.
etcdctl --endpoints=http://10.96.1.142:2379 endpoint health
http://10.96.1.142:2379 is healthy: successfully committed proposal: took = 2.873091ms

from milvus.

@TonyAnn You can try to redeploy milvus. According to the log, there should be a problem with the index node startup that caused the entire milvus to fail to start.

from milvus.

@TonyAnn What version of milvus did you use?

from milvus.

@TonyAnn What version of milvus did you use?

@SimFG version is 2.2.14

from milvus.

You can try the latest milvus version. I checked the logs and the core reason is not because of permissions. If you want to solve the permission warn, you can try to add the following configuration in the deployment:

 securityContext:
   capabilities:
     add: ["SYS_NICE"]

It seems to be mainly abnormal in connecting to etcd. I recommend trying the latest version, because we rarely maintain 2.2.x now. The latest version of milvus is 2.4.3

from milvus.

please use v2.4.4
/assign @TonyAnn

from milvus.