On 07/01/2016 07:11 AM, Joe Julian wrote:
> Isn't that what tiering is for?
Yes, I believe tiering would be a great use case for such scenarios.
Regards
Rafi KC
>
> On June 30, 2016 4:54:42 PM PDT, Serg Gulko wrote:
>
> Hello!
>
> We are running purely distributed(no replication) glu
Isn't that what tiering is for?
On June 30, 2016 4:54:42 PM PDT, Serg Gulko wrote:
>Hello!
>
>We are running purely distributed(no replication) gluster storage.
>Is there a way to "bind" files to certain brick? Reason why I need it
>is
>very simple - I prefer to keep most recent data on more fast
Hello Russell!
Great idea, thank you very much!
Original Message
From: Russell Purinton
Sent: Thursday, June 30, 2016 20:00
To: Serg Gulko
Cc: gluster-users@gluster.org
Subject: Re: [Gluster-users] Is there a way to manage data location manually?
I do this using separate volumes… One fast
I do this using separate volumes… One fast volume, one slow volume, and just
move the data between them as necessary…
I don’t believe there’s a way to do it as you describe.
Russ
> On Jun 30, 2016, at 7:54 PM, Serg Gulko wrote:
>
> Hello!
>
> We are running purely distributed(no replicatio
Hello!
We are running purely distributed(no replication) gluster storage.
Is there a way to "bind" files to certain brick? Reason why I need it is
very simple - I prefer to keep most recent data on more faster storage pods
and offload stale files into slower pods(read - less expensive).
I tried t