xiaozhuang

yes，it's kubernetes ’s problem，I'm already aware of it。thanks

> @xiaozhuang-a did you use any module? and can you give the fully crash log? Not using any module This is the complete crash log

> @xiaozhuang-a did you use any module? and can you give the fully crash log? Are we affected by the large and high concurrency use of 'stream' and 'block' in...

> yes, it's probably block related. > yes, it's probably block related. There is a way to avoid this crash, let's complete the rebalance

> @xiaozhuang-a do you mean you wanna avoid this crash? you can temporarily close `serverAssert(c->duration == 0);`, in theory it should have no side effects. yes ths

yes,I think the hot update mechanism is necessary.

Has this issue been resolved? I still have this error in milvus version 2.2.10. Can you help me resolve it

dataNode： ```bash [2023/07/29 15:43:27.374 +00:00] [INFO] [datanode/flow_graph_insert_buffer_node.go:469] ["insertBufferNode syncing BufferData"] [segmentID=442776935130016392] [flushed=false] [dropped=false] [auto=false] [position="channel_name:\"by-dev-rootcoord-dml_444_442776935130016343v0\" msgID:\"\\010\\225\\227\\202\\001\\020\\214\\230\\001\\030\\000 \\000\" msgGroup:\"by-dev-dataNode-55-by-dev-rootcoord-dml_444_442776935130016343v0\" timestamp:443192549629755393 "] [channel=by-dev-rootcoord-dml_444_442776935130016343v0] [2023/07/29 15:43:27.374 +00:00] [INFO] [datanode/flush_manager.go:287] ["handling insert task"] ["segment...

> It needs to be fixed. Do you have any solutions I understand. Can we solve this by not distinguishing between leaders and followers in STS ？ or rather, what...