How to solve the problem of several miner in the same data center sharing the same boostd-data program during retrieval

### Checklist

- [x] This is **not** a question or a support request. If you have any boost related questions, please ask in the [discussion forum](https://github.com/filecoin-project/boost/discussions).
- [x] This is **not** a new feature request. If it is, please file a [feature request](https://github.com/filecoin-project/boost/issues/new?assignees=&labels=need%2Ftriage%2Ckind%2Ffeature&template=feature_request.yml) instead.
- [x] This is **not** an enhancement request. If it is, please file a [improvement suggestion](https://github.com/filecoin-project/boost/issues/new?assignees=&labels=need%2Ftriage%2Ckind%2Fenhancement&template=enhancement.yml) instead.
- [x] I **have** searched on the [issue tracker](https://github.com/filecoin-project/boost/issues) and the [discussion forum](https://github.com/filecoin-project/boost/discussions), and there is no existing related issue or discussion.
- [x] I am running the [`Latest release`](https://github.com/filecoin-project/boost/releases), or the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
- [x] I did not make any code changes to boost.

### Boost component

- [ ] boost daemon - storage providers
- [ ] boost client
- [ ] boost UI
- [ ] boost data-transfer
- [ ] boost index-provider
- [ ] Other

### Boost Version

```text
boostd version 2.4.2
```

### Describe the Bug

How to solve the problem of several miner in the same data center sharing the same boostd-data program during retrieval

```
http://14.17.107.56:7777/ipfs/bafybeigxnwe6y3amuybgxaykcq5d3ezgxudvkiefi5uwegjmkws2h2dm6i?dag-scope=block

failed to load root node: failed to load root CID: 1 error occurred:
* getting piece reader: 3 errors occurred:
* get reader: no endpoint registered for miner f03499888, len(readers)=1
* get reader: no endpoint registered for miner f03373337, len(readers)=1
* checking unsealed state of sector 4: failed to get sector info: RPC client error: unmarshaling result: failed to parse big string: 'null'
```

### Logging Information

```text
failed to load root node: failed to load root CID: 1 error occurred:
* getting piece reader: 3 errors occurred:
* get reader: no endpoint registered for miner f03499888, len(readers)=1
* get reader: no endpoint registered for miner f03373337, len(readers)=1
* checking unsealed state of sector 4: failed to get sector info: RPC client error: unmarshaling result: failed to parse big string: 'null'
```

### Repo Steps

1. Run '...'
2. Do '...'
3. See error '...'
...

Start by reproducing the retrieval request against boostd-data version 2.4.2 and inspect the reported endpoint and sector-info errors. The issue names no files or tests; completion would require a documented, working configuration for several miners sharing one boostd-data instance, with the retrieval request succeeding.

Written by the indexing model from the issue text.