[Bug]: querynode has too many logs

[iytprince2]

Is there an existing issue for this?

• I have searched the existing issues

Environment

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

Current Behavior

there are too many logs in querynode causing k8s node crashes, the logs like
2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]
[2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]
[2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]
[2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]
[2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]
[2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]
[2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]
[2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]
[2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]
[2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]
[2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]
[2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]
[2023/09/11 03:52:55.228 +00:00] [WARN] [flowgraph/node.go:204] ["Invalid operate message input"] ["input length"=0]

Expected Behavior

there are little logs

Steps To Reproduce

noop

Milvus Log

noop

Anything else?

noop

[yanliang567]

@jiaoew1991 what these logs for, can we improve that?
/assign @jiaoew1991
/unassign

[jiaoew1991]

These logs indicate that there is channel multiplexing, and during recovery, data from other collections needs to be filtered out.
These log contents are indeed useless, we need to limit the frequency.

@congqixia what do you think?

[xiaofan-luan]

we should remove it agreed

[jiaoew1991]

/assign @smellthemoon
/unassign
plz help on this issue