[Bug]: Etcd is abnormal, milvus keeps generating coredump.

[zhoujiaqi1998]

Is there an existing issue for this?

• [X] I have searched the existing issues

Environment

- Milvus version:2.4.1
- Deployment mode(standalone or cluster):cluster and standalone
- MQ type(rocksmq, pulsar or kafka):    pulsar and rocksmq
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

The program can exit, but I think generating a core dump is abnormal. https://github.com/milvus-io/milvus/issues/36774

Expected Behavior

No response

Steps To Reproduce

https://github.com/milvus-io/milvus/issues/36774

Milvus Log

milvus.log

Anything else?

No response

[yanliang567]

@czs007 can we not coredump here in this case?

/assign @czs007 /unassign

[zhoujiaqi1998]

I think the default value 'all' is better. https://github.com/milvus-io/milvus/blob/v2.4.13/pkg/util/symbolizer/symbolizer.go#L26C2-L26C29

[xiaofan-luan]

O think this only means we print all stack when server crash. Not related to core dump I believe

[zhoujiaqi1998]

The value is 'crash ', which will generate a core dump when running a panic. If you want to print an all stack, you can set it to 'all '.

[xiaofan-luan]

@zhoujiaqi1998 if we make this a configurable param and default with "all" I think is should be just fine

[zhoujiaqi1998]

@zhoujiaqi1998 if we make this a configurable param and default with "all" I think is should be just fine

good idea.

[xiaofan-luan]

@zhoujiaqi1998 if we make this a configurable param and default with "all" I think is should be just fine

good idea.

could you generate a pr for this?