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)

首先通过 ExceptionFactory.java、Response.java 和 FallbackPolicyManager.java 跟踪报告的故障，然后检查相关的服务隔离和恢复流程。使用现有日志确定为什么恢复服务实例会产生消费者错误。完成的标准是恢复路径能够在不出现此异常的情况下运行，并且可以通过一个可复现的案例验证该故障。

由索引模型根据 Issue 内容生成。