Dear HaopengZH, Thanks for your advice. Just wanted to make it clear for me. I can extending the listener interface and implement a new listener in my Java project, OR I have to change the Dubbo 2.7.6 original code to add this new listener?
Best regards Tien Dat PHAN On 2020/04/09 06:44:09, HaopengZH <[email protected]> wrote: > dubbo support disable services at consumer side at now,you want to disable > special service ,I think you need change the original code ,add a listener to > listen the configurator's changes > At 2020-04-08 23:50:46, "Tien Dat PHAN" <[email protected]> wrote: > >Dear experts, > > > >We are using Dubbo 2.7.6. > >The DubboBootstrap is the newest way of managing the exported APIs and the > >API references. > >For our use case, we have several different APIs to be exported. Each API > >exposes a specific service from one or several components of our cluster. > >During the runtime, we have health check threads to check the health of the > >underlying components. Accordingly, we would like to un-export the exported > >APIs using the unhealthy component (without un-exporting the other APIs > >using heathy components). Upon the components health status is back to good, > >we also would like to re-export the corresponding APIs. > > > >So far, we could not find a proper way to handle this use case with > >DubboBootstrap. > >With DubboBootstrap, the initialization (including exporting services) is > >only invoked when starting the Bootstrap. And a > >DubboBootstrap.getInstance().stop() will simply stop every services. > >We could not find a way to update a targeted service after starting the > >DubboBootstrap. > > > >Do you have any experience regarding this aspect? > >We will highly appreciate if you can enlighten us with your expertise. > > > >Best regards > >Tien Dat PHAN >
