congqixia

@yhmo checked all .out files(which I guess is the err output), all query node panicked due to Segment Violation: ``` [signal SIGSEGV: segmentation violation code=0x1 addr=0x7fb28c000018 pc=0x7fbeebc5644a] runtime stack: runtime.throw(0x2e6f15b,...

@BUPTAnderson could you please provide the actual commit you compile with? Need to verify whether this problem still persist. Thanks in advance!

/assign @bigsheeper

@ThreadDao #17111 shall fix the load balance failure problem. Could you please verify?

@ThreadDao According to the log (Line 377-412), the first load balance is successful. ``` [2022/05/19 15:28:34.100 +00:00] [INFO] [query_coord.go:634] ["loadBalanceSegmentLoop: memory usage rate of all online QueryNode"] [collection=433317243251789121] [replica=433317010215796743] ["mem...

@ThreadDao segment info not changed issue might be related to an known issue for querySegmentInfo API. Let's check after fix PR merged.

@ThreadDao There are several fix for load balance, does this problem still persist?

It make sense that `entityExpiration` should be an attribute of a collection. Shall we make it mutable, which could be alter by DDL? Or make it immutable, which is determined...

Let's keep this open.

I think this feature is still needed. Let's keep it open.