Skip to content

Conversation

wujimin
Copy link
Contributor

@wujimin wujimin commented Jul 25, 2017

No description provided.

@coveralls
Copy link

Coverage Status

Changes Unknown when pulling 5ee0109 on wujimin:register-schema-fail-reason into ** on ServiceComb:master**.

HttpClientResponse response = restResponse.getResponse();
if (response == null) {
// invoke failed, call another SC instance
if (!retry(requestContext, syncHandlerEx(countDownLatch, holder))) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about the service center doesn't send the response back.
Do we have timeout mechanism for CountDownLatch?
BTW, is it enough if we just retry once?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

httpClientRequest.setTimeout to control timeout.
if no response, then timeout and callback with new RestResponse(requestContext, null),that means response is null
retry just copy from old code, infact maybe no need to retry, because registerSchema failed means registerMicroservice failed, and will auto retry.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we don't need the retry here, we can consider to remove this part of code.

@WillemJiang WillemJiang merged commit 15692ed into apache:master Jul 27, 2017
@wujimin wujimin deleted the register-schema-fail-reason branch August 11, 2017 09:19
@WillemJiang WillemJiang modified the milestone: 0.2.0 Aug 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants