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

GRPC channel: PubSub inbound message size limit #164

Closed
emanuele-pirro opened this issue Jun 11, 2018 · 2 comments
Closed

GRPC channel: PubSub inbound message size limit #164

emanuele-pirro opened this issue Jun 11, 2018 · 2 comments

Comments

@emanuele-pirro
Copy link

Hi everyone,

For various reasons my source connector is trying to ingest a big-boy message.

INFO Error while retrieving records, treating as an empty poll. java.util.concurrent.ExecutionException: io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: io.grpc.netty.NettyClientTransport$3: Frame size 5435421 exceeds maximum: 4194304. (com.google.pubsub.kafka.source.CloudPubSubSourceTask)

The data size exceeds the maximum allowed by GRPC (about 4MB) so to allow the connector to ingest the message need to add the option .maxInboundMessageSize(eightMegabytes) to the GRPC channel builder.

Would it be useful to achieve this via configuration? I can contribute on that but I'm very busy lately so that would be released for our nephews :)

Thanks in advance.

@kamalaboulhosn
Copy link
Collaborator

I went ahead and made the default 10MB to match the maximum Pub/Sub message size. I don't think we need to make it a configurable option. Thanks for reporting the issue!

@emanuele-pirro
Copy link
Author

Thank you! ;)

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