OpenListTeam / OpenListTeam/OpenList

[Feature] 负载均衡复制文件夹时,任务分发也均衡分配

Open
#588 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
24.7k
Forks
2.3k
Avg merge
1d 20h
Merged PRs (30d)
36

Description

请确认以下事项
  • 我已确认阅读并同意 AGPL-3.0 第15条
    本程序不提供任何明示或暗示的担保,使用风险由您自行承担。

  • 我已确认阅读并同意 AGPL-3.0 第16条
    无论何种情况,版权持有人或其他分发者均不对使用本程序所造成的任何损失承担责任。

  • 我确认我的描述清晰,语法礼貌,能帮助开发者快速定位问题,并符合社区规则。

  • 我已确认阅读了OpenList文档

  • 我已确认没有重复的问题或讨论。

  • 我认为此问题必须由OpenList处理,而非第三方。

  • 我已确认此功能尚未被实现。

  • 我已确认此功能是合理的,且有普遍需求,并非我个人需要。

需求描述

假如两个存储负载均衡分别是A(主)和B(副),现在列表显示重新加载,会一次显示A,一次显示B。

复制文件夹是,所有复制任务都聚集在一个存储上。

可否显示列表永远都是A,下载先正常负载均衡,假如B(副)没有这个文件自动切换从A(主)下载。

复制文件夹时,也是把任务平均分到所有存储上,假如B(副)找不到文件都自动切换从A(主)获取文件。

实现思路

文件列表显示永远都是主存储,获取文件在负载均衡的基础上,负载均衡时发现副存储没有这个文件,自动使用主存储获取文件。

可以把这模式做成新负载均衡模式,保留新旧,或者用一个开关切换。

附加信息

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the load-balancing behavior for file listing, downloads, and folder-copy task dispatch described in the issue. Clarify how the primary and secondary storages are selected and how a missing file should fall back to the primary. Done means listings consistently use the primary, downloads and copy tasks are distributed across storages, and secondary misses fall back correctly.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.