-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New version of cx-oracle (7.3.0) breaks oracle connection with old sqlalchemy #645
Comments
Googling for it, brought me to this issue under the SQLAlchemy project: where they suggest to update to SQLAlchemy >= 1.1.11, which removes the hard-coded @yuyiguo Yuyi, if you agree, I can try building a specific SQLAlchemy for DBS (based on 1.1.13, which has some unicode performance bugfix) and ask Imran for a new deployment tomorrow. |
I have created this PR: cms-sw/cmsdist#6578 which might fail to build, since I didn't test it myself. |
Thanks Alan |
@yuyiguo Hi Yuyi, I'm just wondering if you managed to test the performance of DBS in cmsweb-testbed? It has the latest COMP cx-Oracle and the changes provided in this PR: once we confirm that performance is Okay, we can continue with other changes and developments. Thanks |
No, I haven't. I have something at hands. Later today or tomorrow I will do it. |
@amaltaro |
Wonderful news, Yuyi! Thanks for testing it. From my side, feel free to close this issue then. |
Tested both k8s and vm BE. All test results were compatible with previous tests. |
As briefly discussed in this HN:
https://hypernews.cern.ch/HyperNews/CMS/get/webInterfaces/1763.html
we decided to update python
cx-oracle
library from 5.2.1 to 7.3.0, which is the latest cx-oracle version still supporting python2.7.It turns out this upgrade broke DBS in cmsweb-testbed, with apparently an incompatibility between the SQLAlchemy and cx-Oracle version. This issue hasn't been seen (yet) in WMAgent, and I think the reason for that is that WMAgent is using one of the latest SQLAlchemy version 1.3.3, while DBS is still using 0.9.6.
Here is the traceback from the DBSGlobaReader logs, when querying the
datatiers
RESTful API:The text was updated successfully, but these errors were encountered: