Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ambassador Agent fails to report snapshot to Ambassador Cloud on "large" snapshots #3593

Closed
acookin opened this issue Jul 2, 2021 · 3 comments · Fixed by #3805
Closed

Ambassador Agent fails to report snapshot to Ambassador Cloud on "large" snapshots #3593

acookin opened this issue Jul 2, 2021 · 3 comments · Fixed by #3805
Assignees
Labels
w:6 Targeted for sixth week of development cycle
Milestone

Comments

@acookin
Copy link
Contributor

acookin commented Jul 2, 2021

In larger installations of ambassador, the agent hits the default grpc max message size when trying to relay the snapshot to the cloud.

Error:

time="2021-07-01 15:22:33" level=warning msg="failed to report: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (8884732 vs. 4194304)" 

We should probably stream the snapshot in chunks (we could bump the default message size, but that's a bandaid, not a solution.)

This error was reported by an ambassador cloud user in slack.

@andrewnazarov
Copy link

I was that reporter. Feel free to ping me here if you need some additional information:)

@ankit-ls
Copy link

ankit-ls commented Jul 20, 2021

@acookin I am observing the same issue consistently.

{"log":"time=\"2021-07-20 07:16:01\" level=warning msg=\"failed to report: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (11909674 vs. 4194304)\" func=\"github.com/datawire/ambassador/pkg/agent.(*Agent).MaybeReport.func1.1\" file=\"/go/pkg/agent/agent.go:474\" CMD=agent PID=1\n","stream":"stderr","time":"2021-07-20T07:16:01.996242695Z"}

Any timeline for a fix on this? We use helm charts to install the agent, so a parameter to increase the message size here (potentially as an agent.env[0] variable) should also be sufficient for us, as a short term fix.

@acookin
Copy link
Contributor Author

acookin commented Aug 13, 2021

@ankit-ls we're working on this issue right now, will update here when we've solved it

@efunk efunk added this to the 2021 Cycle 6 milestone Aug 20, 2021
@efunk efunk added the w:3 Targeted for third week of development cycle label Sep 7, 2021
@LukeShu LukeShu mentioned this issue Sep 24, 2021
4 tasks
@efunk efunk added w:6 Targeted for sixth week of development cycle and removed w:3 Targeted for third week of development cycle labels Sep 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
w:6 Targeted for sixth week of development cycle
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants