Databricks driver frequent timeout
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 151
- Forks
- 183
- Avg merge
- 14m
- Merged PRs (30d)
- 2
Description
Hi @anthonysena,
We upgraded our WebAPI to v2.15.0 and switched to DatabricksJDBC42.jar v2.7.3 for connecting to our OMOP CDM. Since then, cohort generation calls immediately time out—despite a very large socketTimeout setting. Occasionally, if we rerun the generation a few times it succeeds, but it almost always fails on the first attempt.
We didn’t see this issue with SparkJDBC42.jar (v2.6.22 and earlier). Have you encountered this behavior, and do you have any suggestions for resolving it?
Contributor guide
No contributing guide indexed for this repository
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
The payload names WebAPI cohort generation and DatabricksJDBC42.jar v2.7.3, but no source file or test. Start by reproducing the first-attempt timeout while comparing with SparkJDBC42.jar v2.6.22; done means identifying a reproducible cause and verifying a fix for the initial call.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100