Apologies. Yes, your right - I built a logging and error handling wrapper and thats spitting out that error
From the documentation:
except CouchbaseError as e:
if e.is_data and isinstance(e, NotFoundError):
# handle not found
print("Got network error")
print("Got other data-related error")
print("Got unhandled error code")
The last part is where the error got caught.
I was able to solve it by using the lockmode=LOCKMODE_WAIT while accessing the singleton bucket.
I still have a multi-threading question for you though. Our API server, currently supports 4-5,000 users/connections simultaneously. When we push cb into prod, would using LOCKMODE_WAIT, still make sense? - As per the documentation, there doesn’t seem to be an alternative other than have a separate connection per thread.