Leader/journal based synchronous and quasi-synchronous replication, as described in http://review.gluster.org/#/c/8915/ and elsewhere.
REVIEW: http://review.gluster.org/12943 (NSR: Volgen Support) posted (#13) for review on master by Jeff Darcy (jdarcy)
REVIEW: http://review.gluster.org/12943 (NSR: Volgen Support) posted (#14) for review on master by Jeff Darcy (jdarcy)
COMMIT: http://review.gluster.org/12943 committed in master by Jeff Darcy (jdarcy) ------ commit fac8038a9fa80e16b557d91b9e2fec271cfda5fa Author: Jeff Darcy <jdarcy> Date: Mon Dec 14 16:25:22 2015 -0500 NSR: Volgen Support Allows the user to convert an afr-volume to a nsr-volume by using cluster.nsr option in the volume set command gluster volume set <volname> cluster.nsr <on/off> Change-Id: Ia1c5aa89d27535f7275d474cf312dc5efb8e222f BUG: 1158654 Signed-off-by: Jeff Darcy <jdarcy> Reviewed-on: http://review.gluster.org/12943 Smoke: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Avra Sengupta <asengupt> CentOS-regression: Gluster Build System <jenkins.com>
Renaming from NSR to JBR. Also, this is now going to be used as a tracker bug, with subsidiary bugs associated with it for the individual pieces.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user
(In reply to Niels de Vos from comment #5) > This bug is getting closed because a release has been made available that > should address the reported issue. In case the problem is still not fixed > with glusterfs-3.8.0, please open a new bug report. > > glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages > for several distributions should become available in the near future. Keep > an eye on the Gluster Users mailinglist [2] and the update infrastructure > for your distribution. > > [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ > [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user Are you sure that this feature is implemented in GlusterFS 3.8? How do I enable Journal-Based Replication in that release?
(In reply to jack.wong from comment #6) > (In reply to Niels de Vos from comment #5) > > This bug is getting closed because a release has been made available that > > should address the reported issue. In case the problem is still not fixed > > with glusterfs-3.8.0, please open a new bug report. > > > > glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages > > for several distributions should become available in the near future. Keep > > an eye on the Gluster Users mailinglist [2] and the update infrastructure > > for your distribution. > > > > [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ > > [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user > > Are you sure that this feature is implemented in GlusterFS 3.8? How do I > enable Journal-Based Replication in that release? It's certainly not. This was done by mistake.
As we do not have any plan to work on any of the SSR/JBR related bugs in the near future, we are closing this bug. In the future if there is a ask and we have enough resources we will reopen and work on this.