Re: [kubernetes/kubernetes] Unrecognized internal errors in apiserver when etcd server is restarted (#65062)
Mike Spreitzer
@kubernetes/sig-api-machinery-bugs
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Mike Spreitzer
I have done some more trials. One (https://docs.google.com/document/d/1jxx-0YHc3YQvW7dIInRD8SBv0DgtJ_F-YvfoM_pRRCI) at 500 kube API writes/sec; that got 2 errors on update operations. Another (https://docs.google.com/document/d/1SF_e6rEcnmlfIUkZ6DtgZ_vl5YX7yvj5-qX1m5Y4xVg) at 2000 kube API writes/sec; that got 17 errors on create operations.
Mike Spreitzer
Here are two examples from the api-server stderr:
E0613 14:59:17.044177 1 status.go:64] apiserver received an error that is not an metav1.Status: grpc: the client connection is closing
E0613 14:59:17.044216 1 status.go:64] apiserver received an error that is not an metav1.Status: rpc error: code = Unavailable desc = the server stops accepting new RPCs
Wenjia
/cc @jpbetz @wenjiaswe
fejta-bot
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
fejta-bot
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
k8s-ci-robot
Closed #65062.
k8s-ci-robot
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Wenjia
/reopen
/assign @wenjiaswe
k8s-ci-robot
Reopened #65062.
k8s-ci-robot
@wenjiaswe: Reopened this issue.
In response to this:
/reopen
/assign @wenjiaswe
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
—
fejta-bot
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
—
Kubernetes Prow Robot
Closed #65062.
Kubernetes Prow Robot
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
—
Wenjia
/reopen
Kubernetes Prow Robot
Reopened #65062.
Kubernetes Prow Robot
@wenjiaswe: Reopened this issue.
In response to this:
/reopen
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
—
fejta-bot
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
—
Kubernetes Prow Robot
Closed #65062.
Kubernetes Prow Robot
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
—
Vladimir Skipor
/reopen
—
You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Kubernetes Prow Robot
@skipor: You can't reopen an issue/PR unless you authored it or you are a collaborator.
In response to this:
/reopen
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
—
Daniel Smith
/reopen
/lifecycle frozen
Kubernetes Prow Robot
Reopened #65062.
Kubernetes Prow Robot
@lavalamp: Reopened this issue.
In response to this:
/reopen
/lifecycle frozen
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
—