ydb-platform / ydb-platform/ydb-python-sdk
feature: 2DC support in python SDK
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 102
- Forks
- 75
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Currently, it doesn't work in case of 2DC: fails to find connection for e.g. table client or new monitoring client:
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/eivanov89/repos/ydb-python-sdk/ydb/monitoring.py", line 47, in self_check
return self._driver(
File "/home/eivanov89/repos/ydb-python-sdk/ydb/tracing.py", line 70, in wrapper
return f(self, *args, **kwargs)
File "/home/eivanov89/repos/ydb-python-sdk/ydb/pool.py", line 459, in __call__
connection = self._store.get(preferred_endpoint)
File "/home/eivanov89/repos/ydb-python-sdk/ydb/tracing.py", line 70, in wrapper
return f(self, *args, **kwargs)
File "/home/eivanov89/repos/ydb-python-sdk/ydb/pool.py", line 144, in get
raise issues.ConnectionLost("Couldn't find valid connection")
ydb.issues.ConnectionLost: Couldn't find valid connection
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the 2DC failure described in ydb/monitoring.py, then trace the connection lookup through ydb/tracing.py and ydb/pool.py. Compare the lookup behavior for the table client and monitoring client in a 2DC setup; the work is done when both can find a valid connection without raising ConnectionLost.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100