HumanSignal / HumanSignal/label-studio

Syncing External Storage lead to Gateway Timeout

Open
#5,890 13 comments 0 reactions 0 assignees View on GitHub
Community community:issue community:reviewed
Dominant language
TypeScript
Stars
28.3k
Forks
3.7k
Avg merge
14h
Merged PRs (30d)
15

Description

**Describe the bug**
I deployed Label Studio on out internal K8s cluster using the official helm-chart (version 14.0.10). When I sync data storage (a minio cluster on the same k8s cluster) which contains about 1000 json file which represent 1000 tasks (the data is a uri to the minio cluster). After a while, the Gateway Timeout error and occasionally, "in time progress" error pop up, the sync request is not converted in "Failed" status but get stuck in "Queued" status and the project is completely frozen, I cannot do anything without syncing.

**To Reproduce**
Steps to reproduce the behavior:
1. Go to Project Settings / Cloud Storage
2. Click on "Sync Storage"
3. Gateway Timeout / In time progress
4. Sync task is Failed/Queued

**Expected behavior**
The sync is executed background, there is no need to immediately return the sync task's result.

**Environment (please complete the following information):**
- Kubernetes: v1.26.10
- Label Studio Helm Chart version 14.0.10

**Additional context**
This question may be out of context. But I am having issue with performance of Label Studio, the UI is quite lag and syncing data consistently gives me error as in this issue. How can I scale up my Label Studio on K8s and what should I scale up ? The hardware resource is not really my concern.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.