How to set in RR, both grpc.max_send_message_length and grpc.max_receive_message_length for PHP?

[route33]

RESOURCE_EXHAUSTED: Bandwidth exhausted

How to set in RR, both grpc.max_send_message_length and grpc.max_receive_message_length for PHP?

In JS can be does as follows:

const grpc = require('@grpc/grpc-js');

const client = new YourServiceClient('localhost:50051', grpc.credentials.createInsecure(), {
    'grpc.max_send_message_length': 10 * 1024 * 1024, // 10 MB
    'grpc.max_receive_message_length': 10 * 1024 * 1024 // 10 MB
});

[rustatian]

Hey @route33 👋🏻
You mean, you have some PHP gRPC client and wanted to set these options in it?

[route33]

I have the option to do like this, but I wonder if is possible from RR settings

use Grpc\ChannelCredentials;
use Grpc\Channel;
use MyServiceClient;

// Set the maximum send message length (e.g., 10 MB)
$maxSendMessageLength = 10 * 1024 * 1024; // 10 MB

// Create a channel with the specified options
$channel = new Channel('my.server.address:port', [
    'grpc.max_send_message_length' => $maxSendMessageLength,
    'grpc.max_receive_message_length' => $maxSendMessageLength,
]);

myClient = new MyServiceClient(
            'localhost:9001',
            ['credentials' => ChannelCredentials::createInsecure()],
            $channel
        );

[rustatian]

You may set these options in .rr.yaml for RR, but not for the PHP client inside the worker. RR does not know anything about the PHP Workers (even that they are PHP workers), they're completely independent from RR (except receiving payloads from RR).

[route33]

Oh, now I get why I had this error on Node.JS services, but not on RR ones. Thank you @rustatian !

Do you also know when a fix for #1992 is going to be released?

[rustatian]

I'll try next week. The problem with that issue is that it is very hard to reproduce.

[rustatian]

@route33 Would you mind creating a test (reproduction) repo for the #1992 with the proto you used and payload examples (could be done in PHP)?