Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature]: 2024-Recruiting developers. #3105

Open
leonrayang opened this issue Feb 20, 2024 · 1 comment
Open

[Feature]: 2024-Recruiting developers. #3105

leonrayang opened this issue Feb 20, 2024 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@leonrayang
Copy link
Member

leonrayang commented Feb 20, 2024

Is your feature request related to a problem? Please describe.

Ideas List

id project title skills required possible mentors expected size of project difficult rating detailed description
1 Adjustment of the number of data replicas datanode/master Leon Chang 175 intermediate Currently support 3 copies instead of 2 copies, and 2 copies are reduced to single copies.The current demand is: single copy can be upgraded to two copies, and two copies can be upgraded to 3 copies.
2 Modification and write optimization client Whale Tang 90 easy When a small file extent is overwritten and modified, the extent is re-created. This part is not necessary. You can consider modifying it directly to improve efficiency.
3 Network communication protocol merging metanode/datanode Victor1319 90 intermediate File deletion is asynchronous, and the actual executor is the metadata system. The deletion from mp to dp is currently a single request. In fact, merging optimization can be done to solve the pressure and efficiency problems of large-scale deletion.
4 Statistical service metanode/datanode Leon Chang 90 easy Currently provide statistics by the master service. We can also consider supporting metanode and datanode.
5 Panic mp and dp try to reload metanode/datanode Leon Chang 90 intermediate Currently some panics are caused by communication with the master and other scenarios. For better service, you can consider following up on the problem classification, such as abnormal communication with the master, or abnormal disk reading, and you can consider reloading
6 Hierarchical flow control metanode/master Whale Tang 350 difficult Build Hierarchical flow control in replica storage subsystem, data reading and writing > data repair > data migration > data balancing > data migration across clusters > data self-checking
7 MP node memory automatic balancing metanode/master Victor1319 175 intermediate Automatically triggers metadata partition migration within the cluster to ensure balanced usage
8 Atomic support for mp migration metanode/master AmazingChi 350 difficult The migration process is managed by the master and metanode participates. Because it is a distributed system, mp migration involves multi-step operations. Abnormalities in some steps will cause some to take effect and some to fail. As a result, the system has no control over the metadata copy. Inconsistency occurs

Describe the solution you'd like.

No response

Describe an alternate solution.

No response

Anything else? (Additional Context)

No response

@leonrayang leonrayang added the enhancement New feature or request label Feb 20, 2024
@leonrayang leonrayang changed the title [Feature]: Ideas List For GSOC [Feature]: Recruiting developers. Apr 13, 2024
@cubefs cubefs deleted a comment from github-actions bot Apr 15, 2024
@leonrayang leonrayang changed the title [Feature]: Recruiting developers. [Feature]: 2024-Recruiting developers. Apr 15, 2024
@leonrayang
Copy link
Member Author

+1

@leonrayang leonrayang pinned this issue May 6, 2024
@leonrayang leonrayang unpinned this issue May 6, 2024
@leonrayang leonrayang pinned this issue May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants