## What was reported

Issue pinecone-io/python-sdk#257 (closed, 5 comments): ### Is this a new bug in the Pinecone Python client?

- [X] I believe this is a new bug in the Pinecone Python Client
- [X] I have searched the existing issues, and I could not find an existing issue for this bug

### Current Behavior

Using the python api client ultimately results in an invocation of `_multiprocessing.SemLock`, which is not implemented on AWS lambda using a python3.11 runtime. Related stackoverflow: https://stackoverflow.com/questions/34005930/multiprocessing-semlock-is-not-implemented-when-running-on-aws-lambda

### Expected Behavior

Using the python API client should work

## The verified resolution

[kazzmir (reporter), closed by daverigby (maintainer)]: Root cause: langchain hard-coded `async_req=True`, which makes the pinecone client spawn a `multiprocessing` pool whose `_multiprocessing.SemLock` is not implemented on AWS Lambda (python3.11). Fixes: upgrade to langchain>=0.1.17 / langchain-pinecone>=0.1.0 / langchain-community>=0.0.37, which no longer hard-code async_req, then pass `async_req=False`; or wrap a concurrent.futures.ThreadPoolExecutor and assign it to `index._pool` (reporter's workaround).