marmot-z commented on issue #14470: URL: https://github.com/apache/dubbo/issues/14470#issuecomment-2693221679
> > > >  > > > > My question is why the process is interrupted? > > > > > > > > > I'm not sure whether the process is interrupted by next retry.  > > > My connection timeout is 3000ms. If it always fails to connect, each retry will take 3000+1000+3000+1000+3000+1000=12000ms. However, the retry period is 10000ms.  > > > > > > Actually, this is a bug. The metadata retry thread calls `retryFuture.cancel(true)`, which will interrupt itself and then throw InterruptedException when trying lock. > > Do you have some thoughts on how we can fix this issue? Since the process of obtaining the meta information of the service instance does not support interruption, the interruption always occurs at this place, which may cause inconsistency between the router and the invoker in the directory, and ultimately cause the router to refuse routing.   So, can we support interruption when obtaining the meta information of the remote service instance to avoid the inconsistent invoker?  -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
