# GRPC Resource Exhausted Error

**URL:** <https://forum.weaviate.io/t/grpc-resource-exhausted-error/3436>\
**Category:** Support\
**Created:** [August 22, 2024, 8:19pm UTC](https://forum.weaviate.io/t/grpc-resource-exhausted-error/3436 "2024-08-22T20:19:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cobyboss](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/cobyboss/32/389_2.png) [@Cobyboss](https://forum.weaviate.io/u/Cobyboss)\
**Post date:** [August 22, 2024, 8:19pm UTC](https://forum.weaviate.io/t/grpc-resource-exhausted-error/3436/1 "2024-08-22T20:19:13Z")

</div>

ErrorObject(message=’WeaviateBatchError(\‘Query call with protocol GRPC batch failed with message \<AioRpcError of RPC that terminated with:\n\tstatus = StatusCode.RESOURCE\_EXHAUSTED\n\tdetails = “CLIENT: Sent message larger than max (146965530 vs. 104858000)“\n\tdebug\_error\_string = “UNKNOWN:Error received from peer {created\_time:“2024-08-22T13:03:51.442771-07:00”, grpc\_status:8, grpc\_message:“CLIENT: Sent message larger than max (146965530 vs. 104858000)“}”\n\>.\‘)’,

I am trying to vectorize images from Google Cloud Platform with Weaviate but am getting RESOURCE\_EXHAUSTED errors. I am using the multimodal model for this. When I was testing this on the Sandbox it worked completely fine, but now it is not working on the serverless cluster. Is it that the image sizes are too big (confusing because it worked on the Sandbox) and if so, how should I workaround this? I tried to vectorize 100 images: 72 worked 28 failed with that error above.

I am using 1.25.10 and the code is below:

```auto
image_b64 = url_to_base64(src_obj["image_url"])
        weaviate_obj = {
            "image": image_b64,
            "image_url": src_obj["image_url"],
            "image_name": src_obj["image_name"],
            "source": src_obj["source"],
        }
        obj_uuid = src_obj["uuid"] if src_obj["uuid"] else generate_uuid5(weaviate_obj)

        batch.add_object(
            properties=weaviate_obj,
            uuid = obj_uuid
            # vector=vector # Optionally provide a pre-obtained vector
        )

```

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [August 22, 2024, 9:11pm UTC](https://forum.weaviate.io/t/grpc-resource-exhausted-error/3436/2 "2024-08-22T21:11:57Z")

</div>

hi @Cobyboss !

For all clusters hosted in our cloud, the best place for support is opening a support ticket. Check the [Support Link](https://console.weaviate.cloud/support) inside your console dashboard for details.

This error message indicates that the size of the payload was too big to be handled.

How are you configuring your batch size? What batch sizes have you tried?

here is an example:

```auto
with collection.batch.fixed_size(batch_size=10, concurrent_requests=2) as batch:
    for data_row in objects:
        batch.add_object(
            properties=data_row,
            uuid=generate_uuid5(data_row.get("reference_id"))
        )

```

Let me know if this helps!

---

<div class="post-metadata">

**Author:** ![bobvanluijt](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/bobvanluijt/32/23_2.png) [@bobvanluijt](https://forum.weaviate.io/u/bobvanluijt)\
**Post date:** [January 20, 2025, 5:50pm UTC](https://forum.weaviate.io/t/grpc-resource-exhausted-error/3436/3 "2025-01-20T17:50:39Z")

</div>

I run into the same thing (the object send to the DB is too large). It’s solved in the next release: [Increase default GRPC\_MAX\_MESSAGE\_SIZE limit to 100MB by antas-marcin · Pull Request #6966 · weaviate/weaviate · GitHub](https://github.com/weaviate/weaviate/pull/6966)