Skip to content

Received message larger than max #10

Open

Description

@jbrozena22

Thank you for this fantastic library. It works great when my returned prediction is small, but I have a model that returns significantly larger outputs. When I try to return them I get:

<_Rendezvous of RPC that terminated with:
status = StatusCode.RESOURCE_EXHAUSTED
details = "Received message larger than max (52383837 vs. 4194304)"
debug_error_string = "{"created":"@1539882985.938759395","description":"Error received from peer","file":"src/core/lib/surface/call.cc","file_line":1099,"grpc_message":"Received message larger than max (52383837 vs. 4194304)","grpc_status":8}"

Looking around this is a common error message seemingly related to the default size set in grpc. I tried naively just bumping the grpc version to 1.15.0 (latest) but that didn't have an effect. I also tried overriding the grpc function as suggested here but still no dice: grpc/grpc#13497 (comment)

You've thought more about this GRPC stuff than I have so figured it would be worth seeing if you'd run into this or how you had resolved it if so. Thanks!

Activity

  1. stianlp commented on Oct 27, 2018

    @stianlp
    Contributor

    Remember running into a similar issue when hosting models on Google Cloud Platform ML Engine.

    I think the easiest way to get around this is to trim your model's response size if possible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions