kayx23 commented on issue #10192:
URL: https://github.com/apache/apisix/issues/10192#issuecomment-1719200460

   
   > I don't see an option to attach screenshots.
   
   Either pasting from the clipboard or dragging and dropping to the input box 
should work.
   
   > UPSTREAM Microservice 1: ms1-1.mydomain.com pointing to host1 and 
ms1-2.mydomain.com pointing to Host2
   
   Here do you mean Host 1 nginx routes to ms1-1 and Host 2 nginx routes to 
ms1-2? In other words, NGINX services are _in front of_ these upstream 
miscroservices, correct?
   
   If that's the case, I fail to understand how these two upstreams jinx with 
each other:
   
   > The health checks of UPSTREAM Microservice 1 affect UPSTREAM Microservice 
2, and those of UPSTREAM Microservice 2 affect UPSTREAM Microservice 1.
   
   Is your UPSTREAM (Microservice 1) configuration something like this:
   
   ```json
   {
     "id": "example-route-with-healthcheck",
     "uri":"/",
     "upstream":{
       "type":"roundrobin",
       "nodes":{
         "nginx1:80": 1,
         "nginx2:80": 1
       },
       "checks":{
         "active": {
           "type": "http",
           "http_path": "/",
             "healthy": {
             "interval": 2,
             "successes": 1
           },
           "unhealthy": {
             "interval": 1,
             "http_failures": 2
           }
         }
       }
     }
   }'
   ```
   
   The name of the microservice won't be configured explicitly here. APISIX 
checks a specific path configured in `upstream.checks.active.http_path` ([doc 
here](https://apisix.apache.org/docs/apisix/next/tutorials/health-check/)). The 
request forwarding to specific microservices is entirely taken care of by NGINX.
   
   If this understanding is quite right, please diagram.


-- 
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]

Reply via email to