search for: replicate

Hi to all the people (again), I'm doing some simulations with the memisc package of an own function, but I've the problem that I didn't know how to read the result of such simulations. My function is: > Torre<-function(a1,N1,a2,N2) + {Etorre<-(a1*N1)/(1+a1*N1) + Efuera<-(a2*N2)/(1+a2*N2) + if(Etorre>Efuera)Subir=TRUE + if (Etorre<Efuera)Subir=FALSE +

This document describes a design for a dsync-replicated Dovecot cluster. This design can be used to build at least two different types of dsync clusters, which are both described here. Ville has also drawn overview pictures of these two setups, see http://www.dovecot.org/img/dsync-director-replication.png and http://www.dovecot.org/img/dsync-director-r...

Hey Richard, Could you share the following informations please? 1. gluster volume info <volname> 2. getfattr output of that file from all the bricks getfattr -d -e hex -m . <brickpath/filepath> 3. glustershd & glfsheal logs Regards, Karthik On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote: > On a side note, try recently released health

I have the following in my log: Mar 21 14:46:59 bubba dovecot: replicator: Panic: data stack: Out of memory when allocating 1073741864 bytes Mar 21 14:46:59 bubba dovecot: replicator: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x97c90) [0x7f4638a7cc90] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x97d6e) [0x7f4638a7cd6e] ->

On a side note, try recently released health report tool, and see if it does diagnose any issues in setup. Currently you may have to run it in all the three machines. On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote: > Thanks for this report. This week many of the developers are at Gluster > Summit in Prague, will be checking this and respond next

Hi Karthik, thanks for taking a look at this. I'm not working with gluster long enough to make heads or tails out of the logs. The logs are attached to this mail and here is the other information: # gluster volume info home Volume Name: home Type: Replicate Volume ID: fe6218ae-f46b-42b3-a467-5fc6a36ad48a Status: Started Snapshot Count: 1 Number of Bricks: 1 x 3 = 3 Transport-type: tcp Bricks: Brick1: sphere-six:/srv/gluster_home/brick Brick2: sphere-five:/srv/gluster_home/brick Brick3: sphere-four:/srv/gluster_home/brick Options Reconfigured: features...

Le mar. 5 mars 2019 ? 10:08, Gerald Galster via dovecot <dovecot at dovecot.org> a ?crit : > > you could try to stop replication for the user you are deleting: > doveadm replicator remove [-a replicator_socket_path] username > > Good idea! But I have a problem. I tried to stop the replication (doveadm replicator remove <myuser>) for an user on both server. Verified with

...tatus [detail]|delete >> [reset-sync-time]} [options...] >> >> >> >> So how can I delete my geo-replication session manually? >> >> Mind that I do not want to reset-sync-time, I would like to delete it >> and re-create it so that it continues to geo replicate where it left >> from. >> >> Thanks, >> M. > > > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-users -------------- next part ----------...

...ens automatically. >> But mx2:~# doveadm -D sync -u abuse at example.com -d -N -l 30 -U >> successfully executed and getting mails from mx1. prw-rw---- 1 dovecot mail 0 May 8 06:29 replication-notify-fifo > Does it work if you issue: > > doveadm replicator replicate '*' mx1:~# doveadm replicator replicate '*' 2 users updated > doveadm replicator status '*' I already posted this output. > Do you have different hostnames for your servers? Sure. You may see in listing that short hostnames are mx1 and mx2.

Where would I find the core file? I'm not finding anything obvious. The replicator path is /usr/local/libexec/dovecot/replicator Daniel On 3/22/2017 12:52 AM, Aki Tuomi wrote: > Can you provide us gdb bt full dump? > > gdb /usr/libexec/dovecot/replicator /path/to/core > > on some systems, it's /usr/lib/dovecot/replicator > > Aki > > On 21.03.2017 23:48,

Hi, I've observed some odd behaviour with dsync replication between two hosts, specifically to do with sieve script replication. In short, I have two hosts which replicate in a master-master type setup where almost all of the reads and writes happen to just one of the two hosts. They are both running 2.2.devel (9dc6403), which is close to the latest 2.2 -git . Pigeonhole is running master-0.4 . This is on x86_64 Gentoo. Normal mail replication between Maildir&...

