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

Beam: reduce MaximumRecordSize to 6900000 bytes #287

Closed
chuwy opened this issue Jul 12, 2020 · 3 comments
Closed

Beam: reduce MaximumRecordSize to 6900000 bytes #287

chuwy opened this issue Jul 12, 2020 · 3 comments
Assignees
Milestone

Comments

@chuwy
Copy link
Contributor

chuwy commented Jul 12, 2020

We have an enrich job with growing backlog and very strange workers behavior that constantly dumps following message into Dataflow logs:

Could not commit request due to validation error: INVALID_ARGUMENT: Pubsub publish requests are limited to 10MB, rejecting message over 7MB (size 7548K) to avoid exceeding limit with byte64 request encoding.

We believe that reducing max size from current 10000000 bytes can mitigate the problem. Enriched event of 5Mb is already big enough to alarm.

@chuwy chuwy added this to the 1.3.0 milestone Jul 12, 2020
@chuwy chuwy self-assigned this Jul 12, 2020
@chuwy chuwy closed this as completed in ed40514 Jul 14, 2020
@fedoz
Copy link

fedoz commented Mar 31, 2021

Hi!
I get an error "Could not commit request due to validation error: INVALID_ARGUMENT: Pubsub publish requests are limited to 10MB, rejecting message over to avoid exceeding limit with byte64 request encoding" on my enrich step.
How I can fix it?

@chuwy
Copy link
Contributor Author

chuwy commented Apr 1, 2021

Hi @fedoz. It should be fixed on tracking side - either reduce amount of events you put into POST payload or find out what is addding this significant amount of data. Also, I'd recommend you to post question on our forums, you should get a response sooner and with higher chance.

@fedoz
Copy link

fedoz commented Apr 5, 2021

@chuwy Thank you for answer.
Maybe do you know, how I can find topics which initiate this error?

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

No branches or pull requests

2 participants