congqixia 1eacdc591b

fix: delegator may mark segment offline by mistake (#29343) ...

See also #29332

The segment may be released before or during the request when delegator
tries to forward delete request to yet. Currently, these two situation
returns different error code.

In this particular case, `ErrSegmentNotLoaded` and `ErrSegmentNotFound`
shall both be ignored preventing return search service unavailable by
mistake.

---------

Signed-off-by: Congqi Xia <congqi.xia@zilliz.com>

2023-12-20 21:22:43 +08:00

..

deletebuffer

Format the code (#27275)

2023-09-21 09:45:27 +08:00

delegator_data_test.go

fix: delegator may mark segment offline by mistake (#29343)

2023-12-20 21:22:43 +08:00

delegator_data.go

fix: delegator may mark segment offline by mistake (#29343)

2023-12-20 21:22:43 +08:00

delegator_test.go

fix: correct autoindex segment num (#28387)

2023-11-22 11:12:22 +08:00

delegator.go

fix: correct autoindex segment num (#28387)

2023-11-22 11:12:22 +08:00

distribution_test.go

Refine offline segments logic in shard delegator (#28073)

2023-11-01 20:04:24 +08:00

distribution.go

Refine offline segments logic in shard delegator (#28073)

2023-11-01 20:04:24 +08:00

mock_delegator.go

Refine queryHook mockery (#27394)

2023-09-28 10:01:26 +08:00

OWNERS

Fix offline set always nil (#23340)

2023-04-11 14:42:30 +08:00

snapshot_test.go

load segment with target version, avoid read redundant segment (#24929)

2023-06-27 11:48:45 +08:00

snapshot.go

Make snapshot.expired atomic (#25177)

2023-06-27 18:12:45 +08:00

types.go

Format the code (#27275)

2023-09-21 09:45:27 +08:00