From ada41a995a5a1d1c69b8fca5bc7e89da25757798 Mon Sep 17 00:00:00 2001 From: SataQiu <1527062125@qq.com> Date: Thu, 4 Oct 2018 13:13:39 +0800 Subject: [PATCH] fix typo (#10487) --- content/en/blog/_posts/2018-09-18-2018-linkerd-2.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2018-09-18-2018-linkerd-2.0.md b/content/en/blog/_posts/2018-09-18-2018-linkerd-2.0.md index b3b9e09b59..d985cec573 100644 --- a/content/en/blog/_posts/2018-09-18-2018-linkerd-2.0.md +++ b/content/en/blog/_posts/2018-09-18-2018-linkerd-2.0.md @@ -119,7 +119,7 @@ Let’s scroll a little further down the page, we’ll see a live list of all tr
-There are two calls that are not at 100%: the first is vote-bot’s call the “/api/vote” endpoint. The second is the “VotePoop” call from the web service to the voting service. Very interesting! Since /api/vote is an incoming call, and “/VotePoop” is an outgoing call, this is a good clue that that the failure of the vote service’s VotePoop endpoint is what’s causing the problem! +There are two calls that are not at 100%: the first is vote-bot’s call the “/api/vote” endpoint. The second is the “VotePoop” call from the web service to the voting service. Very interesting! Since /api/vote is an incoming call, and “/VotePoop” is an outgoing call, this is a good clue that the failure of the vote service’s VotePoop endpoint is what’s causing the problem! Finally, if we click on the “tap” icon for that row in the far right column, we’ll be taken to live list of requests that match this endpoint. This allows us to confirm that the requests are failing (they all have [gRPC status code 2](https://godoc.org/google.golang.org/grpc/codes#Code), indicating an error).