Fabriceli opened a new pull request, #9204:
URL: https://github.com/apache/apisix/pull/9204
### Description
Thank you for your previous work @dyrnq
Create TWO threads to watch the catalog services and health services:
```mermaid
flowchart TD
subgraph Thread 1: watch catalog
A[Start] --> catalog{Catalog any change?}
catalog -->|Yes| cindex[return catalog index]
catalog ---->|No| E[End]
cindex --> E
end
subgraph Thread 2: watch health
A2[Start] --> health2{health any change?}
health2 -->|Yes| hindex[return health index]
health2 ---->|No| E2[End]
hindex --> E2
end
subgraph Wait any thread
A3[Start] --> spawn[Spawn TWO threads]
spawn --> wait[wait any Thread]
wait --> catalog2[Query all services]
catalog2 --> H[Query health nodes]
H --> update[Update all services]
update --> e[End]
end
```
Fixes # (issue)
Reference: #8856, https://github.com/apache/apisix/issues/8928
### Checklist
- [x] I have explained the need for this PR and the problem it solves
- [x] I have explained the changes or the new features added to this PR
- [x] I have added tests corresponding to this change
- [ ] I have updated the documentation to reflect this change
- [x] I have verified that this change is backward compatible (If not,
please discuss on the [APISIX mailing
list](https://github.com/apache/apisix/tree/master#community) first)
<!--
Note
1. Mark the PR as draft until it's ready to be reviewed.
2. Always add/update tests for any changes unless you have a good reason.
3. Always update the documentation to reflect the changes made in the PR.
4. Make a new commit to resolve conversations instead of `push -f`.
5. To resolve merge conflicts, merge master instead of rebasing.
6. Use "request review" to notify the reviewer after making changes.
7. Only a reviewer can mark a conversation as resolved.
-->
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
