I just wanted to check if gluster replace brick commit force is
officially deprecated in 3.6? Is there any other way to do a planned
replace of just one of the bricks in a replica pair? Add/remove brick
requires that new bricks be added in replica count multiples which may not
be always
'replace-brick commit force' is still going to be available. It's just
that data-migration for replace-brick is going to be removed. So
'replace-brick (start|stop)' are going to be deprecated.
To replace a brick in a replica set, you'll need to do a
'replace-brick commit force'. Self-healing will
On 2014-10-28 20:33, Niels de Vos wrote:
On Tue, Oct 28, 2014 at 05:52:38PM +0100, Anders Blomdell wrote:
On 2014-10-28 17:30, Niels de Vos wrote:
On Tue, Oct 28, 2014 at 08:42:00AM -0400, Kaleb S. KEITHLEY wrote:
On 10/28/2014 07:48 AM, Darshan Narayana Murthy wrote:
Hi,
Installation of
On Tue, 28 Oct 2014 11:35:49 -
John Hearns john.hea...@viglen.co.uk wrote:
snip
Gluster on ZFS is of course very interesting.
http://www.gluster.org/community/documentation/index.php/GlusterOnZFS
I guess this must get discussed here a lot!
Anyone care to comment on the roadmap for this?
On 10/30/2014 04:36 AM, Anders Blomdell wrote:
I think a compat package would make the coupling between server and client
looser, (i.e. one could run old clients on the same machine as a new server).
Due to limited time and dependency on qemu on some of my testing machines, I
still have not
Hi,
Thanks! Seems like an interesting document. Although I've read blogs about how
extended attributes are used as a change log, this seams like a more
comprehensive
document.
I won't write directly to any brick. That's the reason I first have to create a
volume which consists of only one
Hi,
I have a requirement to run my gluster hosts within a firewalled section of
network and where the consumer hosts are in a different segment due to IP
address preservation, part of our security policy requires that we run local
firewalls on every host so I have to get the network access
On 2014-10-30 14:52, Kaleb KEITHLEY wrote:
On 10/30/2014 04:36 AM, Anders Blomdell wrote:
I think a compat package would make the coupling between server and client
looser, (i.e. one could run old clients on the same machine as a new server).
Due to limited time and dependency on qemu on
On 10/27/2014 07:05 AM, Prasun Gera wrote:
Just wanted to check if this issue was reproduced by RedHat. I don't
see any updates on Satellite yet that resolve this.
To exasperate this issue, CentOS 6.6 has now dropped, including
GlusterFS 3.6.0, making the problem more widespread.
The Bitergia team have updated their GlusterFS Community stats page,
so it now shows more of the companies in our Community. :)
http://bitergia.com/projects/redhat-glusterfs-dashboard/browser/scm-companies.html
Previously it was:
#1 Red Hat
#2 IBM
#3 CERN
Now it's:
#1 Red Hat
#2
Which means, of course, no redundancy until that self heal is completed.
Furthermore, replace-brick start stopped working at all some versions ago so
the removal of start and stop may as well just happen.
On October 30, 2014 12:41:17 AM PDT, Kaushal M kshlms...@gmail.com wrote:
'replace-brick
On 2014-10-30 14:52, Kaleb KEITHLEY wrote:
On 10/30/2014 04:36 AM, Anders Blomdell wrote:
I think a compat package would make the coupling between server and client
looser, (i.e. one could run old clients on the same machine as a new server).
Due to limited time and dependency on qemu on
This is because in 3.4, they changed the brick port range. It's mentioned
on
https://forge.gluster.org/gluster-docs-project/pages/GlusterFS_34_Release_No
tes:
Brick ports will now listen from 49152 onwards (instead of 24009 onwards
as with previous releases). The brick port assignment scheme
On Wed, Oct 29, 2014 at 1:18 PM, craig w codecr...@gmail.com wrote:
I am trying to run a GlusterFS server in a Docker container. It works fine,
the problem I have is when I create a volume it's associated with the
private IP address of the container, which is not accessible to other hosts
in
Hi Paul,
I will agree from experience that finding accurate, up-to-date
documentation on how to do some basic configuration of a Gluster volume can
be difficult. However, this blog post mentions the updated firewall ports.
http://www.jamescoyle.net/how-to/457-glusterfs-firewall-rules
Get rid
Hey folks
We're having a Gluster event in Paris on 4-November, to get together and
celebrate a number of new technologies, including the GlusterFS 3.6.0
release.
Sign up here:
http://www.eventbrite.com/e/inscription-gluster-night-paris-10413255327?aff=es2rank=0
Our agenda is pretty
https://github.com/gluster/glusterfs/blob/master/doc/admin-guide/en-US/markdown/admin_settingup_clients.md#installing-on-red-hat-package-manager-rpm-distributions
(also restated again under Installing on Debian-based Distributions)
Any thoughts on what would make this any easier to find?
On
On 10/30/2014 01:50 PM, Anders Blomdell wrote:
On 2014-10-30 14:52, Kaleb KEITHLEY wrote:
On 10/30/2014 04:36 AM, Anders Blomdell wrote:
I think a compat package would make the coupling between server and client
looser, (i.e. one could run old clients on the same machine as a new server).
On 2014-10-30 20:55, Kaleb KEITHLEY wrote:
On 10/30/2014 01:50 PM, Anders Blomdell wrote:
On 2014-10-30 14:52, Kaleb KEITHLEY wrote:
On 10/30/2014 04:36 AM, Anders Blomdell wrote:
I think a compat package would make the coupling between server
and client looser, (i.e. one could run old
On 10/30/2014 04:34 PM, Anders Blomdell wrote:
On 2014-10-30 20:55, Kaleb KEITHLEY wrote:
On 10/30/2014 01:50 PM, Anders Blomdell wrote:
On 2014-10-30 14:52, Kaleb KEITHLEY wrote:
On 10/30/2014 04:36 AM, Anders Blomdell wrote:
I think a compat package would make the coupling between server
On 2014-10-30 22:06, Kaleb KEITHLEY wrote:
On 10/30/2014 04:34 PM, Anders Blomdell wrote:
On 2014-10-30 20:55, Kaleb KEITHLEY wrote:
On 10/30/2014 01:50 PM, Anders Blomdell wrote:
On 2014-10-30 14:52, Kaleb KEITHLEY wrote:
On 10/30/2014 04:36 AM, Anders Blomdell wrote:
I think a compat
On 2014-10-30 22:44, Anders Blomdell wrote:
On 2014-10-30 22:06, Kaleb KEITHLEY wrote:
On 10/30/2014 04:34 PM, Anders Blomdell wrote:
On 2014-10-30 20:55, Kaleb KEITHLEY wrote:
On 10/30/2014 01:50 PM, Anders Blomdell wrote:
On 2014-10-30 14:52, Kaleb KEITHLEY wrote:
On 10/30/2014 04:36 AM,
22 matches
Mail list logo
