Read your writes consistency support (as alternative to read-cache-after-write feature)

未關閉
#3,671 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 1 天內回覆

還沒有人認領這個 Issue。

評估

難度
4/5
預估耗時
3-5 天
新手友好度
42/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
活躍
技術堆疊
java, kubernetes
領域
backend

研究方向

Read the linked controller-runtime discussion and issue #3670 first; the issue does not name implementation files or tests. Compare the proposed read-your-writes behavior with the existing read-cache-after-write feature, then trace the mechanism from #3670. Done means the SDK supports this consistency approach as an alternative, with its behavior and tests defined.

由索引模型根據 Issue 內容生成。

描述

on-demand

Note that we already support a feature called read-cache-after-write consistency, what should provide a better performance that what controller-runtime implements under read-your-writes consistency, also simpler reconciler implementations in general. On the other hand it is more complex and mainly has some interesting properties, see discussion here: https://github.com/kubernetes-sigs/controller-runtime/issues/3320

However, we might want to support for sake of completeness this other approach to. The implementation should be relatively simple.

主要語言
Java
星號
945
分支
247
平均合併
2 天 10 小時
30 天內合併 PR
27

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

operator-framework/java-operator-sdk 的其他 Issue

查看 operator-framework/java-operator-sdk 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。