Startup check

By default, the framework checks the availability of dependent services (whether the registry has available addresses) at startup. If not available, it throws an exception to prevent the application from finishing initialization, allowing issues to be discovered early during deployment. The default is check=“true” and waits for 3 seconds.

The Dubbo framework, by default, checks the availability of dependent services at startup (whether the registry has available addresses). If not available, it throws an exception to prevent the application from completing initialization, allowing early detection of problems during deployment. The default is check=“true” and waits for 3 seconds.

You can disable the check with check=“false”. For example, during testing, some services may not be of concern, or there may be circular dependencies, requiring one party to start first.

After disabling check, please note that when there are many providers, the consumer subscribing to the provider and generating service addresses may have some delay. If the consumer starts providing services immediately, it may cause a “cold start”. Therefore, at this time, please preheat the services.

Example:

  1. dubbo:
  2.   consumer:
  3.     check : false
  4.     reference: 
  5.       myservice:
  6.        check: true

Or

  1. cli, err := client.NewClient(
  2.     client.WithClientCheck(false),
  3. )

Or

  1. svc, err := health.NewHealth(cli)
  2. svc.Check(context.Background(), &health.HealthCheckRequest{Service: "greet.GreetService"}, client.WithCheck(false))

Feedback

Was this page helpful?

Yes No

Last modified September 30, 2024: Update & Translate Overview Docs (#3040) (d37ebceaea7)