On 11/04/2013 06:40 PM, James wrote:
On Mon, Nov 4, 2013 at 8:07 AM, Paul Simpson wrote:
that is what i'm planning to test. i guess my underlying question is - will
gluster automatically "know" that a volume of replica count 2 is not
replicated any more? and if so, how will it react to the fact
On Mon, Nov 4, 2013 at 8:07 AM, Paul Simpson wrote:
> that is what i'm planning to test. i guess my underlying question is - will
> gluster automatically "know" that a volume of replica count 2 is not
> replicated any more? and if so, how will it react to the fact that the
> replicated bricks are
thanks lukas,
that is what i'm planning to test. i guess my underlying question is - will
gluster automatically "know" that a volume of replica count 2 is not
replicated any more? and if so, how will it react to the fact that the
replicated bricks are now missing? ie, should i / or is there a way
Hi, I would say it's quite OK unless you don't shrink the distribute.
For example volume with replica 2 distribute 2 would look like:
_/test1:/test
\test2:/test
_/test3:/test
\test4:/test
if your gluster volume heal test info is empty (eg theres nothing to
heal) it should be fairly safe to remo
ping!
On 31 October 2013 11:47, Paul Simpson wrote:
> hi all,
>
> as the title says - i'm looking to change a volume from dist/repl -> dist.
>
> we're currently running 3.2.7. a few of questions for you gurus out there:
> - is this possible to do on 3.2.7?
> - is this possible to do with 3.4.
hi all,
as the title says - i'm looking to change a volume from dist/repl -> dist.
we're currently running 3.2.7. a few of questions for you gurus out there:
- is this possible to do on 3.2.7?
- is this possible to do with 3.4.1? (would involve upgrade)
- are there any pitfalls i should be aware