...] [force]|start [force]|stop [force]|pause [force]|resume [force]|config|status [detail]|delete [reset-sync-time]} [options...] So how can I delete my geo-replication session manually? Mind that I do not want to reset-sync-time, I would like to delete it and re-create it so that it continues to geo replicate where it left from. Thanks, M. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.gluster.org/pipermail/gluster-users/attachments/20170801/676ec246/attachment.html>

...op [force]|pause [force]|resume [force]|config|status [detail]|delete [reset-sync-time]} [options...] >>> So how can I delete my geo-replication session manually? >>> Mind that I do not want to reset-sync-time, I would like to delete it and re-create it so that it continues to geo replicate where it left from. >>> Thanks, >>> M. >> >> _______________________________________________ >> Gluster-users mailing list >> Gluster-users at gluster.org >> >> http://lists.gluster.org/mailman/listinfo/gluster-users -------------- next part ---...

...ons...] >>>> >>>> >>>> >>>> So how can I delete my geo-replication session manually? >>>> >>>> Mind that I do not want to reset-sync-time, I would like to delete >>>> it and re-create it so that it continues to geo replicate where it >>>> left from. >>>> >>>> Thanks, >>>> M. >>> >>> >>> >>> _______________________________________________ >>> Gluster-users mailing list >>> Gluster-users at gluster.org >>> http...

...would be very happy to receive an opinion on this. All the details are put at the bottom Regards, Ove Details and logs ---------------- My environment * single machine with OpenSuse 12.1 * gluster 3.3beta2 * xfs is used for the brick-fs (each one to a separate disk) Volume Name: d1 Type: Replicate Status: Started Number of Bricks: 4 Transport-type: tcp Bricks: Brick1: glusterdev:/b1 Brick2: glusterdev:/b2 Brick3: glusterdev:/b3 Brick4: glusterdev:/b4 Options Reconfigured: diagnostics.brick-log-level: DEBUG diagnostics.client-log-level: DEBUG * My glustervolume is mountet as glusterfs on /d1...

The Xapian documentation talks about a situation where you don't want to do two database swaps while in the process of replicating. It says... To confuse the replication system, the following needs to happen: 1. Start with two databases, A and B. 2. Start a replication of database A. 3. While the replication is in progress, swap B in place of A (ie, by moving the files around, such that B

Very minor bug; not specifying the user mask with 'doveadm replicator replicate -f' causes a segfault: server:~# doveadm replicator replicate -f Segmentation fault server:~# doveadm replicator replicate -f '*' 123 users updated server:~# gdb /usr/bin/doveadm core.2418 GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-100.el7 This GDB was configured as "x86_64-re...

Please tell me about Dsync replicator. The following are set to enable the "replication" plug-in /etc/dovecot/conf.d/10-mail.conf *---mail_plugins = notify replication---* And I made the following file /etc/dovecot/conf.d/30-dsync.conf *---service replicator { process_min_avail = 1} dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server

Hi all, I use gluster 3.12 on centos 7. I am writing a snapshot program for my geo-replicated cluster. Now when I started to run tests with my application I have found a very strange behavior regarding geo-replication in gluster. I have setup my geo-replication according to the docs: http://docs.gluster.org/en/latest/Administrator%20Guide/Geo%20Replication/ Both master and slave clusters...

...client ??? option remote-host gbe04 ??? option remote-subvolume /brick03/gluster ??? option transport-type tcp end-volume volume strato-client-23 ??? type protocol/client ??? option remote-host gbe08 ??? option remote-subvolume /brick03/gluster ??? option transport-type tcp end-volume volume strato-replicate-0 ??? type cluster/replicate ??? subvolumes strato-client-0 strato-client-1 end-volume volume strato-replicate-1 ??? type cluster/replicate ??? subvolumes strato-client-2 strato-client-3 end-volume volume strato-replicate-2 ??? type cluster/replicate ??? subvolumes strato-client-4 strato-client-5 e...