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

[MikeH1999]

Checklist

• This is not a question or a support request. If you have any boost related questions, please ask in the discussion forum.
• This is not a new feature request. If it is, please file a feature request instead.
• This is not an enhancement request. If it is, please file a improvement suggestion instead.
• I have searched on the issue tracker and the discussion forum, and there is no existing related issue or discussion.
• I am running the Latest release, 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.
• 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

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

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 '...'
   ...

[zelin44913]

I also encountered the same problem, but I used multiple boostd-data programs for multiple databases, but these databases were running on the same yugabyte

boostd version 2.4.3

2025-05-30T00:40:56+08:00 203.160.84.158 GET "/piece/baga6ea4seaqkhycdxiqpm63hwb37a5vwotjclqdh7fd3ui5zq3cozllnngrgami" 500 0 0 - "Go-http-client/1.1" "server error getting content for piece CID baga6ea4seaqkhycdxiqpm63hwb37a5vwotjclqdh7fd3ui5zq3cozllnngrgami: getting unsealed CAR file: checking unsealed status of 2 deals containing piece baga6ea4seaqkhycdxiqpm63hwb37a5vwotjclqdh7fd3ui5zq3cozllnngrgami - 1 are sealed, 1 had errors: [Deal 116500428: Sector 4521 Deal 123456: Sector 4706]: 1 error occurred:\n\t* is unsealed: no endpoint registered for miner BMiner, len(readers)=1\n\n"