Fix: fix potential memory leak in getDirectQueryConnections with node 20 (#9575)

* Fix: fix potential memoery leak in getDirectQueryConnections

Signed-off-by: Zhongnan Su <szhongna@amazon.com>

* Changeset file for PR #9575 created/updated

---------

Signed-off-by: Zhongnan Su <szhongna@amazon.com>
Co-authored-by: opensearch-changeset-bot[bot] <154024398+opensearch-changeset-bot[bot]@users.noreply.github.com>

Author: zhongnansu

changelogs/fragments/9575.yml

@@ -0,0 +1,2 @@
+fix:
+- Fix potential memory leak in getDirectQueryConnections ([#9575](https://github.com/opensearch-project/OpenSearch-Dashboards/pull/9575))

src/plugins/data_source/config.ts

@@ -41,7 +41,7 @@ export const configSchema = schema.object({
     ),
   }),
   clientPool: schema.object({
-    size: schema.number({ defaultValue: 5 }),
+    size: schema.number({ defaultValue: 10 }),
   }),
   audit: schema.object({
     enabled: schema.boolean({ defaultValue: false }),

src/plugins/data_source_management/server/routes/data_connections_router.ts

@@ -222,7 +222,9 @@ export function registerDataConnectionsRoute(router: IRouter, dataSourceEnabled:
         let dataConnectionsresponse;
         if (dataSourceEnabled && dataSourceMDSId) {
           const client = await context.dataSource.opensearch.legacy.getClient(dataSourceMDSId);
-          dataConnectionsresponse = await client.callAPI('ppl.getDataConnections');
+          dataConnectionsresponse = await client.callAPI('ppl.getDataConnections', {
+            requestTimeout: 5000, // Enforce timeout to avoid hanging requests
+          });
         } else {
           dataConnectionsresponse = await context.opensearch_data_source_management.dataSourceManagementClient
             .asScoped(request)