Recover service instance from isolation 接口仍然不通

org.apache.servicecomb.swagger.invocation.exception.InvocationException: InvocationException: code=490;msg=CommonExceptionData [message=Unexpected consumer error, please check logs for details]
at org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory.doCreate(ExceptionFactory.java:81)
at org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory.convertException(ExceptionFactory.java:124)
at org.apache.servicecomb.swagger.invocation.exception.ExceptionFactory.convertConsumerException(ExceptionFactory.java:85)
at org.apache.servicecomb.swagger.invocation.Response.createConsumerFail(Response.java:178)
at org.apache.servicecomb.swagger.invocation.Response.createFail(Response.java:171)
at org.apache.servicecomb.swagger.invocation.Response.failResp(Response.java:219)
at org.apache.servicecomb.bizkeeper.FallbackPolicyManager.getFallbackResponse(FallbackPolicyManager.java:44)

Start by tracing the reported failure through ExceptionFactory.java, Response.java, and FallbackPolicyManager.java, then inspect the relevant service-isolation and recovery flow. Use the available logs to determine why recovering the service instance produces the consumer error. Done means the recovery path works without this exception and the failure can be verified against a reproducible case.

Written by the indexing model from the issue text.