alibaba/GraphScope

Coordinator should not try to pull all resources after restarts, it should connect.

Open

#2,872 opened on Jun 13, 2023

View on GitHub
 (0 comments) (0 reactions) (0 assignees)HTML (2,401 stars) (301 forks)batch import
component:coordinatorgood first issue

Description

In kubernetes deployment if the coordinator restarts due to OOM or pod evicted, it will try to pull all components again upon start up, and it will fail cause all resources is already exists, thus causing a infinite failed condition.

It should try to connect in such case.

Contributor guide

Tech stack
gokubernetes
Domain
devopsinfrastructure
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Go programmingKubernetes basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the coordinator startup logic in the GraphScope Kubernetes deployment, likely in the go files under the coordinator package. Identify where it attempts to pull all resources on restart and modify it to connect to existing resources instead. Look for related comments or code sections handling pod restarts.