From 75a6d0a24b01d18448f72dc6df3a4e1de497d333 Mon Sep 17 00:00:00 2001
From: Michael Lumish <mlumish@google.com>
Date: Fri, 14 Oct 2022 09:45:57 -0700
Subject: [PATCH] grpc-js: Handle the grpc-node.max_session_memory option
 consistently on the client and server

---
 packages/grpc-js/package.json  | 2 +-
 packages/grpc-js/src/server.ts | 6 ++++++
 2 files changed, 7 insertions(+), 1 deletion(-)

diff --git a/packages/grpc-js/package.json b/packages/grpc-js/package.json
index c0db93ae..08706015 100644
--- a/packages/grpc-js/package.json
+++ b/packages/grpc-js/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@grpc/grpc-js",
-  "version": "1.7.1",
+  "version": "1.7.2",
   "description": "gRPC Library for Node - pure JS implementation",
   "homepage": "https://grpc.io/",
   "repository": "https://github.com/grpc/grpc-node/tree/master/packages/grpc-js",
diff --git a/packages/grpc-js/src/server.ts b/packages/grpc-js/src/server.ts
index 974c3dfc..499fde4a 100644
--- a/packages/grpc-js/src/server.ts
+++ b/packages/grpc-js/src/server.ts
@@ -346,6 +346,12 @@ export class Server {
       serverOptions.maxSessionMemory = this.options[
         'grpc-node.max_session_memory'
       ];
+    } else {
+      /* By default, set a very large max session memory limit, to effectively
+       * disable enforcement of the limit. Some testing indicates that Node's
+       * behavior degrades badly when this limit is reached, so we solve that
+       * by disabling the check entirely. */
+      serverOptions.maxSessionMemory = Number.MAX_SAFE_INTEGER;
     }
     if ('grpc.max_concurrent_streams' in this.options) {
       serverOptions.settings = {