Bug 762789 (GLUSTER-1057) - Support multiple local volumes with weighting
Summary: Support multiple local volumes with weighting
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-1057
Product: GlusterFS
Classification: Community
Component: nufa
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-08 18:40 UTC by Jeff Darcy
Modified: 2013-12-19 00:04 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)
Patch to make nufa work again, with multiple weighted local volumes (7.56 KB, patch)
2010-07-08 15:40 UTC, Jeff Darcy
no flags Details | Diff

Description Jeff Darcy 2010-07-08 18:40:40 UTC
Pursuant to a recent discussion on gluster-users, I've made some changes to nufa so that it can recognize multiple subvolumes as local (instead of just one) and thus prefer those for file creation.  Since it was easy to do, I also made it so that the volumes could be assigned different weights - sort of a poor man's storage tiering.  I also had to fix a couple of issues that kept the version of nufa that's currently in git from working at all.  I've attached the patch.  For the post part, the same code could be used in dht instead if that's what people prefer.

Comment 1 Amar Tumballi 2011-04-21 09:02:04 UTC
Hi Jeff,

This patch needs rebase with master, and also, we have to get it tested by QA. How critical is it overall for CloudFS? As we are not supporting NUFA in CLI, this is categorized as a low priority as of now. Let us know your requirement on this, and I will check how to prioritize this.

Comment 2 Jeff Darcy 2011-04-21 09:56:31 UTC
(In reply to comment #1)
> This patch needs rebase with master, and also, we have to get it tested by QA.
> How critical is it overall for CloudFS? As we are not supporting NUFA in CLI,
> this is categorized as a low priority as of now. Let us know your requirement
> on this, and I will check how to prioritize this.

I would say this is a very low priority, perhaps even nil as it's not really needed by CloudFS.  It was just a need I saw at the time, and so I whipped up some code in a spare moment.  At some point I'd like to discuss similar issues around controlling data placement in DHT, but probably not until a CloudFS2/GlusterFS4 kind of timeframe.

Comment 3 Amar Tumballi 2011-06-03 11:03:37 UTC
Jeff,

I tried applying this patch and it didn't apply fine. We are concentrating on DHT data placement and layout enhancement at this time. Will be closing this bug as won't fix. Please re-open if you think its important, so we will try to get someone fix the patch and test it.

Regards,
Amar


Note You need to log in before you can comment on or make changes to this bug.