alibaba/GraphScope

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

Open

#2,872 建立於 2023年6月13日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)HTML (2,401 star) (301 fork)batch import
component:coordinatorgood first issue

描述

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.

貢獻者指南

技術棧
gokubernetes
領域
devopsinfrastructure
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Go programmingKubernetes basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
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.