apache / apache/kyuubi

[Bug] DataGrip executes refresh command slowly

Open
#6,797 1 comment 0 reactions 0 assignees View on GitHub
kind:bug priority:major
Dominant language
Scala
Stars
2.4k
Forks
1k
PR merge metrics
No merged PRs in 30d

Description

### Code of Conduct

- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

### Search before asking

- [X] I have searched in the [issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no similar issues.

### Describe the bug

When DataGrip executes refresh, I see that the following operations have been performed, mainly table list operations and table columns operations are time-consuming. Currently, my test results show that it takes four minutes to complete refresh.

Operations:
Routine list in database
Table list in database
Table columns in database
Keys in database.table

image

image

image

image

image

### Affects Version(s)

1.10.0

### Kyuubi Server Log Output

_No response_

### Kyuubi Engine Log Output

_No response_

### Kyuubi Server Configurations

_No response_

### Kyuubi Engine Configurations

```yaml
spark.master yarn
spark.yarn.queue default
spark.executor.cores 1
spark.driver.memory 3g
spark.executor.memory 3g
spark.dynamicAllocation.enabled true
spark.dynamicAllocation.shuffleTracking.enabled true
spark.dynamicAllocation.minExecutors 1
spark.dynamicAllocation.maxExecutors 10
spark.dynamicAllocation.initialExecutors 1
spark.cleaner.periodicGC.interval 5min
```

### Additional context

_No response_

### Are you willing to submit PR?

- [ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix.
- [ ] No. I cannot submit a PR at this time.

Contributor guide

Open the contributing guide

Research direction

Reproduce the DataGrip refresh against Kyuubi 1.10.0 using the supplied Spark engine settings, and measure the routine, table, column, and key metadata operations listed in the report. Trace the slow requests through the Kyuubi server and engine; done means the reported four-minute refresh delay is reduced and the affected operations have evidence of the improvement.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala, spark, sql
Domain
backend, databases, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.