Does anybody know why quarkus has different payload limits for grpc calls depending on whether you are using a dedicated grpc server or a single one (Vertx) ?

More specifically:

quarkus.grpc.server.max-inbound-message-size

The max inbound message size in bytes.

When using a single server (using quarkus.grpc.server.use-separate-server=false), the default value is 256KB. When using a separate server (using quarkus.grpc.server.use-separate-server=true), the default value is 4MB.

Environment variable: QUARKUS_GRPC_SERVER_MAX_INBOUND_MESSAGE_SIZE

Or actually the main question is:

Should I use a dedicate grpc server (quarkus.grpc.server.use-separate-server=true) if my common payload size is close to 4MB ?

Thank you.

Does anybody know why quarkus has different payload limits for grpc calls depending on whether you are using a dedicated grpc server or a single one (Vertx) ?

More specifically:

quarkus.grpc.server.max-inbound-message-size

The max inbound message size in bytes.

When using a single server (using quarkus.grpc.server.use-separate-server=false), the default value is 256KB. When using a separate server (using quarkus.grpc.server.use-separate-server=true), the default value is 4MB.

Environment variable: QUARKUS_GRPC_SERVER_MAX_INBOUND_MESSAGE_SIZE

Or actually the main question is:

Should I use a dedicate grpc server (quarkus.grpc.server.use-separate-server=true) if my common payload size is close to 4MB ?

Thank you.

• grpc
• quarkus
• vert.x

1 Answer 1

This issue should be fixed, see here:

• https://github/quarkusio/quarkus/issues/43573