You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please describe the feature you are requesting.
Multi-directory storage has been supported in 4.9.2, but it only supports master-slave deployment mode. We should also support this feature in DLedger deployment mode.
Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
Should-have.
If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
Task-1: Make DLedger support mult-directory storage.
We can combine this feature with RIP-31, because if a server has 12 disks, it is impossible for us to deploy 12 brokers. We can use this feature to allocate a few disks to each broker, so that each node of a group can be utilized and It can also ensure that a broker has enough space to use. How do you think about it? @duhengforever@RongtongJin@Jason918
We can combine this feature with RIP-31, because if a server has 12 disks, it is impossible for us to deploy 12 brokers. We can use this feature to allocate a few disks to each broker, so that each node of a group can be utilized and It can also ensure that a broker has enough space to use.
FEATURE REQUEST
Please describe the feature you are requesting.
Multi-directory storage has been supported in 4.9.2, but it only supports master-slave deployment mode. We should also support this feature in DLedger deployment mode.
Provide any additional detail on your proposed use case for this feature.
Refer to this pr RIP-7 Multiple Directories Storage Support #3357 to implement it.
Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
Should-have.
If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
The text was updated successfully, but these errors were encountered: