You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior:
Expecting QueriySessionPool to close all created sessions
Steps to reproduce:
Using QuerySessionPool(200) to generate some failing queries ~ 300 (single process, multiple threads)
Wait for the queries to finish processing pool.stop()
Related code:
The problem is consistent after approx 2 minutes of sessionPool usage, so increase iteration number as needed
def test_pool(self):
s_pool = ydb.QuerySessionPool(self.driver, size=200)
conn = self.ydb_queues[0]
pool = ThreadPoolExecutor(200)
def work():
try:
blob = next(conn.blobs_iter)
res = s_pool.execute_with_retries("BATCH UPDATE `{}` SET value = $value;".format(
conn.table_name), retry_settings=ydb.RetrySettings(max_retries=0),
parameters={"$value": blob},
settings=ydb.BaseRequestSettings().with_operation_timeout(19).with_timeout(20))
print(res)
except Exception as e:
print(e)
for i in range(100):
if len(self.worker_exception) == 0:
self.pool_semaphore.acquire()
pool.submit(self.wrapper, work)
else:
assert False, f"Worker exceptions {self.worker_exception}"
pool.shutdown(wait=True)
s_pool.stop()
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Bug Report
YDB Python SDK version:
3.21.2 (?)
Environment
Python 3.12.9
10 node cluster
Current behavior:
When invoking
pool.stop()
after queries with failures (in my case it isBATCH UPDATE
)Expected behavior:
Expecting
QueriySessionPool
to close all created sessionsSteps to reproduce:
Using QuerySessionPool(200) to generate some failing queries ~ 300 (single process, multiple threads)
Wait for the queries to finish processing
pool.stop()
Related code:
The problem is consistent after approx 2 minutes of sessionPool usage, so increase iteration number as needed
The text was updated successfully, but these errors were encountered: